>> 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 randyReceived on Mon Apr 12 2004 - 14:17:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:50 UTC