From: Sergey Zhilkin <szhilkin@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] linux mount -t 9p permissions problem
Date: Wed, 3 Aug 2016 16:19:43 +0300 [thread overview]
Message-ID: <CAOFTvPKKDTSXxnpWtLW-3dSTUEbG=j9VdDkD=VLW0rmtvO4MDQ@mail.gmail.com> (raw)
In-Reply-To: <CAPv5z_1CdSkFSM9wAeW+W==U6HBSTiozioTiH27R3dkcbyG_BQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Great ! :)
2016-07-29 15:40 GMT+03:00 Costin Chirvasuta <costinc@gmail.com>:
> I love 9P! It was the only way I could export a FUSE filesystem over
> the network and it works flawlessly!
>
> On Fri, Jul 29, 2016 at 12:31 PM, Costin Chirvasuta <costinc@gmail.com>
> wrote:
> > Well, this was because the exported directory on FreeBSD has
> > permission 0. It is the mountpoint of torrentfs
> > (github.com/anacrolix/torrent).
> >
> > On Fri, Jul 29, 2016 at 2:54 AM, Costin Chirvasuta <costinc@gmail.com>
> wrote:
> >> I have ufs (https://github.com/rminnich/go9p/) running on a FreeBSD
> >> box and I'm trying to mount it on linux but the directory has
> >> permission 0:
> >>
> >> ~$ 9mount -in 'tcp!fs!5640' fs
> >> mount -t 9p -o
> tcp,trans=tcp,name=ctn,uname=ctn,noextend,nodev,uid=1000,gid=1000,dfltuid=1000,dfltgid=1000,port=5640
> >> 192.168.0.3 fs
> >> ~$ 9mount -i 'tcp!fs!5640' fs
> >> ~$ ls fs
> >> ls: cannot open directory fs: Permission denied
> >> ~$ ls -ld fs
> >> d--------- 1 ctn ctn 0 Jul 26 23:52 fs
> >>
> >> Any idea how I can fix this? I tried adding umask=0002 as a mount
> >> option but it doesn't seem to work.
>
>
--
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey
[-- Attachment #2: Type: text/html, Size: 2158 bytes --]
prev parent reply other threads:[~2016-08-03 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 23:54 Costin Chirvasuta
2016-07-29 9:31 ` Costin Chirvasuta
2016-07-29 12:40 ` Costin Chirvasuta
2016-08-03 13:19 ` Sergey Zhilkin [this message]
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='CAOFTvPKKDTSXxnpWtLW-3dSTUEbG=j9VdDkD=VLW0rmtvO4MDQ@mail.gmail.com' \
--to=szhilkin@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).