From owner-freebsd-arch@FreeBSD.ORG Fri May 21 14:47:36 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EB0116A4CE for ; Fri, 21 May 2004 14:47:36 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23DC343D3F for ; Fri, 21 May 2004 14:47:36 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i4LLlYs0002618; Fri, 21 May 2004 14:47:34 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i4LLlYQx002616; Fri, 21 May 2004 14:47:34 -0700 Date: Fri, 21 May 2004 14:47:34 -0700 From: Brooks Davis To: cjclark@alum.mit.edu Message-ID: <20040521214733.GA1549@Odin.AC.HMC.Edu> References: <20040521193605.GA8246@blossom.cjclark.org> <20040521194231.GA22816@Odin.AC.HMC.Edu> <20040521213944.GB8246@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <20040521213944.GB8246@blossom.cjclark.org> User-Agent: Mutt/1.5.4i cc: freebsd-arch@freebsd.org Subject: Re: Move /usr/sup to /var/db/sup? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2004 21:47:36 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 21, 2004 at 02:39:44PM -0700, Crist J. Clark wrote: > On Fri, May 21, 2004 at 12:42:32PM -0700, Brooks Davis wrote: > > On Fri, May 21, 2004 at 12:36:05PM -0700, Crist J. Clark wrote: > > > Just a minor thing, but I would think[0] most people would agree that > > > /var/db/sup is a much more logical place for the CVSup "base" directo= ry > > > than /usr/sup. Yes, it doesn't take up much space on /usr, but for > > > those who don't want to write to /usr[1] too much or mount /usr read- > > > only, it's an irritant. > > >=20 > > > Of course, there is one big reason not to change it, because it would > > > be a change. > > >=20 > > > Personally, I don't think it will be disruptive to make changes to the > > > example files in /usr/share/examples/cvsup. People who already have > > > /usr/sup populated are using their own localized versions of these > > > files, so the change won't affect them (not that losing the "sup" > > > directory is that big of a deal). A person starting with a copy of > > > one of the examples is probably starting a fresh CVSup and will be > > > creating a new sup dir anyway. > >=20 > > This seems reasionable. If you're going to do it, I suggest adding > > /var/db/sup to the appropriate mtree file so it always exists. That > > way people who blindly copy their supfiles to /usr/sup will still get > > something that works and their finger memory won't be broken. >=20 > Hmmm... /usr/sup is not in BSD.mtree.usr. I believe cvsup(1) creates > it when it does not exist. Are you saying we should add it to > BSD.mtree.var even though we don't create /usr/sup? Or are you > saying to create /var/db/sup and make a symlink in /usr to it? Hmm, for some reason I've always copied the example supfiles to /usr/sup before editing them. For some reason I'd assumed this was something I read in the documentation in the distant past, but I can't find any evidence of such a recommendation so I may just made that convention up. Given that, I don't think it's necessicary to create /var/db/sup, but it might be a nice idea anyway. Another directory in /var/db certaintly wouldn't hurt anything. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD4DBQFArnj1XY6L6fI4GtQRAq3FAJjixUcHH79yxhJh6yApO6oDR+0jAKCiCJMu Cs3rrQoZ4UQPnmS8AxRIHA== =adDF -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--