Date: Wed, 11 Dec 2002 08:43:45 -0200 From: "Daniel C. Sobral" <dcs@tcoip.com.br> To: Gordon Tetlow <gordont@gnf.org> Cc: Mike Makonnen <mtm@identd.net>, current@freebsd.org, obrien@freebsd.org, Doug Barton <DougB@freebsd.org> Subject: Re: RC NG, ntp and routed Message-ID: <3DF716E1.5090903@tcoip.com.br> In-Reply-To: <3DF4996E.1040706@tcoip.com.br> References: <3DF4996E.1040706@tcoip.com.br> <20021210024350.GC16008@matrix.identd.net> <20021210162208.GJ45512@roark.gnf.org> <3DF61DE4.9070205@tcoip.com.br> <20021210225014.GA22267@matrix.identd.net> <20021211002318.GT45512@roark.gnf.org>
index | next in thread | previous in thread | raw e-mail
Gordon Tetlow wrote: > On Tue, Dec 10, 2002 at 02:50:14PM -0800, Mike Makonnen wrote: > > >On Tue, Dec 10, 2002 at 03:01:24PM -0200, Daniel C. Sobral wrote: > > > >>On another note, I thought the patch a bit excessive. Here, I just > added > >>BEFORE: ntpd to routed. OTOH, it seems that patch did a bit more. > > > >It's not excessive. It's the correct solution. > >Your solution solves your specific problem but it's > >not the right way to go about solving the problem. It's kind of hard to > >explain, you have to work with it for a while to get the hang of it. For > >some things it might be easier _and_ right to say this must come before > >that. In this case; however, ntpd requires that routing be available > as a > >prerequisite, but there's no real relationship that exists between > >the two that necessitates routed having to know about ntpd. If we were > >to follow your example to its logical conclusion the BEFORE line for > >the routing daemons would have to include _every_ daemon that requires > >network availability. I think in this case it would be more correct to > >have the network daemons REQUIRE the routing daemons. Does that make > >sense? I agree with this analysis. It's just that the patch presented touched more files than ntpd alone. > Ideally, ntpd should require NETWORKING and that should solve all > problems. > The real problem is that routed is included with DAEMON, not NETWORKING. I > think that's the real problem and judging that routed is in /sbin, we > could > probably move it there without a problem. Err, not so fast, please. FreeBSD's routed is in /sbin, but I daresay quite a few of those who actually need a dynamic router resort to ports (specifically, Zebra and Gated). So let's not haste needlessly here. We are in code freeze, and these changes need not enter before 5.0-R. Let's understand the problem and the issues throughly, and produce a correct solution. -- Daniel C. Sobral Gerência de Operações Divisão de Comunicação de Dados Coordenação de Segurança TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DF716E1.5090903>