Date: Mon, 17 Jan 2005 14:53:31 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Doug Hardie <bc979@lafn.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: 5.3 Building Kernel/World Message-ID: <20050117225331.GC31567@xor.obsecurity.org> In-Reply-To: <FDB0FD52-68C5-11D9-8611-000393681B06@lafn.org> References: <CC0E9838-684B-11D9-8611-000393681B06@lafn.org> <20050117060510.GA63358@xor.obsecurity.org> <8DC9B67A-6857-11D9-8611-000393681B06@lafn.org> <20050117071900.GA92079@xor.obsecurity.org> <F2AAD8B1-6859-11D9-8611-000393681B06@lafn.org> <20050117190712.GA70520@xor.obsecurity.org> <FDB0FD52-68C5-11D9-8611-000393681B06@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--z4+8/lEcDcG5Ke9S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 12:25:55PM -0800, Doug Hardie wrote: > >The number of changes between RELENG_5_3_0_RELEASE and RELENG_5_3 is > >very small. If you're seeing lots of changes, it means that you > >didn't actually have a 5.3-RELEASE source tree installed before now, > >which explains the problems you were seeing in compiling it. > > > >Kris > > >=20 > Thats interesting. I was using the 5.3 release CD. The checksums=20 > match those listed. It was installed onto a re-formatted drive as I=20 > wanted the UFS-2. The source was installed as part of the original=20 > installation. Anyway, either the cvsup or the cleandirs worked. I was= =20 > able to buildworld and a new kernel. Installation of both appears to=20 > have gone correctly. uname gives the new kernel and strings of=20 > /boot/kernel/kernel also shows the new name. uname before said=20 > 5.3-RELEASE. It would appear that when I build the production systems=20 > I will immediately after instalation cvsup to RELENG_5_3 and then run=20 > make cleandir before anything else. Fortunately right now I am playing= =20 > with test systems. >=20 > It it at all possible to not have to buildworld when building a new=20 > kernel? For example, I was trying to add option atapicam. It would=20 > seem that buildworld would not be necessary in that situation. If you're modifying the kernel configuration and you have not updated your sources you can use the 'config' method to build your kernels. If you update your sources then you must use buildworld/buildkernel, or you will occasionally encounter errors. This is described in the handbook in greater detail. Kris --z4+8/lEcDcG5Ke9S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7EHqWry0BWjoQKURAgA6AJ4tFK9uRtPNxD8pJEUAandtNTnKTACg4oA6 w0GIDcrD46HhgldHicrUWjI= =gPQY -----END PGP SIGNATURE----- --z4+8/lEcDcG5Ke9S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050117225331.GC31567>