linux-from-scratch/lfs-buildscripts
1
0
Fork 0
mirror of https://github.com/YellowJacketLinux/lfs-buildscripts.git synced 2025-01-23 22:42:28 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
286e1e4c52
lfs-buildscripts/README.md
YellowJacketLinux 286e1e4c52 typo fix
2024-10-08 01:33:32 -07:00

3.7 KiB
Raw Blame History

LFS SystemD Build Scripts

Shell scripts for building LFS SystemD

Based upon https://www.linuxfromscratch.org/lfs/view/stable-systemd/ version 12.2

Do not yet use

This git repository contains shell scripts needed to build LFS 12.2-systemd and is being worked on in an x86_64 LFS 11.3 (modified) system.

There are some deviations from LFS 12.2, namely:

  • LibreSSL is used instead of OpenSSL
  • LTS Kernel series 6.6 is being used in place of 6.10.x kernel series
  • 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.

As of present, these scripts are not complete and probably broken.

These instructions are incomplete notes.

Chapter 03 ‘Get Sources’ Script

This script is to be run by the lfs user. The partition LFS is to be built on must already be mounted at /mnt/newlfs and the directory /mnt/lfs/sources should exist and be owned by the lfs user.

The script will download the needed sources (sourcing versions.sh) and make a backup of the downloaded sources so that if run again, it can get the sources from the backup and not need to download them again.

The file versions.sh also includes sha256sum digests so that the script can verify the integrity of the fetched file.

Chapter 05 Building

In the CH5Build directory, the lfs user should execute the Master.sh script:

lfs$ 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 CH05.* scripts.

The Madness

Long term goal is to produce a GNU/Linux distribution largely based upon LFS but using RPM packages with a ‘core’ package repository and then additional package repositories that require the ‘core’ package repository.

Multilib is not a goal, nor is compatibility with WINE. The goal is to allow ‘Free Libre Open Source Software’ to have a capable GNU system running the Linux kernel upon which to run.

I personally will be involved in the package repository for the MATE Desktop Environment when it gets that far, but as far as GNOME, KDE, etc. if they are to have package repositories then others will have to provide them.

What I want is a stable ‘LTS’ distribution along the lines of what CentOS used to be but third-party package repositories providing for the needs of the user community, similar to how ‘Fedora Extras’ supplemented Red Hat Linux back in the day.

Is that too much to ask?

The Plan

These scripts will be used to build a bootable USB thumb drive that will then be used to run the scripts again to rebuild itself on the hard disk. The thumb drive then becomes my emergency boot device.

Once installed on the hard drive, BLFS packages will be added until I have a basic usable system bootstrapped with the RPM package manager.

At that point, packages will be added until I am able to run the XFCE desktop environment. Long-term goal personally is MATE but MATE will be done as a separate package repository. Hopefully KDE and GNOME will also be done as separate package repositories as well.

Users who are happy with XFCE will not need a separate package repository for their desktop environment.

Back on topic, once XFCE is properly packaged and working, then the scripts used to build the bootable USB thumb drive will be used to build an installer thumb drive with a crude basic installer to create a system using RPM packages.

That will be the first release of ‘Yellow-Jacket GNU/Linux’ and it is probable that by the time that happens, the LTS kernel will have changed and quite likely other core components like GCC and GlibC and Python.