Date: Tue, 13 Apr 2004 08:17:26 +0900 From: Randy Bush <randy@psg.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: very current won't mount /tmp Message-ID: <16507.9094.803648.85615@roam.psg.com> References: <16505.6623.99276.241321@roam.psg.com> <20040412210200.GB5340@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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 randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16507.9094.803648.85615>