You are not logged in.
Pages: 1
I recently set up fprint for login and sudo for my laptop. I installed pam-fprint-grosshack along with it, but I don't like the default prompt of "Enter password or Place finger on fingerprint reader." Is there a way I can change this to "Enter authentication" or something similar? Thank you!
Edit: my shell is fish if that's relevant at all
Last edited by babel_f1sh (2024-01-31 01:45:36)
Offline
Offline
Thanks! I'm having trouble rebuilding the program though. The commands in the README don't work and the ones given in Meson's docs don't either. I'm fairly new to compiling so I'm not sure what I might be missing.
Offline
Thanks! I'm having trouble rebuilding the program though. The commands in the README don't work and the ones given in Meson's docs don't either. I'm fairly new to compiling so I'm not sure what I might be missing.
Nevermind, I figured it out.
Offline
I recompiled the package, but how do I find the "correct directory" to move the pam_fprintd_grosshack.so to? I see some .so files in /usr/lib but when I install the package from the AUR it isn't located there.
Offline
You probably should apply the patch as part of the PKGBUILD you got from the AUR so that all files are properly tracked, but for a stop gap test look at where the AUR package placed the file
pacman -Ql pam-fprint-grosshackOffline
You probably should apply the patch as part of the PKGBUILD you got from the AUR so that all files are properly tracked, but for a stop gap test look at where the AUR package placed the file
pacman -Ql pam-fprint-grosshack
I see, so it goes in /usr/lib/security/. Thank you! How would I apply the patch? It seems to work fine by just uninstalling the AUR package and building it from source instead.
Offline
No, you build the AUR package and add the patch to the PKGBUILD
Offline
No, you build the AUR package and add the patch to the PKGBUILD
I'm not really sure how to do that. Is there a particular reason why this would be a more proper method?
Offline
You're installing and managing packages w/ the package manager and it will allow proper dependency management as well as later removal, updating etcetc.
All you have to do is to add the name of the patch file to the source array of the PKGBUILD, maybe a secon 'SKIP' to the sha256sums and rebuild the package.
Offline
You're installing and managing packages w/ the package manager and it will allow proper dependency management as well as later removal, updating etcetc.
All you have to do is to add the name of the patch file to the source array of the PKGBUILD, maybe a secon 'SKIP' to the sha256sums and rebuild the package.
That first part makes sense, I struggled with the second though. I tried the guide in the first section here https://wiki.archlinux.org/title/Patching_packages but it didn't apply my patch. I ended up running "makepkg --nobuild," editing the file in the src directory, and then running "makepkg --noextract --install." I'm not sure if this is a proper method but I'm able to remove the package with pacman if need be. The only potential issue I've noticed is there is no output for "whereis pam-fprint-grosshack."
Last edited by babel_f1sh (2024-01-30 19:28:57)
Offline
You can just clone the AUR, add the patch and edit the PKGBUILD and run makepkg as usual.
If you need the sources to generate the patch first, you can or not first run it --nobuild to obtain them (though I think gitlab allows you to create patches using their webinterface)
For clarification:
You're NOT supposed to edit the sources in place but add a patch file to the local sources and reference that in the PKGBUILD.
You're also not getting "whereis pam_unix.so" because whereis doesn't search /usr/lib/security/ - so nothing to worry there.
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
You can just clone the AUR, add the patch and edit the PKGBUILD and run makepkg as usual.
If you need the sources to generate the patch first, you can or not first run it --nobuild to obtain them (though I think gitlab allows you to create patches using their webinterface)
For clarification:
You're NOT supposed to edit the sources in place but add a patch file to the local sources and reference that in the PKGBUILD.You're also not getting "whereis pam_unix.so" because whereis doesn't search /usr/lib/security/ - so nothing to worry there.
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.
I appreciate all your clarification, thanks. I'm having a bit of a hard time wrapping my head entirely around the process for building and patching packages, but I guess that'll come with practice. Are there any guides you'd recommend? I'll be sure to look through what the wiki has to offer more too.
Offline
The wiki you linked is the most relevant guide.
If you plan to patch a lot and dynamically, a prepare() routine like in https://gitlab.archlinux.org/archlinux/ … =heads#L67 will come handy.
Offline
Pages: 1