From owner-freebsd-ports Tue Oct 29 18: 0: 0 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0229C37B404 for ; Tue, 29 Oct 2002 17:59:59 -0800 (PST) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B55E43E77 for ; Tue, 29 Oct 2002 17:59:58 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.6/8.12.6) with ESMTP id g9U20cDh063170; Wed, 30 Oct 2002 05:00:38 +0300 (MSK) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.6/8.12.6/Submit) id g9U20UEJ063166; Wed, 30 Oct 2002 05:00:30 +0300 (MSK) Message-Id: <200210300200.g9U20UEJ063166@aaz.links.ru> Subject: Re: Importance of using correct hierarchy for ports. X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20021029193740.37fa5190.shurd@sasktel.net> To: Stephen Hurd Date: Wed, 30 Oct 2002 05:00:30 +0300 (MSK) From: "."@babolo.ru Cc: freebsd-ports@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > If this BBS package can't execute > > in read only mounted directory > > (try to store data in the same directory > > as executable, libraryes or configs), > > then it must be repaired to use /var for data > > Which reminds me, what is the proper use of /var for ports? > Should changeable data go in /var/PACKAGE? Probably yes > What about data that's user changeable? $HOME? > Really, I suppose I should plow through the ports > and see where for example chrooted ftp servers like > their data and where databases keep theirs for some > good examples. Usually ports keep data in $PREFIX, but real data path can be configured before service start so that sysadmin decide where to place data. > What makes this even more difficult is that all of the files except for a single text file and the binaries themselves are used in such a way that the BBS can be easily distributed across multiple platforms running multiple OSs. > > This really is a relatively large program, containing an FTP server, two HTTP servers, a Gopher server, an NNTP server, a POP3 server, an SMTP server, a finger server, and a telnet server in addition to the standard BBS (Classic Dial-up style) interface. Splitting all the files up into the generally accepted "correct" locations (/var/backups, /var/mail, /var/msgs, /var/run, /var/spool/*, /usr/local/bin, /usr/local/sbin, /usr/local/etc, etc) is a non-trivial task... one I'm not overly sure is worth it. > > It also uses binary configuration files, which I'm not sure are suitable for ${PREFIX}/etc and if not would go in /var yet again... There is terrible layout port - mail/qmail It reminds me one more restriction - it is possible, that /var is mounted with noexec option :-) > Perhaps a /var/PKG and /usr/local/PKG IMHO yes > with symlinks into ${PREFIX}/bin, ${PREFIX}/sbin, and ${PREFIX}/libexec would be better... What is purpose of links in ${PREFIX}/libexec? There no */libexec in PATH Does shared libraryes used? -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message