Date: Tue, 29 Oct 2002 19:37:40 -0600 From: Stephen Hurd <shurd@sasktel.net> To: "."@babolo.ru Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Importance of using correct hierarchy for ports. Message-ID: <20021029193740.37fa5190.shurd@sasktel.net> In-Reply-To: <200210292256.g9TMurBV058826@aaz.links.ru> References: <20021029141151.5e803c78.shurd@sasktel.net> <200210292256.g9TMurBV058826@aaz.links.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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? What about data that's user changeable?
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. 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...
Perhaps a /var/PKG and /usr/local/PKG with symlinks into ${PREFIX}/bin, ${PREFIX}/sbin, and ${PREFIX}/libexec would be better...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021029193740.37fa5190.shurd>