On 3/10/2017 1:29 PM, Aaron Bains wrote: Tim, yes that's what I'm getting at. Basically I wouldn't be chrooted into the LFS system. I build the tool chain on the host and make install destdir all my desired packages to the mounted LFS system. This would save lots of space resulting in a very small OS. Pretty sure this is how embedded Linux systems are made with cross compiling toolchains.
But you will chroot, or else your packages will be dependent upon /mnt/lfs/tools as Bruce explained to you initially. Anything else, and you're not building Linux From Scratch. Based on your goal, I'm not sure why you need Chapter 5 either. Anyway, it seems like you already have all of the answers to your own questions... So I say go for it dude! ...and be sure to report back how it works out for you! On Mar 10, 2017 1:44 PM, "Tim Tassonis" <[email protected]<mailto:[email protected]>> wrote: On 03/10/2017 07:17 PM, Aaron Bains wrote: But if I'm getting and building all the packages on the host and installing them on LFS, why would LFS need wget, etc. Im assuming LFS would only need the basic stuff such as glibc and Linux headers and coreutils and bash and their dependencies. I wouldn't expect minimal systems like tinycore or http://minimal.linux-bg.org systems using busybox to require all those packages in chapter 6, unless they intended to compile packages and download them and install all right on the system. The difference of your proposed solution to the "proper" LFS way is that LFS will gradually override the tools stuff with stuff from chapter 6 and later stuff in Chapter 6 depends on earlier stuff in Chapter 6. The tools stuff is not enough for every package in chapter 6 and definitely not enough for additional blfs stuff. This will leave you with unresolved dependencies. I'd suggest you go for "best of both worlds": First, you do a normal make install to /usr etc, as described in the book, and right after that, you do a make DESTDIR=/path/to/your/livecd/root install for any packages you want on your livecd. That's what I basically did on my first lfs install. Now, I use a package manager and then install the packages, but for a first try, it would be wise to follow the book until you fully understand all the reasons why lfs does it as described. Which you obviously don't. Cheers Tim Aaron Bains, CPA, CA On Mar 10, 2017 12:04 PM, "Bruce Dubbs" <[email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>>> wrote: Aaron Bains wrote: I want to make a live CD based on the LFS 8.0 documentation. I have made my tool chain (completed chapter 5) and I am starting to build the packages for the final system. I don't want to compile any packages inside the actual LiveCD, since I want my LiveCD to be very lightweight. To add packages to the LiveCD, I would compile them in my host environment (using my toolchain) and |make install| to the root of my LiveCD filesystem. I do want to have a very minimal GUI to run a basic webcam package. Am I correct that I don't need to install any of the packages in Chapter 6 of the LFS documentation? No. After Chapter 5 packages will be dependent on /mnt/lfs/tools and your system will not boot. You will not have any networking or way to get packages (e.g. wget, etc). Except for maybe Linux headers and GlibC because of packages relying on their libraries, or do I not even need those? I am under the impression that when I run |make| and |make install| that it puts all the libraries I need in the directories so I wouldn't need these packages that LFS is specifying in chapter 6, since I don't intend to compile packages directly within the LiveCD OS. Please let me know if I am on the right track here, or if what I am saying is wrong. You can try it, but I'm highly doubtful for the above reasons. Have you even built LFS through boot? It doesn't sound like it. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-support <http://lists.linuxfromscratch.org/listinfo/lfs-support> FAQ: http://www.linuxfromscratch.org/blfs/faq.html <http://www.linuxfromscratch.org/blfs/faq.html> Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style <http://en.wikipedia.org/wiki/Posting_style> -- decentral.ch<http://decentral.ch> - IT Stuff Tim Tassonis Dennlerstasse 36 8047 Zürich [email protected]<mailto:[email protected]> +41 79 229 36 17<tel:%2B41%2079%20229%2036%2017> -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
