All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 20:32:30 +0100	[thread overview]
Message-ID: <200506202032.30771.nick@linicks.net> (raw)
In-Reply-To: <20050620192118.GA13586@suse.de>

On Monday 20 June 2005 20:21, Greg KH wrote:

> > 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.)
>
> Any Slackware users want to pester them for updates?

Remember this is Slackware 10 here I am talking about - Slackware 10.1 has 
been released since, that uses as stock udev 50.  Slackware current uses udev 
54.  Trouble is here also, GLIBC has been updated in latest Slackware[s], so 
there is no real upgrade path for Slack 10 users other than the whole 
caboodle - which breaks a lot if you have all the latest 'other stuff' built 
from source anyway.

I guess many users don't upgrade all the system like I do to find these 
problems.  This appears to be just a gotcha for old Slackware 10 users like 
me.  Sometimes you read stuff about doing an upgrade, and unless it pokes yer 
eye out with a big stick you miss it... so it is isn't a big deal as long as 
people know about it - it's an easy fix.

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

  reply	other threads:[~2005-06-20 19: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
2005-06-20 19:00             ` Nick Warne
2005-06-20 19:21               ` Greg KH
2005-06-20 19:32                 ` Nick Warne [this message]
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=200506202032.30771.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.