From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Evans Subject: Re: Linux mdadm superblock question. Date: Fri, 19 Feb 2010 01:04:02 -0800 Message-ID: <4877c76c1002190104x3c801023x3ba2e3c7a11fcdf7@mail.gmail.com> References: <201002141940.35716.volkerarmin@googlemail.com> <20100217130103.3ca65ef3@notabene.brown> <4B7BB927.5000305@grumpydevil.homelinux.org> <20100217181016.GA14983@emergent.ellipticsemi.com> <87sk8z9q0h.fsf@frosties.localdomain> <20100218141230.GA26473@emergent.ellipticsemi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20100218141230.GA26473@emergent.ellipticsemi.com> Sender: linux-raid-owner@vger.kernel.org To: Goswin von Brederlow , david@lang.hm, Kyle Moffett , Rudy Zijlstra , Neil Brown , Mr. James W List-Id: linux-raid.ids I actually much prefer building my own kernel for servers and higher-end workstations. I like having all the core drivers needed to 'get running' in there; even if the more delicate but static logic of how to track down and assemble/unlock the drives is in the initramfs image. The only really annoying issue I've had with my custom initramfs creator is getting it 'chained' by various distros auto-initramfs update triggers so that it can grab the version of modules that match a given kernel. I have several ways in mind to work around that issue at various steps, but no known userbase to support besides my self and thus less motivation to work on that task. Everything else of course works exactly the same as long as the configuration hasn't changed on the host system.