From owner-freebsd-stable Sun Jun 24 17:53: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-172.zoominternet.net [24.154.28.172]) by hub.freebsd.org (Postfix) with ESMTP id 7E9B137B406 for ; Sun, 24 Jun 2001 17:53:00 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.4/8.11.4) with ESMTP id f5P0sTM18384 for ; Sun, 24 Jun 2001 20:54:29 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sun, 24 Jun 2001 20:54:29 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <15157.18428.497356.447656@zircon.zircon.seattle.wa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Jun 2001, Joe Kelsey wrote: > I think we need to change the handbook to indicate the pitfalls inherent > in attempting to track stable or current via cvsup or other source > updating. Even tracking RELEASE_X_Y is problematic since it involves > recompiling from source, which is, of course the only way to customize > your kernel. Sort of. You can do a lot with klds, as you observe, and you can do still more with sysctl. (Aside: what *can't* you set with sysctl? It'd be a useful exercise to compile that list, and make it smaller.) -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message