After upgrading to the current version of initscripts (6.82-1) and rebooting, I got errors from mount about /proc and /proc/bus/usb already being mounted. If initscripts is going to take over responsibility for mounting these, then its postinstall script needs to comment out the entries for them in /etc/fstab.
/proc is always in /etc/fstab. /proc/bus/usb never is. What sort of system do you have?
I could have sworn /proc/bus/usb ended up in my /etc/fstab because something had previously added it. In any case, even if I'm wrong about that, you still have a problem, because /etc/rc.d/rc.sysinit is now mounting /proc.
rc.sysinit has always mounted /proc, since the dawn of time. Something else has broken your system. :)
I *think* this was a mkinitrd bug. If you build an initrd with the latest mkinitrd, does it behave better?
I don't have an initrd. I'm not sure how this could be an initrd problem -- the basic issue is that both /etc/fstab and initscripts are trying to mount /proc. (Although I haven't checked the current Rawhide initscripts etc. - having a new baby in the house cuts into your free time :-)
rc.sysinit mounts proc before most anything else, and before anything using /etc/fstab would mount it. What does your /etc/fstab look like?
Here's the line for /proc from /etc/fstab: none /proc proc defaults 0 0
Where in rc.sysinit do you see these errors at?
I'm not seeing this problem anymore with current Raw Hide after commenting out /proc/bus/usb in /etc/fstab but leaving /proc alone (i.e., not commented out). I still think that there are going to be problems for people who have /proc/bus/usb listed in their /etc/fstab.
Closing bugs on older, no longer supported, releases. Apologies for any lack of response. If this persists on a current release, such as Fedora Core 4, please open a new bug.