From owner-freebsd-current@FreeBSD.ORG Thu Apr 15 13:00:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07C5C16A4CE; Thu, 15 Apr 2004 13:00:34 -0700 (PDT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 129A743D1D; Thu, 15 Apr 2004 13:00:33 -0700 (PDT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i3FK0H8a012509; Thu, 15 Apr 2004 13:00:18 -0700 From: Kent Stewart To: freebsd-current@freebsd.org Date: Thu, 15 Apr 2004 13:00:30 -0700 User-Agent: KMail/1.6.1 References: <16507.9094.803648.85615@roam.psg.com> <20040415061146.GD4415@ip.net.ua> In-Reply-To: <20040415061146.GD4415@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404151300.30275.kstewart@owt.com> cc: Randy Bush cc: Robert Watson Subject: Re: very current won't mount /tmp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 15 Apr 2004 20:00:34 -0000 On Wednesday 14 April 2004 11:11 pm, Ruslan Ermilov wrote: > On Mon, Apr 12, 2004 at 07:54:26PM -0400, Robert Watson wrote: > > On Tue, 13 Apr 2004, Randy Bush wrote: > > > >> very current (08:00gmt the 11th) > > > >> thinkpad t40p > > > >> > > > >> make world and kernel > > > >> boot single abuser to do the installworld > > > >> > > > >> can mount drives one at a time until i get to /tmp which is > > > >> defined as > > > >> > > > >> md /tmp mfs -s131072,rw,nosuid,nodev,noatime 0 0 > > > >> > > > >> locks up > > > >> > > > >> as installworld has not happened, it should not be the new > > > >> automagic /tmp mfs. or am i misunderstanding that? > > > > > > > > The new auto /tmp creation code should only kick in after you > > > > run mergemaster. Even then, it shouldn't have any effect in > > > > single user mode because it hasn't been run yet at that point. > > > > If you're being really paranoid, you simply verifying that > > > > nothing is mounted on /tmp before trying to mount it yourself > > > > should eliminate that from the equation. > > > > > > i tried removing md /tmp from fstab and rebooting -sw > > > > > > mount -a went fine > > > > > > vi locks up immediately > > > > > > make installworld locks up immediately > > > > > > all this is new and very disturbing > > > > Any chance you can get into DDB eitgher using console break or > > serial console break? > > The vi(1) will be shown as blocked. One now needs to manually feed > /dev/random, while in single-user mode. > > Mark, please do something about it in a short term, add it to > UPDATING at least. > > I think updating UPDATING is a good idea. I tried "feed /dev/random" and it couldn't find "feed". What are we supposed to do to get installworld to work? Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html