Date: Wed, 8 Jun 2011 16:07:52 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Garrett Cooper <yanegomi@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: IPv4 broken on r222048 Message-ID: <66750835-22BE-4F95-8940-567D74BC0488@lists.zabbadoz.net> In-Reply-To: <BANLkTikdy1effxAwiWOqoMwa989kKapm=g@mail.gmail.com> References: <BANLkTinWSP0ko69qi9Qca7O2=LRpSn19yw@mail.gmail.com> <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> <BANLkTi=PXebdMw9X7=WJ4ygZ6iom=TDJhA@mail.gmail.com> <4434466E-F4B0-47B1-98BF-80E4E495AA4C@lists.zabbadoz.net> <BANLkTikdy1effxAwiWOqoMwa989kKapm=g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 7, 2011, at 6:15 PM, Garrett Cooper wrote: >> I think I just found a good "recovery" idea -- I should disable the >> features with rescue builds. That should give one a working >> /rescue/ifconfig in all cases and should be sufficient to recover? > > That would be a good backup plan so people could at least avoid > painting themselves into a corner by accident. Can you confirm that http://people.freebsd.org/~bz/20110608-02-ifconfig-rescue.diff would work for you? One will still be screwed if doing it remotely without serial console or keyb access, but with that there should be a way to recover. Note that the rc scripts also check the AF to be present and will not configure them if not. Bjoern -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66750835-22BE-4F95-8940-567D74BC0488>