Date: Thu, 12 Dec 2002 16:02:22 -0800 From: Tim Kientzle <kientzle@acm.org> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: Brad Knowles <brad.knowles@skynet.be>, current@FreeBSD.ORG Subject: Re: RC NG, ntp and routed Message-ID: <3DF9238E.9000704@acm.org> References: <bulk.90313.20021211100352@hub.freebsd.org> <3DF7E948.9060508@acm.org> <a05200f33ba1e20f870f1@[10.0.1.2]> <3DF8C3B3.2060601@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
> Brad Knowles wrote: >> At 5:41 PM -0800 2002/12/11, Tim Kientzle wrote: >> > NETWORKING ... does not, in itself, depend on any filesystems. >> >> Sure it does. In order to do anything, you have to run programs -- right? The NETWORKING script does nothing. It runs no programs, therefore it needs no filesystems. It's purely a placeholder to simplify dependency specifications: all networking initialization is gauranteed to happen before NETWORKING. Therefore, scripts that require networking (such as lpd, sshd, ftpd, etc.) can safely depend on NETWORKING without having to know the details of the network initialization. For example, someone who needs a special routing daemon can add a script that REQUIREs network2 and comes BEFORE NETWORKING, and then their routing daemon will be started at the appropriate time: before any network-capable daemons (or remote filesystems), but after the initial interface configuration. Tim Kientzle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DF9238E.9000704>