[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Question on mdev's custom command invocation
From:       Didier Kryn <kryn () in2p3 ! fr>
Date:       2016-11-17 12:39:24
Message-ID: 582DA4FC.1030604 () in2p3 ! fr
[Download RAW message or body]

Le 17/11/2016 13:09, Peter Korsgaard a écrit :
> On Thu, Nov 17, 2016 at 11:02 AM, Didier Kryn <kryn@in2p3.fr> wrote:
>>> I'm assuming you already use environment variables in your script,
>>> e.g. $MDEV, $SEQNUM, etc Maybe you missed $ACTION, sounds like what
>>> you're looking for.
>>      Good to know that; https://git.busybox.net/busybox/plain/docs/mdev.txt
>> only mentions $MDEV .
> That is because those environment variables comes from the kernel when
> it invokes the hotplug helper (mdev):
>
> http://lxr.free-electrons.com/source/Documentation/driver-model/porting.txt#L375
>

     I knew that of course, how else could it work! But I seem idiotic 
enough to not have even imagined that mdev passed all these variables to 
its child.

     Thanks all.
                                     Didier

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]