9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Oleg <lego12239@yandex.ru>,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] linux 9p: uid & gid
Date: Thu, 20 Jun 2019 17:34:03 +0100	[thread overview]
Message-ID: <CAOw7k5hn5BEp9maxK-wjgYSJbBFy+9megiCjhiNjUzYGHrV8Ow@mail.gmail.com> (raw)
In-Reply-To: <20190620150435.GA31903@legohost>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

4294967294 probably started off as -2, which some systems used for user
"nobody"

On Thu, Jun 20, 2019 at 4:04 PM Oleg <lego12239@yandex.ru> wrote:

> Hi, all.
>
> I wrote a 9p fs with help of libixp and after mounting i see strange uid
> and
> gid numbers for files:
>
> ~# mount -t 9p -o trans=unix,noextend q t
> ~# ls -l t
> -rw-rw-rw- 1 4294967294 4294967294 1 Jan  1  1970 conf
> -rw-rw-rw- 1 4294967294 4294967294 1 Jan  1  1970 data
> -rw-rw-rw- 1 4294967294 4294967294 1 Jan  1  1970 stat
>
> If i do mount with dfltuid and dfltgid, i get normal values:
>
> ~# mount -t 9p -o
> trans=unix,noextend,trans=unix,noextend,dfltuid=0,dfltgid=0 q t
> ~# ls -l t
> -rw-rw-rw- 1 root root 1 Jan  1  1970 conf
> -rw-rw-rw- 1 root root 1 Jan  1  1970 data
> -rw-rw-rw- 1 root root 1 Jan  1  1970 stat
>
> But in any case chown call to these files sends empty uid and gid strings
> in
> wstat T-message.
>
> Is there any way to make uid & gid works as expected?
>
> Thanks.
>
> --
> Олег Неманов (Oleg Nemanov)
>
>

[-- Attachment #2: Type: text/html, Size: 1459 bytes --]

  reply	other threads:[~2019-06-20 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 15:04 Oleg
2019-06-20 16:34 ` Charles Forsyth [this message]
2019-06-21  8:34   ` Oleg
2019-06-21  9:28     ` [9fans] [OBORONA-SPAM] " lego12239

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=CAOw7k5hn5BEp9maxK-wjgYSJbBFy+9megiCjhiNjUzYGHrV8Ow@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    --cc=lego12239@yandex.ru \
    /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).