Date: Mon, 22 Jan 2001 11:36:41 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: John Baldwin <jhb@FreeBSD.ORG> Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, freebsd-current@FreeBSD.ORG, The Hermit Hacker <scrappy@hub.org>, Peter Wemm <peter@netplex.com.au> Subject: Re: lastest kernel from cvs ( sh exists with signal 8 ) Message-ID: <20010122113641.A92053@citusc17.usc.edu> In-Reply-To: <XFMail.010121231244.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on Sun, Jan 21, 2001 at 11:12:44PM -0800 References: <20010122015502.A18847@cae88-102-101.sc.rr.com> <XFMail.010121231244.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2001 at 11:12:44PM -0800, John Baldwin wrote: > Rarely if ever do you need the new tools. The only cases are for a > binutils upgrade that is not backwards compatible (such as the 2.9 > -> 2.10 upgrade), or if you need a newer version of config, which > can be handled by installing config and then building your kernel. > The config(8) changes won't happen in stable, and I don't foresee > anymore drastic buildkernel changes in the future. I agree that developers don't need to use buildkernel because we are mostly capable of doing the manual workarounds on the rare occasions when things need to be done differently. But if you cast your mind back to the many dozens of support messages on -stable and other lists after the binutils upgrade, you will note that users are incapable of following special-case directions even when their mailbox is full of messages repeating them, and they need to have a magic wand which does it for them. That's what buildkernel is supposed to be..whether or not it's broken or can be fixed is a separate question. I never use buildkernel either because I know enough to fix things when they break, but that's not true for Joe Random, and we shouldn't advocate against it to the general user base unless we have a better magic solution. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6bIvJWry0BWjoQKURAoILAKCW6ZNyJ1fv5RH8FlQ3aoi/qu/ECACdG3Hp bIGjdP/jJW2xCtHXk4eQkQA= =77g8 -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- 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?20010122113641.A92053>