From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6aa470f7e6a47430d0ae0cea21dd93d7@coraid.com> From: erik quanstrom Date: Tue, 17 Jul 2007 13:41:37 -0400 To: 9fans@cse.psu.edu Subject: Re: [9fans] the perpetual disk partition problem In-Reply-To: <13426df10707171008u66031dc1g883b4eadfb0a10b4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 957fef8e-ead2-11e9-9d60-3106f5b1d025 On Tue Jul 17 13:08:26 EDT 2007, rminnich@gmail.com wrote: > On 7/17/07, erik quanstrom 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