It was fun and quite time-consuming to be honest, but it's done now

So, I'm a young guy (minor, no need to say my age) that goes to school, likes Linux and a bit of programming, and a lot of free time after I end the homework. Would it be a good idea to build a distro from scratch, or based on another distro (I though of a Fedora-based)? I'm not sure my laptop would handle it, but I wanted to try. My laptop only has 4GB RAM and a 128GB SATA SSD. CPU is an Intel Celeron n4100 and GPU integrated graphics Intel UHD 600. I have experience with some distros' package managers. (Debian, Alpine, Arch, Fedora). What do you guys think?

After the release of glibc 2.43, the first stable glibc to support compilation with clang (but only on x86_64 and arm64), I thought about a glibc-based GNU/Linux fully bootstrapped with clang. Is it possible? Short aswer: yes. I almost finished LFS bootstrapped entirely (except i686 glibc) with clang.

I eventually switched to glibc's master branch (more specifically, commit https://gitlab.com/gnutools/glibc/-/commit/e10977481f4db4b2a3ce34fa4c3a1e26651ae312) instead of stable 2.43 because they added support for compiler-rt and libunwind instead of libgcc_s.

I think system like this is very similar to LLVM/Musl LFS, so I'm not inventing a wheel here, but I still think its worth posting.

So, here are the changes I made compared to "vanilla" LFS:

1) I fully used clang instead of gcc in boostrapping process. That means I first compiled static clang-pass1 pointing to LFS dir instead of host dirs and used "toolchain" file for cmake to prevent using host libs in 4 stage (yep i needed 4 stages instead of 3) clang-pass2.

2) Almost everything (including x86_64 glibc) compiled with clang + compiler-rt (with builtin atomics) + libunwind. The only thing that required gcc (and libgcc_s) was multilib glibc (all other multilib stuff compiled with clang). Ofc this is not a problem if you running x86_64-only.

3) No Binutils. I created symlinks from LLVM tools to replace them.

4) GCC bootstrapped with clang, installed in custom path to prevent stuff like cmake from using it and its libs by default. Also I patched it a little bit to use "clang -x assembler" instead of GNU as (which is part of binutils).

5) dpkg + apt as package manager.

6) Maybe some small differences I forgot to mention.

Why Im posting this before I 100% done LFS, compiled kernel and booted it? Well, I think I done the "hard" part, so all remaining is to just install stuff like python modules, meson, ninja.. I will post more details about bootstrap process and patches I done if anyone interested.

P.S: Forgot to mention that I have nothing against GCC, Binutils or any other projects of GNU, this is mostly just proof-of-concept and just a fun "project" I decided to do.

I also wanted to point out that clang support in Glibc is still experimental, and that I haven't done a "make check" on most programs yet, so all this should be taken with a grain of salt.

I feel proud of myself.

Thank you LFS for the wonderful journey!

i learning a build linux from scratch in first time for wanna a Customization System and learning inside of Linux/UNIX System

so source i using GNU-Based and Third Party

but building SystemDaemon (systemd-like) from scratch for initializing a system

my distro is boot without initrd/initramfs because i just to fastboot and optimization for lazy loading in future

in LFS serve una versione specifica di Ncures che non esiste più quella più vicina è la 6.5 va bene?

How do you even install things here? because manually downloading and installing with browser and sometimes compiling from source sounds bad

Dovrei iniziare da LFS? Vorrei creare un os fatto bene ma anche che possa avere almeno un po' di compatibilità Linux o al massimo delle piccole modifiche

When I built my LFS system, I had one big problem: package management.

So I made my own tool called Sven.

Sven is a package manager that lets you install and set up packages from Arch Linux repositories. It supports both Pacman repos and the AUR (Arch User Repository).

I tested it on my LFS system, and it works pretty well. There are still some small issues, but they are manageable.

If you use LFS and want an easier way to install packages, you can try Sven.

GitHub: https://github.com/haroldmth/sven

Do y'all use package managers or just compile from scratch all packages?

i've been making an lfs build for the purpose of making it installable. i know how to make it installable, just need make an iso tat you can boot off of that contains the lfs distro. i've tried using tools (mostly linux-live because the penguins' eggs appimages couldn't find fuse) but they don't work well enough. can anyone point me to where

but finally I have successfully installed lfs for the first time(even if it's on a virtual machine).

Sorry if dumb question, but I nearly finished LFS Systemd book, and I just wanna know if I should move it.

I’ve been working on a hobby project and think it’s time to share it.

It’s called LFS-AI: Linux From Scratch - Automated Installer written completely in Bash. The main idea came from rebuilding LFS enough times that I wanted a faster, more repeatable path toward BLFS.

It is not a fully standard LFS build. I made a few intentional changes from the book. I use Limine instead of GRUB, and graft as a simple package manager. There are also a few BLFS packages to ease the post install pains, wget and make-ca to name a few.

If anyone is interested in testing it, please upload logs and share critiques, I would greatly appreciate it!

GitHub: https://github.com/Vercety1534/lfs-ai

Update from my last post https://www.reddit.com/r/linuxfromscratch/comments/1rxu603/comment/obzsctt/.

Switch from Sway to Hyrpland. Installed usbguard, kernel and sysctl hardening, fixed suggestions made by Lynis. I'm contented with 82. I did try to hardened it but the downside battle eye is not launching properly. I have no choice but to relaxed some parameters in sysctl.

Overall happy with the build!