Date: Tue, 8 Oct 2002 17:52:13 -0500 From: "DaleCo, S.P.---'the solutions people'" <daleco@daleco.biz> To: <martin@dc.cis.okstate.edu>, <freebsd-questions@FreeBSD.ORG> Subject: Re: Safe Use of cvsup Message-ID: <009e01c26f1e$e80774e0$fa00a8c0@DaleCoportable> References: <200210081920.g98JKBw58996@dc.cis.okstate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Can't think of anything offhand. However, using an incorrect tag is not a great problem, IMO, because generally there's nothing under /usr/src that can't be replaced by fixing the supfile and running cvsup again. I have on several occasions just done this: $cd /usr $rm -rf src $cvsup /stable-supfile The quid pro quo here, I guess, is that I keep my kernconfs and my supfiles copied to / Kevin Kinsey, DaleCo, S.P. ----- Original Message ----- From: "Martin McCormick" <martin@dc.cis.okstate.edu> To: <freebsd-questions@FreeBSD.ORG> Sent: Tuesday, October 08, 2002 2:20 PM Subject: Safe Use of cvsup > If one uses an incorrect tag in cvsup, it tends to > destroy the /usr/src tree, a sort of make zapworld. Would there > be anything wrong with backing up the /usr/src directory to a tar > file before running cvsup so that if the worst happens, one can > restore the directory to what it was before the mishap? > > I am building a new FreeBSD system from a CDROM that is a > bit out of date so I need to upgrade it after installation. > > The only thing I was thinking of was that there might be > links or something else not obvious that would make the restored > /usr/src useless. > > Martin McCormick WB5AGZ Stillwater, OK > OSU Center for Computing and Information Services Network Operations Group > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009e01c26f1e$e80774e0$fa00a8c0>