Date: Thu, 11 Apr 1996 23:04:38 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: pst@freefall.freebsd.org (Paul Traina) Cc: current@freefall.freebsd.org Subject: Re: feedback sought on proposed change to netstart Message-ID: <199604120604.XAA17874@GndRsh.aac.dev.com> In-Reply-To: <199604120527.WAA23125@freefall.freebsd.org> from Paul Traina at "Apr 11, 96 10:27:19 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Currently /etc/netstart evaluates /etc/start_if.<foo> if the file exists, > and THEN does any standard ifconfig commands if defined. > > This seems very backwards and broken to me. Here's my justification: > Basic stuff can be done by executing the commands in sysconfig, just like > we always do. /etc/start_if.<foo> is for additional stuff or exceptions, > such as configuring aliases. > > It makes sense to set up the interface, first, and then get fancy with it. You can't ifconfig some interfaces until they are setup, you don't want to ifconfig a slip line until sl0 is setup, same goes for ppp. start_if.<foo> was not meant to add aliases, it was added to ``start'' the interface so you could configure it. Perhaps we need to add a /etc/setup_if.<foo> to handle aliases, etc. > Here's the change, 24 hours to comment: Don't.... you'll break all the folks who are using start_if.<foo> for what it was meant to do. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604120604.XAA17874>