From owner-freebsd-stable  Thu Sep 23 11:25: 5 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id 478DD1550F; Thu, 23 Sep 1999 11:24:55 -0700 (PDT)
	(envelope-from dispatch@blackhelicopters.org)
Received: (from dispatch@localhost)
	by blackhelicopters.org (8.9.3/8.9.3) id OAA80333;
	Thu, 23 Sep 1999 14:24:43 -0400 (EDT)
	(envelope-from dispatch)
From: Dispatcher <dispatch@blackhelicopters.org>
Message-Id: <199909231824.OAA80333@blackhelicopters.org>
Subject: Re: Minimum Stable Cvsup
In-Reply-To: <005001bf05ed$0b249c80$abd396ce@eznet> from Jim Flowers at "Sep 23, 1999  1:57: 3 pm"
To: jflowers@ezo.net (Jim Flowers)
Date: Thu, 23 Sep 1999 14:24:43 -0400 (EDT)
Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jim,

(Disclaimer: I am not a FreeBSD committer, just some who's researched
this issue.)

The short answer is, this will be a headache and definitely more trouble
than it's worth.

Longer answer:

The X stuff isn't included in FreeBSD's source tree, so you won't be
upgrading that via cvsup.  Any X security fixes will have to be
applied the hard way, with pkg_delete and pkg_add or via ports.

If all you're worried about are networking and kernel bugs, then you
can probably get away with src-sys.  You run a high risk of userland
and kernel falling out of sync, however.  FreeBSD is designed to be
upgraded monolithically.

Make world will take no less time with an out-of-sync source
collection (unless you use -DNOCLEAN).

If your system falls out of sync internally, you might be stuck with a
non-operational/non-booting/weirdly-failing system.  Complaints to the
lists will probably be met with "Well, we *say* don't do that."

I have a simple shell alias that does the upgrade for me; it boils
down to "cd /usr/src && cvsup -g stable-supfile && make world && cd
/sys/i386/conf && config KERNEL && cd ../../compile/KERNEL && make
depend && make all install" (typed from memory; do *not* cut and paste
without checking it!).  Since I replicate my .cshrc when I install a
machine, it follows me everywhere.

I use this to upgrade several remote VPN boxes without difficulty
(although I always run a test at the home office first, to see if
someone's fried -stable).  If I'm feeling brave, I even add "&&
reboot" at the end.  No muss, no fuss.

==ml
 
> I build several minimal FreeBSD systems each week with the X kernel
> developer selection and a handful of packages  (including cvsup) and 1 port
> (SKIP).  Lately I have started to use the latest -stable versions to get all
> of the bug fixes using src-all.
> 
> I would like to minimize the size, time, and complexity involved.  Can I use
> subcomponents of src-all and then build world to do this without added
> problems?
> 
> What subcomponents of src-all would I use to match the X kernel developer
> profile?  Or where do I look to figure it out?
> 
> Thanks
> 
> Jim Flowers mailto:jflowers@ezo.net
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message