Date: Mon, 12 Apr 2004 19:54:26 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Randy Bush <randy@psg.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: very current won't mount /tmp Message-ID: <Pine.NEB.3.96L.1040412195402.19174B-100000@fledge.watson.org> In-Reply-To: <16507.9094.803648.85615@roam.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040412195402.19174B-100000>