This is for development, to package up the latest build to be installed below

This is how to install the final build on your machine (Install my own custom distro). The idea is to simply download my root directories tar.gz and extract it to your partition then setup grub...

1. Boot the ArchLinux Installer Live CD
2. aif -p partial-configure-network
3. Use cfdisk to make your partitions, I will do a small swap on sda1 and the remainder / on sda2, you can substitute to your desire
4. mount /dev/sda2 /mnt; cd /mnt
5. wget http://mreschke.com/files/lfs/i686/build/lfs-current.tar.gz
6. tar -xzvf lfs-current.tar.gz
7. Edit /mnt/etc/fstab with the correct root, swap... partitions
8. Edit /mnt/etc/resolv.conf or copy over from LiveCD
9. Edit /mnt/etc/sysconfig/ifconfig.eth0
10. Edit /mnt/etc/udev/rules.d/70-persistent-net.rules and remove those eth0 lines
11. Enter the new environment (chroot) with:
    chroot

    mount -v --bind /dev /mnt/dev
    mount -vt devpts devpts /mnt/dev/pts
    mount -vt tmpfs shm /mnt/dev/shm
    mount -vt proc proc /mnt/proc
    mount -vt sysfs sysfs /mnt/sys
    chroot /mnt /usr/bin/env -i HOME=/root TERM="$TERM" /bin/bash --login
     

12. Setup grub: See http://mreschke.com/files/lfs/manual/7.0/chapter08/grub.html
    1. STILL WITHIN CHROOT
    2. /usr/sbin/grub-install /dev/sda adjust to whatever partition you want, sda is MBR, sda2 is partition...etc (usually MBR unless you multiboot)
       1. If you get buffer IO errors on fd0 (your floppy), just delete the fd0 line from your /boot/grub/device.map (thats from in the chroot) then run with grub-install /dev/sda --no-floppy
    3. Make a simple /boot/grub/grub.cfg file like so:
       /boot/grub/grub.cfg

       cat > /boot/grub/grub.cfg << "EOF"
       # Begin /boot/grub/grub.cfg
       set default=0
       set timeout=5
       insmod ext2
       set root=(hd0,2)
       menuentry "GNU/Linux, Linux 3.1-lfs-7.0" {
               linux   /boot/vmlinuz-3.1-lfs-7.0 root=/dev/sda2 ro
       }
       EOF
        

13. Exit chroot
14. Unmount everything mounted in the chroot command above including /mnt itself
15. Reboot and enjoy the mReschke lfs-current build of LFS 7.0!
16. The root password of this LFS build is techie
17. Thats it! You have a fresh LFS base, now there are a few optional things to configure
    1. PATH=$PATH:/usr/local/bin
    2. port update
    3. mkdir /root/build
    4. cp -rf /var/ports/port /root/port; cd /root/port; port install
    5. cp -rf /var/ports/lfs-profile /root/build; cd /root/lfs-profile; port install
    6. Logout and back in, should now have all your profile stuff (~/.bashrc, /etc/profile...)
    7. Install Sudo cp -rf /var/ports/sudo /root/build; cd /root/sudo; port install
       1. Edit the /etc/sudoers and uncomment what you want (I like the wheel no passwd one)
    8. Create user mreschke
       1. groupadd -f -g 1000 wheel
       2. groupadd -f -g 1001 users
       3. useradd -g wheel -G users -m -N -s /bin/bash mreschke
       4. passwd mreschke

All build files are at /nwq/admin/www/data/mrcore_files/lfs/i686/build/ or http://mreschke.com/files/lfs/i686/build/
All versions here are LFS 7.0 i686

1. lfs-1.0.tar.gz - Initial build, just after last page in the LFS 7.0 manual except does NOT contain grub and you must edit fstab because it points to sda13 (my qdesk partition)
2. lfs-1.0.1.tar.gz - Initial build + wget (bc, openssl, nettle, gnutls, wget). Plus /etc/port.conf and /usr/local/bin/port. Ready to start porting!

These are NOT my main deployable build backups (those would be in the i686/build directory like lfs-1.0.1-tar.gz...)
These are backups of different stages during the actual building of the LFS system itself.
All backups are in /nwq/admin/www/data/mrcore_files/lfs/i686/backups/

1. backups/01-TempSystem - This is the recommended backup of the Temporary System, this is not a working system. This was taken right at this page http://mreschke.com/files/lfs/manual/7.0/chapter05/changingowner.html
   1. If you wanted to start back at this point you would have to follow most of the mounting docs found before that spot in the manual! Remember - GCC 4.6.2
   2. Remember that to build this TempSystem and the Actual system with chroot I always use the export MAKEFLAGS='-j 4' to utilize my quad-core CPU.
2. backups/02-BuildLFS - This is just after the actual Build of LFS, before any boot scripts or kernel. The source and tools directories are still in there. This is the best place to start fresh, perhaps build your own boot scripts... This is right at this point http://mreschke.com/files/lfs/manual/7.0/chapter07/introduction.html. Remember GCC 4.6.2 and everything is from the chroot, so mount it up properly.

I removed the LFS /usr/share/doc/* and /tools and /source directories after the final page in the LFS 7.0 manual since they are not needed for an actual deployment. Those files are in NOT on /nwq but in archdev /home/mreschke/Projects/lfs/lfs-final-source-tools-backup

I have decided to leave the base LFS (my sda13) pretty much bare. Basically just after the last page in the LFS 7.0 manual I only basically only do the following to my sda13 base
# install bc
# install openssl
# install nettle
# install gnutls
# install wget

In other words, I want my LFS system to be as bare as possible, then add what you want to each individual install instance with the ports manager! So my LFS system is simply raw LFS 7.0 + wget

Any changes you make to this base system should then be wrapped up into a build tar.gz (see How to Package LFS for Installation above)

Host system info

1. qdesk name of the working platform: i686-pc-linux-gnu
2. qdesk name of the platform's dynamic linker: ld-linux.so.2
3. binutils build time (make: 27 sec, make install: 1 sec), so one SBU = 28 sec)

When customizing the kernel, any item marked as M means it will not be compiled directly into the kernel but placed on your filesystem (your regular root fs, not an initrd) as a module in /lib/modules. LFS recommends that most items NOT be marked as module, but compiled directly (denoted by a *). Also note the LFS does NOT use any sort of initrd, so any modules required to boot must be compiled (like sata, pata, ext3/4...). I have less than 1mb of /lib/modules while ubuntu has 117mb Though the more modules or build-in items you have the more hardware your kernel can boot.

I moved the kernel from /source/linux-3.1 to /usr/src/linux-3.1 so I can re-compile later

Get the boot penguin logo: http://www.articleworld.org/index.php/How_to_change_the_Linux_penguin_boot_logo

1. Currently I do have the penguin logo, but I use vga=791 on the grub kernel string, which is deprecated, haven't figured out how to apply this for grub2 yet, gfx something or other.