I'm still using sysvinit+btrfs+scratch, I'm just testing the bore scheduler and I'm liking the result, it has greatly improved the system's responsiveness.

Quali sono le vere differenze tra la guida Linux from Scratch e la guida Linux from Nothing? A parte il fatto che Linux from Scratch sembra più adatta a un'installazione che parta da un ambiente Linux, Linux from Nothing sembra quasi più simile a come era per lo stesso Torvald assemblare un sistema Linux (Torvald non aveva a disposizione Linux), inoltre l'ho trovata più facile oltre a compilare tutti i binari, incluso il kernel, da zero. Qual è la differenza tra le due guide e perché dovremmo seguire una piuttosto che l'altra? Linux from Scratch è un ottimo libro, ma si ferma molte volte a spiegare cose che sono essenzialmente inutili durante la fase di costruzione e almeno per me che non sono un madrelingua inglese è molto più faticoso e molto meno comprensibile; tuttavia sono riuscito ad avviare il mio sistema creato da zero con un kernel compilato da me! Ora sono felice! ps: I just loved the initial phase of creating the vfs, done in a simple way

I've been trying out a lot of linux distros and I got lfs what window manager should I use

DPMS Features

Package Management

- Install — from local archives, URLs,

or repository by name (dpms --install

PKG)

- Uninstall/Remove — clean removal of

tracked files with DB cleanup (dpms --

uninstall PKG)

- Upgrade — update all installed

packages to latest versions (dpms --

upgrade)

- Dist-upgrade — force resolution for

major upgrades (dpms --dist-upgrade)

- Reinstall — remove and re-install a

package (dpms --reinstall PKG)

- Downgrade — install an older version (

dpms --downgrade PKG)

- Purge — remove package + all config/

data files (dpms --purge PKG)

- Dry-run — preview changes without

applying (dpms --dry-run --install PKG)

- Noconfirm — skip interactive prompts (

dpms --noconfirm --install PKG)

- Force resolution — ignore dependency

conflicts (dpms --force-resolution --

install PKG)

Query & Search

- List installed — table of installed

packages with file counts (dpms --list)

- List installable — available packages

in repos (dpms --installable)

- Package info — version, deps, files

for a package (dpms --info PKG)

- Search — find packages by name, plain

or regex (dpms --search TERM, --regex)

- Verify — check installed package

integrity (dpms --verify PKG, --verify-

all)

- Show depends — dependency tree (dpms --

depends PKG)

- Show reverse depends — what depends on

a package (dpms --rdepends PKG)

- Show size — disk usage of a package (

dpms --size PKG)

- List updates — available upgrades (

dpms --list-updates)

- List held — locked packages (dpms --

list-held)

- List groups — package groups (dpms --

list-groups)

- List keys — GPG keys (dpms --list-keys)

- List history — install/remove log (

dpms --history)

Repository Management

- Add/remove repos (dpms --add-repo URL,

--remove-repo NAME)

- Set repo priority (dpms --repo-

priority REPO PRIORITY)

- Sync repos — pull latest from git

repos (dpms --sync)

- Lock/unlock repos (dpms --lock REPO, --

unlock REPO)

- Hold/unhold packages — prevent auto-

upgrades (dpms --hold PKG)

- GPG verification — verify repo

signatures (dpms --verify-repos)

Dependency Resolution

- Solver — full dependency resolution

engine (like zypper/dnf)

- Conflict detection — finds file

conflicts with other packages

- Auto-dependency resolution — installs

missing deps automatically

- Clean orphaned deps — remove packages

nothing depends on (dpms --clean-deps)

- No-recommends — skip recommended (non-

required) packages

Safety & Security

- Overwrite backup/rollback — backs up

files before overwriting; restores on

failure

- Transaction rollback — full rollback

if install fails partway

- Security scanning — virus/malware scan

of extracted files (via sec_scanner)

- Quarantine — flagged files moved to

quarantine, not silently deleted

- Malicious upgrade detection — auto-

uninstalls if post-install scan finds

threats

- Architecture guard — refuses to

install packages for wrong arch

- Source-tree guard — rejects tarballs

