On Sat, 7 Nov 2015 01:10:53 +0100 Tim Tassonis <[email protected]> wrote:
> But since openssl probably already is one of the first blfs packages > people install (to get remote ssh access via openssh), it also wouldn't > harm much moving it to lfs. By the time people build the kernel for their system, they already have pulled packages from BLFS before they chroot. Some users get real exotic and put wget and ncftp in their temp system. We don't need openssl even in ch5 or ch6. All that is needed is a note stating if the user decides to sign their modules, to install OpenSSL from BLFS. When building a bootable temp system I like to cross-compile openssl, wget, dropbear, iproute2, iputils, dhcpcd, and some others before I even boot into the system, but that is beyond the scope of the book. If the user decides they want to sign their modules for whatever reason, they will already know they'll need OpenSSL when building their kernel. All they have to do is read https://www.kernel.org/doc/Documentation/module-signing.txt LFS is just a base build. Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
