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?

Reply via email to