From: Greg KH <gregkh@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Denis Vlasenko <vda@ilport.com.ua>, Nick Warne <nick@linicks.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 10:34:11 -0700 [thread overview]
Message-ID: <20050620173411.GB15212@suse.de> (raw)
In-Reply-To: <42B6FBC7.5000900@pobox.com>
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.)
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-20 17:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 12:32 2.6.12 udev hangs at boot Nick Warne
2005-06-18 13:03 ` Alistair John Strachan
2005-06-18 13:44 ` Nick Warne
2005-06-18 14:58 ` Andrew Walrond
2005-06-18 16:53 ` Jeff Garzik
2005-06-18 17:06 ` Nick Warne
2005-06-19 15:04 ` Andrew Haninger
2005-06-20 10:04 ` Denis Vlasenko
2005-06-20 10:17 ` Stefan Smietanowski
2005-06-20 11:13 ` Denis Vlasenko
2005-06-20 16:25 ` Stefan Smietanowski
2005-06-20 16:39 ` Bill Davidsen
2005-06-20 16:48 ` Greg KH
2005-06-20 17:24 ` Jeff Garzik
2005-06-20 17:34 ` Greg KH [this message]
2005-06-20 19:00 ` Nick Warne
2005-06-20 19:21 ` Greg KH
2005-06-20 19:32 ` Nick Warne
2005-06-20 19:42 ` David Lang
2005-06-21 6:28 ` Greg KH
2005-06-21 6:31 ` David Lang
2005-06-21 6:47 ` Greg KH
2005-06-20 19:46 ` Jesper Juhl
2005-06-20 19:34 ` Andrew Haninger
2005-06-20 19:49 ` Josh Boyer
2005-06-21 6:42 ` Greg KH
2005-06-20 19:24 ` Olaf Hering
2005-06-20 21:26 ` Daniel Barkalow
2005-06-20 22:14 ` Jesper Juhl
2005-06-20 22:26 ` Tomasz Torcz
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 15:32 Nick Warne
2005-06-21 6:40 ` Greg KH
2005-06-19 15:39 Nick Warne
2005-06-19 21:23 ` Andrew Haninger
2005-06-21 6:45 ` Greg KH
2005-06-21 17:06 ` Nick Warne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050620173411.GB15212@suse.de \
--to=gregkh@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=vda@ilport.com.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox