Re: udev still stinks

On Tue, Mar 14, 2006 at 11:11:33AM +0100, Benjamin Schieder wrote:
[...]
> > > 
> > > mount --bind works for me.
> > 
> > i think that's by far the worst solution.
> > 
> > quoting from udev/README:
> > =================
> >   - It is recommended to use the /lib/udev/devices directory to place
> >     device nodes and symlinks in, which are copied to /dev at every boot.
> >     That way, nodes for broken subsystems or devices which can't be
> >     detected automatically by the kernel, will always be available.
> > =================
> > 
> > that should always be the way how we create or /dev/fd -> /proc/self/fd
> > symlink.
> 
> Yes, but that's not the problem we're talking about here.
> The problem here is the chroot after installation. So:
> Boot CD -> partition harddisk -> install gems -> a bit of magic ->
> -> chroot into installed system -> some more magic
>    ^^^
> This has nothing to do with /lib/udev/devices
> 

oh yes it has!
chrooting into that installed system is like booting into the system.
so instead of bind-mounting one should mount tmpfs and copy from
/lib/udev/devices.
that way you get exactly what you would get when booting.

th
--

> 
> Greetings,
> 	Benjamin
> -- 
> Go away, or I will replace you with a very small shellscript!
> 	http://shellscripts.org/



> _______________________________________________
> rock-devel mailing list
> [email protected]
> http://www.rocklinux.net/mailman/listinfo/rock-devel


-- 
Tobias Hintze http://hbs-solutions.de
HBS solutions GbR - Network & Information Systems