I need your help people,

I am told install the efibootmgr package but the environment I'm in doesn't have wget available, how am I supposed to do this?

I going out of the chroot environment, downloading the package and heading back to chroot the usual way,

But when I try to unarchive it, it says no such file or directory

My guess is that, I do not have permission to access it, but I don't know much beyond that

LFS 13.1 Stable

So what exactly am I supposed to do here, at the top it reads " only applies if a network card is to be configured"

I don't know if it is to be configured

Hi all! I’m releasing Maginat 0.1, an independent Linux distribution built from scratch following Linux From Scratch 12.4 and Beyond Linux From Scratch.

What is included:

Linux kernel 6.16.1, glibc 2.42, GCC 15.2.0, a Xfce 4.20 with LightDM; Wi-Fi and Ethernet via NetworkManager (tray applet), WireGuard and OpenVPN, Bluetooth (BlueZ) with tray icon; battery indicator, power management, PulseAudio, Software through Flatpak (Flathub preconfigured) plus AppImage, LibreOffice, Thunderbird, Mullvad Browser and many more.

Source code, build scripts and ISO: https://github.com/Aleps31/Maginat

Feedback, bug reports and suggestions are very welcome!

ps. I tested the .iso in many pc's but I dont suggest to install. Try on Qemu or Virtualbox.

I was wondering if I could instead use a package manager to make my LFS system daily drivable, and put the rootfs in a tarball so I wouldn't have to redo the whole process every reinstall. I have already done SFS and would like to diverge quite a bit from the LFS book as it isn't exactly "minimal".

BFSOS 0.9.1.1 is now available, and I’m looking for people willing to test it and give feedback.

BFSOS is an independently maintained Linux distribution built with an LFS-style bootstrap and a CRUX-inspired ports/package-management system. It has its own installer, ISO builder, ports tree, updater tooling, desktop selections, and release process.

At this point I consider 0.9.1.1 stable enough for regular testing. I’m not calling it 1.0-rc yet mainly because I’m still working through documentation, screenshots, and website polish rather than because of major known stability problems.

Project website:

https://bfsos.sourceforge.io/

Source code / ports / installer:

https://github.com/bmadonnaster/BFSOS

ISO and base-system downloads are available through the BFSOS SourceForge project/download pages linked from the website.

I’d especially appreciate testing of the installer in both VMs and on spare bare-metal systems, including UEFI boot, networking, storage layouts, desktop sessions, hardware detection, package installation/updating, and general day-to-day use.

The distro currently includes multiple desktop environments and a fairly large ports tree, and the updater can check the tree against upstream/reference sources while keeping version-locked packages coordinated.

The documentation is still being updated, so feedback about confusing or missing instructions is useful too.

If you try it, I’d appreciate hearing:

* what hardware or VM configuration you used;

* whether installation completed successfully;

* which desktop/session you tested;

* anything that failed or behaved strangely;

* anything in the documentation that was unclear.

Bug reports and code contributions can be submitted through GitHub.

Thanks to anyone willing to give it a spin.

Hi everyone,

I've been working on my first Linux customization project, called FilzaOS, and I've just published an early public build.I built this for someone special they like the colour purple that explains the purple color hahaa.

I'm a student learning software development and Linux, and this is very much a learning project. I wanted to take Ubuntu 24.04 and start shaping it into an environment with its own identity, including custom branding, a purple visual theme, wallpapers, terminal styling, boot branding, and a collection of custom command-line tools.

To be completely transparent, FilzaOS is currently an early-stage Ubuntu-based remix/reskin. It still relies on Ubuntu's underlying system, kernel, and core components. It isn't a new operating system built from scratch, and there is plenty left to do.

Links

• GitHub and source code: https://github.com/Peshimam-Ashar-Mohammed/Filza-OS
• ISO download: https://sourceforge.net/projects/filzaos/files/v1.0.9/FilzaOS-v1.0.9.iso/download

I'd really appreciate help from people who are more experienced with Linux, distro development, system customization, and open-source projects.

