Re: udev still stinks

On Mon, Mar 13, 2006 at 08:36:58AM +0100, Benjamin Schieder wrote:
> On 12.03.2006 22:50:56, Thomas fake Jakobi wrote:
> > hi,
> > 
> > i tried a build of the basic-package selection with the following journal:
> > 
> > smap <lots>
> > 
> > whereof
> > 
> > smap <still more>
> > 
> > failed to apply.
> > 
> > i added own interpretions of 2006022216461208081 and 2006022810451609842.
> > 
> > the build went fine, though when installing, right after the chroot into
> > the installed system, an endless loop of 'password 1 and password 2
> > don't match' show up, because there is exactly nothing (expect what we
> > create explicitely) in /dev. sysfs, proc and the /dev ramfs are mounted
> > and udevd is running.
> > 
> > what is the supposed 'right' thing to do in this situation?
> 
> 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.

th
--
> 
> You may also try to kill udevd, restarting it in the chroot and then running
> the new and improved udevstart-obseleting simple shell script:
> 
> find /sys -name uevent | while read u ; do
> 	echo 1 > ${u}
> done
> 
> Greetings,
> 	Benjamin
> -- 
> The Nethack IdleRPG! Idle to your favorite Nethack messages!
> http://pallas.crash-override.net/nethackidle/



> _______________________________________________
> 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