Date: Fri, 12 Apr 1996 08:46:55 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: jgreco@brasil.moneng.mei.com (Joe Greco) Cc: pst@freefall.freebsd.org, current@freefall.freebsd.org Subject: Re: feedback sought on proposed change to netstart Message-ID: <199604121546.IAA21589@GndRsh.aac.dev.com> In-Reply-To: <199604121409.JAA17433@brasil.moneng.mei.com> from Joe Greco at "Apr 12, 96 09:09:55 am"
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,
>
> See my previous mail. What if we _remove_ the ifconfig in netstart in the
> case where there is a start_if.<xxx> file?
>
> Theory being, that script is entirely responsible for starting the
> interface. In my book that may include establishing a physical link, and/or
> setting up whatever addresses and aliases are appropriate.
>
> This seems like a very generalized solution to me (at least, it's what I do
> here, and it works great for me).
That seems quite reasonable... I have done this by setting ifconfig_${INT}
to null in /etc/sysconfig. That does have the nasty side effect of of
echoing the config parameters out twice, but it does what you want.
I have no objection to the removal of if_config ${ifn} ${ifconfig_args]
if an /etc/start_if.${ifn} is called.
--
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?199604121546.IAA21589>