From: David du Colombier <0intro@gmail.com>
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 23:53:37 +0100 [thread overview]
Message-ID: <20111104235337.070d2ba7@zinc.9fans.fr> (raw)
In-Reply-To: <CADSkJJWoXj7=k4m=y+h4dK1CyvVNwtvdqf_3-7aGV4AHAYazdg@mail.gmail.com>
> > 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?
>
> You can port it if you want. Plan9port tries to integrate well with
> the host operating system. Part of that means using the same
> file tree, and the host OS cannot talk to fossil.
>
> There is disk code that knows how to read Plan 9 partition tables.
> The venti server uses it to let you write /dev/sdC0:arenas.
I started a port of Fossil to plan9port few months ago.
It seems to be working fine, but:
- the console doesn't work,
- it doesn't handle Plan 9 partitions tables,
- I haven't wrote the manuals.
I hope to fix all of these problems in the future. The lack of
console is obviously a big issue.
Beware this is not exactly the Plan 9 Fossil. This is the modified
Fossil I use on Plan 9. This Fossil is based on libventi and
libthread, instead of liboventi.
This is why liboventi haven't been ported.
I considered it is too experimental to be submitted to plan9port,
but the patches are available online:
- [1] fossil-plan9: import Fossil from Plan 9,
- [2] fossil-new: modified Fossil,
- [3] fossil-new-p9p: required plan9port changes on Fossil.
However, I recently submitted two needed patches to libventi:
- [4] libventi-redial: add redial and reconn functions,
- [5] libventi-noarchive: add VtEntryNoArchive.
These two patches add features, currently part of liboventi,
missing from libventi, but useful to Fossil.
[1] http://www.9legacy.org/p9p/patch/fossil-plan9.diff
[2] http://www.9legacy.org/p9p/patch/fossil-new.diff
[3] http://www.9legacy.org/p9p/patch/fossil-new-p9p.diff
[4] http://codereview.appspot.com/download/issue5325046_1.diff
[5] http://codereview.appspot.com/download/issue5298088_1.diff
If you want to contribute, I will be happy to receive patches
and bug reports.
--
David du Colombier
next prev parent reply other threads:[~2011-11-04 22:53 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
2011-11-04 20:57 ` Russ Cox
2011-11-04 22:53 ` David du Colombier [this message]
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=20111104235337.070d2ba7@zinc.9fans.fr \
--to=0intro@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).