[openbeosnetteam] Re: Quiet List
- From: Evan Anderson <evan.k.anderson@xxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Mon, 11 Apr 2005 08:06:22 -0700
On Apr 11, 2005 7:09 AM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
> Evan Anderson <evan.k.anderson@xxxxxxxxx> wrote:
> > But I don't think there's a need to put this into the kernel, so long
> > as there is a way to register device changes to a userspace program
> > (which seems like a more flexible idea to me, as well as safer than
> > adding code to the kernel).
>
> Definitely. The way I imagine it, there is a net_server running that
> does the auto-configuration and inetd services, etc. Running this would
> set up the whole networking - of course, with some useful default
> values if it hasn't been configured yet.
Some other useful things that could be run by this service (although
it's not clear to me that it all needs to be in one process):
1) Maintain local DNS cache
2) Maintain routing tables
3) Run other services/modules as needed.
Of course, these should either be separate programs, or there should
be a configuration file to control/disable each of them.
- References:
- [openbeosnetteam] Re: Quiet List
- From: Evan Anderson
- [openbeosnetteam] Re: Quiet List
- From: Axel Dörfler
Other related posts:
- » [openbeosnetteam] Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- » [openbeosnetteam] Re: Quiet List
- [openbeosnetteam] Re: Quiet List
- From: Evan Anderson
- [openbeosnetteam] Re: Quiet List
- From: Axel Dörfler