2009/9/19 Bruce Dubbs <bruce.du...@gmail.com>: > I've been investigating the Linux Standards Base core specification. > > http://dev.linux-foundation.org/betaspecs/booksets/LSB-Core-IA32/LSB-Core-IA32.html#REQUIREMENTS > > 1. Looking at the required libraries, I see that libncurses.so.5 is required. > We have libncursesw.so.5 and libcurses.so.5. I think we may also need to add > a > symlink: > > libncurses.so.5 -> libncursesw.so.5
Confirmed - alsa-mixer needs it on my boxes. > > 2. To meet the spec, we also need to add a symlink: > > For ia32: > /lib/ld-lsb.so.3 -> /lib/ld-linux.so.2 > > For amd64: > /lib64/ld-lsb-x86-64.so.3 -> /lib64/ld-linux-x86-64.so.2 > This part seems to only tick a box . I suppose it's a way of not having to know the real name (for different architectures), but I don't understand how it would be supposed to work - if it's for binaries, they've still got to be compiled for the correct architecture. > 3. For the full spec, we also need libpam. Does this LSB core requirement > justify promoting PAM from BLFS to LFS? > > Comments? > > -- Bruce My antipathy to PAM is known. After Simon's comment the other month that all the distros use it, I started to consider adding it, but chickened out because too much could go wrong if it didn't spend time understanding the detail of it. I agree with your follow-up (page in LFS introducing LFS, anything else in BLFS). ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
