From owner-freebsd-questions@FreeBSD.ORG Tue Jan 16 17:33:09 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC9CD16A40F for ; Tue, 16 Jan 2007 17:33:09 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2289B13C4B8 for ; Tue, 16 Jan 2007 17:33:08 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 9A3235199A for ; Tue, 16 Jan 2007 12:33:07 -0500 (EST) Date: Tue, 16 Jan 2007 17:33:05 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070116173305.0c8b2621@gumby.homeunix.com> In-Reply-To: <20070114212456.GA3744@kobe.laptop> References: <73161.84816.qm@web51108.mail.yahoo.com> <20070114202517.GA3404@kobe.laptop> <20070114153515.ae528666.wmoran@collaborativefusion.com> <20070114212456.GA3744@kobe.laptop> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: advice on compiling a new kernel & upgrading to the latest sources X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2007 17:33:09 -0000 On Sun, 14 Jan 2007 23:24:56 +0200 Giorgos Keramidas wrote: > On 2007-01-14 15:35, Bill Moran > wrote: > > Giorgos Keramidas wrote: > > [copious snippage] > > > > 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL > > > > > > No it doesn't. CVSup will delete the files it doesn't know > > > about, so you should *SAVE a copy* of your favorite kernel config > > > file outside of the source tree and *copy* it into > > > `/usr/src/sys/amd64/conf' after CVSup finishes updates the > > > sources. > > > > Really? What have I been doing wrong? I've been keeping custom > > kernel configs for years and cvsup has never deleted any of them. > > That's what the ``*default delete use-rel-suffix'' option does, AFAIK. > > The default supfile examples in `/usr/share/examples/cvsup' have this > option enabled, and cvsup(1) says about it: > > delete The presence of this keyword gives cvsup permission to > delete files. If it is missing, no files will be deleted. > > The presence of the delete keyword puts cvsup into > so-called exact mode. In exact mode, CVSup does its > best to make the client's files correspond to those on > the server. This includes deleting individual deltas > and symbolic tags from RCS files, as well as deleting > entire files. In exact mode, CVSup verifies every > edited file with a checksum, to ensure that the edits > have produced a file identical to the master copy on > the server. If the checksum test fails for a file, > then CVSup falls back upon transferring the entire > file. > > In general, CVSup deletes only files which are known to > the server. Extra files present in the client's tree > are left alone, even in exact mode. More precisely, > CVSup is willing to delete two classes of files: > o Files that were previously created or updated by CVSup > itself. > o Checked-out versions of files which are marked as dead > on the server. > > If the option doesn't work this way, then I stand corrected. > Note the sentence: "Extra files present in the client's tree are left alone, even in exact mode" If a file has *never* been under CVS it's left alone. Having said that I still prefer to symlink because I like to be able to delete directories maintained by cvsup without losing anything.