On Mon, Jun 1, 2009 at 12:38, Rob Desbois <rob.desbois@xxxxxxxxx> wrote:
> I'm using udev 135 (as it's the latest version supporting my kernel, 2.6.21)
>
> README states "The content of /lib/udev/devices/ directory...should be
> copied over to the tmpfs mounted /dev" - when I build udev I don't
> have this directory.
> I have resorted to manually mknod-ing /dev/{console,null,ttyS3} (ttyS3
> is the console UART device node).
>
> If this directory is missing, am I fine to mknod those devices - and
> are there any more I should create?
The udev sources don't do anything with /lib/udev/devices/, it's
completely up to the distribution how to handle that. You can hardcode
mknod into your bootup scripts, or copy the the nodes over, it does
not really make a difference.
/lib/udev/devices/ is just easier for some package managed distros,
where packages can just drop "static" device nodes, and they will
always be there, regardless of the state of the kernel, and the loaded
modules.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
