From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: remove detach_state from udev's wait_for_sysfs
Date: Mon, 20 Jun 2005 18:30:13 +0000 [thread overview]
Message-ID: <20050620183013.GA16470@wonderland.linux.it> (raw)
In-Reply-To: <20050619230126.GA7496@vrfy.org>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Jun 20, Greg KH <greg@kroah.com> wrote:
> > > > Can you clarify this?
> > > > udev releases >= 059 will require a kernel >= 2.6.12?
> > > Yes, would that be a problem?
> > Yes, thinking again about this I think it could be very annoying: users
> > would need to upgrade both the kernel and udev at the same time, but it
> > would not be possible because the udev package should abort the
> > installation if an old kernel is detected. Users would need to upgrade
> > the kernel, reboot to a partially working system and then upgrade udev.
> No, this doesn't "break" support on older kernels, just makes new
> device discover a little slow. It will all still work just fine. So a
> user can upgrade udev, and then their kernel.
OK, then newer kernels are not actually required.
I will have the init script print a big warning instead.
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-06-20 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 23:01 remove detach_state from udev's wait_for_sysfs Kay Sievers
2005-06-20 1:19 ` Ananth N Mavinakayanahalli
2005-06-20 12:15 ` Kay Sievers
2005-06-20 16:46 ` Greg KH
2005-06-20 17:45 ` Marco d'Itri
2005-06-20 18:03 ` Greg KH
2005-06-20 18:21 ` Marco d'Itri
2005-06-20 18:24 ` Greg KH
2005-06-20 18:30 ` Marco d'Itri [this message]
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=20050620183013.GA16470@wonderland.linux.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).