linux-from-scratch/lfs-buildscripts
1
0
Fork 0
mirror of https://github.com/YellowJacketLinux/lfs-buildscripts.git synced 2025-01-23 14:32:20 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

documentation work

Browse Source
This commit is contained in:
YellowJacketLinux 2024-10-14 12:25:11 -07:00
parent 7864d09d29
commit 0ef6e080e5
2 changed files with 54 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

71
README.md
View File

@ -5,31 +5,50 @@ Shell scripts for building LFS SystemD
Based upon https://www.linuxfromscratch.org/lfs/view/stable-systemd/ Based upon https://www.linuxfromscratch.org/lfs/view/stable-systemd/
version 12.2 version 12.2
This git assumes the use user `lfs` has already been created according to the
LFS book __except `$LFS=/mnt/newlfs` in these scripts__.
This set of scripts does not use `fdisk` or `mke2fs`, those need to be run and This set of scripts does not use `fdisk` or `mke2fs`, those need to be run and
formatted for the appropriate partitions before starting. With caution of formatted for the appropriate partitions before starting. With caution of
course. course. See Chapter Two of the LFS book.
Do not yet use The scripts associated with Chapter Nine and Ten in this git are *very* specific
to my system and even then, currently not perfect (e.g. my network did not come
This git repository contains shell scripts needed to build LFS 12.2-systemd and up on first boot and there was a time zone issue). A future modification to
is being worked on in an `x86_64` LFS 11.3 (modified) system. these scripts may allow some of the hardware specific stuff (like filesystem
`UUID`) to be set in a config file the scripts source but that has not yet been
done.
My build host is an is an `x86_64` LFS 11.3 (modified) system.
There are some deviations from LFS 12.2, namely: There are some deviations from LFS 12.2, namely:
* LibreSSL is used instead of OpenSSL *except* with Python3 * LibreSSL is used instead of OpenSSL *except* with Python3
* LTS Kernel series 6.6.x is being used in place of 6.10.x kernel series * LTS Kernel series 6.6.x is being used in place of 6.10.x kernel series
* Some versions are updated from what is in the LFS book. * Some versions are updated from what is in the LFS book.
The host I am building from is an LFS 11.3 system with similar modifications. The host I currently am building from is an LFS 11.3 system with similar
modifications. If curious, that LFS 11.3 system was built from a CentOS 7 host
but some mods were needed to the CentOS 7 host and the LFS 11.3 build
instructions for it to work (however I did then bootstrap build LFS 11.3 in
LFS 11.3 without using the needed build instruction changes).
The idea for this git was to first build LFS 12.2 to a thumb drive, and then
boot the thumb drive to rebuild it to the hard disk.
When LFS 12.2 is built on the USB Thumb Drive, it should then be possible to When LFS 12.2 is built on the USB Thumb Drive, it should then be possible to
boot from the USB Thumb Drive and run the scripts again to build LFS 12.2 from boot from the USB Thumb Drive and run the scripts again to build LFS 12.2 from
LFS 12.2 on a hard disk partition where I can then proceed with the other steps LFS 12.2 on a hard disk partition where I can then proceed with the other steps
in `THE_PLAN.md` towards creating a RPM distro from scratch. in `THE_PLAN.md` towards creating a RPM distro from scratch.
As of present, these scripts are not complete and some are probably broken. As of present (14 October 2024) the scripts build an LFS 12.2 SystemD system on
my build host *except* the thumb drive does not boot and some of the initial
configuration in Chapter Nine was not quite correct. See the file
`INSTALL_NOTES.md` for details.
These instructions are not complete notes. Now that I have a working system, I am moving on to ‘Phase Two’ in `THE-PLAN.md`
and am unlikely to make revisions to this git for some time.
-------------------------
If you run the script `version-check.sh` (copy-pasta straight from the LFS If you run the script `version-check.sh` (copy-pasta straight from the LFS
book) and everything on your build system passes, there is a *good chance* book) and everything on your build system passes, there is a *good chance*
@ -85,8 +104,9 @@ __PAY ATTENTION__: First, the `root` user must execute the `CHROOT.sh` script:
root# bash CHROOT.sh root# bash CHROOT.sh
That script will copy `CH7Build` and `CH8Build` into `/mnt/newlfs/sources` and That script will copy `CH7Build`, `CH8Build`, `CH9Config`, and `KernelBuild`
then fix some permissions and set up `/mnt/newlfs` for the `chroot` into `/mnt/newlfs/sources` so that those scripts will be available within the
`chroot` and then fix some permissions and set up `/mnt/newlfs` for the `chroot`
environment. environment.
Finally, it echoes the command that the `root` user must execute to enter the Finally, it echoes the command that the `root` user must execute to enter the
@ -105,21 +125,18 @@ Then, still inside the `chroot` at `/sources/CH7Build`, execute:
root# bash Master.sh root# bash Master.sh
The script works but is not finished. To do, it needs to verify the system is
ready for the script to run. The `Master.sh` script calls the `CH07.*` scripts.
Some important build tools previously built in the host environment will be Some important build tools previously built in the host environment will be
rebuilt within the `chroot` environment. After the script runs, it will echo rebuilt within the `chroot` environment. After the script runs, it will echo
instructions on how to back things up. The backup takes a few minutes but it instructions on how to back things up. The backup takes a few minutes but it
saves time if something goes wrong in Chapter 8 building. saves time when starting over if something goes wrong in Chapter 8 building.
Chapter 08 Building Chapter 08 Building
------------------- -------------------
__PAY ATTENTION__: After running the build scripts for LFS Chapter 7, the __PAY ATTENTION__: After running the build scripts for LFS Chapter 7, the
instructions for creating the backup involved deleted the `/mnt/newlfs/sources` instructions for creating the backup involved deleting the `/mnt/newlfs/sources`
directory. directory to reduse the size of the chroot tools backup.
As the `lfs` user, re-run the `CH03-get-sources.sh` script to restore the As the `lfs` user, re-run the `CH03-get-sources.sh` script to restore the
sources: sources:
@ -143,11 +160,17 @@ Again, the script will echo the command to enter the `chroot`. Execute it as
That will run many of the `CH08.*` scripts, building the LFS system through That will run many of the `CH08.*` scripts, building the LFS system through
`CH08.34-bash`. Note that when it builds the `shadow` package, it first builds `CH08.34-bash`. Note that when it builds the `shadow` package, it first builds
the `cracklib` package from BLFS and then links `shadow` against it. It does the `cracklib` package from BLFS and then links `shadow` against it. It does
not however build PAM. not however build PAM. PAM is a complex solution to complex problems that exist
in enterprise. For the home user, those complex problems generally do not exist
so the complex solution is not needed and using it is potentially dangerous as
complex solutions that are not needed sometimes introduce remote exploitable
code that otherwise would not exist.
After it finishes building `bash`, the `Master.sh` script will instruct you to After it finishes building `bash`, the `Master.sh` script will instruct you to
set the `root` password. After doing so, exit the `chroot` and re-enter so that set the `root` password. After doing so, exit the `chroot` and re-enter so that
the freshly rebuilt `bash` will be loaded. the freshly rebuilt `bash` will be loaded. Reloading `bash` within the `chroot`
*probably* would work too but since the binary the `chroot` command originally
called has been replaced, just exit and re-enter.
Once in the `chroot` environment again: Once in the `chroot` environment again:
@ -157,14 +180,15 @@ Once in the `chroot` environment again:
That will run the rest of the `CH08.*` scripts. Assuming all goes well, the That will run the rest of the `CH08.*` scripts. Assuming all goes well, the
system will be ready for LFS Chapter 9 configuration. system will be ready for LFS Chapter 9 configuration.
It also builds several packages from BLFS, specifically enough so that `wget` It also builds several packages from BLFS, specifically enough so that a mouse,
and `curl` are built, along with the TLS certificate bundles needed for those `wget`, `curl`, and the TLS certificate bundle (BLFS `make-ca`) are built, so
tools to make TLS (HTTPS) connections. that the new system will be capable of HTTPS connections.
Note that `Master2.sh` does have a major deviation from the LFS book. It builds Note that `Master2.sh` does have a major deviation from the LFS book. It builds
LibreSSL to provide the OpenSSL API (e.g. as used by the `kmod` package). Most LibreSSL to provide the OpenSSL API (e.g. as used by the `kmod` package). Most
software that builds against OpenSSL will build against LibreSSL and I have software that builds against OpenSSL will build against LibreSSL and I have
more trust in the LibreSSL developers. more trust in the LibreSSL developers. LibreSSL is also a smaller, more simpler
code base.
As of Python 3.10, Python 3 no longer allows building against LibreSSL. So As of Python 3.10, Python 3 no longer allows building against LibreSSL. So
OpenSSL is still built, the `_ssl` and `_hashlib` Python modules need it and OpenSSL is still built, the `_ssl` and `_hashlib` Python modules need it and
@ -177,6 +201,9 @@ run the `PRENINE.sh`:
root# bash PRENINE.sh root# bash PRENINE.sh
Note that running that script is only needed when building the USB thumb drive
that is used to run the scripts again.
You can then enter re-enter the chroot (using the same command used before, You can then enter re-enter the chroot (using the same command used before,
it should be in very recent bash history) and proceed to the Chapter Nine it should be in very recent bash history) and proceed to the Chapter Nine
configuration scripts. configuration scripts.

