linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Report: Threaded udevd
Date: Wed, 22 Oct 2008 17:02:25 +0000	[thread overview]
Message-ID: <20081022170225.GA23609@bongo.bofh.it> (raw)
In-Reply-To: <48FF3458.6030909@tuffmail.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Oct 22, Greg KH <greg@kroah.com> wrote:

> > > I see no problem with depending on the very latest kernels; using a
> > > latest udev version goes hand-in-hand with using a latest kernel.
> > I do, since this tends to badly mess upgrades...
> How?  Can't you just specify a minimum kernel version in your packaging
> system for the latest version of udev?  That's what we do for other
> distros...
The problem is handling upgrades between two different major revisions
of a distribution. e.g. Debian 3.1 shipped udev 56 and kernel 2.6.8,
while Debian 4.0 shipped udev 105 and kernel 2.6.18.
udev 105 did not work with kernel 2.6.18 and udev 56 did not work with
kernel 2.6.8, so the udev installation script had to jump hoops to not
start the new udev, make sure that a suitable updated kernel was
installed at the same time and recommend the administrator to reboot
ASAP.
And if for some reason the new kernel does not work, the user will be
left with a mostly broken (no working udev) system.
This is why I would really really like to see kernel 2.6.26 supported by
udev for the next few years.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-10-22 17:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 14:10 Report: Threaded udevd Alan Jenkins
2008-10-22 14:32 ` Scott James Remnant
2008-10-22 15:15 ` Marco d'Itri
2008-10-22 16:12 ` Alan Jenkins
2008-10-22 16:22 ` Scott James Remnant
2008-10-22 16:24 ` Greg KH
2008-10-22 17:02 ` Marco d'Itri [this message]
2008-10-22 17:11 ` Scott James Remnant
2008-10-22 17:14 ` Marco d'Itri
2008-10-23 16:25 ` Karl O. Pinc
2008-10-23 16:29 ` Marco d'Itri
2008-10-23 16:55 ` Karl O. Pinc

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=20081022170225.GA23609@bongo.bofh.it \
    --to=md@linux.it \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).