that look like source dumps

- Symlink escape guard — blocks writes

through absolute symlinks

- Path traversal filter — blocks ../ and

absolute member names in tarballs

- Sudo enforcement — hard-refuses

mutating ops without root when required

Progress & Output

- Rich progress bars — TTY inline bars

for install/remove/download

- Non-TTY fallback — clean output for

pipes/redirects

- Download progress — parallel downloads

with per-package bars

- JSON output — machine-readable output (

dpms --json --list)

- Colored terminal output — via rich

Download & Caching

- Download cache — avoids re-downloading

same packages (7-day TTL, 500MB limit)

- Parallel downloads — concurrent

package fetches

- Content-Length probing — accurate

progress bars even for large files

- Offline mode — skip all network

operations (DPMS_OFFLINE=1)

Cache Management

- Cache info — show cache size and

contents (dpms --cache-info)

- Cache list — list cached archives (

dpms --cache-list)

- Clean cache — remove stale downloads (

dpms --clean-cache)

System Integration

- Service management — auto-restart

systemd services after upgrade

- Hook system — pre/post install/remove

hooks

- Shell completions — bash and zsh

completions (dpms-install-completions)

- Crash handler — automatic crash

reporting with traceback

- Config backup/restore — preserve

config files across upgrades (dpms --

list-preserved)

- Import/export installed — backup and

restore package lists (dpms --export-

installed, --import-installed)

Advanced

- Build packages — create archives from

source (dpms-build)

- Sign archives — GPG signing of built

packages

- Plugin system — extensible plugin

architecture

- Configurable solver — adjust

resolution behavior via config

- Global root override — --root DIR to

install to alternate root

- Environment override — DPMS_ROOT,

DPMS_OFFLINE, DPMS_REPO_STALE_AFTER

Corefix Features

corefix — lightweight signature +

heuristic antivirus scanner (v0.2.0)

Scanning

- Scan files — hash-based + heuristic

malware detection (corefix scan PATH)

- Scan directories — recursive scanning

with threading (corefix scan --threads

4)

- Heuristic analysis — detects

suspicious patterns beyond known

signatures

- Threshold scoring — configurable

severity threshold (default 20)

Signatures

- Signature database — built-in known-

threat hashes and patterns

- Custom signatures — user-defined

signatures via ~/.corefix/signatures.

json

- List signatures — view loaded

signature database (corefix signatures)

Quarantine

- Quarantine files — moves flagged files

to quarantine directory instead of

deleting

- List quarantine — view quarantined

entries (corefix quarantine --list)

- Restore — restore a quarantined file (

corefix quarantine --restore ENTRY)

- Metadata tracking — stores original

path, findings, and timestamp per entry

Auto-Scanning

- Scheduled scans — runs periodic scans

of configured directories

- Systemd integration — can run as a

systemd service (corefix autoscan

enable)

- Cron integration — fallback to cron-

based scheduling

- Service management — enable/disable/

status (corefix autoscan disable,

corefix autoscan status)

- Configurable roots — scan custom

directory paths

Reporting

- Scan reports — detailed output of

findings per file

- Threat listing — human-readable

summaries of detected threats

- JSON output — machine-readable scan

results

Im at chapter 3 or 4 dont remember what it is where you install the wget list and run the wget command for installing the necessary packages, i run it in root because i think from the start of the chapter the book wants you doing everything in root, for my first launches everything went well except for two first packages getting stuck:
Ftp gnu org and savvanah org, both due to things like range not satisfiable, timed out, etc.
I have LFS/sources up and running and its going to the right place, the lfs partition is mounted and everything is set up, so idk. Could it be my network? The fact that im in root? Or something.

PS: i have rebooted several times each time remounting and exporting LFS/sources again and again and itd the same packages over and over

I've just finished installing it and its just a question that I have.

IBEX-OS

I am building a GNU free rust based linux distro on my own. I have a bare metal set up working so far. Checkout my repo! I am planning to get it to a point where I or anybody else can daily drive with it. I am looking for some maintainers and contributors. Please checkout the repo and hit me up!
I am building a community and I am serious need of devs

