From: Eric Van Hensbergen <ericvh@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p on Yeeloong (gNewSense Linux)
Date: Mon, 29 Jun 2009 10:03:23 -0500 [thread overview]
Message-ID: <a4e6962a0906290803m5edec6d0o92339e609f65651d@mail.gmail.com> (raw)
In-Reply-To: <906a85070a784fabc9457db2fc3f4706@proxima.alt.za>
On Mon, Jun 29, 2009 at 3:49 AM, <lucio@proxima.alt.za> wrote:
>> cat /proc/filesystems
>
> Returns
>
> nodev 9p
>
> but "mount -t 9p" returns "Protocol not supported". Is the problem
> not within "mount"?
>
There are actually several modules which work together to provide 9p,
there is the 9p file system, the 9p network module (which includes as
a default the socket transport), and then additional transport plugins
(for KVM, infiniband, etc.) Its possible you have the file system
module, but not the network module -- however, I thought the
dependencies have been setup to fix that for some time. The best
thing to do is to turn on debug with your mount and look at the
/var/log/messages. Linux errno error codes don't give the best error
and protocol not supported could actually mean one of several things,
the /var/log/messages with debug on will clarify the problem. So add
-o debug=0xffff to your mount line and post the /var/log/messages
output and we'll see what we can do to help you.
Thanks,
-eric
next prev parent reply other threads:[~2009-06-29 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 4:55 lucio
2009-06-29 5:41 ` ron minnich
2009-06-29 8:49 ` lucio
2009-06-29 12:14 ` erik quanstrom
2009-06-29 15:03 ` Eric Van Hensbergen [this message]
2009-06-29 17:37 ` Skip Tavakkolian
2009-07-02 11:33 ` Uriel
2009-07-02 11:34 ` Uriel
2009-06-29 5:31 Akshat Kumar
2009-06-29 9:10 ` lucio
2009-07-01 7:47 ` Richard Miller
[not found] <32d9733a263818587ab347169fd8a312@quanstro.net>
2009-06-29 17:29 ` lucio
2009-06-29 17:39 ` erik quanstrom
2009-06-29 17:59 ` lucio
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=a4e6962a0906290803m5edec6d0o92339e609f65651d@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).