From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <5884D992-3267-4D6F-AAEA-F290B1420F3A@fastmail.fm> From: Ethan Grammatikidis To: ebo@sandien.com, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 15 Apr 2010 10:22:22 +0100 References: <17291D00-8580-474A-B398-8DCE626A9042@fastmail.fm> , , Subject: Re: [9fans] 9vx patch to read environment var PLAN9 Topicbox-Message-UUID: 01a4461c-ead6-11e9-9d60-3106f5b1d025 On 15 Apr 2010, at 08:39, EBo wrote: > >> Define reasonable. For me, that=92s just 1 single spot. But it seems >> the Linux people are very insistent on Freedom meaning do what you >> want, even if it's against the build suggestions. >> I say stick to one hardcoded path, and make everyone else stop doing >> it their own way, and stick to one simple, consistent solution. > > Two possible guides are: > > Linux Standard Base = > > > and > > Filesystem Hierarchy Standard I deliberately avoided referring to these two... _interesting_ =20 documents. I studied the FHS at some length some years ago, not the =20 latest version but the one before. As I understood it, it provides no =20= possible place for a 9vx tree, for a plan9port tree, for a GNUStep =20 tree, in short, for anything which does not conform precisely to the =20 same layout of directories it specifies for /usr. The requirements =20 for /opt at least have been softened in the latest version, so that a =20= distro could 'legitimately' install 9vx or p9p under /opt, but I doubt =20= it could be put anywhere else. I won't comment on the LSB except to say that between the way Linux =20 has been going lately and the almost perversely obsolete document the =20= LSB was the last time I looked at it, I don't really want to know =20 anything about it, least of all if it's been brought up to date. I deliberately used the phrase "commonly used" in my earlier email =20 because at the end of the day that's the only useful guide. In any =20 case these standards are only made by taking common use and =20 constraining it within (sometimes perverse) reasoning. --=20 Simplicity does not precede complexity, but follows it. -- Alan Perlis