Re: [TiLP-devel] ti-89 titanium with tilp-2 svn

[Kevin K. <kev...@ch...>]

> The good part of this is that (from what I've seen anyway) RH
> derivatives tend to standardise on pam.  So the RPMs for them can be
> built like Kevin does and the problem goes away.  There really are
> only two other options: hotplug and udev.

Be careful, there are more possible combinations than you think:
* current udev + pam_console (This is what Fedora uses.)
* older udev + hotplug + pam_console
* devfs + hotplug + pam_console
* plain old devices + hotplug + pam_console
* devfs without hotplug + pam_console
* plain old devices without hotplug + pam_console
* current udev without pam_console (This is what Gentoo uses by default.)
* older udev + hotplug without pam_console
* devfs + hotplug without pam_console
* plain old devices + hotplug without pam_console
* devfs without hotplug without pam_console
* plain old devices without hotplug without pam_console
(Some of these might not be workable in practice or possible but unused. But 
in principle they could all exist.)

Also note that using PAM doesn't necessary imply using pam_console. PAM is 
designed to be modular, so distros get to pick the modules they enable by 
default. And pam_console isn't even included in upstream PAM, it's a module 
developed by Red Hat, Fedora is apparently the upstream for it (at least the 
Gentoo pam_console ebuild gives a pointer to the Fedora CVS as the upstream). 
Almost all distros use PAM these days (I think even Slackware uses it now!), 
but this doesn't mean they use the pam_console module. Whether they use PAM 
without pam_console or no PAM at all doesn't really matter when it comes to 
setting device permissions.

        Kevin Kofler