21–30 of 50 posts
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.
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 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.
Earlier quoted context omitted.
Do non systemd, then do systemd
Is it possible to do the systemd book and then non-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…
Earlier quoted context omitted.
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.
At this point I'd recommend starting with Manjaro. Nothing compares to the AUR.
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.
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.
The biggest issue with doing it is the time it takes. Some of the compiling can take ages, and you tend to forget you are waiting for it, and get busy with something else, only to come back 3 days later with no idea what stage you got to!
My advice is to use the fastest machine you have as the host for the LFS build process - it'll take a lot of the pain away.
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.
>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.
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.
>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.
Earlier quoted context omitted.
At this point I'd recommend starting with Manjaro. Nothing compares to the AUR.
You don't need the AUR for LFS.