id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
2196	LSB compliance for LFS	DJ Lucas	bdubbs@…	"This ticket serves as a staging area for LSB compliance strictly WRT LFS, as most of the unmet LSB compliance issues will fall into BLFS territory.  Please append any LSB issues that fall into LFS book territory to this ticket.

For LFS, the only bit I have to add ATM are the boot scripts. Distribution provided boot scripts are not strictly required to use the LSB provided functions for LSB compliance.  In fact, the lsb-v3 scripts that I've been working on do not (or rather, not directly).  They use helper functions provided by the distro functions file (/etc/init.d/lfs-functions) that provide easy to use, convenience wrappers around the LSB functions.  However, I would still prefer that the scripts in contrib/lsb-v3 be considered for LFS mainstream.  At this time, they require only minor cleanups, and for the BLFS side, I have about ~70% of them written and in use already, though I've never added a contrib directory for them in BLFS due to naming conventions and size concerns.  

I also know that Dan Nicholson is working on an implementation of install_initd and remove_initd programs written in C, but I unfortunately do not know the current status of that endeavor.  However, once a stable release is created, these should also be considered for inclusion into LFS rather than BLFS, and perhaps the bootscripts makefile could also be retooled to use the new tools as soon as they are installed.

I will also be opening a few related future bugs in BLFS Trac concerning some other items that I am aware of including the bootscript naming collisions I mentioned above (NTP/setclock/$time, apache/httpd, etc.).
"	task	closed	normal	6.6	Book	SVN	normal	fixed