From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] P9p's mount(1) on linux
Date: Thu, 19 Jun 2008 03:42:35 +0200 [thread overview]
Message-ID: <5d375e920806181842t77de05f8v91bb7bd0c4d91819@mail.gmail.com> (raw)
Here is a tinny patch to make p9p's mount(1) work on linux even if you
have the v9fs (or fuse *yuck*) modules built into your kernel rather
than as modules.
Still there is the issue of what to do if you are not root, maybe a
9pmount helper program that is suid could take care of this? Sqweek
wrote a very nice 9mount program (
http://sqweek.dnsdojo.org/code/9mount/docs ) that maybe could be
added to p9p, unfortunately v9fs has changed its interface/params once
more and 9mount doesn't work with recent kernels *sigh*
Peace and best wishes
uriel
P.S.: Can someone please forward this to russ, last I heard he had my
email address in his kilfile.
diff -r fe7a4a762f75 bin/mount
--- a/bin/mount Sun Jun 15 01:46:23 2008 -0400
+++ b/bin/mount Thu Jun 19 03:41:08 2008 +0200
@@ -6,12 +6,12 @@
}
switch(`{uname}){
case Linux
- if(lsmod|9 grep -si '^9p(2000)? '){
+ if(cat /proc/filesystems|9 grep -si ' 9p(2000)?$'){
if(u test -S $1)
exec u mount -t 9p -o proto'='unix,name'='$USER $1 $2
exec u mount -t 9p -o proto'='tcp,name'='$USER $1 $2
}
- if(lsmod|9 grep -si '^fuse ')
+ if(cat /proc/filesystems|9 grep -si ' fuse$')
exec 9pfuse $1 $2
echo 'don''t know how to mount (no 9p, no fuse)' >[1=2]
case FreeBSD
next reply other threads:[~2008-06-19 1:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 1:42 Uriel [this message]
2008-06-19 1:57 ` Eric Van Hensbergen
2008-06-19 3:05 ` Uriel
2008-06-19 11:08 ` Rodolfo kix García
2008-06-19 15:10 ` Russ Cox
2008-06-19 20:29 ` Uriel
2008-06-19 23:21 ` Russ Cox
2008-06-19 23:40 ` Eric Van Hensbergen
2008-06-19 23:55 ` Skip Tavakkolian
2008-06-19 21:08 ` sqweek
2008-06-19 22:59 ` Russ Cox
2008-06-20 1:34 ` sqweek
2008-06-19 11:35 ` Iruata Souza
2008-06-19 15:53 ` Eric Van Hensbergen
2008-06-19 15:56 ` erik quanstrom
2008-06-19 20:25 ` Uriel
2008-06-19 20:39 ` sqweek
2008-06-19 21:52 ` Eric Van Hensbergen
2008-06-19 22:04 ` Eric Van Hensbergen
2008-06-19 22:46 ` Rob Pike
2008-06-20 12:37 ` sqweek
2008-06-20 13:20 ` Eric Van Hensbergen
2008-06-20 14:59 ` ron minnich
2008-06-19 13:33 ` Sape Mullender
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=5d375e920806181842t77de05f8v91bb7bd0c4d91819@mail.gmail.com \
--to=uriel99@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).