From: Bruno <bonbons67@internet.lu>
To: gentoo-dev@lists.gentoo.org
Cc: zzam@gentoo.org
Subject: Re: [gentoo-dev] About udev-145: new features / extras and kernel requirements
Date: Sun, 30 Aug 2009 17:05:05 +0200 [thread overview]
Message-ID: <20090830170505.150f6242@neptune.home> (raw)
In-Reply-To: <200908301611.53087.zzam@gentoo.org>
On Sun, 30 August 2009 Matthias Schwarzott <zzam@gentoo.org> wrote:
> The new udev-145 and newer have some new kernel requirements. How
> should the ebuild verify they are met?
> Some possible ways:
> 1. Check config under /usr/src/linux
/usr/src/linux is not the best place to look at...
Checks should rather be done on first kernel config found in following
locations (checked in this order):
- KBUILD_OUTPUT
- KERNEL_DIR
- /usr/src/linux, /proc/config.gz, /lib/modules/$(uname -r)/build/.config
Maybe just use linux-info eclass for the checks
> 2. Check /proc/config.gz
This should rather happen in init script, if possible do not check
on every boot but only when a "new" kernel is used (e.g. when uname
output changes)
> 3. Print message for user in pkg_postinst
This makes sense in any case.
> Second point: udev-145 bundles a lot of new extras, but they can only
> be enabled/disabled all or nothing.
>
> These extras are:
> * udev-acl: Apply consolekit permissions to devices for users (audio,
> video, joysticks, scanner, cameras, ...)
Is this bound to consolekit or does it rather fall under 'acl' use-flag?
I guess this includes a kernel requirement (ACL support for tmpfs)
> * usb-db: Provide udev-rules with device names of pci and usb devices
> * hid2hci: Special utility to fix resume of some hid devices
> * keymap: Auto-configure model specific keys found on many laptops
> ("brightness up", "next song", "www browser", or "suspend")
> * modem-modeswitch: Switch modems that provide virtual cd-drive with
> drivers to modem mode
> * gudev: glib/gobject support for libudev
Is gudev just a binding or is it more? If it's just a binding it may
be nice to have it tied to a use-flag.
> This makes udev depend on these libs:
> libacl, libglib2, libusb, usbutils, pciutils, gperf
Bruno
next prev parent reply other threads:[~2009-08-30 9:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 14:11 [gentoo-dev] About udev-145: new features / extras and kernel requirements Matthias Schwarzott
2009-08-30 14:24 ` Arun Raghavan
2009-08-30 15:26 ` [gentoo-dev] " Duncan
2009-08-30 14:46 ` [gentoo-dev] " Nirbheek Chauhan
2009-08-30 15:45 ` William Hubbs
2009-08-30 16:18 ` Mike Auty
2009-08-31 15:46 ` Jeremy Olexa
2009-08-31 4:25 ` Lars Wendler
2009-08-30 15:05 ` Bruno [this message]
2009-08-30 19:20 ` Robin H. Johnson
2009-11-09 16:35 ` Mart Raudsepp
2009-11-12 9:08 ` Matthias Schwarzott
2009-11-09 19:22 ` Daniel Drake
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=20090830170505.150f6242@neptune.home \
--to=bonbons67@internet.lu \
--cc=gentoo-dev@lists.gentoo.org \
--cc=zzam@gentoo.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