From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Tvx update
Date: Fri, 28 May 2010 12:04:20 +0100 [thread overview]
Message-ID: <7D233404-70D3-4A89-B311-EADB4503D43D@fastmail.fm> (raw)
In-Reply-To: <32d9c93c2ea01194aa50b1b2546ec06d@kw.quanstro.net>
On 28 May 2010, at 11:34, erik quanstrom wrote:
>> Anyway, what really stuck in my mind from Korn's post was his
>> characterization of symbolic links as a "non local goto", and I got
>> the impression from the "paper" that he was not enthusiastic about
>> the
>> idea in general, much less the implementations.
>
> and, the whole idea breaks down unless there is a single,
> global namepace.
Oh, good point. I remember having trouble with symlinks & chroots. I
had several chroots in linux with scripts to set them up, & even
symlinks from outside into the chroot (e.g. to make 32-bit home easily
accessible from 64-bit home) were enough of a nuisance that I ended up
substituting binds.
OTOH I also have a vague memory of doing something clever with a
symlink & a chroot, but I can't remember what now.
>
> - erik
>
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-05-28 11:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 18:46 EBo
2010-05-25 19:34 ` Nick LaForge
2010-05-25 19:57 ` EBo
2010-05-26 18:02 ` Nick LaForge
2010-05-26 18:17 ` erik quanstrom
2010-05-26 20:35 ` EBo
2010-05-26 20:42 ` EBo
2010-05-26 23:31 ` Nick LaForge
2010-05-26 23:53 ` erik quanstrom
2010-05-26 23:58 ` ron minnich
2010-05-27 1:50 ` Nick LaForge
2010-05-27 2:51 ` ron minnich
2010-05-27 4:19 ` EBo
2010-05-27 5:03 ` Nick LaForge
2010-05-27 5:18 ` EBo
2010-05-27 7:17 ` EBo
2010-05-27 14:30 ` hiro
2010-05-27 18:14 ` Jorden M
2010-05-27 19:26 ` EBo
2010-05-28 3:42 ` ron minnich
2010-05-27 5:48 ` ron minnich
2010-05-27 7:02 ` EBo
2010-05-27 14:39 ` ron minnich
[not found] ` <5147DCD3-BD95-4D54-96B7-30DCA4D113DA@mit.edu>
2010-05-27 19:59 ` Chad Brown
2010-05-27 20:16 ` Bakul Shah
2010-05-28 3:41 ` ron minnich
2010-05-28 10:34 ` erik quanstrom
2010-05-28 11:04 ` Ethan Grammatikidis [this message]
2010-05-28 11:51 ` Ethan Grammatikidis
2010-05-28 11:59 ` erik quanstrom
2010-05-28 12:19 ` Ethan Grammatikidis
2010-05-28 13:20 ` erik quanstrom
2010-05-28 15:09 ` Steve Simon
2010-05-28 16:21 ` Ethan Grammatikidis
2010-05-28 16:26 ` erik quanstrom
2010-05-28 16:38 ` Ethan Grammatikidis
2010-05-28 16:04 ` Bakul Shah
2010-05-28 16:13 ` erik quanstrom
2010-05-28 16:53 ` Ethan Grammatikidis
2010-05-27 20:20 ` EBo
2010-05-27 4:54 ` EBo
2010-05-27 6:57 ` ron minnich
2010-05-27 7:07 ` EBo
2010-05-27 14:38 ` ron minnich
2010-05-27 19:11 ` EBo
2010-05-28 3:44 ` ron minnich
2010-05-28 10:24 ` erik quanstrom
2010-06-13 8:43 [9fans] tvx update EBo
2010-08-19 2:39 ` Ryousei Takano
2010-08-19 3:02 ` EBo
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=7D233404-70D3-4A89-B311-EADB4503D43D@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).