9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] ape/psh can't exec in 9vx
Date: Wed, 24 Sep 2008 20:31:00 +0200	[thread overview]
Message-ID: <5d375e920809241131v46962f15j5e9b4c7837238c29@mail.gmail.com> (raw)
In-Reply-To: <b859d44d0d45efc8b0511766dd642a96@quintile.net>

Or we could use extended attributes to store the plan9-related bits.

I'm joking, I'm joking! I just couldn't resist mentioning such wicked idea ;))

Probably having fossil become part of the default setup would be the best.

Peace

uriel


On Wed, Sep 24, 2008 at 5:56 PM, Steve Simon <steve@quintile.net> wrote:
> I may be wrong but I assumed the problem with replica was that unless you run 9vx
> setuid to root and trust the permssion checking in the host interface there is
> no way for wstat to change the username of a file to anything else that the user
> who started 9vx.
>
> aditionally there may b e no relevant host user to become the owner of the file,
> e.g. bootes or glenda.
>
> If it is just limitations of the host filesystem emulating a 9p server then replica
> should work fine when it uses a seperate fossil disk partition rather than a host
> filesystem.
>
> If I am right you could always add a file which contains extra metadata not stored
> in the host filesystem (e.g. the append bit, the 't' bit (don't venti) and of
> course owner and group - overriding the owner and group from the native filesystem.
>
> wether this is worth the effort... thats another question.
>
> alternatively the 9vx host filesystem interface or replica itself could be hacked to
> be less strict when wstats()ing.
>
> then again I may have the wrong end of the stick completely.
>
> -Steve



  parent reply	other threads:[~2008-09-24 18:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  5:17 Gary V. Vaughan
2008-09-24  5:52 ` andrey mirtchovski
2008-09-24  7:17   ` Gary V. Vaughan
2008-09-24 14:15     ` andrey mirtchovski
2008-09-24 15:56       ` Steve Simon
2008-09-24 16:09         ` roger peppe
2008-09-24 18:32           ` Uriel
2008-09-24 18:31         ` Uriel [this message]
2009-10-19  1:44 Dimitry Golubovsky
2009-10-19 15:27 ` Russ Cox
2009-10-19 16:47 ` Dmitry Golubovsky
2009-10-20  9:14 ` Dmitry Golubovsky

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=5d375e920809241131v46962f15j5e9b4c7837238c29@mail.gmail.com \
    --to=uriel99@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).