11–20 of 50 posts
They used to have a live CD for this but not anymore. What kinda setup does anybody who does this go for? I been wanting to try LFS for a while.
You just need a linux distro. I did it back in the day with mandrake linux. Probably easiest to start with ubuntu. LFS walks through isolation when you are building the system, so it doesn't really matter what you start with.
I never followed this but in ca 1995 I built a Linux boot / rescue floppy disk from scratch. The amount of confidence this gave me with Linux was insane, and I benefit from it to this day.
I would suggest anybody thinking seriously about Linux (if you want to call yourself devops or SRE) to go through a full build at least once.
Did this years ago and learned a ton, that said I'd probably never do it again. Once you know, you know. And sometimes you wish you knew less.
I would appreciate some thoughts on whether to go by the systemd route or the non-systemd route. The pros and cons.
I am eager to try this out. As a self-taught developer, I'm in a big turtles-all-the-way-down phase and I feel learning the ins-and-outs of Linux will give me intellectual satisfaction. I would appreciate some thoughts on whether to go by the systemd route or the non-systemd route. The pros and cons.
I am eager to try this out. As a self-taught developer, I'm in a big turtles-all-the-way-down phase and I feel learning the ins-and-outs of Linux will give me intellectual satisfaction. I would appreciate some thoughts on whether to go by the systemd route or the non-systemd route. The pros and cons.
In any case, I would only go the systemd route if it is what you want to learn. Otherwise just use runit -- much simpler and probably a bit easier to bootstrap. That leaves you time and energy to spend on other areas.
This is a great resource for those building embedded systems and want to understand how everything is really put together. Did this years ago and learned a ton, that said I'd probably never do it again. Once you know, you know. And sometimes you wish you knew less.
This is how I felt when learning Go, coming from a background of OOP languages. But it was worth it.
I am eager to try this out. As a self-taught developer, I'm in a big turtles-all-the-way-down phase and I feel learning the ins-and-outs of Linux will give me intellectual satisfaction. I would appreciate some thoughts on whether to go by the systemd route or the non-systemd route. The pros and cons.
Do non systemd, then do systemd
I did the systemd one a few weeks ago and I think that besides a few small affordances for some systemd quirk, the main issue was installing all the prereqs for building systemd (namely meson, ninja, which openrc probably doesn't require).
They give a nifty tar command to snapshot the disk, which could help create a "fork point" for the setup. `pixz` is very helpful addition in this case (e.g. `tar -cp $LFS | pixz -9 > my_backup.tar.xz`)