9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: don bailey <don.bailey@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] why not Lvx for Plan 9?
Date: Tue,  8 Jul 2008 18:01:15 -0600	[thread overview]
Message-ID: <4873FFCB.7040908@gmail.com> (raw)
In-Reply-To: <fc7f972d0807081532x66cbe95ex9bb9f0f0ca44959@mail.gmail.com>

> But Linux use symlinks. Is there a way to make symlinks
> on the Plan 9 filesystem and make them accessible with NFS?
>

The kernel probably doesn't care. Symlinks are just files
whose contents are another file's path. As long as the kernel
knows how to interpret it I'm sure it'd be fine. Look at the
inverse: Plan 9 on Linux simply sees a Linux symlink as what
ever the symlink points to. For example, in your 9vx tree
do: `ln -s sparc64 v9` and run 9vx.Linux.

D



  reply	other threads:[~2008-07-09  0:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 15:28 kokamoto
2008-07-08 15:58 ` David Leimbach
2008-07-08 16:04   ` erik quanstrom
2008-07-08 16:33     ` ron minnich
2008-07-08 16:47       ` Charles Forsyth
2008-07-09  4:33         ` LiteStar numnums
2008-07-08 17:46     ` Eric Van Hensbergen
2008-07-08 17:49       ` erik quanstrom
2008-07-08 18:38         ` a
2008-07-08 19:01           ` erik quanstrom
2008-07-08 19:46             ` a
2008-07-08 20:03         ` Eric Van Hensbergen
2008-07-08 20:15           ` William Josephson
2008-07-08 20:38             ` Eric Van Hensbergen
2008-07-08 21:25             ` ron minnich
2008-07-08 22:16               ` Steve Simon
2008-07-08 22:32                 ` David du Colombier
2008-07-09  0:01                   ` don bailey [this message]
2008-07-09  0:13                     ` ron minnich
2008-07-09  3:17                       ` Eric Van Hensbergen
2008-07-09  3:43                         ` ron minnich
2008-07-09  3:45                           ` erik quanstrom
2008-07-09  4:44                           ` David Leimbach
2008-07-08 18:50     ` David Leimbach
2008-07-08 17:19 ` Skip Tavakkolian
2008-07-10 12:58   ` matt
2008-07-10 13:47     ` Russ Cox
2008-07-10 14:03       ` erik quanstrom
     [not found]         ` <B94154D0-97B5-4FFF-A140-E47D95FC1307@flyingwalrus.net>
2008-07-12 15:59           ` erik quanstrom
2008-07-10 15:18       ` ron minnich
2008-07-10 16:33         ` Charles Forsyth
2008-07-10 16:36           ` ron minnich
2008-07-10 19:25             ` cinap_lenrek
2008-07-10 19:50               ` ron minnich
2008-07-11  9:10                 ` Kernel Panic
2008-07-11 16:12                   ` ron minnich
2008-07-10 14:01     ` erik quanstrom
2008-07-08 17:27 ` Russ Cox
2008-07-08 17:39   ` a

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=4873FFCB.7040908@gmail.com \
    --to=don.bailey@gmail.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).