Date: Wed, 20 Feb 2008 13:27:52 -0500 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "Brooks Davis" <brooks@freebsd.org> Cc: freebsd-hackers@freebsd.org, sam <samflanker@gmail.com> Subject: Re: [trouble] restart network & vlan`s interface Message-ID: <5f67a8c40802201027r17ffef92ga5089bc8badde506@mail.gmail.com> In-Reply-To: <20080220170825.GA347@lor.one-eyed-alien.net> References: <47BBD9A2.4000706@gmail.com> <20080220161919.GA99421@lor.one-eyed-alien.net> <47BC5CCA.8060003@gmail.com> <20080220170825.GA347@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 20, 2008 12:08 PM, Brooks Davis <brooks@freebsd.org> wrote: > On Wed, Feb 20, 2008 at 08:00:58PM +0300, sam wrote: > > Brooks Davis wrote: > >> On Wed, Feb 20, 2008 at 10:41:22AM +0300, sam wrote: > >> > >>> > >>> please help me for writing /etc/rc.conf with vlan`s interfaces > >>> (without problem network sub-system restart) > >>> > > /etc/netstart just ignores it's arguments. It's really intended for > those times when you want to bring networking up from singleuser > mode, not what you chance configurations. We do not currently have a > one-size-fits-all mechanism for handling network configuration changes. > > -- Brooks > Which inevitably leads to problems in running systems where the "restart configuration" does not match the "running configuration" of the network. It's a non-trivial problem. non-trivial to solve, non-trivial to be left unsolved.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40802201027r17ffef92ga5089bc8badde506>