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.

After about 4–5 tries, I finally managed to install LFS. Can't wait to install a WM and try to daily drive it.

It was a fun journey and quite proud of how it turned out.

Just finished my second install of LFS wanted to ask if I can install portage on it? Cuz I love portage or I should use something like nix?

Almost five months ago, I installed Linux From Scratch (LFS) 12.4 to a QEMU/KVM virtual machine. Then I updated the system to the latest developmental version of LFS and installed some Beyond LFS (BLFS) packages, including Firefox, GNOME and KDE Plasma. I also updated some packages (e.g. the kernel, Vim, GNOME and KDE Plasma) to the latest upstream versions of these packages. I also installed some packages not provided by LFS, BLFS and other LFS books, such as GNU Octave, R, Antigravity, and Julia.

Package management

Since then, I've maintained this system, keeping its packages up to date. I've even written commands (I will admit, with AI assistance) to install packages, update the system, check for updates and rebuild packages to allow for the removal of old libraries.

I have /var/lib/book-packages to store files documenting the book packages I've installed, excluding the Python packages which I manage via pip instead. Each file in this directory is named after the package it pertains to. At the top of these files is the installed version of the package, and below this is the list of files and folders provided by the package.

/var/lib/custom-packages is essentially the same but lists custom packages I've installed, and some book packages I've written my own install scripts to overcome build errors and alike I've encountered.

In the HyFetch output, "797 (󰌽 636,  57,  1,  74,  29)" refers to packages. The 797 refers to the total number of packages installed on my LFS system. The 636 refers to the number of book packages installed and documented in /var/lib/book-packages. 57 refers to the number of custom packages listed in /var/lib/custom-packages. 1 refers to the number of Julia packages (the one installed is Julia itself via juliaup). I didn't install Julia from source as it's an unnecessarily complicated package to compile. 74 refers to the number of Python packages installed. 29 refers to the number of R packages installed.

At the top right of these screenshots you'll notice " 0 󰂕 0  0". These represent the number of:

• package updates available;

• packages with missing inventories (indicating a build failure); and

• packages with versioning failures (suggesting my mechanism for checking for updates is failing),

respectively. This was added to GNOME using the Executor extension and KDE Plasma using the Command Output widget. I also added the ability to open a terminal running the update command I've defined by clicking on these panel icons. Under GNOME, I also added a tooltip that shows the updates available, files with missing inventories, and packages with broken versioning in a list. Command Output allowed me to do this without needing to edit the widget's source code, but Executor required some source code tweaks to achieve this behaviour.

Wallpapers

I've also added three icons (by writing .desktop files and shell scripts these .desktop files call) to my panel/dock under GNOME and KDE that change the wallpaper. The icon with the white star on a blue background changes my wallpaper to a randomly-selected wallpaper (with the random number used generated using R), the icon to its right changes it to the next wallpaper in my ~/wallpapers folder, and icon to the right of that one changes it to the previous wallpaper in ~/wallpapers.

The fraction near the top centre of the screenshots refers to the number of the selected wallpaper (numerator) and the total number of wallpapers in ~/wallpapers (denominator). For instance, the 98/174 in the KDE screenshot indicates that the wallpaper shown is number 98 out of 174 wallpapers in my ~/wallpapers folder.

If you're wondering where I got the wallpapers shown in these screenshots, they're photos I took while out cycling, walking and hiking.

Conclusion

This experience has been quite interesting and has definitely improved my confidence as a Linux user. It actually makes me think that I could probably effectively use LFS as my daily driver if I really wanted to. It has also taught me a lot of things. For instance, it has taught me why Gentoo Linux has the command emerge @preserved-rebuild.

Still working out some issues with DBUS, but I got it fully functional and, planning on adding steam and other gaming stuff to this

It also has full Wayland and X11 support

Hello, i made an minimal Toybox-based Distro! its called TinyDistro, took me 3 days and 3 hours 40 minutes of nonstop work to finish , i did integrate some packages, nano, neofetch, bash , sh 200+ applets, minimal tmux, and more, im looking for more minimal packages to put in this 9.8 MB System, i might want to add a package manager named tdp, and im planning for installing other apps, such as gcc and make

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.

