Date: Tue, 18 Nov 2003 08:58:06 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Garance A Drosihn <drosih@rpi.edu> Cc: current@freebsd.org Subject: Re: upgraded to CURRENT = system is dead Message-ID: <xzp65hiyupd.fsf@dwp.des.no> In-Reply-To: <p06002020bbdf02dbe856@[128.113.24.47]> (Garance A. Drosihn's message of "Mon, 17 Nov 2003 18:17:12 -0500") References: <1068849539.3fb559840029b@webmail.lphp.org> <xzpr807z67t.fsf@dwp.des.no> <p06002020bbdf02dbe856@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn <drosih@rpi.edu> writes: > 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. These instructions should be changed. Doing 'buildworld' before 'buildkernel' works just fine this time as always, and instructing users to do the opposite will only confuse them. There's nothing in the kernel build that calls statfs64. > 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 ...' I assumed that this was a typo in the email, but even if it wasn't, it shouldn't make any difference; since he didn't build a new world, 'make install' will just reinstall the world he already had, and 'make kernel' will build and install a new kernel. It'll just take a while longer than it should. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp65hiyupd.fsf>