From owner-freebsd-hackers Sun Dec 10 13:35:00 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17711 for hackers-outgoing; Sun, 10 Dec 1995 13:35:00 -0800 (PST) Received: from snake.hut.fi (root@snake.hut.fi [193.167.6.99]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA17692 for ; Sun, 10 Dec 1995 13:34:54 -0800 (PST) Received: from lk-hp-5.hut.fi (lk-hp-5.hut.fi [130.233.244.36]) by snake.hut.fi (8.7.1/8.7.1) with ESMTP id XAA06752; Sun, 10 Dec 1995 23:34:50 +0200 (EET) Received: (vode@localhost) by lk-hp-5.hut.fi (8.6.12/8.6.7) id XAA08928; Sun, 10 Dec 1995 23:34:47 +0200 Date: Sun, 10 Dec 1995 23:34:47 +0200 Message-Id: <199512102134.XAA08928@lk-hp-5.hut.fi> From: Kai Vorma To: rkw@dataplex.net (Richard Wackerbarth) cc: hackers@freefall.freebsd.org In-reply-to: rkw@dataplex.net's message of 10 Dec 1995 23:03:15 +0200 Subject: Re: Sup's Freefall-centric tree conventions Reply-to: Kai.Vorma@hut.fi Sender: owner-hackers@FreeBSD.ORG Precedence: bulk Richard Wackerbarth writes: > There will be multiple servers. Each of them should (I would say MUST) > have the same structure. Joe User should be able to reference anyone of I'm mirroring sup trees on nic.funet.fi. It's a big ftp/www/etc. server with strict rules for administrators. I really cannot create new file trees outside the well defined places, so the above is impossible. The sup trees are /pub/mirrors/sup.freebsd.org/current stable ports cvs (ports and cvs aren't ready yet - I'm currently supping them from freefall, but it takes some time) If Joe User wants to use multiple sup servers he can use multiple supfiles (one for freefall, one for nic etc.). I know this isn't ideal but it is the reality.. Besides you don't want switch servers often, because sup will update (not receive fortunately) every file after switching servers. I think this happens because inode ctimes are different and you cannot sync them. One way to solve your problem is to create a front-end for sup which creates the actual supfile from a user friendly configuration file and then fires sup client. I can make a perl-script that does this if there is a need for it. ..vode