9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the perpetual disk partition problem
Date: Tue, 17 Jul 2007 13:41:37 -0400	[thread overview]
Message-ID: <6aa470f7e6a47430d0ae0cea21dd93d7@coraid.com> (raw)
In-Reply-To: <13426df10707171008u66031dc1g883b4eadfb0a10b4@mail.gmail.com>

On Tue Jul 17 13:08:26 EDT 2007, rminnich@gmail.com wrote:
> On 7/17/07, erik quanstrom <quanstro@coraid.com> wrote:
> 
> > why can't you just put the (known) offsets in your plan9.ini like i am doing
> > for aoe?  it's distasteful, but it does get the job done.
> >
> 
> Until the offsets change. This is intended to be used by people other than me.

there always has to be a catch.... ;-)

can you generate these offsets as part of the install?

> 
> > 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.

it seems like a good thing to keep the setup out of the kernel proper,
but any sort of sd device that needs to use the network is going to be difficult
with the current 9load.  perhaps with a few tweaks it could be
much easier.

- erik


  reply	other threads:[~2007-07-17 17:41 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 [this message]
2007-07-17 19:08         ` Uriel

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=6aa470f7e6a47430d0ae0cea21dd93d7@coraid.com \
    --to=quanstro@coraid.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).