[patch] wireless patch, take 2
kay.sievers at vrfy.org
Thu May 27 11:24:25 PDT 2004
On Thu, 2004-05-27 at 00:32 +0200, David Zeuthen wrote:
> On Wed, 2004-05-26 at 18:30 -0400, Joe Shaw wrote:
> > On Wed, 2004-05-26 at 23:27 +0200, David Zeuthen wrote:
> > > Here is an idea; maybe HAL shouldn't provide that API I was talking
> > > about and we should do it like Joe suggest by just changing
> > > net.ethernet.80211.ess_id but HAL should do nothing.
> > >
> > > Instead a callout in property.d just does all the heavy lifting like
> > > changing the ESS ID, reconfiguring the interface and stuff? Joe, maybe
> > > this was what you meant in the first place?
> > Actually, no, I was going to do these things in the HAL code itself, but
> > this sounds like a cleaner solution given that network scripts are
> > different for every distro.
> Thinking a bit more about it, there's some nasty corner cases here like
> the fact that net.ethernet.80211.ess_id is updated before the change is
> complete; what happens if we cannot connect to that network etc. etc.
> Maybe it would be even cleaner to have a directory
> and have the method org.freedesktop.Hal.Device.<name_of_method> execute
> the appropriate script? If non-zero is returned then an exception is
> thrown at the caller with the message from stderr of the script. Or
> We'd still have to specify all methods in the spec and provide
> convenience functions in libhal but at least this gives an expandable
> framework for such tasks as setting the ESSID - I imagine we run into a
> few others like this in the future.
> How does that sound?
After following the discussion about the inclusion of the wirleless
configuration inside of HAL, I'm wondering about the border of features
to be included in HAL? Should it be able to eject my CD or set the
volume of my soundcard too? What is the long term goal here?
hal mailing list
hal at freedesktop.org
More information about the Hal