From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 24 Feb 2013 04:19:09 +0000 Message-ID: From: Stuart Morrow To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] What's up with $home? And a security question. Topicbox-Message-UUID: 1d90d24e-ead8-11e9-9d60-3106f5b1d025 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).