Earlier quoted context omitted.
> And you add the bootloader dead last, even though it’s the first thing you see when you boot a Linux machine? That actually makes perfect sense. If you did the bootloader first, how are you going to build it? How do you know what to boot from which filesystem on what device? By the time you've got your root filesystem complete, it's easy to tell. If you do things step by step incrementally, you keep having to go fu…
Except that if you fail to install the bootloader - which happened to me many times - then you do not have a working system. So really the prior argument makes sense. IMO the guy is right - LFS could be way better. But it has this current structure and does not deviate from it. That's the bad part. > If you do things step by step incrementally, you keep having to go further back in the process. Starting over repeated…
Linux from Scratch
71–79 of 79 posts
Re: Linux from Scratch
#72Earlier quoted context omitted.
I'd like to counter your comment. LFS helped me a lot. It taught me how to compile packages manually, and how GNU/Linux components fit together. Armed with that knowledge, I could do things others could not do: - Make applications that bundle/automatically download their dependencies, compile them with custom flags (static linking) - Diagnose build errors buried in deep dependencies when using vcpkg - Compile program…
Learning how to compile packages manually it was a common skill long before Linux came to be, and how GNU/Linux fits together could also easily be learnt with Slackware or Yggdrasil.
I certainly do not miss compiling X11!
Re: Linux from Scratch
#73Earlier quoted context omitted.
> And you add the bootloader dead last, even though it’s the first thing you see when you boot a Linux machine? That actually makes perfect sense. If you did the bootloader first, how are you going to build it? How do you know what to boot from which filesystem on what device? By the time you've got your root filesystem complete, it's easy to tell. If you do things step by step incrementally, you keep having to go fu…
You build it on your non-lfs computer. What is the other option? And you dont need to boot anything, just a busy loop after a log "Hello World" is enough, if you feel fancy, maybe make a simple shell ?
Re: Linux from Scratch
#74Earlier quoted context omitted.
> And you add the bootloader dead last, even though it’s the first thing you see when you boot a Linux machine? That actually makes perfect sense. If you did the bootloader first, how are you going to build it? How do you know what to boot from which filesystem on what device? By the time you've got your root filesystem complete, it's easy to tell. If you do things step by step incrementally, you keep having to go fu…
Agreed, it's near the end of the Gentoo installation as well. If you forget to install GRUB, just chroot back into it and continue. If I installed the bootloader first, I'd have to remember to run dracut after the system was installed. Or I install it last, create the init at the same time and make a habit of it.
Re: Linux from Scratch
#75LFS takes the wrong approach in my opinion. I did it once manually over a couple of days. I suppose I hoped enduring the pain of waiting for the packages to compile would somehow make me smarter. It didn’t. I didn’t learn much. It was like following a baking recipe. I know I need to add eggs and sugar in the ratio it says but I’d be damned if I could tell you why that specific ratio works. It’s just too much to take…
Bare LFS is not enough (I run my own): you need a kind of userland (above glibc) multi-version system which some kind of "atomic-ish" switching (always have a stable SSH running in case something goes wrong, better than unplugging the system disk and fix it on another computer).
For linux, same thing, with a kind of flip-flop-ing for updates/fix/etc.
The insight that gives you will probably scare you: the current "open source" stack is an abomination (the worst is the SDKs I think).
That's why we need _LEAN_ open source, and that includes the SDKs.
Re: Linux from Scratch
#76Re: Linux from Scratch
#77Re: Linux from Scratch
#78Earlier quoted context omitted.
I'd like to counter your comment. LFS helped me a lot. It taught me how to compile packages manually, and how GNU/Linux components fit together. Armed with that knowledge, I could do things others could not do: - Make applications that bundle/automatically download their dependencies, compile them with custom flags (static linking) - Diagnose build errors buried in deep dependencies when using vcpkg - Compile program…
Learning how to compile packages manually it was a common skill long before Linux came to be, and how GNU/Linux fits together could also easily be learnt with Slackware or Yggdrasil.
Re: Linux from Scratch
#79LFS takes the wrong approach in my opinion. I did it once manually over a couple of days. I suppose I hoped enduring the pain of waiting for the packages to compile would somehow make me smarter. It didn’t. I didn’t learn much. It was like following a baking recipe. I know I need to add eggs and sugar in the ratio it says but I’d be damned if I could tell you why that specific ratio works. It’s just too much to take…
The step by step is the right approach... but you'll discover that many 'components' are _INSANE_ and that includes their SDK. Bare LFS is not enough (I run my own): you need a kind of userland (above glibc) multi-version system which some kind of "atomic-ish" switching (always have a stable SSH running in case something goes wrong, better than unplugging the system disk and fix it on another computer). For linux, sa…
I promised myself not to work for any of those anymore :)