9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] directly opening Plan9 devices
Date: Sat,  3 Jan 2009 23:21:20 +0100	[thread overview]
Message-ID: <8ccc8ba40901031421l430abd92je774b81862b1fb31@mail.gmail.com> (raw)
In-Reply-To: <1231019796.11463.212.camel@goose.sun.com>

Usign #X means doing a mount (you are attaching to the root
of the driver's tree).

However, for, drivers with letters |decp
you can always attach to them no matter if RFNOMNT was
used.

Probably it was considered too restrictive not doing so, but that's IMHO.

On Sat, Jan 3, 2009 at 10:56 PM, Roman V. Shaposhnik <rvs@sun.com> wrote:
> On Sat, 2009-01-03 at 16:46 -0500, erik quanstrom wrote:
>> > while replying to Nathaniel's post it dawned on
>> > me that something like this:
>> >     open("#c/cons", OWRITE|OCEXEC);
>> > completely breaks the paradigm of namespaces.
>> >
>> > IOW, if I wanted to construct a namespace with
>> > a specially crafted server offering /dev/cons,
>> > the above would easily break out of that jail.
>>
>> see RFNOMNT in rfork(2).
>
> Did you see the example I provided in the original
> email? "rfork m" is *exactly* RFNOMNT. And it doesn't
> seem to work for one simple reason: RFNOMNT doesn't
> restrict bind(2).
>
> So the question still stands.
>
> Thanks,
> Roman.
>
>
>



  parent reply	other threads:[~2009-01-03 22:21 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 [this message]
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
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=8ccc8ba40901031421l430abd92je774b81862b1fb31@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).