9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] directly opening Plan9 devices
Date: Sun,  4 Jan 2009 16:52:33 -0800	[thread overview]
Message-ID: <1231116753.11463.295.camel@goose.sun.com> (raw)
In-Reply-To: <69a918481d4c7236d6e30d2bf8093221@quanstro.net>

On Sun, 2009-01-04 at 00:27 -0500, erik quanstrom wrote:
> > > Usign #X means doing a mount (you are attaching to the root
> > > of the driver's tree).
> >
> > You're right, of course. But it feels like a very special mount
> > if one can refer to files served by the drivers directly through:
> > '#X/bla-bla'.
>
> s/driver/file server/
> there doesn't need to be any hardware involved.

Well, that's part of the problem. I can't refer to things served
by the actual 9P servers via something like /srv/sources/plan9.
/srv/sources is a channel and as such it needs to be explicitly
mounted before I can access what is being served by it. If all
I could do with #X is to bind/mount it -- it would make a much
more coherent model. From my point of view, of course.

> could you explain why you think this is special?

I have nothing (major) against bind/mount interpreting names that
start with # in a special way. I feel quite confused when namec()
does that interpretation for a variety of system calls. Things
like
   term% cd '#|'
   term% pwd
   #|
just don't seem right.

But let me ask you this in return: do you feel that constraining #X to
bind/mount only would, actually, be worse compared to the behavior
we have today?

Thanks,
Roman.




  parent reply	other threads:[~2009-01-05  0:52 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 21:44 Roman V. Shaposhnik
2009-01-03 21:46 ` erik quanstrom
2009-01-03 21:56   ` Roman V. Shaposhnik
2009-01-03 22:03     ` erik quanstrom
2009-01-03 22:40       ` Roman V. Shaposhnik
2009-01-03 22:46         ` Francisco J Ballesteros
2009-01-03 22:56           ` erik quanstrom
2009-01-04  5:00             ` Roman V. Shaposhnik
2009-01-04  5:40               ` erik quanstrom
2009-01-04  4:58           ` Roman V. Shaposhnik
2009-01-03 22:57         ` erik quanstrom
2009-01-03 23:15           ` Russ Cox
2009-01-03 23:17             ` erik quanstrom
2009-01-04  5:07             ` Roman V. Shaposhnik
2009-01-04  5:05           ` Roman V. Shaposhnik
2009-01-03 22:21     ` Francisco J Ballesteros
2009-01-03 22:40       ` erik quanstrom
2009-01-04  5:12       ` Roman V. Shaposhnik
2009-01-04  5:27         ` erik quanstrom
2009-01-04  5:39           ` lucio
2009-01-04  5:42             ` erik quanstrom
2009-01-05  0:52           ` Roman V. Shaposhnik [this message]
2009-01-05  6:21             ` Roman Zhukov
2009-01-05 11:00             ` Charles Forsyth
2009-01-06  5:02               ` Roman Shaposhnik
2009-01-06 14:17                 ` erik quanstrom
2009-01-07 16:55                   ` ron minnich
2009-01-07 17:16                     ` erik quanstrom
2009-01-08  5:13                       ` ron minnich
2009-01-08 13:37                         ` erik quanstrom
2009-01-08 14:03                           ` Charles Forsyth
2009-01-08 15:36                           ` ron minnich
2009-01-08 15:44                             ` erik quanstrom
2009-01-08 17:34                             ` Roman V. Shaposhnik
2009-01-08 17:35                             ` Charles Forsyth
2009-01-08  7:45                     ` Dave Eckhardt
2009-01-08 17:43                     ` Roman V. Shaposhnik
2009-01-08 23:30                   ` Roman V. Shaposhnik
2009-01-04  7:01         ` Russ Cox
2009-01-04 11:41           ` lucio
2009-01-04 13:01             ` Uriel
2009-01-04 13:16               ` lucio
2009-01-05  0:41           ` Roman V. Shaposhnik

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=1231116753.11463.295.camel@goose.sun.com \
    --to=rvs@sun.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).