9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rc scripts in /386/bin/aux
Date: Tue,  9 Aug 2011 15:59:55 -0700	[thread overview]
Message-ID: <CAL4LZyiPEz1zERjceDWuwq2vzHUkpykD7=sA5-z2-YFB_Jo1zg@mail.gmail.com> (raw)
In-Reply-To: <CAB8pEY4=O=dw0J+CYAe8CMkE0Ci2E1yP_XxTGtzHLBrjWL7f2Q@mail.gmail.com>

On Tue, Aug 9, 2011 at 3:54 PM, Jacob Todd <jaketodd422@gmail.com> wrote:
>
> On Aug 9, 2011 6:30 PM, "erik quanstrom" <quanstro@labs.coraid.com> wrote:
>>
>> On Tue Aug  9 18:26:01 EDT 2011, lyndon@orthanc.ca wrote:
>> the tradition has been to copy scripts into /$cputype/bin/$somesubdir
>> for every arch.
>>
> I've always been under the impression they went in /rc/bin/.

Try creating /rc/bin/aux and sticking a file in there--can you see it
if you do 'ls /bin/aux'? Not unless you do a 'bind -a /rc/bin/aux
/bin/aux'. It's an artifact of the fact that we don't have recursive
unions under Plan 9--we can either specifically bind every
subdirectory of /rc/bin into /bin, or we can just stick the scripts
into /386/bin/subdir/

John



      reply	other threads:[~2011-08-09 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 22:24 Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-09 22:29 ` erik quanstrom
2011-08-09 22:48   ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-10  0:06     ` erik quanstrom
2011-08-10  0:07       ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-10  0:24         ` andrey mirtchovski
2011-08-10  0:28           ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-09 22:54   ` Jacob Todd
2011-08-09 22:59     ` John Floren [this message]

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='CAL4LZyiPEz1zERjceDWuwq2vzHUkpykD7=sA5-z2-YFB_Jo1zg@mail.gmail.com' \
    --to=john@jfloren.net \
    --cc=9fans@9fans.net \
    /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).