On 6/25/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
Dan Nicholson wrote these words on 06/25/06 13:26 CST:
> If anyone is interested in pam_console, let me know. It's not
> difficult to get set up. Debian has also created pam_foreground which
> is very similar. I haven't tried it yet.
I'm guessing that in order to use pam_console, the system must be
set up with Linux-PAM already, right?
Yes. It's just another module.
And if so, is it worth trying to put a mention (with instructions)
of pam_console on the Linux-PAM BLFS page?
I think so.
The last thing we probably want to do, though, is have to provide
two sets of instructions for GVM (one with pam_console, one without).
There really isn't any difference besides the one configure switch.
Basically, when you build with --disable-multiuser, all the functions
in g-v-m that check /var/run/console return true. So, having
pam_console just allows g-v-m some additional checks about whether the
current user can invoke methods, etc.
I'm asking you for your opinion on this one, Dan. I will be the first
to admit that I (like DJ) haven't bothered to learn the details of
all this stuff yet.
pam_console is really simple. It just says which user is currently at
the console by touching files in /var/run/console. They're just
trying to address the situation of having multiple logged in users and
who's got control of the hardware.
My biggest thing was seeing how KDE responded to the new HAL/DBUS
setup and if there was any major shakeup on the KDE side. And, BTW,
there didn't appear to be any, so that is when I decided to go with
the new HAL/DBUS for BLFS-6.2
I have no idea how that's going to go. I think kio does a lot of this
stuff itself, but in KDE 4 they will move to doing more things through
HAL/DBUS.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
