From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /lib/namespace vs /rc/bin/*rc
Date: Tue, 24 Apr 2007 18:01:03 -0400 [thread overview]
Message-ID: <7d07056781f74b48f508a2975885be3a@coraid.com> (raw)
In-Reply-To: <20070424214714.6904E1E8C26@holo.morphisms.net>
right. i'm not sure i see the advantage of hiding #t. surely
this isn't a performance argument?
- erik
On Tue Apr 24 17:47:12 EDT 2007, rsc@swtch.com wrote:
> > why are some devices bound in /lib/namespace while some others
> > are bound in /rc/bin/*rc? for example: '#$'.
>
> /lib/namespace gets run every time you
> create a fresh name space.
> termrc and cpurc are for initializing the machine.
>
> for example,
> '#t' should be in the termrc/cpurc so that the
> bootup programs can have it, but it doesn't
> need to be in everyone's.
>
> russ
next prev parent reply other threads:[~2007-04-24 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 21:36 erik quanstrom
2007-04-24 21:47 ` Russ Cox
2007-04-24 22:01 ` erik quanstrom [this message]
2007-04-24 22:08 ` Russ Cox
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=7d07056781f74b48f508a2975885be3a@coraid.com \
--to=quanstro@coraid.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).