From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spragg Subject: Re: module 90kernel-modules-loaded Date: Tue, 10 Mar 2009 08:06:33 +0000 Message-ID: <49B61F89.4020902@spra.gg> References: <49B1439A.7030208@redhat.com> <20090306160822.GD10711@nostromo.devel.redhat.com> <1236361391.6517.0.camel@sentry-no.fnordovax.org> <20090306203921.GA28154@nostromo.devel.redhat.com> <1236382532.5147.38.camel@sentry-no.fnordovax.org> <20090309031111.GC3983@redhat.com> <1236595028.14649.40.camel@sentry-no.fnordovax.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1236595028.14649.40.camel-76q0VzFBGGr21HsLBtNmTckMGDeJXHgy@public.gmane.org> Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Victor Lowther Cc: Jeremy Katz , initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Victor Lowther wrote: > 4: Add a few udev rules that call scripts to configure a few key device > types as they are detected, and have another process running that looks > for the root filesystem to appear running in tandem with udev. [snip] > We have made large advances using the fourth approach Something that worries me slightly ... ISTR that a large part of the goal of udev was to get device naming policy out of the kernel tree and into an externally maintained module. But one of the goals of dracut seems to be to become part of the kernel source tree. So, if dracut imports udev naming rules and, therefore, device naming policy, and is in turn imported into the main kernel source tree, doesn't that kind of defeat one of the main reasons for udev's existence? Is this something we need to worry about? Adam Spragg. -- The fundamental cause of the trouble is that in the modern world the stupid are cocksure while the intelligent are full of doubt. -- Bertrand Russell -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html