On Sun, Jul 30, 2006 at 04:01:43PM +0200, Laurent Riffard wrote:
> In this situation, udev (version 096 here) is unable to create these
> device files (/dev/full, /dev/kmem, /dev/kmsg, etc.). /dev/null does
> exist (with wrong permissions) because it has been created by the
> initrd script.
Something's really broken with that version of udev then, because the
094 version I have running here works just fine with these symlinks.
> In order to get back the device files, I have to run the following
> command:
> # for f in /sys/class/mem/*/uevent; do echo 1 > $f; done
Ah, ok, it sounds like it's not a bug in udev itself, but rather a bug
in the way your distro does it's initialization of udev, at boot. I
suggest you file a bug with them, as they are known for doing this a bit
differently than any other distro (and different from how the udev
developers recommend), so they can fix it. It's probably just a shell
script issue.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
