Christian Holzberger wrote: > hi, > > iam new to gobolinux and this list so tread me like a noob :-D > > i see some problems with pam.d and the way filesystem linkage works > > programms that use pam.d install their own /etc/pam.d (on sysv fslayout) > authentication scripts, in gobo it will > be /Programs/Linux-PAM/Settings/pam.d/. > > the way programms normally install they install their new pam scripts > directly into the pam directory. > > if i install a programm that needs pam.d i cant just add > Settings/pam.d/thenewscritp to the programm using pam (it wont get > linked where it should), i think it is that way because /etc/pam.d > or /System/Settings/pam.d is linked directly (and unique) to the > Linux-PAM folder. > > > if there is an issue with such situations it has to be solved genarally > and not just for libpam. a one to many configuration folder should > always be possible. > > greetings from germany, > C. Holzberger > > > > -- > Christian Holzberger > MOSAIK Software > [EMAIL PROTECTED] > > > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel@lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > > I'm not a dev, but I believe that what you're saying is already true in GoboLinux. The same happens with aclocal files, which are all added to the /S/L/Shared/aclocal folder, so that every program has its own subdir inside it. I think that pam would work the same way: a program would add its scripts in its own Settings/pam.d folder and then this would be linked against /S/S/pam.d, resulting in a new symlink within it, pointing at the program folder. But maybe this is valid for the Shared tree only.
Bye _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
