mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Subject: Re: udev in kernel source?
Date: Sun, 25 Oct 2009 20:04:15 +0100	[thread overview]
Message-ID: <200910252004.21546.Martin@lichtvoll.de> (raw)
In-Reply-To: <200910251930.36658.elendil@planet.nl>

[-- Attachment #1: Type: Text/Plain, Size: 1809 bytes --]

Am Sonntag 25 Oktober 2009 schrieb Frans Pop:
> Martin Steigerwald wrote:
> > Would that qualify as a reason to put it there and have make-kpkg /
> > make deb / make rpm spit out a udev package as well?
> 
> How would that help?

That udev and kernel match each other. But you are right, rest of 
userspace that uses udev might not necessarily match.

And there is another issue: AFAIK distributors handle at least parts of 
the udev configuration including rules.

Well other solution would be to guarentee that SYSFS_DEPRECATED works 
correctly in udev until it will be deprecated and remove in kernel source. 
But then you suggest it the other way around:

> Sure, there will be cut-off points (one of which you seem to have hit
> here), but in general it's a lot easier to ensure a kernel is
>  compatible with your current version of udev than ensuring random
>  upstream versions of udev are compatible with your userland
>  (especially if you're running the stable version of a distro).

I am running a mixture of Debian testing/unstable/experimental.

martin@shambhala:~> apt-show-versions | grep udev
libgudev-1.0-0/squeeze uptodate 146-5
libudev0/squeeze uptodate 146-5
udev/squeeze uptodate 146-5

martin@shambhala:~> cat /proc/version
Linux version 2.6.31.5-tp42-toi-3.0.1-04850-g4eddd0d (martin@shambhala) 
(gcc version 4.3.4 (Debian 4.3.4-5) ) #5 PREEMPT Sun Oct 25 18:39:35 CET 
2009

Anyway, I disabled CONFIG_SYSFS_DEPRECATED now.

Maybe its more about the discoverability of such issue: I don't look into 
the boot log / syslog every day. ;)

Hopefully upward incompatible changes in SysFS could be avoided in the 
future.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-10-25 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 17:33 Martin Steigerwald
2009-10-25 18:30 ` Frans Pop
2009-10-25 19:04   ` Martin Steigerwald [this message]
2009-10-25 19:33     ` Frans Pop
2009-10-25 22:37 ` Ben Nizette

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=200910252004.21546.Martin@lichtvoll.de \
    --to=martin@lichtvoll.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome