FreeLists / openbeosnetteam / [openbeosnetteam] Re: Network preflet, the future?

["Niels Reedijk" <n.reedijk@xxxxxxxxx>]

> > That's basicly the way our current stack is setup today: via
> > ifconfig.
> > BONE do that in his /beos/boot/netscript, too.
> > I find this way too Unix-y, too init.d-y.
> 
> The good thing is, that if we are using driver_settings all over the
> place, the stack could load its initial settings automatically.
> What we still need, however, is something that starts the stack. It
> would only need to open the stack once, to keep it loaded and running,
> it could end directly after this.

The same place where the app_server is loaded?

> > The current (or default if none) profile should be determined by the
> > stack "settings" helpers functions, and the settings loads from them
> > at each
> > module request.
(...)
> > If this file don't exists, the helper function will try to get it
> > from /etc/network/profiles/default/interfaces file.
> 
> I like that. We could even say "if that section is missing" instead of
> "if this file doesn't exist", at least I would like that even more.

Could be tricky though, I can't really imagine a way to implement that
without a lot of code.

> > I will rather like to move the "restart the stack" button under a
> > stack
> > overview/status add-on than right in front user every time.
> > net_server syndrom, I know...
> 
> Do we really need this "restart the stack" button at all? I think even
> a "Stop Stack" button would make more sense to me, than just
> restarting. At least, I don't understand, what it is good for?
It's replaceble, it's function is the same of an 'apply' button. It's
just
me copying a bit of the current network preflet.

Niels