On Fri, Sep 17, 2004 at 10:39:22AM -0500, Brian Millett wrote:
>
>> MAKEDEV-3.13-1
>> --------------
>> * Tue Sep 14 2004 Nalin Dahyabhai <nalin(a)redhat.com> 3.13-1
>>
>> - excise all architecture-specific logic and configuration data --
>> udev knows
>> no arch-specific details, so they should be irrelevant now
>> - remove build conflicts on older RPM, unnecessary now that dev is
>> gone - remove dev's %post fstab munging
>> - add a short-circuit test for the common non-match cases
>>
>> * Tue Sep 14 2004 Jeremy Katz <katzj(a)redhat.com> - 3.12.2-1
>>
>> - add the vcsa user and floppy group in the MAKEDEV package now
>>
>> * Mon Sep 13 2004 Nalin Dahyabhai <nalin(a)redhat.com> 3.12.1-1
>>
>> - nuke the "dev" subpackage
>>
>>
>> udev-030-26
>> -----------
>> * Mon Sep 13 2004 Jeremy Katz <katzj(a)redhat.com> - 030-26
>>
>> - require a 2.6 kernel
>> - prereq instead of requires MAKEDEV
>> - obsolete and provide dev
>> - add a trigger for the removal of /dev so that we set things up
>>
>> * Fri Sep 10 2004 Dan Walsh <dwalsh(a)redhat.com> - 030-25
>>
>> - Use matchmediacon
>>
>
> Ok, right now after updating to this latest, I can not boot. I get to
> the point of this:
>
> Red Hat nash version 4.1.9 starting
> Mounted /proc filesystem
> Mounting sysfs
> Loading jdb.ko module
> Creating block devices
> Creating root device
> Mounting root filesystem
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted file system with ordered data mode.
> Switching to new root
>
>
> Then it just hangs and nothing happens. It doesn't matter if I use
> older kernels, same behavior. I have no clue. Is it because the dev
> package was deleted? I had set in /etc/udev/udev.conf
> UDEV_INITRD="no"
> to avoid the many error messages at boot time, should that be set to
> "yes"? Then remake the initrd?
Well, normally I hate to answer my own post, but in this case I'm
ecstatic. Setting UDEV_INITRD="yes" and regenerating the initrd fix my
situation.
kernel=2.6.8-1.549
MAKEDEV-3.13-1
udev-030-26
Thanks! I was having the same problem and was into the rescue mode too when
I read your solution.
The only thing now is that the nvidia driver is not autoloaded anymore when
starting X...
-Marcel
--
======-------- Marcel J.E. Mol MESA Consulting B.V.
=======--------- ph. +31-(0)6-54724868 P.O. Box 112
=======--------- marcel(a)mesa.nl 2630 AC Nootdorp
__====
www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
They couldn't think of a number, Linux user 1148 --
counter.li.org
so they gave me a name! -- Rupert Hine --
www.ruperthine.com