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…
The fact that it, got "promoted/voted" to the front-page(again) is that not in itself proof that is is valuable and still worthwhile to be submitted again ?
Linux from Scratch 10.0
41–50 of 50 posts
Re: Linux from Scratch 10.0
#42Earlier quoted context omitted.
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)
probably because Go lacks a lot of features for abstraction that more powerful languages have. Once you've worked with generics for instance, its hard to go back to copy-pasting entire code snippets for data structures only to change a few lines here and there.
Parent has answered the first part of your question. As for why Go was worth the trouble, is because of its Utility nature, it has been the perfect replacement for Python as it doesn't have performance limitations(no need to find C extensions) and I'm rolling out production applications faster than ever before with Go.
Re: Linux from Scratch 10.0
#43This 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…
Re: Linux from Scratch 10.0
#44Earlier quoted context omitted.
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.
I also did it 20 years ago, but I got a lot more out of it. As each piece went in, I looked at it and what it did, and understood it as part of the whole that was built at the end. 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.…
Re: Linux from Scratch 10.0
#45The 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…
The fact that it, got "promoted/voted" to the front-page(again) is that not in itself proof that is is valuable and still worthwhile to be submitted again ?
Posts about new releases by well-known projects are something of a grey area, but if you want to read a long explanation of how we treat them, one is here: https://news.ycombinator.com/item?id=23071428.
Re: Linux from Scratch 10.0
#46I introduced the idea of using quilt for applying all the patches. I've noticed more recently that OpenEmbedded and Yocto do the same thing.
Re: Linux from Scratch 10.0
#47I 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'm not sure what you mean by the ins and outs of Linux. I assume you mean the userspace plumbing rather than the kernel? 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.
I'm inclined to go the systemd route because I use it myself regularly, but I also understand that systemd is a bit of a monolithic piece within Linux. I suspected that it might hide a lot of things that used to be more discrete and manual (but more unix-y).
Re: Linux from Scratch 10.0
#48I 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.
It's not like you will be up to your neck trying to set up dozens of services in LFS, is it? I mean does the choice really matter?
Re: Linux from Scratch 10.0
#49I 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
Re: Linux from Scratch 10.0
#50Earlier quoted context omitted.
The fact that it, got "promoted/voted" to the front-page(again) is that not in itself proof that is is valuable and still worthwhile to be submitted again ?
No, it's definitely not in itself proof of that. If we went with that standard, the front page would be mostly dupes. The few most popular/sensational stories would get upvoted over and over again. And then the threads would mostly be full of complaints about the dupes. Posts about new releases by well-known projects are something of a grey area, but if you want to read a long explanation of how we treat them, one is…