From owner-freebsd-current Wed May 1 03:57:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA00404 for current-outgoing; Wed, 1 May 1996 03:57:45 -0700 (PDT) Received: from epprod.elsevier.co.uk (epprod.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA00385 for ; Wed, 1 May 1996 03:57:41 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id LAA22838 for ; Wed, 1 May 1996 11:56:52 +0100 Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Wed, 1 May 1996 11:56:30 +0100 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id LAA21427 for FreeBSD-current@FreeBSD.org; Wed, 1 May 1996 11:56:18 +0100 From: Paul Richards Message-Id: <199605011056.LAA21427@cadair.elsevier.co.uk> Subject: Re: cvs commit: ports/net/socks5 Makefile To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Wed, 1 May 1996 11:56:18 +0100 (BST) In-Reply-To: <199604301626.JAA13472@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Apr 30, 96 09:26:28 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I've redirected this to -current rather than committers. In reply to Rodney W. Grimes who said > > > Give me a few days to look into the other ports. > > Be careful in your judgement call. Perhaps if you could produce a list > of the files that end up in local/etc if all of the ports are installed > and label them with your judgement then pass that to the list for some > other judgements and rational. > This is a bit silly. It doesn't matter what ports install what where. What we need to do is evaluate what the possible requirements are and agree a directory structure that fits. A few things have come up recently. I think a bit of a step back is needed and a look at the whole NFS issue and it's impact on file layout is needed. The ports issue and the /etc issue have both shown up some warts in the current layout. I'm beginning to think that all of /usr should be shareable across a single architecture (not much point in a wider requirement since they're binaries in the main) with /usr/share containing architecture independant stuff, as it already should. /usr/local would then contain all shareable aspects of ports. I think perhaps we should have a /local directory for host specific files that are not part of the generic OS but are added by local admins. It would have a mirror of / i.e. /local/etc /local/var and so on. This makes me happy since the ports are still segregated from the main OS. The NFS folks are happy since they can export /usr and still have host specific config files that the binaries will pick up from whatever machine they are run on. I'm not won around on the /usr/arch/i386 idea yet since if /usr is architecture dependant then a /usr/arch/{i386,sparc,alpha} seems wrong somehow. Maybe /usr/config would be better since what will go there is architecture dependant config files such as /etc templates and syscons maps. They should all be shareable so it won't break the NFS model above. Any other possible uses I might not have thought of? -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155