[gobolinux-devel] [gobolinux-users] configuration internet access

[Carlo Calica]

On 2/4/07, Lucas C. Villa Real <lucasvr at gobolinux.org> wrote:
> On 2/5/07, Carlo Calica <carlo at calica.com> wrote:
> > Wireless-Tools makes sense.  I'm thinking it should be called
> > WirelessConfig.  It'll only deal with iwconfig settings.  Everything
> > else (ifconfig, dhcpcd) should be handled by NetworkInterface.  Then
> > changes won't need to be synced.
> [...]
> >
> > An alias won't work (needs to be executable from outside a shell) but
> > a wrapper would work great.  Which package?  And if its one of ours,
> > wouldn't living in bin be less confusing?
>
> Hmm, it sounds strange to put a "foreign" binary inside
> Wireless-Tools' bin dir. Being a task it should be ok, but then we
> would need to store settings somewhere. Are you fine on using a task
> instead, plus a new file at Wireless-Tools/Settings to store the
> network settings?
>

Sorry, two different things.  WirelessConfig is a task that lives with
 Wireless-Tools.  I think keeping the config vars in NetworkOptions
would be least confusing.

The other issue is ifup/ifdown scripts.  These compatibility wrappers
aren't tied to wireless.  In fact, I really want them for ifplugd on
my wired ethernet.

> Another option is to merge this into Scripts/bin instead, having the
> script a first check to verify whether the user has Wireless-Tools
> installed. I was only a little reluctant on this because network
> settings are currently stored in BootScripts. Maybe we should also
> take the time and perform a general cleanup on this, putting
> everything inside Scripts and/or in a new NetworkScripts package?
>

A NetworkScripts package is overkill.  Putting ifup/ifdown in
BootScripts is the most straight forward but seems conceptually wrong.
 Putting them in Scripts might cause problems in rootless.



-- 
Carlo J. Calica