From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261516AbVFTTyf (ORCPT ); Mon, 20 Jun 2005 15:54:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261552AbVFTTvC (ORCPT ); Mon, 20 Jun 2005 15:51:02 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:16800 "EHLO e6.ny.us.ibm.com") by vger.kernel.org with ESMTP id S261511AbVFTTtc (ORCPT ); Mon, 20 Jun 2005 15:49:32 -0400 Subject: Re: 2.6.12 udev hangs at boot From: Josh Boyer To: Greg KH Cc: Jeff Garzik , Denis Vlasenko , Nick Warne , linux-kernel@vger.kernel.org In-Reply-To: <20050620173411.GB15212@suse.de> References: <200506181332.25287.nick@linicks.net> <42B45173.6060209@pobox.com> <200506181806.49627.nick@linicks.net> <200506201304.10741.vda@ilport.com.ua> <20050620164800.GA14798@suse.de> <42B6FBC7.5000900@pobox.com> <20050620173411.GB15212@suse.de> Content-Type: text/plain Date: Mon, 20 Jun 2005 14:49:28 -0500 Message-Id: <1119296968.16063.1.camel@weaponx.rchland.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2005-06-20 at 10:34 -0700, Greg KH wrote: > On Mon, Jun 20, 2005 at 01:24:23PM -0400, Jeff Garzik wrote: > > Greg KH wrote: > > >On Mon, Jun 20, 2005 at 01:04:10PM +0300, Denis Vlasenko wrote: > > > > > >>Greg, any plans to distribute udev and hotplug within kernel tarballs > > >>so that people do not need to track such changes continuously? > > > > > > > > >Nope. But if you use udev, you should read the announcements for new > > >releases, as I did say this was required for 2.6.12, and gave everyone a > > >number of weeks notice :) > > > > Since udev is required for booting, it sounds like you're putting people > > in an upgrade-or-no-boot situation. > > Well, they don't _have_ to upgrade their kernel :) > > > That's lame. The kernel should support udev's out in the field, on > > people's boxes (RHEL, SLES?, Fedora, ...). > > This was caused by an unfortunate assumption in older versions of udev > about what was contained in the sysfs tree. udev is now fixed to not > make that assumption. So this was not a kernel bug, but a udev/libsysfs > one (and I wasn't going to keep the old kernel behavior for this minor > issue.) > > As for working with people's boxes, only the very oldest versions of > udev (like the reported 030 version which is a year old and I do not > think shipped by any distro) would have the "lockup" issue. On all of > the other ones, only custom rules written by users would have issues > (meaning, not work). I do not know of any shipping, supported distro > that currently has a boot lockup issue (if so, please let me know.) SLES 9 shipped with udev-021. http://www.novell.com/products/linuxpackages/enterpriseserver/i386/udev.html Is that effected by this? josh