Date: Mon, 28 Oct 2002 12:08:04 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Tim Kientzle <kientzle@acm.org> Cc: "M. Warner Losh" <imp@bsdimp.com>, current@FreeBSD.ORG, peter@wemm.org Subject: Re: HEADS UP: you need to install a new kernel before an installworld. Message-ID: <20021028200804.GA40020@troutmask.apl.washington.edu> In-Reply-To: <3DBD9672.9000308@acm.org> References: <bulk.15293.20021025234418@hub.freebsd.org> <3DBAE1FA.2010209@acm.org> <20021026.234211.117680655.imp@bsdimp.com> <3DBD9672.9000308@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 28, 2002 at 11:56:34AM -0800, Tim Kientzle wrote: > M. Warner Losh wrote: > > >Tim Kientzle <kientzle@acm.org> writes: > > >: ... 'installkernel' is not filling it's contract: it is > >: not ensuring that the next boot uses the new kernel. > > > >Are you sure you need new bootblocks? I've not had issues and am > >pretty careless about when I do installworld vs installkernel. > > > >You need them for the 4.x -> 5.0 upgrade, but I didn't think you've > >needed new ones for a long time now. > > In case you've forgotten, in another month or two, > thousands of people are going to be upgrading > from 4.x -> 5.0. Those are going to be people > who don't regularly read -current or even -stable. > The upgrade process right now is getting pretty > ugly and needs to be cleaned up some before > release. > Peter's comments that started this thread included info for people *already* running -current. He simply reviewed the *standard* procedure for updating a -current system. He was not addressing the 4.x to 5.0 upgrade path. Installing new boot blocks is a one time issue and it is not part of the standard updating procedure. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021028200804.GA40020>