Archaic wrote these words on 08/06/05 14:07 CST: > On Sat, Aug 06, 2005 at 01:41:32PM -0500, Randy McMurchy wrote: > >>The login.def file is installed in LFS, not BLFS, so the BLFS >>instructions wouldn't recreate this file (though it would be simple >>to do so, and maybe we should). >> >>So, there's a couple of things we can do. >> >>1) Move the login.def changes up in the instructions *and* install >>the default login.def file during the installation section of Shadow, >>or, >> >>2) Add some text to the warning message that some of the configuration >>errors are expected. > > > If it is assumed that PAM isn't being added at any time other than > during initial LFS or immediately thereafter, then #1 is possible. > However, if login.def was modified by a user prior to hitting BLFS, then > user added customizations would be lost.
Yes, and I forgot to mention that in my previous message when I was explaining why it is at the end of the Shadow instructions. However, making a copy of the existing login.def file is elementary and would at least preserve the existing file before it is overwritten. That way a guy would at least have whatever changes he made before installing PAM and reinstalling Shadow. Let's stay on top of this discussion, because whatever we decide to do needs to go into the 6.1 book, which is due to be released in a couple of days. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 14:10:01 up 126 days, 13:43, 2 users, load average: 1.28, 1.05, 0.59 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
