9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] remedial sources auth, connect, and mount in plan9port
Date: Thu,  1 Oct 2009 10:34:05 -0500	[thread overview]
Message-ID: <d50d7d460910010834r40c926barbc3dedd5828f3bd1@mail.gmail.com> (raw)
In-Reply-To: <140e7ec30910010331o5dbe12c5lac6ae914a8ebe696@mail.gmail.com>

On Thu, Oct 1, 2009 at 05:31, sqweek <sqweek@gmail.com> wrote:
> 2009/10/1 Ethan Grammatikidis <eekee57@fastmail.fm>:
>> On Thu, 1 Oct 2009 04:50:40 -0500
>> Jason Catena <jason.catena@gmail.com> wrote:
>>> $ ls -lad
>>> drwxrwxr-x 1 4294967294 4294967294 0 2009-09-30 23:11 .
>>
>> You have numbers for user and group names there.  Un*x likes the
>> numbers, but plan 9 wants strings.
>
>  Yeah, I suspect at this point the linux kernel is denying the
> operation based on its idea of permissions. there's a v9fs mount
> option you might try... I forget what it is exactly but 9mount -i does
> it :)
>  Try:
>
> 9mount -i 'unix!/tmp/ns.jdc.192.168.1.101:0/sources.cs.bell-labs.com' /n/sources

This does mount, and let me write into my directory, thanks!

Every time I do so, either with touch or  chmod for example, I get
errors like this:

Oct  1 08:52:39.288 read bad packet from 5

I can 9umount and then 9mount again for my next write operation as root.

Oddly enough, cp does not throw the error.  I can cp fine, then touch
gives me this

$ sudo touch that
[sudo] password for jdc:
Oct  1 10:20:25.502 read bad packet from 6
$ ls
ls: cannot open directory .: Input/output error

I unmount and remount and then I can cp again.

$ cd -
/home/jdc
$ sudo 9umount /n/sources
[sudo] password for jdc:
$ sudo 9mount -i
'unix!/tmp/ns.jdc.192.168.1.101:0/sources.cs.bell-labs.com' /n/sources
$ cd -
/n/sources/contrib/catenate
$ sudo cp /home/jdc/contrib/latin1.7a.font .
$ ls
lsguide  latin1.7a.font  that  this

So all the files get there, it's just annoying to have to
unmount/remount, and to have everything owned by root.

$ ls -la
total 2
-rw-r--r-- 1 root root  62 2009-10-01 08:59 guide
-rw-r--r-- 1 root root 577 2009-10-01 10:21 latin1.7a.font
-rw-r--r-- 1 root root   0 2009-10-01 10:20 that
-rw-r--r-- 1 root root   0 2009-10-01 08:49 this

> -sqweek

I also tried Abhishek's command also, but still got "permission denied".

Thanks everyone for your help.

Jason Catena



  parent reply	other threads:[~2009-10-01 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  5:06 Jason Catena
2009-10-01  7:44 ` Venkatesh Srinivas
2009-10-01  9:50   ` Jason Catena
2009-10-01 10:04     ` Ethan Grammatikidis
2009-10-01 10:31       ` sqweek
2009-10-01 12:38         ` Abhishek Kulkarni
2009-10-01 15:34         ` Jason Catena [this message]
     [not found] <<d50d7d460910010834r40c926barbc3dedd5828f3bd1@mail.gmail.com>
2009-10-01 16:22 ` erik quanstrom
2009-10-02  3:03   ` Jason Catena
     [not found] <<d50d7d460910012003h6aec0d3bj40ebdadac3358b6a@mail.gmail.com>
2009-10-02  3:11 ` erik quanstrom
2009-10-02 16:52   ` Jason Catena

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=d50d7d460910010834r40c926barbc3dedd5828f3bd1@mail.gmail.com \
    --to=jason.catena@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).