From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] v9fs question
Date: Sat, 11 Jul 2009 16:03:55 -0400 [thread overview]
Message-ID: <3aaafc130907111303r5203bfcdye9af2e6c46e4a7d5@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.0907110901260.5249@malasada.lava.net>
On Sat, Jul 11, 2009 at 3:03 PM, Tim Newsham<newsham@lava.net> wrote:
> On Sat, 11 Jul 2009, Eric Van Hensbergen wrote:
>>
>> Hmmm, that's really new behavior-- never used to fail without mount
>> helper. Can you give the exact error message?
>
> # strace -o trace.txt mount -t 9p thenewsh.com /mnt
Linux doesn't do resolution for you, you have to give raw ip
addresses. Maybe not the problem, but worth pointing out.
> mount: Protocol not supported
>
> Trace.txt is attached with full details.
>
> I've tried several variants, such as thenewsh.com:/path
> with similar results.
>
>> On Jul 11, 2009, at 1:46 PM, Tim Newsham <newsham@lava.net> wrote:
>>
>>> The documentation in the linux kernel says you merely
>>>
>>> mount -t 9p ipaddress /mntpoint
>>>
>>> this fails on my system since /sbin/mount tries to execute /sbin/mount.9p
>>> and fails. Am I supposed to have an /sbin/mount.9p? (Anyone know which
>>> ubunutu package should have this? If not, where I might find sources?
>>> Ironic since Ubuntu came with the 9p kernel module) Or should I be using a
>>> different mount program for the purpose?
>>>
>>> The linux Documentation/filesystems/9p.txt should probably be updated
>>> with more details, either way.
>>>
>>> Tim Newsham
>>> http://www.thenewsh.com/~newsham/
>>>
>>
>
> Tim Newsham
> http://www.thenewsh.com/~newsham/
next prev parent reply other threads:[~2009-07-11 20:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 18:46 Tim Newsham
2009-07-11 18:50 ` Eric Van Hensbergen
2009-07-11 19:03 ` Tim Newsham
2009-07-11 19:47 ` Eric Van Hensbergen
2009-07-11 20:03 ` J.R. Mauro [this message]
2009-07-12 3:19 ` Uriel
2009-07-13 8:24 ` sqweek
2009-07-13 8:51 ` hiro
2009-07-13 14:20 ` Eric Van Hensbergen
2009-07-13 20:44 ` hiro
2009-07-13 21:45 ` hiro
2009-07-13 22:05 ` Eric Van Hensbergen
2009-07-13 22:18 ` J.R. Mauro
2009-07-13 23:16 ` ron minnich
2009-07-13 23:22 ` Eric Van Hensbergen
2009-07-13 23:37 ` ron minnich
2009-07-13 23:47 ` Eric Van Hensbergen
2009-07-13 23:41 ` J.R. Mauro
2009-07-13 23:50 ` erik quanstrom
2009-07-14 0:00 ` J.R. Mauro
2009-07-14 0:06 ` erik quanstrom
2009-07-14 0:01 ` Eric Van Hensbergen
2009-07-14 0:08 ` ron minnich
2009-07-14 0:46 ` J.R. Mauro
2009-07-14 0:42 ` J.R. Mauro
2009-07-14 0:58 ` Eric Van Hensbergen
2009-07-14 1:28 ` Latchesar Ionkov
2009-07-14 1:35 ` Devon H. O'Dell
2009-07-14 2:05 ` Tim Newsham
2009-07-14 0:42 ` Tim Newsham
2009-07-14 0:50 ` erik quanstrom
2009-07-14 0:56 ` Eric Van Hensbergen
2009-07-14 4:51 ` lucio
2009-07-14 4:29 ` lucio
2009-07-14 4:26 ` lucio
2009-07-13 22:00 ` Eric Van Hensbergen
2009-07-14 19:05 ` sqweek
2009-07-14 20:11 ` Eric Van Hensbergen
2009-07-13 14:59 ` lucio
2009-07-13 15:04 ` Eric Van Hensbergen
2009-07-13 15:08 ` Latchesar Ionkov
2009-07-13 19:51 ` Tim Newsham
2009-07-14 7:34 ` sqweek
2009-07-14 11:08 ` roger peppe
2009-07-14 11:20 ` hiro
2009-07-14 12:48 ` Eric Van Hensbergen
2009-07-14 15:45 ` ron minnich
2009-07-14 16:31 ` Tim Newsham
2009-07-14 20:21 ` roger peppe
2009-07-14 13:10 ` Eric Van Hensbergen
2009-07-14 13:23 ` erik quanstrom
2009-07-14 14:26 ` Eric Van Hensbergen
2009-07-14 14:44 ` erik quanstrom
2009-07-14 14:33 ` Latchesar Ionkov
2009-07-14 14:54 ` Eric Van Hensbergen
2009-07-14 15:01 ` erik quanstrom
2009-07-14 15:13 ` Eric Van Hensbergen
2009-07-14 15:19 ` erik quanstrom
2009-07-14 15:37 ` Eric Van Hensbergen
2009-07-14 16:12 ` erik quanstrom
2009-07-14 16:19 ` Eric Van Hensbergen
2009-07-14 15:06 ` Latchesar Ionkov
2009-07-14 15:48 ` ron minnich
2009-07-14 15:59 ` Eric Van Hensbergen
2009-07-14 14:37 ` Latchesar Ionkov
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=3aaafc130907111303r5203bfcdye9af2e6c46e4a7d5@mail.gmail.com \
--to=jrm8005@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).