From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Subject: udev in kernel source?
Date: Sun, 25 Oct 2009 18:33:55 +0100 [thread overview]
Message-ID: <200910251834.06321.Martin@lichtvoll.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
Hi!
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?
shambhala:/var/log> grep -i deprecated syslog | grep udev
Oct 25 09:41:22 shambhala udevd[21078]: udev: missing sysfs features;
please update the kernel or disable the kernel's CONFIG_SYSFS_DEPRECATED
option; udev may fail to work correctly
Oct 25 09:41:37 shambhala kernel: <3>udev: missing sysfs features; please
update the kernel or disable the kernel's CONFIG_SYSFS_DEPRECATED option;
udev may fail to work correctly
Oct 25 13:35:10 shambhala kernel: <3>udev: missing sysfs features; please
update the kernel or disable the kernel's CONFIG_SYSFS_DEPRECATED option;
udev may fail to work correctly
It seems that nothing critical is not working, but I only found this by
closely watching the boot process at all.
Granted, for a long time I did not see any udev/kernel version mismatch or
configuration option mismatch issues, but back in udev early days I were
hit several times by those annoyances.
Ironically I was about to disable CONFIG_SYSFS_DEPRECATED when it was
introduced, but then HAL didn't work.
There should be an easy way to figure out whether kernel and deeply related
userspace tools are matching each other.
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 --]
next reply other threads:[~2009-10-25 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 17:33 Martin Steigerwald [this message]
2009-10-25 18:30 ` udev in kernel source? Frans Pop
2009-10-25 19:04 ` Martin Steigerwald
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=200910251834.06321.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 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.