From: Jesper Juhl <jesper.juhl@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: Nick Warne <nick@linicks.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 21:46:14 +0200 [thread overview]
Message-ID: <9a87484905062012464a76a175@mail.gmail.com> (raw)
In-Reply-To: <20050620192118.GA13586@suse.de>
On 6/20/05, Greg KH <gregkh@suse.de> wrote:
> On Mon, Jun 20, 2005 at 08:00:08PM +0100, Nick Warne wrote:
> > On Monday 20 June 2005 18:34, you wrote:
> >
> > > 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.)
> >
> > It appears the issue people are seeing is with Slack 10, which shipped with
> > udev 0.26 - and I presume there was 'custom' rules Patrick had built in.
>
> Ick. Hm, there's not been any updates for slack since then? (note,
> there was no 0.26 release, there are no '.' in udev releases.)
>
There has been updates since then.
There's been a newer stable Slackware release since 10.0. Slackware
10.1 was released on 2005-02-06 and ships udev 050.
Slackware-current (the unstable/development branch) is currently using udev 054.
Both the udev 050 and udev 054 Slackware packages should install fine
on a Slackware 10.0 box as far as I can see. So people just need to
upgrade their distro, or at least the udev bit of it :)
I'm running Slackware-current here with udev 054 and everything is just fine.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-06-20 19:50 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
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 [this message]
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=9a87484905062012464a76a175@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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