On Fri, Mar 21, at 05:47 Bryan Kadzban wrote:
> Therefore, I believe that BLFS is fine installing stuff into
> /usr. But it depends on what you see as the definition of "the distro".
Yes, is a controversial material at the minimum and I guess we can also
interpret FHS differently and so on and so on... but I will try not to be
ambiguous in a desperate try to express my position with clarity
(doubtful). :)
Lets say that we started to write a book with just a blank page in our
editor. Lets say that we are building a system from scratch; to be precise
to build a system from a working host. The term scratch (in LFS title) is
little misleading. We don't actually building a system from scratch!
And lets say that we have all the prerequisites (and the desire) to build the
absolutely perfect system; we do, don't we? So we don't give a dime about
the difficulties we are going to meet in the road, because we know to write
code if we need to and because we know to read man pages. :)
At first, of course, we'll have to boot the system and to reach in the
logging prompt.
We don't care about network or other devices, we just need to find the
absolute minimum build method, so to have a working shell and to be able to
mount the filesystems.
The executables and the libraries that we'll need for that purpose is the
/ (root filesystem), i.e.,
/bin /sbin /etc /lib /proc /dev /sys /var (and maybe /boot)
And actually this is the first page of our new book.
Can we do it by using only the shell?
Can we do it without e.g., coreutils (just an example),
or with just a small portion of it.
Can we do it without vim? Yes, we can, because we have ed and we know how
to use ed, aren't we? :)
Can we do it without Bash? Wow, then my hidden dream will come to be true.
Excellent, lets now turn to the second page to our new book.
We want to have a functional system and we need to "speak" to our hardware.
We want our network, our sound, our printer, our scanner and finally, YES,
we want to view some images (yes I know we can do it with framebuffer) but we
want also to start clicking buttons (small buttons, huge buttons, gold
buttons - all kind of buttons). [For what is worth, I am using X for the fonts,
for the clipboard, the clientserver facilities in Vim and the kind of windows
manipulation that wmii offers me.]
So we start to build the relative software.
Alsa, cups, sane and finally, YES, X.
Okey this is our half of our second page and the half of: /usr/bin /usr/sbin
/usr/include /usr/lib /usr/share /usr/etc (although the last item is debatable)
The other half is:
I. Security software,
- a SSL/TLS implementation
- pam
etc...
II. Network services and servers,
- Apache
- Openssh
- Mailserver
etc...
III. Databases and languages
- Python
- MySql
etc...
IV. System Administration Tools
- Reiserfs
- Fcron
etc...
Enough!
I might be missing something because is early morning :).
Everything else belongs (for me, I repeat it, for me) in /usr/local
hierarchy.
It might be worths to mention in that point, that in a try to distinguish
the software in three levels of a accessibility, *independently* of the
hierarchy, I found that info very promising.
http://blog.flameeyes.eu/articles/2008/02/18/capabilties-and-pam
--
http://wiki.linuxfromscratch.org/blfs/wiki/Hacking
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
