before I begin

Gerard Beekmans gerard at
Mon Oct 16 06:34:23 PDT 2000

> The official download location listed in the 2.4.2 appendix for is 
> still, so my question stands: What's special about 
> this package? It doesn't seem to make sense. Why would LFS's ldd be 
> different from that used by RedHat?

In a long gone past (ala LFS-1.3) I wasn't able to find an official
download location for So I downloaded the source package from
Debian and uploaded it to and left it there. I
never searched for a new one since.

Why didn't I point the book to Debian then? The package name seemed to be
changing from time to time so that would just be confusing for people
who aren't very familiar with the Debian package naming scheme.  

> Yes, of course but that doesn't answer my question. What I want to know is 
> why the book tells me to do
> make PREFIX=$LFS/usr install
> and then move files from $LFS/usr/bin to $LFS/bin
> instead of 
> make PREFIX=$LFS install

If you would do that, you would end up with man pages in $LFS/man and
info pages in $LFS/info and other stuff in $LFS/share

After you enter chroot your man pages would be located in /man/man1
instead of /usr/man/man and other files in /share instead of /usr/share

So we give a prefix of /usr so that all files end up in /usr/* but the
files from /usr/bin are then moved to /bin

But that has been changed in LFS-2.4.2 by passing the --bindir=$LFS/bin
to configure scripts. This only affects what happens in chapter 5 of the
book, so my suggestion download chapter 5, print it out and use it as an
errate or something like that. That way you don't have to print out the
almost 400 pages worth of LFS-book.

> > > c) Do I really need to distinguish between /bin and /usr/bin or can I just 
> > > make the latter a symlink to the former (or the other way around). After 
> > > all, I don't want a separate /usr partition. 
> > 
> > You don't have to, allthough don't expect you aren't going to have any
> > problems later down the road (and i do don't recommend you do that :)
> > but just because you have /bin and /usr/bin it doesn't mean you have two
> > partitions.
> If I don't have separate partitions for / and /usr, what kind of problems 
> could I get if I have /usr/bin as a symlink to /bin, or /bin as a symlink 
> to /usr/bin ?  The only possible problem I can see is if 2 programs with 
> the same name but different contents should be in the 2 directories. Is 
> there a package that does something like this, or a package that wants to 
> create a symlink from the one directory to the other automatically?
> I don't think this would be a proper action for an install script.
> > LFS is about choice and personal preference... it's only a guide, and
> > guides are meant, only as that; a guide, do you always follow a guide to
> > the letter? :)
> Exactly. But if you're going to leave the guide, it's best to ask about 
> possible problems first.
> > > d) Is it important that the kernel is 2.2.16? I have a 2.4.0 lying around 
> > > on my disk that I'd like to try out.
> > 
> > You can use any kernel version you want, 2.2.17 is the latest _stable_
> > kernel which is recommended, allthough quite a few ppl have build an LFS
> > system using 2.4.0test kernels, again, personal preference.
> > 
> > > e) I'd like to log everything I do. What's the easiest way to do that?
> > 
> > Wanna elaborate? do you just want to list which files go with which
> > package, or do you want to keep all your log files, or do you...?
> > 
> > We need a little more information before we can answer that =)
> I want to log the commands I enter like
> cd $LFS
> mkdir blabla
> cd blabla
> ...
> and maybe the output of those commands (although I'm not so sure I want 
> the complete output from a "make"). As you've already noticed I'm going to 
> deviate from the directions in the LFS book. 
> If (or should I say "when" :-) I run into problems it would be very useful 
> if I had a log of exactly what I did, especially if I should seek help on 
> this mailing list. If I can't state exactly what I did and what I did not 
> do according to the LFS book, people here most likely will not be able to 
> help me.
> ----
> Join the Army, meet interesting people, kill them.
> -- 
> Unsubscribe: send email to lfs-discuss-request at
> and put unsubscribe in the subject header of the message

Gerard Beekmans

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

Unsubscribe: send email to lfs-discuss-request at
and put unsubscribe in the subject header of the message

More information about the lfs-dev mailing list