Red Hat Bugzilla – Bug 130523
initrd makes a system unusable by a bogus inclusion of udev
Last modified: 2007-11-30 17:10:47 EST
Description of problem:
A system startup files use the following tests
if [ -f /etc/sysconfig/udev ];then
if [ "$USE_UDEV" = "yes" -a "$UDEV_RAMFS" = "yes" ]; then
[ -x /sbin/start_udev ] && /sbin/start_udev
But new version of mkinitrd has this:
if [ -f /etc/udev/udev.conf ]; then
[ "$USE_UDEV" = "yes" -a "$UDEV_INITRD" = "yes" -a -x
/sbin/udevstart ] || USE_UDEV=
# use ramfs if keep_dev is set
[ "$UDEV_KEEP_DEV" = "yes" ] && UDEV_RAMFS="yes"
The net result is if 'udev' is installed but not turned on
then after a boot one ends up with system one can barely
log on because most of devices are missing and what is left,
including things like /dev/null and /dev/zero, has 600 permissions.
An attempt to start X, which is a natural thing in a startup,
kills a machine cold with a blank screen.
Recovery is not obvious as '--noudev' flag to mkinitrd is
not documented either in 'mkinitrd --help' nor in 'man mkinitrd'
and also one has to guess that this is mkinitrd screwing up
Version-Release number of selected component (if applicable):
initscripts was the broken one in this case, it's fixed since.