"John Johnson" <[EMAIL PROTECTED]> writes:
>> /dev/hda1 -> /mnt (root partition)
>> /dev/hda6 -> /usr
>>
>> /dev/ram3 is mounted to /
>>
>> After which, I ran /usr/sbin/mdk_makedev /mnt/dev
>
> chroot /mnt
> /usr/sbin/mdk_makedev /dev
>
> "find /dev|wc -l" should report ~19k files
>
>
> My /dev directory has ~16.8k files in it after executing these commands. The
> system now gets further along in the boot process but now I'm getting the
> following errors:
>
> setting default font: dup2: bad file descriptor [Failed]
> /etc/rc.sysinit: /dev/null: read-only file system
something has accedded /dev/null at the bad time and create a file
instead of a device.
on the rescue, you can do "find /dev/ | xargs rm -fr" in the chrooted
environment before running mdk_makedev (which don't overwite already
existing entries).
longer explanation:
1) 1mdk and 2mdk had typos :-(
2) while updating from <3.3.1-1mdk, there's a 7 seconds race
window, which make possible to have a program that write to
/dev/null whereas the old one has been delete by rpm but the
new one isn't yet created, thus resulting in a file insead
of a special device;
then the next process which'll try to access /dev/null 'll
have some problems ....
as /dev/null is one of the rare /dev/ entries one write to, and
is the device that get 99% of the writes in /dev/, i'll put a
special case in dev-3.3.1-4mdk, something as:
while [[ ! -c /lib/root-mirror/dev/null ]]; do
rm -f /lib/root-mirror/dev/null
mknod -m 0666 /lib/root-mirror/dev/null c 1 3
chown root.root /lib/root-mirror/dev/null
done
so that we'll be sure to have a valid /dev/null after dev update
