From owner-freebsd-hubs Mon Sep 2 11:05:07 1996 Return-Path: owner-hubs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04656 for hubs-outgoing; Mon, 2 Sep 1996 11:05:07 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04635; Mon, 2 Sep 1996 11:05:03 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id LAA04538; Mon, 2 Sep 1996 11:04:57 -0700 (PDT) Message-Id: <199609021804.LAA04538@austin.polstra.com> To: rkw@dataplex.net (Richard Wackerbarth) cc: hubs@freebsd.org, hackers@freebsd.org Subject: Re: cvsup question, src/tools not updated, make release trouble In-reply-to: Your message of "Mon, 02 Sep 1996 12:47:28 CDT." Date: Mon, 02 Sep 1996 11:04:57 -0700 From: John Polstra Sender: owner-hubs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >And the sup control files are under > >/home/sup, which we're more-or-less stuck with because it's hard-coded > >into everybody's supfiles. > > But if we establish a new set of sup-files, who cares what "is in everybody's" My point is that there are thousands of FreeBSD supfiles out there in the world, and each line of every one contains "hostbase=/home". That means that every FreeBSD sup/CVSup mirror _must_ have a set of valid sup control files under "/home/sup". The only alternative would be to ask every existing sup user to change his supfiles. The dust from that might settle within a year or so, if we were lucky. > The standard files will still apply only to someone who gets > "everything". Otherwise, the update to the sup-files will destroy > local modifications. I don't understand what you mean. Aren't we talking about keeping the sup _mirrors_ up-to-date? It's only the mirrors who would be supping the sup control files. The mirrors should not have any local modifications. If they do, then they're not really mirrors. Maybe we're using different terminology? When I say "supfile", I mean the file that a client feeds to the "sup" or "cvsup" program. When I say "sup control files", I mean the set of files (under /home/sup for FreeBSD) that the server "supfilesrv" or "cvsupd" looks at. > > I'd propose that we standardize on /home/current or > >/home/FreeBSD-current, and likewise for -stable. > > >Of course, those could be symlinks to whereever the mirror administrator > >wanted to put the actual files. > > The argument AGAINST that standard is that the mirrors have to have the > files in /pub anyway. > > The /home directory is usually under more administrative restriction than > is the /pub space. I bet there's not one official FreeBSD sup mirror that's maintained by a person who does not have root privileges. > Symlinks can go either way. No, they cannot. The FTP daemon runs chrooted to ~ftp. It cannot follow symlinks that lead out of there. Any symlinks would have to point into the ~ftp tree, not out of it. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth