From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil option -m
Date: Sat, 18 Aug 2012 10:57:45 -0400 [thread overview]
Message-ID: <0d222a32d99cd6e44274c7ca2367d08d@brasstown.quanstro.net> (raw)
In-Reply-To: <5FF01BA4-294A-4EEA-AED9-BBECF6A67642@ar.aichi-u.ac.jp>
> I have looked contents in /boot/bootfs.paq of 9front.
> I like the booting process: flexible, elegant and probably powerful.
it's another stage of bootloading which requires a number of things to be built-in
to the kernel. in this sense, it's like initrd.
if we were to instead make the local file servers (fossil+venti, kfs, cwfs, etc.)
idiomatic enough in their arguments, it should be easy enough to drive them
with the same boot code, that needn't bloat the kernel, or require fancy
memory reclaim.
also,
> let's make it "fsmb". that way we need not enumerate file servers.
> i've always found listing things in mb is easier to work out.
i take it back. $fsname^mb is idiomatic enough to automate.
sorry for the noise.
- erik
next prev parent reply other threads:[~2012-08-18 14:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 5:03 arisawa
2012-08-18 5:30 ` erik quanstrom
2012-08-18 5:40 ` John Floren
2012-08-18 10:04 ` arisawa
2012-08-18 11:14 ` Richard Miller
2012-08-18 14:57 ` erik quanstrom [this message]
2012-08-18 16:23 ` cinap_lenrek
2012-08-18 17:11 ` erik quanstrom
2012-08-18 18:05 ` cinap_lenrek
2012-08-18 18:17 ` Richard Miller
2012-08-18 11:12 ` Richard Miller
2012-08-18 11:36 ` David du Colombier
2012-08-18 13:02 ` Richard Miller
2012-08-18 14:53 ` erik quanstrom
2012-08-19 9:04 ` David du Colombier
2012-08-19 15:04 ` erik quanstrom
2012-08-19 16:06 ` Bakul Shah
2012-08-19 16:08 ` cinap_lenrek
2012-08-19 16:15 ` Richard Miller
2012-08-19 16:17 ` erik quanstrom
[not found] ` <CAL4LZyimqPZVQGmTDXzKBJsJNUaLsCEQBZz4qY8YSCb7pMkypA@mail.gmail.c>
2012-08-18 15:00 ` erik quanstrom
2012-08-18 15:18 ` erik quanstrom
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=0d222a32d99cd6e44274c7ca2367d08d@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).