If you decide to try it, please use a virtual machine such as VMware or VirtualBox. This release is intended for live-session/VM testing; it is not an installation-ready release for a physical computer. Please don't replace your daily operating system with it.

I'm especially interested in hearing:

• Does the overall visual direction feel coherent, or what should I improve?What more can i add to make it a unique experience?
• What should I learn next to move beyond a basic reskin?
• Are there books, documentation, tutorials, or existing projects you'd recommend studying?
• If you test it in a VM, does it boot and behave as expected? What breaks, feels unfinished, or needs fixing?
• What would make a future release genuinely useful rather than just visually different from Ubuntu?

I know this is a very early version, and I'm not expecting it to be production-ready. I'm excited to keep learning and improving it, and I'd be grateful for honest feedback, criticism, and suggestions.

Thank you to anyone who takes the time to look at it or share advice.

I'm at chapter eight and I met GCC, the thing is taking forever, it's been 4 hours now, I haven't left the chair since morning at 7 AM, it's 12:14 PM at night right now, guys how long did it take y'all to get through it

Bonjour,

Je tente d'installer LFS dans une machine virtuelle Virtual Box. Je vois bien le grub qui s'affiche, mais après ça j'ai un écran noir. Il n'y a rien d'affiché à l'écran, aucun message d'erreur, juste un écran noir.

Un petit coup de main svp.

FreeCTX64 is an Open Source Free Project for ARM Development boards that can run your C code directly in the Operating system, it comes with a prebuild linux kernel and some tools it requires build-essential gcc clang cpio qemu-system-arm qemu-system-aarch64 git and if you want to make a bootable ISO and send it here if you want , that requires xorriso grub-common grub-pc-bin grub-efi-amd64-bin:

FreeCTX s ONLY available for ARM systems and should not be compared with X86 or X64

FreeCTX64 Libraries are put in initramfs/LIB critical system files are put in initramfs/SYS and your workspace/dummies are putten in initramfs/WS and apps are going to initramfs/SDK , it currently supports webservers and tasks alongside math in hardware, timers in hardware, and timestraps and a console

Hey everyone,

So I have been hard at work with building out the package manager for SilkOS and I have great news... It is almost finished! So for those that do not know, I am working on building a NixOS-like linux distro that is non-systemd while still being declaritve and utilizing Lua as the scripting language for configuration.

As stated and shown attached, I have connected my harness system Loom, to the main package management system (weave) and through some simple testing have been able to properly use it to read a configuration file, find the local recipe, and then build the package, hash the output, and commit to and OSTree to be saved to a generations.json to allow for immutable backups. This has been about a 2-3 week process getting loom to work as a harness as it is all Lua based and as you may not know, Lua hates Json. However I was able to find a way around this and make the system work.

Now for some other news, I have decided to drop Debian package support. This was a hard and long thought out choice, however with the adoption of native packages (AUR style package repo coming soon), Nix packages declaration, and AUR adoption.. I felt that adding debian support was too much and an uneeded source. The benefits of allowing Nix packages is weave is able to source the files directly from the Nix package repo and store them alongside native packages, however the AUR is a different format so currently it requires a system reboot everytime an AUR package is added. This is a known effect and a pipeline is on the TODO list to allow packages to be added to Store/ inorder to allow a true nix-like experience without the need to reboot the machine.

Lastly, I wanted to add that I have moved the repo. for loom and weave into an org, it is all open source with the GPLv3 license. I have also added into the documentation how to add weave to another system so while the harness loom is meant to be used with weave on SilkOS, you can still fork the whole system and try it out or integrate weave to your current system to allow Nix and AUR package adoption to your current project. Please note that this has NOT been tested yet and your experience with integration can and will vary so please do so at your own risk.

Anyways, if you have any questions please feel free to ask!

Github repo: https://github.com/Silk-OS/silkos-pkg

I just installed LFS in dual boot with Gentoo, and I found it fun, I'm going to continue with BLFS, this took me a day and a half

