On Mon, 2008-03-24 at 18:26 +0000, Mario Limonciello wrote:
> The udev rules file is generated dynamically at package build time. What in the changelog between our package and debian's latest fixes it?
>
I see
debian/rules: Do not install the udev rules, since hal now provides
dynamic ACLs on device nodes. (See hardy-hardware-detection spec.)
Device ownership: Make removable USB devices (scanners, cameras,
external hard disks, etc.) accessible to the user on the current
foreground console instead of providing static udev rules and using
group membership based access control.
Then the current set of fine-tuned udev rules and large lists of
autogenerated udev rules for model-based vendor/product ID matching can
disappear entirely, and the access control will work for e. g. future
scanners or cameras, too.
and
Drop the default system groups plugdev and scanner. Enable ConsoleKit
support in hal, which assigns read/write permission to removable USB
devices with dynamic ACLs.
* As a followup to above, drop the long vendor/product ID based
udev rules of libgphoto and libsane. Ensure that their preinsts
remove the obsolete conffiles on upgrade.
* Drop the default system groups netdev and powerdev, drop our
in-house development libpam-foreground, drop the network-manager
and gnome-power-manager patches to query libpam-foreground.
Instead, do the "user is in foreground session" test with
PolicyKit rules.
so I think this is actually something that should be fixed in hal.
On Mon, 2008-03-24 at 18:26 +0000, Mario Limonciello wrote:
> The udev rules file is generated dynamically at package build time. What in the changelog between our package and debian's latest fixes it?
>
I see
debian/rules: Do not install the udev rules, since hal now provides detection spec.)
dynamic ACLs on device nodes. (See hardy-hardware-
in the sane-backends changelog, which leads me to
https:/ /wiki.ubuntu. com/DesktopTeam /Specs/ HardyHardwareDe tection
and
Device ownership: Make removable USB devices (scanners, cameras,
external hard disks, etc.) accessible to the user on the current
foreground console instead of providing static udev rules and using
group membership based access control.
Then the current set of fine-tuned udev rules and large lists of
autogenerated udev rules for model-based vendor/product ID matching can
disappear entirely, and the access control will work for e. g. future
scanners or cameras, too.
and
Drop the default system groups plugdev and scanner. Enable ConsoleKit
support in hal, which assigns read/write permission to removable USB
devices with dynamic ACLs.
* As a followup to above, drop the long vendor/product ID based
udev rules of libgphoto and libsane. Ensure that their preinsts
remove the obsolete conffiles on upgrade.
* Drop the default system groups netdev and powerdev, drop our
in-house development libpam-foreground, drop the network-manager
and gnome-power-manager patches to query libpam-foreground.
Instead, do the "user is in foreground session" test with
PolicyKit rules.
so I think this is actually something that should be fixed in hal.
Thanks,
James