On Thursday 28 June 2007, Jason Curl wrote: > Mike Frysinger wrote: > > On Thursday 28 June 2007, Jason Curl wrote: > >> Mike Frysinger wrote: > >>> On Thursday 28 June 2007, Jason Curl wrote: > >>>> As a nice feature, does it exist in the newest mdev.conf the ability > >>>> to specify the name of the device that should be created? > >>> > >>> all mdev functionality is explained in docs/mdev.txt > >>> > >>> if you want to change the name, write a little script to do so and have > >>> mdev.conf execute it > >> > >> Do all the hotplug variables set by the kernel propogate to the programs > >> that mdev run? > > > > of course ... that's how the environment works, children processes > > inherit from the parent (mdev) > > > >> mdev > >> already knows about the device, so a symlink option like udev has would > >> save flash space overall (less scripts, faster and as an option in the > >> menuconfig would mean only those who want it would use it). > > > > there is a patch on the mailing list to add this ... i'm debating adding > > it as the purpose of mdev is to provide the bare min required features; > > if you need more, go use udev > > I like the link especially for 'stderr' and what not, certainly much > faster at boot.
thinking about it, mdev symlink support wouldnt help here at
all ... /dev/std{in,out,err} are normally created by the init system as
symlinks to /dev/fd/{0,1,2} ... and /dev/fd itself is just a symlink
to /proc/self/fd
none of these things get kernel events to trigger the symlink creation in the
first place ...
-mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
