From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756899Ab0CCWDo (ORCPT ); Wed, 3 Mar 2010 17:03:44 -0500 Received: from fg-out-1718.google.com ([72.14.220.155]:56448 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756888Ab0CCWDc (ORCPT ); Wed, 3 Mar 2010 17:03:32 -0500 MIME-Version: 1.0 In-Reply-To: References: <20100302230933.GA32287@kroah.com> <1267572541-410-19-git-send-email-gregkh@suse.de> From: Kay Sievers Date: Wed, 3 Mar 2010 12:01:31 -1000 Message-ID: Subject: Re: [PATCH 19/62] Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default To: "Eric W. Biederman" Cc: Linus Torvalds , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 3, 2010 at 10:21, Eric W. Biederman wrote: > Kay Sievers writes: >> For the "must have", we will not be able to bootup the upcoming Ubuntu >> and openSUSE development distros without it, not sure about Fedora, >> the support is there, but it might still work without it. Some smaller >> distros also already depend on it. > > Is this a case of the initial ramdisks won't work, or have you removed > support from udev to create device nodes? Udev has not changed, it still works without any kernel-created nodes, as it always did. It's the distro-specific system coldplug/bootstrap logic that got simplified with the kernel device-node support. There is more pending, which will take the advantage of not needing to synchronize some steps, like it was needed the former asynchronous device-node-creation behavior. It affects initramfs and kernel-mounted rootfs setups, both now expect devtmpfs to be available. Kay