> Sent: Wednesday, December 09, 2020 at 9:29 AM > From: "Scott Andrews via blfs-support" > <blfs-support@lists.linuxfromscratch.org> > To: blfs-support@lists.linuxfromscratch.org > Cc: "Scott Andrews" <scott.andr...@columbus.rr.com> > Subject: Re: [blfs-support] How to make an iso of BLFS > > On Tue, 8 Dec 2020 14:03:51 -0600 > Bruce Dubbs via blfs-support <blfs-support@lists.linuxfromscratch.org> > wrote: > > > On 12/8/20 1:22 PM, Scott Andrews via blfs-support wrote: > > > On Tue, 8 Dec 2020 12:33:48 -0600 > > > Bruce Dubbs via blfs-support > > > <blfs-support@lists.linuxfromscratch.org> wrote: > > > > > >> On 12/8/20 12:00 PM, Scott Andrews via blfs-support wrote: > > >> > > >>> 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). > > >> > > >> > > >> Not true. You can tar up the LFS system and untar it on an empty > > >> partition on the target machine. One caveat is if the target > > >> machine is less capable than the build system, you need to build > > >> gmp generically. > > > > > >> > > >> Other minor things are to change the host name, ip address, fstab, > > >> grub.cfg, and maybe unprivileged user(s). Also any kernel modules > > >> and (potentially) firmware for the target system must be available. > > >> > > >> -- Bruce > > > > > > That is a straw man argument and you know it. > > > > It is not. I've done it. I didn't say your way doesn't work. It's > > just that using tar does not require the overhead of a package > > manager. I does require you to know what you are doing. > > > > -- Bruce > > > > It is NOT an answer that the OP is looking for, nor is it a process the > OP could be successful with. > > How does grub get installed correctly? > > If the PARTID or UUID is different does it work? > > UEFI, BIOS? something else? > > Grub config setup to work? > > Again the OP is looking for an iso ( or something like that ) that he > can install and have it boot. Your answer is woefully incorrect. > > My method works as described, batteries are included, yours ????? > > Again straw man
Scott, you need to know and accept that: - your project, while fun, challenging and (I assume) functional, is not LFS. It is based on LFS. (B)LFS is a core set of instructions which are carefully designed and exhaustively tested to achieve the project's stated objectives: http://www.linuxfromscratch.org/lfs/index.html - other people have extended LFS is many ways. There are others who have used RPM. There are other package managers (I use a manager, but not RPM). People use other hardware - RaspPi springs to mind. Remember: Your Distro, Your Rues. - LFS is a basis which can be used, extended, altered at will. There have been published distributions based on BLFS - remember Yoper? - there is no way that the LFS community is going to accept your versions of all these things as the only one, the right one, the best one just because you make most noise about it. Please stop your badgering of the editors and users. Why not start your own project if it is that important to you. Teresa -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
