9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more silly fossil questions
Date: Tue, 24 Jun 2003 21:34:31 -0400	[thread overview]
Message-ID: <200306250134.h5P1YV707256@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 24 Jun 2003 20:08:02 EDT." <991e41889b450ad510090cda76b22a72@plan9.bell-labs.com>

> > I suppose another solution is to dedicate a (very) small partition at
> > the beginning of the disk for the fossil/venti bootstrap.  Put a simple
> > filesystem, such as the flash FS, on it and then the kernel image need
> > only contain just enough logic in /boot/boot to mount it and run a
> > script.  It would certainly make alterations easier as they are no
>
> Then you have to maintain the script.  As long as you can build
> one kernel that works for many people I think it's better to have
> the logic in the kernel.

The way I see it, we can have it both ways.

The issue seems to be that that one kernel isn't ideal for some people,
who want to change around their configuration without rebuilding their
kernel.  But as I see it, those who want to experiment can keep a
script elsewhere.  Those who just want the default can use the single
kernel image you describe.

> You can use the venti/conf and fossil/conf commands to brand
> configurations onto your disks.  Then /boot/boot will just do the
> right thing.  There's a new kernel 9pcf that is a fossil terminal.
> I don't remember if I pushed out though.  I'll check.

Cool!

	- Dan C.



  reply	other threads:[~2003-06-25  1:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 17:09 andrey mirtchovski
2003-06-24 17:26 ` Andrew
2003-06-24 18:08 ` plan9
2003-06-24 18:19   ` Dan Cross
2003-06-25  0:08     ` Russ Cox
2003-06-25  1:34       ` Dan Cross [this message]
2003-06-25  0:49     ` bs
2003-06-25  1:42       ` Dan Cross
2003-06-26 10:58         ` Martin C.Atkins
2003-06-26 13:45           ` Dan Cross
2003-06-26 14:00             ` boyd, rounin
2003-06-25  7:59   ` Fco.J.Ballesteros, nemo
2003-06-25  8:06 ` Fco.J.Ballesteros, nemo

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=200306250134.h5P1YV707256@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).