Date: Wed, 25 Aug 2010 11:49:10 +0800 From: Adrian Chadd <adrian@freebsd.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: xcllnt@mac.com, freebsd-arch@freebsd.org Subject: Re: RFC: enhancing the root mount logic Message-ID: <AANLkTika4Njgrz=cmgyZJxofz9gvSiwuFhnDVjXk_rEB@mail.gmail.com> In-Reply-To: <20100824.195145.29593248078694701.imp@bsdimp.com> References: <C6B677DB-5CC8-46C1-B551-7BEB7BF953E0@mac.com> <20100824.105546.1002438156525560711.imp@bsdimp.com> <AANLkTimUgLAYfM7FJ32hMmF8SEtUYYTrOMKBZep0zDJs@mail.gmail.com> <20100824.195145.29593248078694701.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 August 2010 09:51, M. Warner Losh <imp@bsdimp.com> wrote: > : I'm not saying the whole Linux initrd approach is -bad-; i'm just > : saying it needs to be thought through a little more first. > > No body is saying that the only way to do things (or even the default > way) is via the Linux mdroot thing. =A0We're saying that it is *A* way > to bootstrap a kernel that uses the ramfs to find the proper location > of root to mount (maybe after initializing the device where root is), > pivot to that new location. > > Marcel's current proposal seems simpler (and less flexible) than > this. =A0The proof in the pudding will be his ability to handle the > 'layered' cases of encryption or compression I brought up earlier. I do like the idea of a formalish description of a bootstrap process rather than "hi, run these scripts." That said, I do like the idea of also being able to run some scripts, prep the system and then re-try the root mount. Having both options would be rather nice. In any case, +1 from me. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTika4Njgrz=cmgyZJxofz9gvSiwuFhnDVjXk_rEB>