9
TLS-README.md
View File

@ -91,7 +91,7 @@ present in OpenSSL 1.0.1g which is the version that LibreSSL forked.
When a script genuinely needs to use the `openssl` binary with newer features, When a script genuinely needs to use the `openssl` binary with newer features,
then (and only then) the script should be packaged via RPM with: then (and only then) the script should be packaged via RPM with:
Requires: /usr/bin/openssl >= n Requires: openssl >= n
where `n` is the minimum version of OpenSSL that provides the needed feature. where `n` is the minimum version of OpenSSL that provides the needed feature.
YJL will maintain an RPM package for a recent versions of OpenSSL to meet that YJL will maintain an RPM package for a recent versions of OpenSSL to meet that
@ -101,10 +101,11 @@ If (like Python 3) all you need is the shared library from the recent version of
OpenSSL, RPM will take of the shared library resolution but the RPM spec file OpenSSL, RPM will take of the shared library resolution but the RPM spec file
should have: should have:
BuildRequires: openssl-devel BuildRequires: openssl-devel >= n
Using `BuildRequire: pkgconfig(openssl)` does not work because both devel
packages provide it and version numbers can not distinguish between them.
so that the proper devel package is present on the system when the package
builds.
On the other hand, packages that build just fine against LibreSSL should have: On the other hand, packages that build just fine against LibreSSL should have: