Re: RC NG, ntp and routed

[Daniel C. Sobral]

Mike Makonnen wrote:

On Wed, Dec 11, 2002 at 03:28:12PM -0200, Daniel C. Sobral wrote:

>[root@piratinga root]# ls -l /usr/local/sbin/ospfd
>-r-xr-xr-x  1 root  wheel  471392 Dec  1 00:58 /usr/local/sbin/ospfd*
>[root@piratinga root]# ls -l /usr/local/sbin/bgpd
>-r-xr-xr-x  1 root  wheel  691952 Dec  1 00:58 /usr/local/sbin/bgpd*


Who said anything about moving ports into /? I meant the routing
daemons in /usr/sbin. But as Gordon pointed out that's still
quite a bit of disk space.

I mean that routed is _one_ routing daemon, one that supports the old, would someone please shot it in the head to give it peace, RIP. If you happen to run a modern routing protocol... hell, if you happen to run a middle-aged routing protocol, you'll be using something else.

And, since you do not seem to be aware of it, Zebra, for one, is run as...

router_enable="YES"
router="/usr/local/sbin/zebractl"
router_flags="start"

ie, it is run by /etc/rc.d/routed. A very good thing, in fact, since one _needs_ it to be run early.

So, please, let's not assume one is using routed(8), just like we do not assume one is using sendmail(8).

>And all this because... people don't want to break fs mounting in local
>and remote?
>
>I saw break it, and have routing run after local. If your /usr is
>remote, then either you'll copy routed (or whatever you use) to a local
>disk, or you won't be using it.
>
>People, let's face it. There *ARE* things you want to be run *after*
>local fs mount and *before* remote fs mount. And we are hurting
>ourselves in a few places just because we haven't admitted to it.


I don't understand what you are saying. Why would we have routing run after
local filesystems are mounted but before the network is up?

Not before network is up. Before one mounts remote filesystems. Network is _not_ up until routing is in place. For most configurations, that is done in network2 (see defaultrouter). For a few, it needs routed.

--
Daniel C. Sobral (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
TCO
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Outros:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

HOW YOU CAN TELL THAT IT'S GOING TO BE A ROTTEN DAY:

#32: You call your answering service and they've never heard of
you.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message