Julian C. Dunn (julian.dunn(a)devlin.ca) said:
> I cannot reproduce this here. Moreover, I cannot see *how* this
> /etc/inittab is marked %config(noreplace) in both the old and new packages.
> In the rpm handling code, this should *never* end up with: old file -> rpmsave,
> no new file.
Hmm. I looked into this further and it looks like somehow the yum update
*removed* the old initscripts, which would explain the behaviour... see
the excerpt from my /var/log/yum.log:
Mar 15 09:01:49 Erased: initscripts
Mar 15 09:01:53 Updated: valgrind.i386 1:3.1.0-2
Mar 15 09:02:23 Installed: kernel-devel.i686 2.6.15-1.2054_FC5
Mar 15 09:02:24 Updated: grub.i386 0.97-5
Mar 15 09:02:26 Updated: initscripts.i386 8.31.1-1
I have no idea why it would do this.
Neither do I. Although... weird. Can you post/attach to bugzilla your whole
> > Also, I'm using a Thinkpad T42 (2378RAU) and the
wireless card shows up
> > as a weird device after boot:
> > dev8569 Link encap:Ethernet HWaddr 00:0E:35:FC:39:23
> > Does anyone know why?
> You have a wired ethernet that is configured to be eth0, and your wireless
> module was loaded first, so it was moved out of the way.
Okay - is that expected behaviour? (I'm currently running without
wireless configured, but I'm not suppressing the load of the kernel
module or anything like that)
Yes. If you configre the wireless, it will be changed to whatever you
configure when you bring it up. We're working on code to do all this
at boot, but it's not ready yet.