From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] dir tree Qs
Date: Thu, 17 Aug 2006 15:57:13 +0100 [thread overview]
Message-ID: <8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com> (raw)
In-Reply-To: <010b16eca074d6f280559da640c69e60@quanstro.net>
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?
next prev parent reply other threads:[~2006-08-17 14:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 13:15 cej
2006-08-17 13:53 ` erik quanstrom
2006-08-17 14:08 ` andrey mirtchovski
2006-08-17 14:33 ` erik quanstrom
2006-08-17 14:57 ` rog [this message]
2006-08-17 16:05 ` jmk
2006-08-17 16:08 ` John Floren
2006-08-17 16:10 ` erik quanstrom
2006-08-17 17:05 ` csant
2006-08-17 17:08 ` andrey mirtchovski
2006-08-17 17:10 ` rog
2006-08-17 17:22 ` Ronald G Minnich
2006-08-17 17:28 ` erik quanstrom
2006-08-17 17:38 ` csant
2006-08-17 17:41 ` erik quanstrom
2006-08-17 17:44 ` rog
2006-08-17 18:56 ` Iruatã Souza
2006-08-17 19:29 ` Charles Forsyth
2006-08-17 19:42 ` Iruatã Souza
2006-08-17 20:07 ` rog
2006-08-17 17:34 ` Re: " Skip Tavakkolian
2006-08-17 17:39 ` csant
2006-08-17 17:42 ` Skip Tavakkolian
2006-08-17 17:44 ` Skip Tavakkolian
2006-08-17 17:45 ` andrey mirtchovski
2006-08-17 18:17 ` Charles Forsyth
2006-08-17 18:40 ` Russ Cox
2006-08-17 20:54 ` csant
2006-08-29 4:27 ` cej
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).