From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I tried it. Lot of fun and fustration. If You hava spare machine and few weeks to play around, do it. It boosted my knowledge and my skills a lot. I would not use it for daily driver, and never for work.
Documentation is super! If You have to do something by hand, it is one of the best source of info!
By the time I finished, half the system was extremely outdated and probably vulnerable to dozens of RCEs. Somehow I managed to compile KDE, but not Firefox. It always crashed the whole Laptop - 2 GB RAM wasn't enough.
All this true and I relate. Firefox is a beast. Compiling browser is a pain. Don't even tought to do KDE. I put together the ui with some suckless tools and had fun with them. Security, stability are a constant question with a system like this. Not a daily driver, used to gain a deeper knowladge. It is like bivaking behind the grandarents house in the foresst: uncomfortable, adveture, goodway to test Yourself and the gear, still have cookies. Not preparation for the alien zombies in the Amazonas.
Yeah, for me it just showed me how nice a customly installed distro is, and how fast it can be even on an old machine, so it was the first to get Arch installed on. Another Laptop followed, then my main PC, Server and finally the PI.
KDE, Gnome, the kernel, you can compile them without any problems. They're large and complex but they're well organized.
X is weird but it can also be compiled fairly easily.
Mozilla stuff is horrendous. There's no rhyme or reason, it's hard to find build instructions, half the time they don't work, when they do the build fails with obscure errors...
I'm from a time where there was ONLY compiling from scratch. No package managers either. Can't say I recommend it.
You haven't lived until you've installed Slackware from floppy disks and compiled the necessary network drivers into the kernel by hand. Good times, but never again.
What impressed me at the time was that it worked ; you'd pull huge amount of stuff and then waited in front of a real-life Reversed Matrix full of mysterious hieroglyphs. But Slackware would compile Ardour, Jack, Jamin and whatever else. Yeah it took a while to fetch all the libraries, but then it just did it.
Last week localsend wouldn't compile on Arch, and took hours to fail it.
I am pretty sure I compiled the kernel once a month back when I had a Pentium 133. Looking back, compiling the kernel must have been a huge chunk of what that machine accomplished.
To be fair there was less to compile, but that still sounds like a lot...
I did it back in 2020 when we all had nothing better to do. Got as far as installing X11 and Openbox, and halfway through setting up the toolchain for Firefox.
It was fun - the kind of fun digging a big hole is. It’s not for everybody, but I sort of enjoyed it.
I did it, learned a lot. But it's not really a system that can be maintained very easily. You don't even have a package manager. :)
Back when I did LFS I dealt with this by giving each package an /opt prefix, symlinking their respective bin/, sbin/, lib/, man/ and so on dirs under a common place, and adding those places to the relevant system integrations (PATH, /etc/ld.so.conf etc.)
I put together a bash script that could manage the sumlinks and pack/unpack tarballs, and also wrote metadata file and a configure/make "recipe" to each package dir. It worked surprisingly well.
A handful of packages turned out to be hardcoding system paths so they couldn't be prefixed into /opt (without patching) but most things could.
You were on your way to reinventing Gentoo
I've done it before. It's not particularly difficult, just very time consuming. And at the end, you're left with a distribution that's not really that useful without repackaging everything you did into a package manager so you can do updates without borking it.
Great as a learning tool to see how the whole GNU/Linux stack works, but not something you'd use practically.
Did it for shits and giggles once back in 2006. I think everyone serious about learning Linux at a "pro" level should go through the process at least once, even if the system gets wiped afterward in favor of a more usable distro. Teaches you what the standardized core components are and what they do, and gives you a clear understanding of how Linux is structured. That knowledge will carry on over to other distros and will make it much, much easier to troubleshoot issues with your system if you know how the parts of that system work.
For those unaware or who never used it, it has a huge setup guide with copy/pastable commands to guide you through each step. Theres even an automated script from what I remember. They don't just give you a pile of source code and tell you "good luck".
I ran it as my primary distro on my main machine for a while way back when. I don't recommend that.
What I do recommend is going though the entire process even if it's just in a VM. It's incredibly educational and will teach you a ton about Linux and OS construction in general. I used to recommend it to everyone I was teaching linux/ Unix too and all the students who actually went through it and completed it now have successful IT careers. 100% an incredibly valuable teaching resource, you will look at all OS's with new eyes after you've built one bit by bit from source by hand.
Its on my bucket list. Maybe a fun project after I retire
“Welcome to the first day of the rest of your life”
That is just the gateway drug to bootstrapping.
Check out https://github.com/fosslinux/live-bootstrap
if you want the real hard stuff.
I did it during the gcc 3 transition. I used a very new gcc 3 (maybe even pre-release), which wasn't at all recommended. A couple of (most?) C++ packages didn't compile (some change having to do with namespace scope), which meant I had to fix the source of some packages (generally pretty trivial changes, usually having to prepend namespace:: to identifiers). Overall this problem was pretty rare, like it affected less than 1% of C++ files, but with things like Qt or Phoenix (or whatever Firefox was called back then), with thousands of files, I had to fix dozens of things. I guess running into problems made it more interesting and fun actually.
Did I learn anything? The main thing I learned is about all the different basic packages and what sort of binaries and libraries are included in them and why you need them. Also about some important config files in /etc. And a bit of shell experience, but I dare say I knew most of that stuff already. How much you learn depends a lot on how much you already know.
Overall what I learned was not very deep knowledge, nor was it a very time-efficient way to learn. But it was a chill learning experience, goal-oriented and motivating. And it made me more comfortable and confident in my ability to figure out and fix stuff.
Also it's obviously not practical to keep that up to date, so I switched back to a distro after a couple of months of this.
I found it was useful for learning bits and pieces of the extra knowledge around working on a Linux system. Yeah, you're not going to learn how a kernel works or how anything about data structures. But you will learn how to apply a patch, be exposed to a lot of work with the shell, and come to appreciate the work that goes into a modern distro.
Did it about 10 years ago. Didn't really understand half of what I was doing at the time but it was a fun way to spend a weekend 😁
It was a lot of fun for me. I did it without a virtual machine (would not generally recommend) on a older laptop I wasn't using anyway. I wasn't very successful in the end however. My own built kernel couldn't produce any vga output. I tried to fix it for a handful of nights, but in the end gave up and called it good enough :P So I might comeback to it later to fully complete an installation.
But it was good learning oppertunity. It showed that just compiling a version of the Linux kernel isn't very complicated. It even comes with a very nice TUI to select your build options!
I did. First page and said fuck it and left. Don't have the energy for it. Lol
I did a long LONG time ago. I don't even remember so I'd say 20 years ago. It was very interesting. I do recommend doing it at least once... well maybe only once actually. If possible do it on a real computer, not a VM, so that you don't get distracted and feel just a bit of risk. Obviously do NOT do it on your main computer where you have important data, just in case.
PS: I do build some things from scratch, including "big" ones like Firefox. I do it because I can prototype with them by modifying just the bits I need. I do like learning how things are made. That being said I don't think it's valuable as an entire system, only on a need to do basis. The true benefit IMHO is the learning, not the running system, so no, not at as a daily driver.
TIL this is a thing. I started doing that over 30 years ago with SLS and Slackware when that was the only choice.
This was pre-PnP (also pre-JPEG!), so you had to know all the addresses, IRQs, DMA info, etc, of your hardware or you'd get... unexpected results. make it and they will come...
After countless distros and flavours over the years, I still use Debian for servers and now use EndeavourOS for desktop/laptops.
NCommander did it for a Christmas charity stream a few years back: https://www.youtube.com/live/tCh0XjyIAKU
Here is an alternative Piped link(s):
https://www.piped.video/live/tCh0XjyIAKU
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
I have never done Linux From Scratch but I have been using Linux long enough that I remember that is how things were. Compiling the kernel was pretty routine. Getting XFree86 up and running could be true black magic though. You were literally controlling how the electron beam moved across the screen.
One of my systems is running Red Hat 5.2 ( not RHEL - the pre-Fedora Red Hat ). I think it has GCC 2.7.2 on it.
For some reason, I want to get a recent kernel and X11 running on the Red Hat 5.2 box. It would be cool to get Distrobox running on it while leaving everything else vintage. I had been thinking that LFS might be the right resource to consult. This article will hopefully kick me into gear.
Did it to learn. Mostly because I had no wifi / internet at home during the time, but did have a burned CD and a book. Was useful, but when I started using Linux as a daily driver I went straight to Ubuntu, and later Fedora
Do recommend for learning and tinkering though.
I did LFS some years back, but only enough to get to a basic working system. It eventually devolves into doing similar steps to compile each piece of software, which after you've compiled a bunch of packages already kind of becomes repetitive. The path of getting there is pretty fun though, it's a lot of reading and I learned a lot.. including that I'd never want to maintain a system like that.
Good learning experience though.
The consensus seems to be: go for it for the learning experience.
I would agree. It's useful to know all the parts of a GNU/Linux system fit together. But the maintenance can be quite heavy in terms of security updates. So I'd advise to do it as a project, but not to actually make real use of unless you want to dedicate time going forwards to it.
For a compiled useful experience gentoo handles updates and doing all the work for you.
Gentoo's USE flags are fuckin' amazing.
Haven't tried LFS yet but I have had my share of compiling custom Arch kernel (basically just making it smaller and boot a little bit faster), or cross-compiling various stuff for embedded and having to crawl through some of the lower level stuff.
It might be that time of a year to give LFS a try now that you mention it.
It’s definitely on my Linux bucket list. I’ve been kinda thinking about making a distro myself (specifically because I want to try some unusual and niche things in terms of system layout and package management), and that would be a good starting point.
Yes, back in the early 00s. We toyed with making a net-bootable image with it for our computer labs, but it was really not practical. It definitely taught me a ton about systems, though.
I got through some of it then life got busy. It was a good and interesting experiences. I didn't finish with a fully functional hand crafted artisinal home desktop, though.
New machine arrives next week. LFS is on my TODO list for it.
Didn't know about this, might give it a try later on, thanks for sharing 🌻
It’s a good time. I built it for a little laptop that was too small for anything else. Cross compiled the binaries on a normal computer.
Before the ArchLinux wiki became as good as it is, people like me used the Gentoo and LFS wikis as documentation for Linux.
There isn't quite enough time in the world for me to be able to use LFS in anger as much I would wish. We make do with source distros with source managers like Gentoo (surprise!), Funtoo and others which give the source distros users just enough helping hands of dependency management.
Real tears would be shed were for LFS to disappear.