What are /r/linuxfromscratch's favorite Products & Services?

From 3.5 billion Reddit comments

When you pick a distro from that list VirtualBox just chooses hardware it thinks is a "sane" default. Things like which soundcard to emulate, which video to emulate, etc. Since you're doing Linux From Sctatch and building the kernel from source that doesn't actually make a difference to you since you'll be picking what to build anyway. So honestly pick whatever you want and then look in the details for what hardware choices it made.

If you're asking me what I personally would pick, I would pick Other Linux 64bit.

*edit: If you look here https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-all/Global.cpp you can see what that menu is doing and what hardware choices are being made based on your selection.

I don't know why you specifically want a torrent. There is a wget list and also tarball containing all the necessary archives. If your internet connection is too shitty to download to tarball, you can still use the wget list since it will just ignore the downloaded files and resume the partial ones.

It's a minimal toolchain that you use to build the rest of the system. If you look in chapters 5 and 6 you'll see that you end up building some of the packages twice. It's a way of separating your host system that you're building LFS on from the target system that you're going to be running it on. They explain it a little better here in their bullet points in the top third of the page.

It might help to imagine what compiler you'd have to use if you were going to build an LFS system for a raspberry pi (arm architecture) on an x86 system. You'd have to build an ARM toolchain first.

Looks like yes.

http://www.linuxfromscratch.org/hlfs/view/development/index.html

Upon reviewing it, it looks under-developed :( oh well, maybe once I get better I can fork it, and who knows, maybe contribute :)

Thanks for your reply. I actually decided to just rebuild the entire tool chain because of this note about the PATH variable in section 4.4:

>By putting /tools/bin ahead of the standard PATH, all the programs installed in Chapter 5 are picked up by the shell immediately after their installation. This, combined with turning off hashing, limits the risk that old programs are used from the host when the same programs are available in the chapter 5 environment.

So my understanding is that as soon has make has been installed in section 5.27 all of the remaining packages in the toolchain should be built using the version of make installed in $LFS/tools/bin.

​

Good link. That's for the systemd. Here's the official patches for the primary Sysvinit system. Currently doing the Sysvinit version, btw.

P.S: Also, here is the unofficial patches.

Make sure that if you get a patch, get one for your exact package version number. As usual, the user contributed packages come with the no-warranty-if-your-computer-explodes. Use, (or not), at your own risk.

Last time I did a build was years ago, and it was gcc that needed patching, something to do with versioning? My guess is with the wrong gcc version it wouldn't compile anything, I wasn't patient enough to test that theory though.

They'll tell you what will need patching in the book, and the patches are found here.

I'm a beginner at building LFS as well, but in your command you didn't put the following option:

--enable-obsolete-rpc According to the LFS Book 7.9:

>This installs NIS and RPC related headers that are not installed by default. They are required to build GCC and by several BLFS packages.

It was hinted in your error message at the end that there was something wrong with your header files.

The phrase "patching or substituting many of the packages used for improved security." (from the HLFS page) lead me to believe it was more than the gcc toolchain and a few low-level utilities. I may be wrong, it wouldn't surprise me.