31–40 of 50 posts
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.
I did it about 20 years ago. It was basically copy and paste. Very little explanation of why are we doing this and what are the options. That is my memory of it.
The project itself was discussed a couple weeks ago here: https://news.ycombinator.com/item?id=24238015 and a month before that here: https://news.ycombinator.com/item?id=23787526 . If curious see also: 2019 https://news.ycombinator.com/item?id=20149111 2016 https://news.ycombinator.com/item?id=11829373 2012 https://news.ycombinator.com/item?id=4488162 2012 https://news.ycombinator.com/item?id=3677350 2011 https://ne…
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.
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.
Is my understanding correct that these are the things that you definitely have to work through with LFS?
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.
Mandrake ! Now there is a name I haven't heard in a long time :D
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.
I did it about 20 years ago. It was basically copy and paste. Very little explanation of why are we doing this and what are the options. That is my memory of 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.
How would you compare the experience of Gentoo / Arch vs LFS? I used to do a lot of Gentoo back in the day, and nowadays occasionally Arch, and while I believe it lead me to have a very solid foundation of a lot the system, especially the kernel bootstrapping process is a bit of a gray area to me (how do initial ramdisks fit in the picture for example). Is my understanding correct that these are the things that you d…
As for bootstrapping, it's been a while since I did it, but that was mostly just setting up grub and pointing it at your newly minted kernel. Grub handles all the "where is this on the disk" issues for you.
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.
I did it about 20 years ago. It was basically copy and paste. Very little explanation of why are we doing this and what are the options. That is my memory of it.
If you don't do it reflectively, and simply copy and paste command lines, then I agree, you're not going to get anything out of it.
As it was, I had to debug a few build issues here and there, with version drift; that too was educational.
The biggest thing to come out of it for me, apart from understanding the Linux boot process better and a greater appreciation for chroot, was getting comfortable with ./configure [options] && make && make install for installing software from source.
Earlier quoted context omitted.
>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.
Interesting, what about Go made you feel that you wished you knew less and why was it worth it? (I am mostly familiar with OOP languages and not so much with Go)