Yesterday the latest release (4.0) of Debian came out. I decided to be big and brave and upgrade immediately; I’ve never had any problems with upgrading Debian before and didn’t expect to now. It took forever to download, ages to install (with me keeping all the old config files as I always do). And then, at the end, our internet connection was dead. Our internet connection is via PPP, which was tricky to set up, so it seemed best to tackle the problem in the morning rather than risk making things worse.
This morning I found that the ppp
script in the /etc/init.d
directory wasn’t there, but a #ppp#
script was, with the right content. So I renamed the file back to ppp
, checked the backups to put the right symlinks into the various /etc/rx.d
directories, and rebooted. Voila! An internet connection. Now I just have to figure out why apache2
isn’t running. [Update: because it was upgraded to version 2.2 and the authentication config file syntax was changed, that’s why.]
I have no idea whether the PPP problem came from the distribution, or something odd in my configuration (although I’ve done full dist-upgrades before with no problems). I did a hunt on the Debian wiki and found that Debian has added more PPPoE support recently, so maybe there was a clash in there somehow. I’m glad I was paranoid enough to make backups of the /etc
directory to compare with. At some stage I guess I should figure out whether to replace the current configuration with the new Debian system, although I don’t like mucking about too much with things that actually work, especially when it comes to something as vital as being able to connect to the Net.
Keeping all the old config files is risky for a major upgrade. I ran into ugly, hard to diagnose problems this way at least once.
My strategy is to view the diff andm if I see edits that I made, save a copy of my version before replacing it with the new version. If I don’t see any edits by me, then I just replace it and figure I’ll be none the wiser.
After the install finishes, I consider how to apply my patches to the new config file(s), if they’re still necessary.
Good point. I know that’s what you’re meant to do; personally I’ve never had problems keeping old config files when Debian has given me the choice but your strategy is the cleanest solution. I guess up till now I’ve been able to rely on Debian just Doing The Right Thing, mostly (I suspect) because I’ve got a boring small installation that’s not running any unstable or testing packages.