Aw: Re: mdev woes

[Mike Frysinger]

On Thursday 28 June 2007, Jason Curl wrote:
> Mike Frysinger wrote:
> > On Thursday 28 June 2007, Jason Curl wrote:
> >> On Thursday 28 June 2007, Mike wrote:
> >>> On Thursday 28 June 2007, Jason Curl wrote:
> >>>> I'm using BusyBox 1.5.0 and I can't get mdev to work as I would
> >>>> expect. It's only populating a very small subset of devices in the
> >>>> kernel.
> >>>
> >>> you've probably disabled the deprecated sysfs kernel option ... older
> >>> versions
> >>> of mdev wont work in that case, you have to enable the kernel option or
> >>> grab the fix out of current trunk
> >>
> >> Checked the kernel configuration file and sysfs_deprecated is disabled
> >> as you suggested. I don't know where I was supposed to find that info -
> >> a wiki site for these tools maybe?
> >
> > no such thing exists
> >
> >> 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

> And the mdev.txt is pretty terse.

what you call "terse" is really "out of scope of mdev"

> There's no mention of having to mount 'proc'.

mdev.txt is not a document that tells you how to create a proper booting 
system.  if you need that, go read LFS.

> And a "full" setup would run that script and then "exec" init.

uhh, what ?  init executes the script, not the other way around

> For the "firmware" directory, where do I find the filename in the
> kernel? I certainly can't grep for what I want.

either you know or you dont ... and if you dont, you grep or you read the 
documentation for the device in question.  i dont actually use any firmware 
things myself.

> I would also suggest 
> changing the numbers so that the first code snippet is [4-6] and the
> second is [1-3] that shows what really must come first even though it's
> not in that order in the document.

the idea is to cover required things before optional, but for the people who 
dont actually read and just copy & paste, this would probably help.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.busybox.net/pipermail/busybox/attachments/20070628/aa7efcfd/attachment-0002.pgp