|
[openbeosnetteam]
||
[Date Prev]
[05-2002 Date Index]
[Date Next]
||
[Thread Prev]
[05-2002 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Unloading modules...
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Wed, 8 May 2002 00:04:02 +0100
In a short time it'll be junked anyway.
Why waste time working on it?
david
----- Original Message -----
From: "Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Tuesday, May 07, 2002 11:59 PM
Subject: [openbeosnetteam] Re: Unloading modules...
> > > - this can't be done via a socket, as a socket needs functions
> > > to be called in modules. Therefore this should be done via a
> > > sysctl call once we get that integrated into the kernel
> >
> > Hum, what about a dedicated /dev/net/stack driver ioctl() ?
> > It's there. We can open() the driver *without* using a socket...
> > AFAIR, there is already some NET_STACK_RESTART opcode, commented out,
> > in the net_stack_control() code...
>
> Why don't we toss /dev/net/stack and make a looper? It can sit on a
> port waiting for control messages. This is a much better solution,
> IMHO.
> -Nathan
>
> --
> Fortune Cookie Says:
>
> " ... I told my doctor I got all the exercise I needed being a
> pallbearer for all my friends who run and do exercises!"
> -- Winston Churchill
>
>
>
|
|
