From: Stuart Morrow <morrow.stuart@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] What's up with $home? And a security question.
Date: Sun, 24 Feb 2013 04:19:09 +0000 [thread overview]
Message-ID: <CABB-WO-NUky4n68LDqkdU+BCfjU+KVWLCcTVDKbQ=ZA__G=BnA@mail.gmail.com> (raw)
In-Reply-To: <CAK4xykXXBwzOJa7=ZU5tbHpaTxx0TSoYbHfQZ36mowP2WykV0A@mail.gmail.com>
I know that about /tmp. I know devenv too. By the way, have you ever
noticed that the *env libc functions only allow accesses to env files
with names of length 100 - strlen("/env/") - sizeof '\0', while rc
allows names of up to 256 characters? I'm not too concerned about
that one, just saying it's inconsistent. Rio is hardcoded for a
maximum of 100 windows and I don't think anyone's ever had a problem.
A more realistic one is: rc doesn't go out to /env every time a
variable is accessed. If they're changed underfoot the only way rc
can see them is if you start up a new rc (like the rc under EXAMPLES
in pipefile(1))
What's the reason for this, just speed? It seems weird to me that a
Plan 9 program would do something "intelligent" like that (and
therefore less predictable, like ls's that do isatty on /fd/1).
next prev parent reply other threads:[~2013-02-24 4:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 2:49 Stuart Morrow
2013-02-24 3:05 ` andrey mirtchovski
2013-02-24 3:43 ` Stuart Morrow
2013-02-24 3:53 ` andrey mirtchovski
2013-02-24 4:19 ` Stuart Morrow [this message]
2013-02-24 4:45 ` Federico G. Benavento
2013-02-24 5:06 ` Stuart Morrow
2013-02-24 5:10 ` andrey mirtchovski
2013-02-24 5:20 ` Stuart Morrow
2013-02-24 6:24 ` Bruce Ellis
2013-02-24 7:05 ` Matthew Veety
2013-02-24 7:14 ` Bruce Ellis
2013-02-24 9:31 ` steve
2013-02-24 4:33 ` cinap_lenrek
2013-02-24 4:27 Erik Quanstrom
2013-02-24 4:53 ` Stuart Morrow
[not found] <CABB-WO9gegFWirXjQhAK0g9vNHn=W2+vwC+bTvRcRDw7xs096g@mail.gmail.c>
2013-02-24 13:29 ` a
2013-02-25 8:49 ` Bruce Ellis
2013-02-25 11:56 ` Charles Forsyth
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='CABB-WO-NUky4n68LDqkdU+BCfjU+KVWLCcTVDKbQ=ZA__G=BnA@mail.gmail.com' \
--to=morrow.stuart@googlemail.com \
--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).