Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Jun 2011 15:55:44 -0700
From:      Jeremy Chadwick <>
To:        ??imun Mikecin <>
Cc:        "" <>, Leroy van Logchem <>
Subject:   Re: ZFS v28 for 8.2-STABLE
Message-ID:  <20110629225544.GA87060@icarus.home.lan>
In-Reply-To: <-8448816796365782292@unknownmsgid>
References:  <> <> <> <> <20110629213054.GA85818@icarus.home.lan> <-8448816796365782292@unknownmsgid>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Jun 30, 2011 at 12:10:33AM +0200, ??imun Mikecin wrote:
> 29. 6. 2011., u 23:31, Jeremy Chadwick <> napisao:
> > BTW, whenever you nuke src, you should probably nuke the csup (or cvsup
> > in your case; not sure why you're using that) CVS "database" as well.
> > For csup, this lives in /var/db/sup.  For cvsup, this lives in /usr/sup.
> Would using svn ( repository) instead of csup be a
> better solution?
> Which repository (svn or CVS) is master, and which one is replicated?

I don't use Subversion so I can't answer that part of the question.

I don't quite understand how/why replication (master vs. mirror) is a
concern here.

My point is that with csup/cvsup, people need to be aware that there is
"CVS checkout"-like file also associated with things which lives in
/var/db/sup (for csup) and /usr/sup (for cvsup) which needs to be
removed if you pull files out from underneath it (e.g. rm -fr
/usr/src/*, etc.).

I could write another 5-6 paragraphs about this explaining the technical
aspects, comparing it to stock CVS (re: CVS/ directory during checkout)
and other things, but it's besides the point.

My point is that most people don't know of /var/db/sup and /usr/sup, and
when you make them aware of it, they go "...oh!  Maybe that's how my
local copy doesn't match with what's on the server!"

| Jeremy Chadwick                                jdc at |
| Parodius Networking              |
| UNIX Systems Administrator                   Mountain View, CA, US |
| Making life hard for others since 1977.               PGP 4BD6C0CB |

Want to link to this message? Use this URL: <>