From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com>
Date: Thu, 17 Aug 2006 15:57:13 +0100
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] dir tree Qs
In-Reply-To: <010b16eca074d6f280559da640c69e60@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: a2018192-ead1-11e9-9d60-3106f5b1d025

i've wondered in the past why this difference. on balance i prefer the way
it's done in $home, as the set of objtypes is open-ended, so it results in a somewhat
less cluttered home directory - it's easy to remove all binaries, for example,
without knowing the name of all objtypes (quick aside: i wish there was a constant
pattern that would match all c compiler intermediate object files...)

maybe the real reason why it's done differently
in / is that there's already a /bin, and it is assumed to contain only binaries
for the current objtype, which having (for instance) /bin/m68k would violate.

one could have had (for instance) /arch/bin/386, /arch/lib/386, ...
but would it have been worth it?