>From: Dan Nicholson <[EMAIL PROTECTED]>
>First thing to note is that what's in LFS isn't supposed to be a
>feature complete system. It tries to create a general development
>system for you to build on. So, if links needs to be part of your base
>install, you shouldn't feel like you're doing something wrong. My
>"base install" is considerably larger than what's in LFS since my
>barrier for "minimum for usability" is higher. Nothing wrong with
>that.
That's true but if you're new to Linux then you need BLFS before installing
anything. Because you have long-time experience with Linux you're forgetting
the chapter in BLFS that deals with post-LFS configuration issues. I could very
well be wrong here but I suspect those with more experience will set up users
and do other configuration tasks as soon as possible before finishing LFS to
limit time spent as root. If an individual already knows these things then why
would that person wait?
Most new users on the other hand will only do these things once they get to
BLFS.
I suppose I could copy-paste chapter three or perhaps all of part II to a text
file then read it using less. Then I would be able to switch to a
non-privledged user to safely poke around the system and ultimately build links
(and/or any other packages) to finish reading BLFS. Even simpler, continue
using the host system and chroot into LFS and do all these things. However,
these are quick work-arounds and not a permanent fix. If I have just created a
bootable, albeit incomplete, system, why can't I immediately start reading BLFS?
>If you're experimenting with a package manager, it may be best to just
>install the needed tools now and just overwrite them once you get your
>actual packages in place. Not ideal, but you can always smooth the
>edges for the next run.
Sure, that's not a problem. The problem is doing all this as root. See above.
>As an aside, what's the difference between less and links? I.e., why
>is it OK to have less be an unpackaged part of LFS, but links must be
>a pacman package? I guess that sort of goes back to the first thing I
>said: the borders of LFS are blurry at best.
Actually, I have plans to go back and package chapter 6 (and possibly chapter
5) of LFS once I learn more about building Linux systems. Also, I stated
earlier that it would best to have BLFS in info page format not a generic text
file readable using less.
>From an earlier post on this thread:
I don't really understand why BLFS is not available in
info format so you can easily read it in a fresh LFS
Walter
____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
