Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752218Ab0BSJJP (ORCPT ); Fri, 19 Feb 2010 04:09:15 -0500 Received: from mail-pz0-f192.google.com ([209.85.222.192]:58910 "EHLO mail-pz0-f192.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751726Ab0BSJJM (ORCPT ); Fri, 19 Feb 2010 04:09:12 -0500 X-Greylist: delayed 309 seconds by postgrey-1.27 at vger.kernel.org; Fri, 19 Feb 2010 04:09:12 EST DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=u6YQqz/371mwKpiMxPApJDVtGInv9qRw4z0C91iS2HbCtHO4aWxBRHgTSuGcnTzxQ6 35/8daFe0otKK2k5hCVakactEtKdzU/20WEePj8e4ZVCz3gwtCtMjxtaaPL9fsnsGf8Z LD+aM0ys8/CS+XkD3L1CjA5xlTNLsOaZiSPGc= MIME-Version: 1.0 In-Reply-To: <20100218141230.GA26473@emergent.ellipticsemi.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> Date: Fri, 19 Feb 2010 01:04:02 -0800 Message-ID: <4877c76c1002190104x3c801023x3ba2e3c7a11fcdf7@mail.gmail.com> Subject: Re: Linux mdadm superblock question. From: Michael Evans To: Goswin von Brederlow , david@lang.hm, Kyle Moffett , Rudy Zijlstra , Neil Brown , "Mr. James W. Laferriere" , Bill Davidsen , Volker Armin Hemmann , Michael Evans , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1025 Lines: 20 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/