
|
[openbeosnetteam]
||
[Date Prev]
[09-2003 Date Index]
[Date Next]
||
[Thread Prev]
[09-2003 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Network preflet, the future?
- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Fri, 19 Sep 2003 11:19:40 GMT
> Axel Dörfler wrote:
> > The /dev/net/stack driver will be load and fire at boot time, like
> > every driver are.
> > He can then start the stack and keep it loaded. B_KEEP_LOADED flag
> > on
> > core module can do that, or
> > the /dev/net/stack can tweak the kernel to stay opened, by opening
> > himself. It's already there in the code.
>
> Errr... no :-)
> 1) I wouldn't like to have the stack loaded automatically and always
> on
> boot too much - if no one is using it, why bother to start it?
Good point.
My bad.
> Although, OTOH, if you really don't want him to start, just remove
> the
> driver... well, perhaps it would be okay :))
>
> 2) OpenBeOS won't do that under normal circumstances. It will be a
> lot
> more clever than R5 in this regard.
> However, there is still the possibility to automatically let it load
> your driver - but you can't rely on it anymore if everything works
> out
> :)
Damn it!
;-)
Okay, so let's say the first time libnet.so will require to open("/dev/
net/stack"), the stack will load, start and keep running...
until death.
If it's kernel module who start the stack (a network file system come
to mind), the stack will be kept loaded, but in this case
we must set the B_KEEP_LOADED flag to core module... bye bye stop/
restart/reload stack feature.
Well, the good thing here is this way, we have to other choice than
make it bug-free ;-)
-Phil
--
Fortune Cookie Says:
Parallel lines never meet, unless you bend one or both of them.
|

|