For those of you who don’t know, Linux From Scratch is a project that teaches you how to compile your own custom distro, with everything compiled from source code.

What was your experience like? Was it easier or harder than you expected? Do you run it as a daily driver or did you just do it for fun?

    • folekaule@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      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.

      • downhomechunk@midwest.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        I’m a long time slackware user, but I joined the party some time in 99 or 00.

        I never had the pleasure of installing from floppies, but I did compile my own kernels to speed up boot time. Sometimes they would boot, sometimes they wouldn’t. That was part of the fun.

        I’ve been on a retro kick lately. I have a pentium 200 mmx based machine that will eventually run a floppy installed slackware. Or at least it will if I can get it to work.

      • ReallyZen@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        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.

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        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.

  • Charadon@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    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.

  • deadcatbounce@reddthat.com
    link
    fedilink
    arrow-up
    2
    ·
    6 months ago

    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.

  • attilag@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    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!

    • 30p87@feddit.de
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      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.

      • attilag@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        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.

  • Brewchin@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    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.

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    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.

  • nbailey@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    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.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      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.

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    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. :)

      • pingveno@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        6 months ago

        There’s no level of package management, binary or source. There’s no practical way to uninstall or upgrade. It’s a toy for learning about Linux, which is great, but don’t expect it to have anything else.

        Edit: I seem to remember some third party package managers, but then you’re going beyond the base level documentation. And at a certain point, then you might as well just use a distro. If you want to have a very minimal package manager so you can learn about package managers, sure, it’s a learning tool.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      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.