I haven’t used Ubuntu in over two and a half years, but I’ve been watching the debate raging with the launch of Ubuntu One last week with interest.
In my opinion, the best commentary on the matter so far has been by Jim Campbell, an Ubuntu member, on his blog. I encourage you to read his take on it, and also the second comment posted.
This may only amuse me, but the number of searches on my blog for “ubuntu banshee 0.98.2” has skyrocketed in the last day or two since Banshee’s recent release.
Just another reason to use Foresight! Conary’s ability to write a recipe to create a package is easier than almost every distribution out there. This gives us the ability not only to add packages quickly, but to maintain Foresight as a rolling distribution. After testing packages, we can keep our distribution up to date without having to have two major releases a year like most distributions do today. Think 0.98.2 will be in Ubuntu? Think again! (Not that I’m trying to start a flame war with Ubuntu, we each have our pros and cons).
Even Aaron Bockover, Banshee’s lead developer commented on his blog:
@trettle: First off, thanks! Ubuntu packages should be on their way, but itΒs really up to those in the Ubuntu community to contribute the packaging. The Foresight guys always have packages available minutes after an upstream release, for instance. It would be nice to see someone do the same for Ubuntu.
Try Foresight today!
One of my New Year’s Resolutions this year was to get more involved with GNOME and / or Ubuntu when the year started. Having used Ubuntu since it was first released, and Linux and GNOME specifically since 1999, I really wanted to give something back. After being utterly confused on where to even start with Ubuntu due to the number of volunteers and convoluted processes, I decided to start with GNOME.
I started the year strong, volunteering to help GNOME with the website revamp, including writing a few pages of content for the revamp, and editing a few more. (The new site still isn’t out so not sure if they’ll be using it or not).
I also volunteered to create a GNOME Live CD in January, and after a week or two of researching, was introduced to Ken VanDine who had also offered to help. Turns out Ken is the lead developer of Foresight Linux, and using the Conary and rPath tools, it was easy for him to create not just a Live CD, but other images including VMWare and QEMU as well.
In talking to Ken, and looking for more information on Foresight, I started hanging out in Foresight’s IRC channel on Freenode, and was impressed with the community, their communication and willingness to help others. See the June Foresight Newsletter for more.
And that began my journey in to Foresight. I installed Foresight shortly after, and just started helping out, first by answering questions in IRC (even when they were the wrong answer), and then really diving in, writing the monthly newsletter and then working on documentation. First developing the userguide on the wiki, and then teaching myself docbook and writing and publishing the userguide in Docbook to be included in Foresight.
Additionally with Foresight, I’m trying to help as a project manager, including keeping tabs on the different workstreams and communication within the group. I’ve been testing the first alpha of Foresight released in early November, and last but not least, continue to work on being a bugmaster and triage issues and tasks in JIRA.
I’m also happy with getting the Twin Cities Linux Usergroup meetings back off the ground after a two year hiatus, even though I haven’t had time to help out in the last few months in planning or organizing meetings.
The resolution I didn’t get to was creating my first podcast. I’ve had the songs picked out, but Jokosher didn’t work exactly as I hoped (as Audacity isn’t in our repos). I also wasn’t happy with my microphone quality. I’ll have to work on this one for next year.
Overall, a great year, and I’m very happy in being able to give back and help out, and looking to do more in 2008!
Reading the article “Mepis to switch from Ubuntu to Debian” one thing jumped out at me:
Woodford explained that Ubuntu is rebuilt almost from scratch every six months using source packages from Debian EXPERIMENTAL.
In using Ubuntu for almost 3 years, that was my experience as well. I formatted and installed fresh more than I just did a apt-get dist-upgrade.
And that is one of the major features of Conary – managing your applications and dependencies so you should never have to “install fresh”. Foresight, using Conary, believes in rolling releases – not big releases every 6 months, but incremental updates to keep you up to date with the latest software and security fixes.
As I mentioned in my last post, I installed Foresight Linux on my second box last week. (Don’t worry Ubuntu fans, I’m still running Feisty on my main machine). To set expectations, this post is part mini-review of Foresight, part comparison to Ubuntu, and just my opinions and thoughts on Foresight after using another distribution for almost 3 years.
Foresight’s website and IRC channel sum up Foresight well:
Foresight Linux is a Distribution which showcases some of the latest and greatest from GNOME. Ah! Some of the things that may not be mature enough for some of the other distros. Some of the more innovative things are included, like beagle , f-spot , avahi (zeroconf), and the latest hal . All of this plus some nice, clean default themes and artwork.
.
And their IRC channel: “Your distro should be cool”. And that’s a great way to sum up the applications included on their CDs.
Installation
It was weird seeing an option to download more than 1 CD – Foresight comes on 2 CDs or one DVD image. I used bittorrent to spare rPath some bandwidth, and it was fast – 600k down, which makes me wonder how many folks are out there using this and sharing the ISO.
I burned the DVD on my Ubuntu box, popped it in to my second box, and was greeted with a blast from the past: the Anaconda installer. Prior to becoming an Ubuntu user, I mostly used Red Hat and later Fedora for almost 5 years. Going through Foresight’s installation GUI, while branded Foresight, is a re-branded Fedora install, and there’s nothing wrong with that, it worked great. My box is pretty standard hardware – P4 3.0ghz, Intel stock 865 board, Nvidia (BFG) 6800, 2 DVD drives, 2 IDE Hard drives, and 2 gigs of RAM.
Installation was quick, a reboot, a little more configuration, and I was presented with the Foresight desktop.
Visuals
It’s a nice clean look – it looks to be a custom theme, with Tango-ified icons everywhere. I’ve been using Ubuntu so long, I’m not sure, but I’m guessing this is very close to a default GNOME install. The GNOME footsteps are in the upper left corner with the Applications menu – it’s been a while since I’ve seen those.
There were a couple new icons I haven’t seen before in my notification area in my panel – one is Glipper, a clipboard manager for GNOME, which I’m excited to see. GNOME’s lack of unified copy / paste is a constant minor annoyance, so that program is slick. The other icon was Desktop Drapes, a tool for managing your wallpapers. It’s a slick application, but I’m not sure the necessity of having it on my panel. The last was a window selector button on the far right of the panel that has uses the icon of the application in the foreground. Clicking on the window selector brings up a menu of all active applications to make it quicker to switch between them.
Customizing Foresight
Once installed, I need to feed my addiction to eye-candy. It was time to get my Nvidia drivers installed. Foresight uses a new package manager called Conary, which is developed by rPath to create their appliances. Conary is unlike any other package manager in that it keeps every version of a file every made, so you can just rollback if you encounter a problem. It also does incremental updates, and from I understand, when you’re updating a package, Conary is just pulling down the changed bits of the file – you don’t need a whole binary.
But back to the Nvidia drivers – I followed the wiki and added the binary drivers to my group:
<br />
sudo conary update group-dist=['!ati, nvidia']
And then I sat there at a terminal. It was probably about 5 minutes, but felt like about 15. I pinged some developers as I was lurking in the #foresight channel on Freenode, and sure enough, soon as I asked after a few minutes, it started. The delay was caused because my system needed to be updated as it was a fresh install. So all kinds of packages had updates available since the ISO I burned was built.
As part of the updates, the Nvidia drivers were installed, so I restarted X, got the Nvidia splash screen, was able to change my resolution from 800×600 to 1280×1024, and lo and behold, I had a new icon on my panel. It looked like some paint splattered – it was new to me. Compiz! Installed and able to run as soon as the binary drivers were installed – very slick. I enabled a GL desktop, and voila – there it was. I had a couple edits to make to my X.org file per the Foresight Wiki for Nvidia cards, applied those changes and had a fully enabled GL desktop running without really lifting a finger. I’ve been using Beryl pretty exclusively with my Edgy and Feisty desktops, but after using Compiz for the last few days here, I don’t see why I would go back to Beryl. This is what Ubuntu users have to look forward to with this week’s announcement of Compiz being installed by default in Feisty – same as this, just enable it and away you go.
Applications
I’ve installed a few other programs, including Bluefish and Mugshot. Foresight’s default choice for applications are perfect for me:
These are applications I use every day, and every time I complete an Ubuntu installation, my first task is to add these. And they’re out of the box on Foresight.
I did try to install avant-window-navigator, and it’s in my menu, but it Segfaults when i run it. I’m not sure if it’s because I’m using Compiz instead of Beryl, a dependency issue, or something else I’ve done. AWN is also in an extremely early alpha stage, so it’s probably a bad example to even bring up. But my real point is wow! It’s a package that’s actually available for automagical installation, that’s cutting edge. It’s an advantage a smaller distro with active package maintainers can bring. Click here to browse Foresight’s available packages.
System Management
Foresight comes with the Foresight System Manager installed in your System menu on your panel as well in Applications under Foresight. It’s a web based app installed locally on your machine, that gives you some basic status information about y our machine. Accessing the Logs resulted in an “unrecoverable error” in my web browser, but everything else seemed to work. For users scared of the command line, probably the most useful tool is the ability to search for other packages and software, and install them right from your browser.
From the command line, adding and removing applications is a breeze – consistent with my experiences with Apt.
Other
Codecs appear to just work. I could play and rip MP3s, a couple different video files I tried just played. That’s a huge win for users. I understand some folk’s in the open source community’s feelings on the matter, but it’s a necessary evil. Just “making it work” is big.
Summary
Foresight has been around for about 2 years, and had their 1.0 release this past January. It appears to be a very active community, especially in their IRC channel, where folks are helpful, friendly and the conversation is always going. Their wiki is up to date with helpful howtos, and for what appears to be a small team of developers, the number of packages being maintained and able to install in Foresight is surpisingly large. The development team is working on a new release to sync up with the upcoming GNOME 2.18 release in March, and is also working on a LiveCD.
I’m really impressed – as a long time Ubuntu user, this is the first distro that really makes me consider switching. I want to get much more active in the Linux communities, and Foresight is one I could see myself helping out, as it has a great bunch of people working on it who were friendly to folks asking questions, and shared information about their distro even with newbies who knew nothing about Linux as I witnessed just a few hours ago tonight.
One of the advantages of using Linux is choice, and Foresight would make a great choice for a lot of users.
I’d like to thank a few folks hanging out in the IRC channel who shared information about Foresight I used in this article, including kenvandine, smithj, pscott and bertux.
Update: Here’s a screenshot of my current Foresight desktop, fairly vanilla from the installation, running Nvidia binary drivers and Compiz:
I’ve been trying to spend some time giving back to projects I believe in. I spent a weekend reading through Ubuntu wiki pages on everything from setting up a LoCo, to helping the documentation team, becoming an Ubuntu member, and a lot more. After being a little overwhelmed by some of Ubuntu’s processes (and I do understand why they have them considering the sheer number of users and folks involved), I volunteered to help write some copy for the new gnome.org website that will debut with the upcoming 2.18 release, take a crack at creating a GNOME 2.18 LiveCD, and am helping to try and get the TCLUG back up and running some regular meetings.
I spent a good chunk of last weekend trying to create a LiveCD, using scripts, a few different programs, and lots of research. I quickly realized I was just a bit, to put it mildly, over my head. I’ve been using Linux off and on for 8 years, a full time user for 2 years, but I’m a user, not a developer. I can barely compile my own packages, and even then I’m sure I’m not always doing it the “right” way.
In my travels in trying to build a LiveCD, I met a gentleman by the name of Ken Vandine on the gnome-marketing mailing list and in the #marketing IRC channel for GNOME, who has also stepped up to create a LiveCD for GNOME 2.18. Ken works for rPath, whose goal is “making software applications radically easier to create, deploy, and manage“. Coincidentally, at our last TCLUG installfest last summer, Dave from rPath demoed their technology for us, showing us a really innovative way to create your own software, including things as complex as your own Linux distribution using their toolset. But back to Ken – not only did Ken seem pretty cool and helpful, turns out Ken is one of, if not the lead developer for Foresight Linux.
Foresight is a GNOME-based distribution, that includes a lot of cutting edge software in the Linux community, including Banshee as the default music manager (and we know how much I love Banshee), F-spot, Beagle, among others. I think it’s safe to safe to say Foresight is a smaller Linux distribution when compared to leaders like Ubuntu, Fedora, Gentoo or Ubuntu.
I did something last Sunday I have done in almost 3 years – installed a different distribution of Linux that wasn’t Ubuntu. It was weird, but strangely comforting at the same time. I’ll post some thoughts on my experiences with Foresight later tonight in my next post.
I was pleasantly suprised to see that Banshee is now supported by Mugshot. I’ve been running Feisty for the last few weeks, and haven’t found a Mugshot .deb yet, but on my second machine I was testing out Foresight (different story for later), which had an up to date package for Mugshot. I was playing music on my main PC, look over to my second PC with Mugshot, and it’s reporting what songs I’ve just played. What a pleasant suprise! Talking to Aaron Bockover in IRC, it wasn’t developed by Banshee, so I’m guessing the lads at Red Hat are grabbing it via Dbus in the latest version of Mugshot.
In other Banshee news, Snorp has created a Banshee plugin for Avant Window Navigator. The plugin replaces the Banshee logo in your dock with the cover art from the current CD you’re playing. Make sure you have a newer version of AWN from Subversion – my AWN build from a week or two wasn’t compatible as Banshee would just keep crashing on Feisty.
With some help from Pveith on the Ubuntu Forums, I was able to compile Avant Window Navigator from Subversion. Per Pveith’s recommendation, I used checkinstall, which created a .deb for installation. I am running Beryl and an Nvidia graphics card. I added a Feisty Fawn Howto on the AWN wiki, here is how I got it working:
Step 1: Prepare your system
Step 2: Download the required dependencies
Step 3: Download Avant Window Navigator from Subversion:
Step 4:
Step 5: Install using checkinstall
Step 6:
cd data
gconftool-2 –install-schema-file=avant-window-navigator.schemas.in
Step 7: Run Avant Window Navigator
Alt-F2
avant-window-navigator
Step 8: Have Avant Window Navigator automatically start up on reboot
Click System, Control Center
Click Sessions
Click Startup Sessions Tab
Click “New” and type “avant-window-navigator” in both name and command fields
Click “OK”
Click “Close”
And here is Avant Window Navigator in all it’s glory on Feisty Fawn on my main machine, running in 1920×1080 on a Dell 24″ monitor:
I took the plunge and installed Feisty Fawn Herd 4 on my main machine last night. Doing a dist-upgrade resulted in kernel panic when GRUB tried to load, so I threw in the Herd 4 CD, and did a clean install. (I know, I should be installing alpha software on my main machine, but it’s running so smooth so far…)
If you haven’t checked out Feisty Fawn yet, check out the wiki pages on Ubuntu.com for the different alpha releases (Herd 2, Herd 3, Herd 4).
It’s amazing to see how far Feisty has come just through the alpha releases.
Some random thoughts:
I love Linux – last month was my 8 year anniversary of using Linux in some form, and next month will be the 2 year anniversary of using Linux as my only operating system when I retired from gaming.
I love Ubuntu – I love the community, the developers committed to making Linux (and Debian) better (and easier), and the wealth of applications.
But some things drive me crazy about Linux, and today’s rant is about trying to get my microphone jack to work. It’s little things like this, that in my mind should just work, but don’t. If you search the Ubuntu Forums for microphone, it’s amazing how many threads pop up that folks can’t get their mics to work.
I have an Intel HDA audio card built in to my motherboard. I spent a good 4 hours today trying different things to get it to work. When I started, I could listen to audio through my speakers and in my headset at the same time. Now I can’t, after changing some setting I’m not aware of. I spent hours playing with Alsamixer, Alsamixergui, Volume Control, and Sound settings. I tried to record using 2 different boom mics, different ports, different options in Sound Recorder and Volume Control, editing alsa files, all to no avail.
I have a slightly newer motherboard, though stock Intel, with a Core 2 Duo processor. Most threads I saw had problems with the Conexant chip, and I have a Sigmatel. It could be anything – it could be I’ve messed with my settings and hosed it myself, it could be that I’m running Ubuntu Edgy and in the last 6 months either Ubuntu or Alsa have a fix, and I’m just running an old version, or my hardware is still to new and folks are out there hacking on it without an answer yet.
It’s maddening, but I’ll keep trying, and when I figure it out, I’ll post an answer and help out the next folks who get stuck. But I may just install Feisty and see if I have better luck. (I know – it shouldn’t be on a main machine as it hasn’t been released yet, but I’m feeling daring!)