Date: Wed, 25 Aug 2010 09:22:02 +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: <AANLkTimUgLAYfM7FJ32hMmF8SEtUYYTrOMKBZep0zDJs@mail.gmail.com> In-Reply-To: <20100824.105546.1002438156525560711.imp@bsdimp.com> References: <760A97A4-62D2-4900-915D-CA5D889855E1@mac.com> <20100824155205.C2A535B23@mail.bitblocks.com> <C6B677DB-5CC8-46C1-B551-7BEB7BF953E0@mac.com> <20100824.105546.1002438156525560711.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 August 2010 00:55, M. Warner Losh <imp@bsdimp.com> wrote: > > You can get away from a large MD by having a small MD and pivoting to > large storage. =A0Linux does this, as Bakul said, and it scales from the > ultra-small 4MB Mips router up to the highest multicore server. > But as someone's said before - and as I've been a Linux sysadmin here and there, I've been bitten more than once by the linux mdroot setup where only the -bare minimum- modules needed to bring the system up are in the mdroot. Woe be if you have to swap hardware in a hurry - double woe if your distribution provides lots of nice "autodetect" methods for figuring out which modules should be in the mdroot and does this for you automatically. You can manually build modules into mdroot but that isn't any good when you're trying to boot a post-failed system on alternative hardware. The FreeBSD method has been nice - I can compile a lean GENERIC but use /boot/loader.conf to load modules at boot time to use alternative storage/network mechanisms. 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. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimUgLAYfM7FJ32hMmF8SEtUYYTrOMKBZep0zDJs>