From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5d375e920707171208y124a3800wdc46ef7eaf803025@mail.gmail.com> Date: Tue, 17 Jul 2007 21:08:00 +0200 From: Uriel To: "Fans of the OS Plan 9 from Bell Labs" <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=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <13426df10707170929r2b780418o8b2018077ae28206@mail.gmail.com> <13426df10707171008u66031dc1g883b4eadfb0a10b4@mail.gmail.com> Topicbox-Message-UUID: 9583d630-ead2-11e9-9d60-3106f5b1d025 > > 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.