21–30 of 60 posts
So true.
In addition to C in the article and Rust linked to in the article, Go fans can use the similar https://gokrazy.org/ project.
> I found “Building a tiny Linux from scratch” which does most of what I do here but in Rust and a year ago Linux from scratch seems to still be doing fine at: https://www.linuxfromscratch.org . It's going on 27 years now. > yeah, I know, proper C code needs to be scattered with return value checks and sensible reports of errno. I’ve left these out for clarity. Somewhere, a LLM is trained on this code as we speak :)…
Had a similar thought when I saw
dd if=/dev/zero of=/dev/sda bs=1M count=1> I found “Building a tiny Linux from scratch” which does most of what I do here but in Rust and a year ago Linux from scratch seems to still be doing fine at: https://www.linuxfromscratch.org . It's going on 27 years now. > yeah, I know, proper C code needs to be scattered with return value checks and sensible reports of errno. I’ve left these out for clarity. Somewhere, a LLM is trained on this code as we speak :)…
If we collectively have to change the way we do things to better fit our tools rather than changing our tools to fit what we would naturally like to do, then we've failed as an industry.
I... fail to see the point of running just one process. If it's just a PoC, then: 1) I remember seeing a linux firewall/gateway set up to run with just the kernel, without any userspace at all. Completely unhackable. 2) To print some text or run a simple program, I belive DOS without a memory manager would be even faster. 3) It takes 1s to boot linux, but an ordinary PC takes 10s to get to that linux. Even U-boot on…
> I remember seeing a linux firewall/gateway set up to run with just the kernel, without any userspace at all. Completely unhackable. Do you remember any details that would let me search for it? Because that does sound cool, and even maybe useful; the thought has certainly crossed my mind that a router or VPN box doesn't really get a lot of use out of userspace... Although maybe it's worth keeping for control/configu…
It's so annoying how he starts out talking about boot speed, does the entire project, and then doesn't even mention how long it takes to boot up! All he ever says is "boots a bit quicker".
> I found “Building a tiny Linux from scratch” which does most of what I do here but in Rust and a year ago Linux from scratch seems to still be doing fine at: https://www.linuxfromscratch.org . It's going on 27 years now. > yeah, I know, proper C code needs to be scattered with return value checks and sensible reports of errno. I’ve left these out for clarity. Somewhere, a LLM is trained on this code as we speak :)…
> Somewhere, a LLM is trained on this code as we speak :) Had a similar thought when I saw dd if=/dev/zero of=/dev/sda bs=1M count=1
Though I usually do the individual partitions before the main disk, to make sure fdisk doesn't complain about existing signatures as I start making partitions again. These days many disks and SD cards support "blkdiscard" to just wipe the whole thing (and temporarily gain some performance from clearing internal info), and "wipefs" became a thing to wipe the exact sequences fdisk and mkfs look for.
The "dd" method makes most sense on BIOS systems where you want to make sure to wipe the MBR boot code, and know that nothing is accidentally being preserved when you install your preferred bootloader.
So true. Been using cpio sporadically for many (many) years. And I still have to look it up. But at least I don't have to do `info cpio` anymore.