From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] dir tree Qs
Date: Thu, 17 Aug 2006 09:33:28 -0500 [thread overview]
Message-ID: <010b16eca074d6f280559da640c69e60@quanstro.net> (raw)
In-Reply-To: <14ec7b180608170708t17e9b47bi35fa28f7dfa20a18@mail.gmail.com>
why would one never keep a library in one's home directory? keeping the
structure the same would make it easier to bind $home/$cputype
before/after /$cputype.
$0.02
- erik
On Thu Aug 17 09:08:52 CDT 2006, mirtchovski@gmail.com wrote:
> /386 contains much more than just binaries, while $home/bin/386
> contains only that: binaries.
>
> i think the rationale was that having a directory for each
> architecture back when 386 wasn't the dominant one would clutter
> $home. we rarely spend any time in / after all. besides, Plan 9
> shouldn't expose the architecture to the user right at the front line:
> what the current arch is was not meant to be something we ought to
> care about.
>
> i could be wrong, of course.
next prev parent reply other threads:[~2006-08-17 14:33 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 [this message]
2006-08-17 14:57 ` rog
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=010b16eca074d6f280559da640c69e60@quanstro.net \
--to=quanstro@quanstro.net \
--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).