Date: Tue, 3 Apr 2007 11:59:49 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Andrew Pantyukhin <infofarmer@freebsd.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: Surviving /dev/null disappearance Message-ID: <20070403095948.GL80382@cicely12.cicely.de> In-Reply-To: <cb5206420704030216r44243573h7981c1e35ef7225@mail.gmail.com> References: <cb5206420704030216r44243573h7981c1e35ef7225@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 03, 2007 at 01:16:41PM +0400, Andrew Pantyukhin wrote: > While porting mtpaint I stumbled upon a hacked up > configure script which has a test like this: > > ld -o /dev/null <some libs> > > If you run this under root the net result is you > don't have /dev/null anymore. > > I fixed the configure script, writing to temp files > instead of /dev/null, but the question is, how can > I survive the situation. > > Without /dev/null very little works. You can mount > a second devfs over the first one, but half of the > programs running in the background (e.g. wmii) are > still freaked out bad. > > So is there a way to revive the system without a > reboot? (hint: /etc/rc.d/dev* scripts refuse to > work without /dev/null) mknod -c 0 0 /dev/null -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070403095948.GL80382>