Weblog entry #4 for summitwulf
See all weblog entries made by summitwulf.
Comments on this Entry
You may also need to change your /etc/apt/sources.list file. Mine have the codename of the version in, so I have to expicitly change it from sarge to etch to force an upgrade. If you have stable then you will upgrade automatically, which may not be a good idea.
I think there are threads here for the Woody to Sarge transision which may also help.
http://www.debian-administration.org/articles/95
http://www.debian-administration.org/articles/96
http://www.debian-administration.org/articles/98
http://www.debian-administration.org/articles/101
http://www.debian-administration.org/articles/156
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Topically: Upgrade testing with Qemu - for Sarge -> Etch.
[ Parent | Reply to this comment ]
I followed this through last night, except my base install upgraded its self to testing before I'd mirrored by base Sarge install... :-( I'll try again tonight.
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]
- after changing apt sources, must purge hotplug to install new Etch kernel --before dist-upgrade
- on a couple of older laptops, pcmcia is a mess; probably because I'm not yet familiar enough with the udev stuff yet to figure out how to make config changes for the crappy pcmcia nic I have... carryover configs from old pcmcia subsystem don't seem to have an effect (axnet_cs vs pcnet_cs headaches)
- still have one that I haven't been able to make sound work with, I've had to add snd_pcm_oss and snd_mixer_oss modules manually to use anything aumix-based; older ISA bus sound stuff is just plain evil
- fvwm95 doesn't understand the default English locales (bug report submitted), and locales will have to be reconfigured; a customized fvwm95rc also had to be edited
...Rob
The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
[ Parent | Reply to this comment ]
I just stumbled upon this thread when I was looking for the "axnet_cs vs pcnet_cs headaches".
I am using etch already for a while on my laptop - it actually works quite well - only that I didn't use my wired network card for a while and now found that it's loading the pcnet_cs module instead of the axnet one.
So I wanted to ask if you found already how to tell udev which module to load.
For the sound: I did add snd-pcm-oss, snd-mixer-oss and snd-seq-oss to /etc/modules. I guess you could also add some post-install statemnets somewhere under /etc/modutils to get the same in an more dynamic way.
[ Parent | Reply to this comment ]