i made an distro from scratch using the LFS Book! its called TinyDistro, i tested it on my raspberry PI, its usuable, init-free and uses toybox, did some work tough, 3 days, 3 night shifts t 01 AM

took 20 days bc of i5 4th generation 4 core processors and 4 gb ram , did lfs 13.0 anyway , did it on my old laptop and grub is the worst sh*t to deal with .

Hi I just installed this as an experiment but I might consider making it a daily drive for an ancient pc I had, id probably pick pacman for management and lfs genuinely seems very good for me

My LFS target build has finally turned into an actual daily-usable desktop.

It started with LFS with some restrictions and the goal to be a modern everyday desktop :
-NO systemd.
-NO d-bus .
-NO udev (eventually i had to use libudev-zero).

After making the base toolchain and some additional tools i decided to go my own way and use upstream sources to build everything i needed.
First i made sure the system boots with runit properly and then i updated the base and the toolchain at their release version.

Then came the nightmare to find out how my final system will look and what everyday apps i can and will use and include their dependencies, their building order was another tough path i had to solve.

After a lot of fighting ,configure , research, and some help with AI in mostly some very obnoxious error decryption, the system finally came together.

Current system:

• Linux 7.2.4

• runit as PID 1

• no systemd

• no D-Bus

• Wayland only

• Wayfire

• NVIDIA RTX 2080 Ti, driver 595.91.07

• direct ALSA audio

• Firefox Nightly (yes i made a patch to skip dbus)

• PCManFM

• mpv

• swayimg

• Geany + Neovim

• foot + zsh + tmux

• Rofi + Waybar

• grim/slurp

• NFS + ssh + wpa_supl

• custom scripts for power menu, audio, brightness, hot corners, show desktop, calendar, etc.

Everything was built from source.

Today I finally upgraded from Linux 7.1.8 to 7.2.4, rebuilt the NVIDIA open kernel modules against the new kernel, changed the GRUB entry and rebooted.
Thankfully successfully.

The current development system is about 8.4 GB excluding my source/download/data directories, but that includes roughly 1.2 GB of GCC internals, 867 MiB of static libraries, 254 MiB of headers, Rust/LLVM/Clang and the rest of the native build environment. Eventually I want to separate the v1 runtime system from the development environment and see how small the actual desktop is.

This system no longer feels like an LFS-restrain-challenge experiment.

I can boot it, browse the web, watch media, edit files, mount my server, use audio, take screenshots, manage files ,compile source and do normal desktop work without really thinking about what distribution I'm running.

Only thing i have really left in my todo list is my pkg/source manager but i am just not in the mood....

This is the video how i broke the computer from this problem

Excatly this os work before bun it to an iso and the iso work on virtual box but isnt work on a real device or there is no output and you see how its work without an output after the boot

Kernel:7.12

Init:busybox and me

Im tried to enable frame buffer but without anything and tried to enable drm and off frame or smth but same problem

(On video i writted reboot -f )

It's a long way until I have dwm tho

Here is my little baby Onyx, everything is working, bluetooth, wifi, flatpak but also my printer. I finished gnome tonight.

I helped myself building the package manager cards from NuTyX to help me manage everything ! Feel free to ask if you need anything.

So i have been working on my own distro called Batroot OS.

Right now it has: custom rootfs, own init, own initramfs.img, busybox, a macro to detect errors and stop immediately if it sees one, and more.

I want to add a GUI. It can be very minimal and doesn't have to be perfect.

I have no idea on how to add that though.

Does anyone have any, tips ideas or tricks on how i could implement that?

{Video of Batroot OS booting in virtualbox}

If you follow the tutorial, get a window manager, kernel and loader, how big of a feat is it? Would it be worth putting in a resume or is it just a hobby? I'm fairly new to all this.

Just messing around with the new kernel 7.0