If it ain't broke, don't fix it?
Apr. 6th, 2009 01:29 pmI have a dilemma about my laptop. Gentoo has announced that its standard windowing server, X, will now be X server 1.5. I'm running version 1.3. As time goes by, products and services that depend upon X will start to use faculties of the later server and I'll be unable to install them on my box. I'm already having some problems with some games.
But my laptop has an ATI video card. The driver I'm using, 8.476, has been amazingly stable for months now. Every time I've upgraded, it's always been the ATI driver's conflict with the hibernate/suspend driver that's made this thing crash. Now, they SAY that driver 8.522 is "stable" as well, but I don't trust it and upgrading to it would be a bear, because if it doesn't work backing out will be one huge goddamned pain in the neck.
But my laptop has an ATI video card. The driver I'm using, 8.476, has been amazingly stable for months now. Every time I've upgraded, it's always been the ATI driver's conflict with the hibernate/suspend driver that's made this thing crash. Now, they SAY that driver 8.522 is "stable" as well, but I don't trust it and upgrading to it would be a bear, because if it doesn't work backing out will be one huge goddamned pain in the neck.
no subject
Date: 2009-04-06 08:58 pm (UTC)no subject
Date: 2009-04-06 10:33 pm (UTC)why can't you upgrade then later downgrade...?
Date: 2009-04-06 09:09 pm (UTC)For my last OS upgrade (Ubuntu 8.10) I was feeling some weird blend of caution and adventurousness, so instead of upgrading, I swapped hard drives and installed fresh. It was nice to see how the system acted out of the box, but it took me weeks to get the configuration really comfortable again, and suspend is still broken randomly. In retrospect, I probably should have made a hard-drive image backup, then upgraded. But I still like the concept of a fresh install...
Anyway, I guess what we really want is package management that's so good you could easily try it out for a few days then change back, later, with the click of a button (or command line, or whatever.) And really easy (mostly automatic) public bug reporting in the process. (Reason for downgrading? [x] it seemed to make my system unstable.)
You can imagine having a control for each package where you just say which version you want, and can adjust it arbitrarily (among available versions). One of the complications would be that formats for configuration information changes between versions, so you'd need loss-less conversion programs in both directions. (This is more manageable if an extensible format like XML or RDF is used, but of course you can't assume it will be.) I don't really know -- how much can you do that with existing package managers...?
An even harder problem might be the combinatorics in the interactions (cf integration testing). Even if all the interations of packages were perfectly well known and documented, changing your versions around would be like solving a 15-puzzle: you upgrade the X server, then you can upgrade package Y, then you can upgrade package Z. Having done that, you see that package W became unstable, so you have to downgrade it two versions to make it stable again. Now if you want to downgrade X again, you have to roll-back each of those other changes.
I dunno, maybe that is manageable....
(I'm also reminded of some projects for zero-install systems, but I don't even remember what they were called.)
no subject
Date: 2009-04-06 09:30 pm (UTC)no subject
Date: 2009-04-06 09:40 pm (UTC)Why upgrade now?
Date: 2009-04-06 09:46 pm (UTC)personally, I tend to be the sort that lives on the slightly more bleeding edge, so I tend to do the backup-image of the server, upgrade and revert wholesale to the backup if it is fubar'd.
no subject
Date: 2009-04-07 01:41 am (UTC)no subject
Date: 2009-04-07 03:25 pm (UTC)This from the gal looking out the window at a sunny day and wishing she'd had time to pull her bike out of winter storage and get it ready for riding season. *sigh* Back to flooring.