How to incorporate LSB specifications

Gerard Beekmans gerard at
Fri May 19 17:57:50 PDT 2000


I just subscribed to this list so I guess a short introduction would be
in place.

I'm leading a project called LinuxFromScratch which, as the name says,
deals with the manual creation of a new Linux distribution. The
documentation on how to do this is written in the form of a book. There are a
lot of reasons why somebody would want to do this. 

One example is where somebody just wants to learn what makes Linux tick. 
By manually building your very own distribution from scratch (in a nutshell: 
from scratch as in  creating a partition, creating the ext2 file system, 
install a couple of  static programs to provide a development environment so 
that the rest of  the system can be build) and using nothing but the sources 
of programs you need (in no case pre-compiled packages are used. Everything 
is compiled manually: kernel, glibc, compiler, and all other stuff that's
used on a typical system).

Another example (which covers the main group of current users who are
using LFS, but was not LFS's original target) is the group of people who
aren't happy with their current distribution. Naturally a distribution
enforces certain standards which aren't always easy to change (the file
system structure, the way the boot scripts in /etc/init.d or
/etc/rc.d/ini.d or /sbin/init.d or other places). The LFS project offers
a change in that. Though the book is based on certain structures, the
reader has the chance to change it and even encourages this. This way
the reader gets the thrill of being able to say "this a system I build
myself and not some system installed from my xxx distribution's cdrom".
Also, the reader knows what's on the system, where is and why it is

And the list of examples could go on a while. But I'm not here to
promote LFS now. Although the reader is not forced to follow the
structure of things (directory structure, boot scrips structure, etc)
the way the book does it, we do want LFS to abide to certain standards
so that if somebody chooses to follow the Linux standards, he or she can
just follow the book. For example the directory structure (almost)
completely abides the FHS (2.0 - I haven't had the time yet to see if there
are any significant changes in FHS 2.1).

I guess you can see where this is leading to: I'd like to make a default
LFS system LSB compliant in areas where it isn't already LSB compliant.
How would I go about that?

Thanks for your time.

Gerard Beekmans

-*- If Linux doens't have the solution, you have the wrong problem -*-

More information about the lsb-discuss mailing list