From: smiley@icebubble.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FS for sharing between Linux and Plan 9
Date: Fri, 4 Nov 2011 20:50:34 +0000 [thread overview]
Message-ID: <86ipmza9yd.fsf@cmarib.ramside> (raw)
In-Reply-To: <861utuht0w.fsf@cmarib.ramside> (smiley@icebubble.org's message of "Mon, 31 Oct 2011 01:03:11 +0000")
smiley@icebubble.org writes:
> Jeremy Jackins <jeremyjackins@gmail.com> writes:
>> I like Fossil/Venti, but if I use this on the HDD I lose the ability
>> to take the disk outside of my home network and plug it into a Linux
>> machine (right?)
>
> There's a port of Plan 9 utilities to Linux userspace. It's called Plan
> 9 Port (aka p9p). See http://swtch.com/plan9port/. Linux machines with
> p9p should be able to talk to fossil/venti.
Hm. It looks like I might have been wrong about that. Digging a little
deeper, it seems like plan9port doesn't have any fdisk, prep, or fossil.
Is that correct? (And if so, why?) I know that Linux doesn't have any
kernel-level support for Plan 9 partitions or the fossil file system.
But can't that stuff be done in userspace, too?
--
+---------------------------------------------------------------+
|Smiley <smiley@icebubble.org> PGP key ID: BC549F8B |
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-11-04 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 22:30 Jeremy Jackins
2011-10-31 1:03 ` smiley
2011-10-31 1:35 ` andrey mirtchovski
2011-10-31 5:51 ` Jeremy Jackins
2011-11-04 20:50 ` smiley [this message]
2011-11-04 20:57 ` Russ Cox
2011-11-04 22:53 ` David du Colombier
2011-11-05 20:32 ` smiley
2011-11-05 22:56 ` David du Colombier
2011-11-07 17:09 ` David du Colombier
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=86ipmza9yd.fsf@cmarib.ramside \
--to=smiley@icebubble.org \
--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).