Linked by Thom Holwerda on Sun 23rd Sep 2007 13:43 UTC
Ubuntu, Kubuntu, Xubuntu Just like Eugenia yesterday, I also upgraded my laptop's Ubuntu Feisty installation to Gutsy a few days ago. The upgrade process went completely awry, though, so I was forced to do a fresh install. Not a bad thing, as it gave me the opportunity to take a look at Ubuntu's soon-to-be-released Gutsy Gibbon with GNOME 2.20
Thread beginning with comment 273645
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Fresh install == good?!
by aent on Sun 23rd Sep 2007 17:24 UTC in reply to "RE[2]: Fresh install == good?!"
aent
Member since:
2006-01-25

That you should follow the recommended procedure of using update-manager instead of dist-upgrade? lol

Reply Parent Score: 7

RE[4]: Fresh install == good?!
by Oliver on Sun 23rd Sep 2007 19:10 in reply to "RE[3]: Fresh install == good?!"
Oliver Member since:
2006-07-15

It's somewhat ridiculous to do so, if the usual way should be an upgrade without new install in Linux. You know like the professionals, not Windows *g*

Reply Parent Score: 0

RE[5]: Fresh install == good?!
by leech on Sun 23rd Sep 2007 20:47 in reply to "RE[4]: Fresh install == good?!"
leech Member since:
2006-01-10

I've done my fair share of fresh installs and I'll say that as far as they go, Ubuntu is pretty good because most things work out of the box, or are rapidly becoming a 5 minute job to get everything working, then it's just a matter of installing the applications you want, and for most people they're installed by default.

Of course the bad thing is, that Ubuntu is not as good at upgrades as it should/could be. I'll explain why....

With Debian, you have everything supported as a whole. Either a package is maintained and updated as the stable release comes to a close, or it simply gets obsoleted and taken out of the repositories, assuming that it doesn't work with new libs, etc.

Ubuntu on the other hand does things differently. They have main, restricted, multiverse and universe. The first two are supported and if you simply stick to those, then you'll not have any upgrade problems (well more than likely) but when you start getting to the non-supported packages, a lot of them aren't maintained as well as they should be. So they can possibly screw things up. A good example of a non-maintained package is Azureus. They changed the packaging dramatically enough from the Debian Azureus that it's still stuck at 2.5.0.0, and Debian has had 2.5.0.4 for a long time. I ended up grabbing the sources from Debian and having to change a lot of files in the debian folder to get it to work (mostly because in Debian the swt library is named slightly different than the one in Ubuntu. Who thought that was a good idea?)

Granted the packaging philosophies is why Debian takes a long time to release a "stable" version and Ubuntu can do it every 6 months.

I'm not sure why people had issues between Dapper and Edgy, but I never had such an issue that I can recall. Then again I think when Etch was released, I switched to that, though I'm now running Gutsy Gibbon and I'm liking it so far!

I am quite angry that Ubuntu has screwed up some upgrades though, since that's supposed to be one of the strongest attributes of Apt in the first place. It screwed up going from Edgy to Feisty on a friend's PC, I had to re-install on that one. Though in it's defense, that's mostly due to it being (at the time) a new Core 2 Duo system and Grub itself would not work, I had to configure Lilo to boot Linux on it. But Feisty worked out of the box when I installed it on there.

I've never messed up an upgrade myself though (he did that one himself) but that's because instead of using update-manager or dist-upgrade, I take synaptic and first update the base system, like the kernel, and libc6, then reboot and pray. If that works, then I start with the user space things.

As far as anything going awry with this though, I think it's mostly Gnome and if you just remove your current settings and go back to default Gnome (the .gnome, .gnome2, .gconf, .gconfd directories) then it should work ok. That's what I had to do.

Reply Parent Score: 5