Date: Tue, 16 Jan 2007 17:33:05 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: advice on compiling a new kernel & upgrading to the latest sources 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Jan 2007 23:24:56 +0200 Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: > On 2007-01-14 15:35, Bill Moran <wmoran@collaborativefusion.com> > wrote: > > Giorgos Keramidas <keramida@ceid.upatras.gr> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070116173305.0c8b2621>