On Tue, 8 Dec 2020 18:14:58 +0530
Palash Tekam via blfs-support <blfs-support@lists.linuxfromscratch.org>
wrote:
> Dear all,
> I have successfully installed BLFS 8.4 and now I want to make its iso
> file so that I can transfer it to my other laptop like any other Linux
> distribution such as Ubuntu, Mint, Manjaro, etc. Please also mention
> all the changes that I have to make in kernel to make it run on
> different laptops.
> I had read somewhere that MacOS X was based on LFS 6.1.
Incorrect MacOS X is based on FreeBSD and always has been.
> This should be possible, else how do they make operating systems and
> distribute it!
>
What you built can not be transferred easily to another machine. There
are too many pitfalls due to the way LFS builds the system.
The only sane way ( successful way ) to build LFS for it to be installed
onto other machine is to....
1. Use a package manager
2. Build ALL the packages in a clean chroot
3. Create a base system of packages and all the add on
packages needed. You have to merge LFS and BLFS together.
You will have issues with controlling dependencies between the
various packages.
4. Build an installation script to install the binary packages
from the package manager (repository). Formatting a drive and
installation of binaries going to the formatted drive included
in this step.
5. Fix up the configuration files for each machine.
6. Transfer drive to the target machine.
7. A way to update the target machine(s).
There are other ways to do this, what I have done "works for me". I
have installed my "distro" onto more than a dozen machines and I can
replicate any of those machines easily. Take about 15 minutes to
replace a server on my network. ( Desktop is almost Completed/Ready ).
LFS does not lend itself to the above. How do I know? I have fought
and learned all the issues for many years. LFS taught me exactly
nothing. LFS requires a few changes that doesn't affect the standard
way LFS builds, but I have been completely unsuccessful in getting any
changes made.
IE they just don't care ( In my opinion ). They build the system their
way and if you change that you typically will not be helped, as in your
on your own. Yes I had to go it completely alone.
Most of the developers for LFS don't know ( and don't understand ) how
to build packages in a "clean chroot" which is required to be successful
in what you want to do. It is also how most if not all distributions
build their systems ( I followed their lead ).
My methods ( not the only way there are others ) produce a repository of
rpm packages that can be installed onto any machine ( same type as the
packages are built for ). Only the ones needed for a particular
function is installed on the target machine. I install a "Base system"
which I can boot from the target machine ( headless ), then log in
over the network using openssh to fix up configuration files and install
other packages ( from a git repository or sshfs/nfs mount ) as needed
for function.
I have a GitHub repository that contains my latest work for the
Raspberry pi platform. That work is shifting away from LFS and into
the Arch linux way/methods.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
