Re: very current won't mount /tmp

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