linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darcoux Christine <bouloumag@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev minimum requirement
Date: Tue, 18 Jan 2011 21:56:21 +0000	[thread overview]
Message-ID: <AANLkTikhEqYyCHgdv2Oh7fn8w2euSPAsh=02k9nheaXE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikdw11L1adphyv4hDk-aG9vn82V80X0zyvZ+Lkc@mail.gmail.com>

2011/1/18 Kay Sievers <kay.sievers@vrfy.org>:
> On Tue, Jan 18, 2011 at 18:25, Darcoux Christine <bouloumag@gmail.com> wrote:
>> I am a little confused about the minimum kernel version need for udev .
>> Is there a contradiction between these two sentences from the README file ?
>>
>> "The upstream udev project's set of default rules may require a most recent
>> kernel release to work properly. This is currently version 2.6.31."
>
> That's what we usually test and should work out-of-the-box.
>
>> and
>>
>> "Requirements:
>>  - Version 2.6.27 of the Linux kernel"
>
> That's the first version of the old kernels that has all the
> requirement to just run udev. It may fail completely with older
> versions. But nobody really tests that, I guess, at least not
> constantly. Rules may be missing. Many possible issues could be worked
> around, are might not be to find in the udev source tree.
>
>> Does it means that the **real** minimum requirement is kernel 2.6.31 ?
>> If not, what will works with 2.6.31 that will not work with 2.6.27 ?
>
> Nobody really knows, I guess, because we usually don't run old kernels
> on new userspace tools. We only make sure that new kernels can run on
> old userspace, not the other way around.
>
> Kay
>

(sorry I did not replyed to the list)
Thank you Kay for the explanations. May I suggest to include them in
the readme ?

Cheers

      parent reply	other threads:[~2011-01-18 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 17:25 udev minimum requirement Darcoux Christine
2011-01-18 17:33 ` Kay Sievers
2011-01-18 21:56 ` Darcoux Christine [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='AANLkTikhEqYyCHgdv2Oh7fn8w2euSPAsh=02k9nheaXE@mail.gmail.com' \
    --to=bouloumag@gmail.com \
    --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).