🚀 go-pugleaf

YARD now overcomes the RH4.2 pam at login problem I was experiencing.

Much thanks Bruce for your solution and assistance.

Grahame. (original poster with the Yard problem).


Bruce Tulloch <bruce@causal.com> writes:
>It's relatively simple.
>
>Include
>
>/etc/pam.conf   <= ./Replacements/etc/pam.conf
>/lib/security/pam_unix_auth.so
>/lib/security/pam_unix_acct.so
>/lib/security/pam_unix_passwd.so
>/lib/security/pam_unix_session.so
>
>in your Bootdisk_Contents file and
>
>OTHER auth     required /lib/security/pam_unix_auth.so
>OTHER account  required /lib/security/pam_unix_acct.so
>OTHER password required /lib/security/pam_unix_passwd.so
>OTHER session  required /lib/security/pam_unix_session.so
>
>in Replacements/etc/pam.conf
>
>Cheers
>
>-bruce
>
>*** complex problems have straight forward easy to understand wrong answers *** 
>> I have been trying to build a Yey Another Rescue Disk (YARD) disk using
>> yard-1.12a. I have used YARD (previous releases) with problem before, so
>> I get the problem is what I have left out of the /etc/yard/Bootdisk_Contents.
>> 
>> Let me first define my problem: 
>> -------------------------------
>> 
>> Built make_root_fs, check_root_fs, write_rescue_disk - OK, no errors.
>> When I boot the YARD boot disk, all OK. Loading the boot ramdisk image, OK.
>> I get the login prompt to login as root. I login as root and get the following
>> message;
>> 
>> "Jul 9 13:14:00 pam[21] no modules loaded for login service"
>> 
>> 
>> What I have tried todate:
>> -------------------------
>> 
>> I have included all the /etc/pam.conf and /etc/pam.d and /lib/security/* files.