Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Jan 2002 19:48:05 +0100
From:      Erik Trulsson <ertr1013@student.uu.se>
To:        Doug Reynolds <mav@wastegate.net>
Cc:        "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>, "Patrick Fish (patrick@pwhsnet.com)" <patrick@pwhsnet.com>
Subject:   Re: 4.4-RELEASE to 4.4-STABLE
Message-ID:  <20020126184805.GA74355@student.uu.se>
In-Reply-To: <20020126163139.678734844F@wastegate.net>
References:  <20020126074219.GA43298@student.uu.se> <20020126163139.678734844F@wastegate.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 26, 2002 at 11:33:40AM -0500, Doug Reynolds wrote:
> On Sat, 26 Jan 2002 08:42:20 +0100, Erik Trulsson wrote:
> 
> >On Sat, Jan 26, 2002 at 02:29:51AM -0500, Doug Reynolds wrote:
> >> 
> >> cvsup
> >> 
> >> make buildworld
> >> make kernel KERNCONF=yourkernelconf
> >> reboot
> >> boot single user mode by hitting the space and typing boot -s and
> >> enter. hit enter when it asks you for the shell; then:
> >> fsck -p
> >> umount -a
> >This umount seems quite unnecessary since if you just rebooted into
> >single-user mode the only thing mounted will be / which is mounted
> >read-only.  OTOH one thing you probably do want here instead is
> >swapon -a
> >to make sure that any swapspace you have can be used.
> >(I once forgot that on a memory-poor machine.  The installworld died
> > halfway through with an out-of-memory error.)
> 
> I thought / was readonly until you fsck'd and remountd it.  swapon -a
> would be good, although my machine has 256megs

Yes, / is readonly until you mount it readwrite.  But there is no need
to *un*mount anything there. The only thing which is mounted is / and
you don't want to umount it. (If you do it (and I am not sure if you
actually can do it) you won't be able to remount it since the mount
command won't be accessible.)
 

> 
> >> mount -a
> >> 
> >> make installworld
> >> mergemaster
> >> reboot
> >> 
> >> that'll up you to the latest.
> >> 
> >> (btw, if anyone sees any safely problems with this order, lemme know,
> >> seems totally redundant)
> >
> >Redundant? No.  You can usually skip the 'reboot into single-user mode'
> >part without any ill-effects but that is about it.
> 
> however, if you just shutdown now, you wont be able to test the kernel
> before you install the userland.  and everyone claims it is hard to go
> back to the old userland after you commit it.

That is quite correct.  That is why I said that you usually can skip
the reboot.  (usually != always)
It is fairly rare that there are any problems with the new kernel.

> 
> on my system, since it isn't production or anything, i'd probably just
> do it all in multi-user mode just to see if i could break it. :)
> ---
> doug reynolds | the maverick | mav@wastegate.net
> 
> PGP Public Key Fingerprint: 6E7B 9993 B503 6D45  E33A 2019 26E5 C1DB
> 
> 

-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020126184805.GA74355>