> Please don't submit comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills.
Furthermore, sure, it gets resubmitted but things on the internet change, new people are in the community, etc. Resubmissions over the course of a few years are bound to happen, the original comment was just linking previous conversations.
Then maybe it would be more appropriate for the poster to link to a blog article or some such which states what's been going on with LFS lately. Just linking to the main page doesn't really accomplish anything when the overwhelming majority of HN readers probably already know what LFS is. It's been around for 20 years, that the project exists isn't news. And the name of this site is, as it happens, Hacker _News_.
We post links to past discussions just to satisfy curious readers. It's great if others do that too! Just make sure that there are interesting comments to read at the other end of the link, since otherwise clicking on it is a no-op.
>HTTPS Everywhere noticed you were navigating to a non-HTTPS page, and tried to send you to the HTTPS version instead. The HTTPS version is unavailable.
Pretty much inexcusable for any company in 2019 (although, I run into this quite a bit...) let alone a tech-orientated one.
Without ssl, someone could hypothetically intercept it, modify the instructions slightly, and lead you to installing something malicious. They could also do other things like inject javascript, etc.
2016 https://news.ycombinator.com/item?id=11829373
2012 https://news.ycombinator.com/item?id=4488162, https://news.ycombinator.com/item?id=3677350
2011 https://news.ycombinator.com/item?id=3171448
Right? What is this, reddit?
> Please don't submit comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills.
Furthermore, sure, it gets resubmitted but things on the internet change, new people are in the community, etc. Resubmissions over the course of a few years are bound to happen, the original comment was just linking previous conversations.
Then maybe it would be more appropriate for the poster to link to a blog article or some such which states what's been going on with LFS lately. Just linking to the main page doesn't really accomplish anything when the overwhelming majority of HN readers probably already know what LFS is. It's been around for 20 years, that the project exists isn't news. And the name of this site is, as it happens, Hacker _News_.
/rant
Reposts are ok on HN if a story hasn't had significant attention in about a year. This is in the FAQ: https://news.ycombinator.com/newsfaq.html.
We post links to past discussions just to satisfy curious readers. It's great if others do that too! Just make sure that there are interesting comments to read at the other end of the link, since otherwise clicking on it is a no-op.
I build a LFS system recently, only to get stuck at the very last step (installing the bootloader), because my system uses UEFI.
LFS supplies a UEFI guide [0], but it's outdated and incomplete. I kinda gave up there, didn't have the time or energy to figure it out.
[0] http://www.linuxfromscratch.org/hints/downloads/files/lfs-ue...
This is probably the most straight-forward way to boot from UEFI:
https://wiki.archlinux.org/index.php/EFISTUB
Naturally, you will want to obtain efibootmgr via "from scratch" means.
Try this one instead [0], there have been some issues updating the website, as I gathered from the mailing list [1].
[0] http://svn.linuxfromscratch.org/hints/trunk/lfs-uefi.txt
[1] http://lists.linuxfromscratch.org/pipermail/lfs-support/2019...
I asked a few days ago if LFS was still a great way to learn internals, build a minimal bistro, etc: https://news.ycombinator.com/item?id=20149111
Just an excellent resource.
>HTTPS Everywhere noticed you were navigating to a non-HTTPS page, and tried to send you to the HTTPS version instead. The HTTPS version is unavailable.
Pretty much inexcusable for any company in 2019 (although, I run into this quite a bit...) let alone a tech-orientated one.
They have http listener on 443 port. Probably misconfiguration.
1. It's not a company
2. There is nothing on the page worth protecting with HTTPS
1. Replace "company" with "website".
2. It's the standard moving forward.
Without ssl, someone could hypothetically intercept it, modify the instructions slightly, and lead you to installing something malicious. They could also do other things like inject javascript, etc.