9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] the perpetual disk partition problem
Date: Tue, 17 Jul 2007 21:08:00 +0200	[thread overview]
Message-ID: <5d375e920707171208y124a3800wdc46ef7eaf803025@mail.gmail.com> (raw)
In-Reply-To: <13426df10707171008u66031dc1g883b4eadfb0a10b4@mail.gmail.com>

> > if you don't like that you could put fdisk and prep in your kernel
> > image, write a new boot method, localpart, that partitions before
> > it calls local.  you could import the code for this from 9load.
>
> That's what I did several years ago for the xen 2.0 port but there was
> an objection to it that I never understood. I'll go with that.

I can't think of why this might be a bad idea, boot certainly has some
limitations (like only allowing a small number of files), but if that
is a problem we should remove those limitations, it seems the ideal
place to put this kind of things.

If we are ever going to kill 9load (and I'm still intending to
eventually do it), putting stuff in boot seems to be the only
reasonable option, and a rather good one I might add.

uriel

P.S.: As a way to bypass the current limitations one could put a paqfs
into boot.


      parent reply	other threads:[~2007-07-17 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 15:52 ron minnich
2007-07-17 16:05 ` erik quanstrom
2007-07-17 16:06 ` erik quanstrom
2007-07-17 16:23 ` Steve Simon
2007-07-17 16:29   ` ron minnich
2007-07-17 16:49     ` erik quanstrom
2007-07-17 17:08       ` ron minnich
2007-07-17 17:41         ` erik quanstrom
2007-07-17 19:08         ` Uriel [this message]

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=5d375e920707171208y124a3800wdc46ef7eaf803025@mail.gmail.com \
    --to=uriel99@gmail.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).