Date: Mon, 17 Nov 2003 18:17:12 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= ), Antoine Jacoutot <ajacoutot@lphp.org> Cc: current@freebsd.org Subject: Re: upgraded to CURRENT = system is dead Message-ID: <p06002020bbdf02dbe856@[128.113.24.47]> In-Reply-To: <xzpr807z67t.fsf@dwp.des.no> References: <1068849539.3fb559840029b@webmail.lphp.org> <xzpr807z67t.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:37 AM +0100 11/17/03, Dag-Erling Smørgrav wrote:
>Antoine Jacoutot <ajacoutot@lphp.org> writes:
>> Here is what I did:
>> $ cvsup blablabla...
> > $ make buildkernel KERNCONF=MYKERNEL &&
> > make install kernel KERNCONF=MYKERNEL
>
>There's not much point in 'make buildkernel' if you haven't
>done 'make buildworld' first.
Uh. /usr/src/UPDATING explicitly says:
20031112:
[...] You should build and boot a new kernel BEFORE doing a
`make world' as the new kernel will know about binaries using
the old statfs structure, but an old kernel will not know
about the new system calls that support the new statfs
structure.
We generally recommend doing a buildworld first, but it has
to be done in a different order for this upgrade.
However, if I am correctly reading the section quoted from
Antione's message, the problem might be that he did:
'make install kernel ...'
instead of: 'make installkernel ...'
Users need to specify a single target of 'installkernel',
with no blanks between the two words. Antoine, was that
just a typo, or did you really do 'make install kernel'?
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06002020bbdf02dbe856>