On Mon, Dec 09, 2013 at 12:01:32PM +0100, Jean Delvare wrote:
Hi Marcus,
Le Monday 09 December 2013 à 11:29 +0100, Marcus Meissner a écrit :
On Sun, Dec 08, 2013 at 06:42:19PM +0100, Jean Delvare wrote:
So I am really curious why these are installed by default. What do I get from having systemd-32bit, samba-32bit, pam-32bit etc. installed on a 64-bit system?
The PAM configuration is agnostic to biarch, it actually is for both.
Thats why all packags with PAM modules Recommend their -32bit equivalent.
Otherwise you might find missing PAM snippets if there is ever a 32bit program trying to do PAM.
But wouldn't that program be responsible for requiring pam-32bit then? Actually it seems to be the case, for example systemd-32bit does require pam-32bit. So this explains why pam-32bit is installed.
What I really need to know is what systemd-32bit itself is good for. Nothing requires it, and the package description doesn't say anything about that sub-package specifically. Same for samba-32bit.
Well yes, but all the PAM modules are not required by main PAM package... So main PAM does not know about the systemd pam module, or about the opie pam module or the samba-winbinds pam module or the ecryptfs pam module. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org