Date: Mon, 19 Jun 1995 23:25:00 +0100 From: "Jordan K. Hubbard" <jkh@freebsd.org> To: Gary Palmer <gpalmer@westhill.cdrom.com> Cc: Mattias Karlsson <matte@sdf.luth.se>, freebsd-bugs@freefall.cdrom.com Subject: Re: misc/535: Sysinstall takes down the network. Message-ID: <10188.803600700@whisker.internet-eireann.ie> In-Reply-To: Your message of "Mon, 19 Jun 1995 12:50:54 PDT." <9910.803591454@westhill.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> If you plan to use the systinstall EHS for doing non-installation > related work, expect the unexpected!!! I honestly can't call this a > bug, and that if you `abuse' the facilites provided, that we can't do > much to provide a safety net. Actually, this is a more than reasonable complaint and I've just added code to leave the network completely alone if you run sysinstall again in "post-installation mode." It was always my intention to make sysinstall more generally useful as a post-configuration tool and I simply failed to put all the requisite "am I really running as init?" checks in to make this more possible. > YES, we can do this, but do we really want to ask the users permission > to ifconfig down the network EVERY time? We'd get requests to take > such a facility out pretty soon, I can tell you!! Sorry Gary, but the truth of the matter is that sysinstall shouldn't be tweaking the network AT ALL when run for the second time! The code that whacked the network up and down (and did a few other obnoxious things which I've now corrected as well) was simply too stupid to know when its services were no longer needed. This has been fixed and was a genuine, bogus, evil nasty bug. Thanks, Mattias, for reporting it! It will be part of the next set of UPDATES floppies I'll be rolling soon. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10188.803600700>