LFS 5.1.1 takes me 5 hours on my Mobile Pentium 4 1.6ghz (512RAM), 4 hours on my AMD athlon-xp 1600 1.4ghz (512RAM), and 6 hours on my friends Pentium 4 2.0ghz (256RAM).
(Double the time when using BLFS in addition to LFS)
Notice how the one with the lower RAM is much slower than the slower systems with more RAM.
How fast you install depends more on your ram than your architecture. All the RAM i tested was 233 bus speeds. Anything slower will make a significant impact.
-----------------
As far as burning an image. I prefer to tar.bz2 it. That way all of the file permissions is saved and it is compressed so I can put a lot more data into the cd-rom. (There probably is a way though for mkisofs to preserve file permissions, but my concern is when mounting, but once again I imagine there is a way around that too...being Linux and all..)
as
root in
/ I ran:
Code:
tar -c bin dev etc home lib root sbin usr var > tar.tar && bzip2 -c tar.tar > lfs-pentium4.tar.bz2 && rm tar.tar
*tar doesn't like grabbing /proc, but /proc doesn't matter as it's mounted & managed by the kernel (as far as LFS-5.1.1) /tmp is pointless to grab, and I don't use /opt, add /boot if you compiled a generic kernel image..
Doing this also allows you to fit 2+gigs into a cd-rom. Thanks to Bzip Compression. (Just LFS alone a 570+ meg space taker compresses to 110+ megs)
------------------
To use mkisofs and make it Windows Friendly (Joliet), I use something like:
Code:
mkdir /lfs-pentium4 && mv /lfs-pentium4.tar.bz2 /lfs-pentium4 && \
mkisofs -iso-level 3 -J -l -o lfs-pentium4.iso /lfs-pentium4
Anything can be added to the
/lfs-pentium4 directory, which represents the root of the cd/iso image.
For cdrecord (dev=0,0,0 is the tricky part...its system dependant):
Code:
cdrecord -eject -v dev=0,0,0 lfs-pentium4.iso
Once I've done that I can format a new partion on my hard drive, untar/unbzip the cd into the blank harddrive.
* This method will not work on a system that doesn't already have Linux on it.
- of course if you have a bootable linux, this can work! and it is better to tar/bzip2 the file if not running on that system, that way you can use * and not worry about proc..