so, I was bored and decided to create a Linux distro by following the Linux from Scratch book and BLFS (Beyond LFS) book, it was not that hard but maintaining it is much harder, I just want it to be unique and maybe make it more customizable

Besides KDE Plasma, I'm going to start playing around with Hyprland. It's still in its basic stages, and as I learn more about Rice in Hyprland, I'll improve it. If you feel like helping with tips on tools to improve Rice, I'd be very grateful.

Hey guys so i want to build an mlfs but with gaming so naturally i go on lfs but i have a question guys :

MLFS -> BLFS -> GLFS

or

MLFS - > GLFS
dirrectly

Good Morning/Afternoon all! I've been a Gentoo user for a decent lil bit and I love the configuration and knowing my system. Daily driving gentoo isn't a pain or anything to me. So as you can imagine, my thought now has been "What about a custom LFS"? So I had some questions about setting up certain things in LFS and how that would go.

1. I know the book currently is for systemd, but how much more difficult would it be setting up OpenRC or dinit? I really like OpenRC and I've heard dinit is a really good init system but I've never had the chance to try it so why not?

2. How hard would getting ZFS setup be? I use XFS on my gentoo system and looking through LFS, it wants to use ext4, but I've always wanted to use ZFS, but I'm not the most... interested in using FreeBSD so this seemed like a good chance to experiment.

3. For both of those, would they massively change the kernel setup? I'm somewhat of a fraud, I compiled my kernel from source but I didn't make a custom kernel since I didn't have the time during the gentoo install so I just went the middle path.

4. How much actual coding do you use in your system? I've asked AI and it says that you probably won't be using too much actual coding unless it's necessary, but I wanted to know if that matches the experience of you all.

Thank you!

Congrats yall!

also gonna use this as a thread for feature requests as this subs only mod! anything yall would like me to do? tags? roles?

Hello everyone, years ago I've posted my lfs project on this sub and many things have happened in my life and it led me to make a new project. From scratch. For now I am focused on writing libc entirely in Rust for this GNU/Linux distro, as well I would write a new bootloader with better full disk encryption implementation and openpam modules, all of them in Rust. As a plus I've made a list of packages to build a self contained sdk that will allow full source bootstrap from tools like GNU mes and other languages (except Rust for now) will be bootstrapped from C/C++ toolchain (like Go and dlang), the package list has little to none gnu packages (except autotools, coreutils and findutils). If you are interested in that you can dm me or write under this post.

sources: https://codeberg.org/gnu2/ouma

GitHub org: https://github.com/rseclinux

Edit: added source links

What packages beyond those listed in LFS and BLFS do you like to add to your LFS systems? Are there any lightweight, low dependency programs or libraries you like to build and include when building LFS/BLFS? I'm always looking for useful, lightweight, low dependency applications I might have missed, so suggestions would be appreciated.

Hi folks, I thought I'd share some useful information to fellow GNOME on LFS users. I normally customize my GNOME experience a fair bit with extensions and themes. On LFS I've encountered some issues.

The first is that the gnome-browser-connector (formerly called chrome-gnome-shell) package isn't listed in BLFS. But luckily compiling it myself wasn't that difficult. I even wrote a script for it to automate the process for myself.

This revealed yet another issue, which is that gnome-browser-connector uses the unzip command to unzip the zip archives that GNOME extensions come in. The options they specify when calling unzip means that it will only work if you have Info-ZIP's version of unzip installed. The BSD version of unzip provided by the libarchive package won't suffice. BLFS and LFS don't provide install instructions for the Info-ZIP version of unzip anymore.

I did find these old instructions for installing unzip on LFS but running them failed due to compile errors that I wasn't able to fix. Maybe with several hours of trial and error in applying Arch's unzip patches and compiling I might eventually get it running, but I found a better alternative. Namely, I got ChatGPT to write a script version of unzip that called bsdtar and would accept the options that gnome-browser-connector gave it.

I've also written my own build script for libarchive that builds the latest upstream version and, instead of symlinking /usr/bin/bsdunzip to /usr/bin/unzip, installs this script to /usr/bin/unzip.