From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: [9fans] making better use of ext2fs?
Date: Mon, 14 May 2001 13:36:16 +0300 [thread overview]
Message-ID: <200105141036.f4EAaG613033@skeeve.com> (raw)
Greetings 9fans,
I've been following 9fans for quite a while over the years, and pretty
steadily since the 3rd release.
One thing I've noticed is that people report kfs sometimes gets flaky
when used in a stand-alone configuration.
So, in a thinking-out-loud sort of mode, I'm wondering if maybe it
might be worth investigating use of ext2fs instead of kfs for that
purpose. This has the non-trivial advantage that, for those 9people
who also use Linux, recovery tools are available just by rebooting.
It also has the potential to make install/bootstrapping easier:
fdisk # set up a separate ext2 partition
newfs /dev/xxx # put a filesystem on it
mount /dev/xxx /mnt
cd /mnt ; tar -xvpzf p9tarball.tgz
# edit various config files using whatever editor
# you have under Linux that you like
umount /mnt
dd if=p9bootblock of=/dev/xxx bs=512 count=1
# edit lilo config
/sbin/lilo
shutdown -r now
This is, obviously, just an outline of the steps, and there's obviously
a ``non-trivial'' amount of work involved. OTOH, if making Plan 9 easier
to install and use is an acknowledged---if secondary---goal, then perhaps
this is worth considering?
The reason I suggest it is that the ext2fs server already exists and works
(for some definition of "works" :-), whereas a bsdfs server would probably
have to be written from scratch --- I'm not trying to start a Linux
vs. *BSD (flame-)war here.
In other words, this is a way to provide an additional bootstrapping
mechanism; I'm not suggesting that this replace the current install.
I almost didn't post this, because I hate it when I'm on the receiving
end of "here's a great idea, why don't you do the work?". OTOH, I
wanted to offer the thought. And if someone can run with it, great.
If not, maybe one day I'll be able to, and in the meantime we're no
worse off than we are now.
Thanks,
Arnold Robbins
arnold@skeeve.com
next reply other threads:[~2001-05-14 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 10:36 Aharon Robbins [this message]
2001-05-14 12:25 forsyth
2001-05-14 17:17 Jonathan Sergent
2001-05-14 18:10 forsyth
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=200105141036.f4EAaG613033@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/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).