From owner-freebsd-current@FreeBSD.ORG Tue Apr 3 17:09:15 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E3F216A403; Tue, 3 Apr 2007 17:09:15 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6895813C458; Tue, 3 Apr 2007 17:09:13 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.47] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id l33GjRkc013694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Apr 2007 09:45:28 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <46128475.9060602@FreeBSD.org> Date: Tue, 03 Apr 2007 09:44:37 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Andrew Pantyukhin References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Surviving /dev/null disappearance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2007 17:09:15 -0000 Patch ld(1) to detect the condition and don't unlink the device node? -Maxim Andrew Pantyukhin wrote: > While porting mtpaint I stumbled upon a hacked up > configure script which has a test like this: > > ld -o /dev/null > > 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) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >