On 3/12/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> On 3/7/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> > On 3/6/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
> >
> > Regarding wired eth; try netplug [1] or ifplugd [2]. For choosing a
> > dynamic wifi essid, I feel that belongs in a desktop helper applet (ie
> > kwifimanager) rather than the boot tasks. Mainly because the essid
> > can change as a machine is moved from location to location.
> > If your essid is static, it makes sense for the boot tasks. Using an
> > essid of "any" lets the kernel choose a suitable ap. How the kernel
> > decides the most suitable I don't know.
> >
>
> I've given some more thought this. I'd like to add some pre/post
> hooks to the ifup/ifdown actions. These hooks would be scripts called
> /S/S/NetScripts/<iface>-{pre,post}{up,down}. Each would be sourced by
> the Network task. The pre hooks could override vars set in
> NetworkOptions (ie allowing the user to search for a preferred ESSID).
>
> Thoughts?
If you feel it's the solution, go for it. As usual, my only concern is
that adding features to boot-related scripts adds code potentially
slowing the boot process down. Might be negligible on new machines but
on slower ones sourcing extra files (or even trying to open them when
they're not there) may add up time. Maybe we should just forget about
this and just rely on Lucas' TinyScripts on really old/slow hardware.
> PS. Anyone try my updated Network and WirelessConfig tasks?
Not yet -- I'm still in the process of assembling my new machine, so
no contributions from me for a (little, hopefully) while.
-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
