You are not logged in.
I have been helping out on the IRC about some odd behaviour right after the arch-chroot step of the installation guide.
pacstrap command in question:
pacstrap -K /home/sysghost/Temp/archtest-DELETE base linux linux-firmware amd-ucode nano
Log of the pacstrap process: https://bpa.st/OFTQ
Then I proceed with:
arch-chroot /mnt /bin/bash
[sudo] password for sysghost:
[root@scraptop /]# passwd
passwd: Module is unknown
passwd: password unchanged
[root@scraptop /]# cat /etc/pam.d/chpasswd
#%PAM-1.0
auth sufficient pam_rootok.so
account required pam_permit.so
password include system-auth
[root@scraptop /]# cat /etc/pam.d/passwd
auth include system-auth
account include system-auth
password include system-auth
[root@scraptop /]# file /lib/security/pam_{unix,permit,rootok}.so
/lib/security/pam_unix.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=9b0fa2857bc61aa87d4f3f616c5317bdec782a31, stripped
/lib/security/pam_permit.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=b45d5b9a91c27c4d71ef139ea9f7c9587ccaf2d6, stripped
/lib/security/pam_rootok.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=3c80e4a5de157624d5375dbc4ab16589f1230a1c, stripped
EDIT: Snipped from the IRC log. Looking into this ...
[09:16:37] <rcf> Ah, yes, this is indeed an issue.
[09:21:38] <rcf> workaround: don't arch-chroot, systemd-nspwan -D
[09:22:13] <rcf> so it's an arch-chroot issue.
[09:26:40] <rcf> With that passwd works fine
So what's going wrong with arch-chroot btw?
EDIT 2:
Welp. Seems the nspawn has the same issue. Wrong rabbit hole.
Last edited by SysGhost (2024-04-12 08:40:41)
Offline
You pacstrap to /home/sysghost/Temp/archtest-DELETE, but arch-chroot into /mnt?
Offline
You pacstrap to /home/sysghost/Temp/archtest-DELETE, but arch-chroot into /mnt?
Yeah ... sorry about that. Did multiple independent clean tests to make sure. Ignore the different paths. All ends up in the same end.
Offline
IRC #archlinux came with a remedy:
[09:51:59] <SysGhost> rcf: well... no go! "systemd-nspawn -D /mnt" ... same result: passwd: Module is unknown
[09:53:22] <rcf> SysGhost: let me try again. Maybe it's a weird timing bug
[09:57:48] <rcf> Well how the fuck did I do that
[10:10:16] <SysGhost> Magic!
[10:11:06] <grawity> pacman -S --asdeps libnsl
[10:11:13] <rcf> That's whatI did.
[10:11:32] <rcf> Not even intentionally, but trying to debug passwd
This is the magic bean that solves everything:
pacman -S --asdeps libnsl
Thanks grawity! \o/
Question: Should libnsl be part of base? Or are we required to include it in the pacstrap command from here on?
Offline
Question: Should libnsl be part of base? Or are we required to include it in the pacstrap command from here on?
Neither, it should be a dependency on the pam package – it's a packaging issue (the libpam build process unexpectedly autodetected libnsl when 1.6.1 was being built). 1.6.1-2 is already in testing with the fixed dependencies.
Last edited by grawity (2024-04-11 08:55:18)
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline