Re: ipw srcipts for hal

[dragoran <drago01 gmail com>]

yelo_3 wrote:
> > I think the scripts will provide multiple killswitches, one for each ipw
> > device found.  And once ipwWirelessCtl uses the UDI that's passed to it,
> > it should work fine with multiple killswitches.
> >     
>
> So the work with the UDI might be done in the shell script hal-system-killswitch-?et-power, so that ipwWirelessCtl is invoked with the device name to shut down!
> this could be done through info.parent as in the C code by dragoran, but in bash
>
>   
we just have to pass something unique to ipwWirelessCtl
> > What other tools like NetworkManager do is another question; right now
> > NM will kill _all_ radios when it detects one that's killed.  I don't
> > see any reason to change that right now.  If the laptop actually has a
> > physical killswitch, it certainly doesn't have more than one for wifi
> > specifically, so I'm not sure we care about support multiple independent
> > wifi killswitches in NM right now.
> >
> > Dan
> >     
>
> This is, in my opinion, good for now.
>
>
>
> I might have done an error in the setrkfill code portion in hal-system-killswitch-set-power-linux:
> I think that the variable "$value" is passed by someone to the script, since it is used in the first lines, but I don't know if value=1 means rfkill=1 or rfkill=0...
>
>
>   
my program just returns 1 for on and 0 for off