From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Tvx update
Date: Fri, 28 May 2010 07:59:32 -0400 [thread overview]
Message-ID: <5df6348b8b8046c072ca79f196e420b2@kw.quanstro.net> (raw)
In-Reply-To: <1362EB69-4238-4794-A949-DB9BC5971E7F@fastmail.fm>
> On 27 May 2010, at 21:16, Bakul Shah wrote:
>
> > If BSD had
> > implemented ".." correctly (i.e. walk back up one level in
> > the given path), symlinks would have been more useful and
> > less surprising.
>
> This "correct" implementation of symlinks has never seemed right to
> me. Linux / Bash used to do it the "wrong" way as recently as 2001 if
> not more recently. I was much more comfortable with the "wrong" way,
> with symlinks just being a portal to another place entirely, and I
> wish I could pinpoint why. Having the path "faked" after following a
> symlink just feels badly wrong, and I wish I could put a semantic
> reason on it.
would you deconstruct bind/mount points as well?
recursively? that way lies vms/windows.
- erik
next prev parent reply other threads:[~2010-05-28 11:59 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
2010-05-28 11:51 ` Ethan Grammatikidis
2010-05-28 11:59 ` erik quanstrom [this message]
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=5df6348b8b8046c072ca79f196e420b2@kw.quanstro.net \
--to=quanstro@quanstro.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).