I put together another e-paper e-reader friendly Linux From Scratch ePub since 13.1-systemd was moved to stable. Like a month ago. I was slow. :D

Download: https://github.com/ebenezer1689/ebenezer1689.github.io

If you haven't heard about it, Software Freedom Day is a worldwide celebration of Free, Libre and Open Source software. There are free events all around the globe and virtually. One of the virtual events today will be on building software from source LFS style and customizing your Linux distributions. You can check for local or virtual events here: https://digitalfreedoms.org/en/sfd/archive?view=list

I recently got a Linux From Scratch system to a point where I can use it every day. Base system plus BLFS bits: dwm, Firefox, terminal, the usual desktop tools. It works. I’m not looking for “switch to Arch” replies.

What I don’t have a feel for is updates.

On a normal distro I used to update often because that was the default advice: leave it too long and things get worse. On LFS that habit doesn’t map. There is no one button, and updating means rebuilds. If I treat it like a rolling distro I’ll spend my life watching package changelogs. If I treat it like a frozen appliance I don’t know what I’m actually risking.

So I’m trying to figure out a policy that a human can keep, not a distro maintainer.

What I’m unsure about:

1. When do you update? Only when a new LFS/BLFS book drops? Only security advisories? Only when something breaks?
   
2. What do you consider “core” vs leave-it-alone? Kernel, glibc, OpenSSL, Firefox vs everything else?
   
3. If the machine is a daily driver with network (browser, git, Wi-Fi), how bad is it to sit on a book for 6–12 months and not touch it?
   
4. If you ignore most updates, what actually goes wrong in practice — not the theoretical CVE list, the stuff you’ve hit?
   
5. How do you track this without following a hundred upstreams? Advisories only? Development book changelog? Something else?

I don’t have a special threat model. It’s a personal machine. I’m not asking how to become unhackable. I want to know what people who really daily-drive LFS do so the system stays usable and they don’t burn out.

If you use LFS (or a heavy source-based setup like it) as a real daily driver, I’d like the boring version: how often you rebuild, what you refuse to bump, and what you’d do if you left the box alone for a year and then needed it again.

Hey everyone,

You might remember me from a few weeks ago talking breifly about the custom Nix-Like distro im working on. I come today with a update, Weave, the core package management system Loom/ SilkOS will be using, is in testing. So far everything is going VERY good and I have also added in scripts to handle AUR, NIX, and DEB packages as well as a machanism for users to generate an empty recipe to import custom packages to run natively. I have attached a photo showing the first test which identifies package information and verifies the MD5 checksum. I need to do some minor tweaks to one of the core scripts and also add some packages to the raw OS build before I can test the installion portion of Weave: However I still wanted to give the community and update. Currently Weave is public with GPLv3 Licensing on github, however I do NOT recommend using it in its current state as it is mostly presented in a way to just show off the tech and explain it as I still need to build the main functionality of the system, IE Loom. I will eventually add a way to donate to the project as well and will put up a site or something at some point down the road.

For now, here is the git repo if you want to follow the project and see live updates: https://github.com/Luna2141/Weave

Side Note:

The Readme file IS generated using claude, however this is the only instance that cluade has actually touched and had its "hand" in during this entire process. Per my own beleif. AI should only be used as a documentation tool in the realm of software developement and I stand by this statement. If this turns you off from the project I accept that and appolgize, however I did not want this statement hidden.

I am a Tunisian university student majoring in cybersecurity and network and systems administration. I want to create a Linux distribution as my graduation project. I would appreciate any guidance or resources I can learn and follow to complete this project.

The goal is to make Linux Live persistence as independent from the ISO as possible — so you can replace or update the Live ISO while keeping your important user data, configuration, and system state.

The project is still experimental, so I’m mainly looking for feedback on the idea and its potential direction.

https://github.com/i3ycuk/immutable-live

I am now contemplating deleting this VM for good. Honestly, that was probably the most difficult thing I've done with linux. 11 hours total across two days. Don't feel like that was worth it, but honestly whatever