Earlier quoted context omitted.
So uh, who's gonna be first to get it running on a Pi Pico?
Pico is a microcontroller whose Cortex-M0+ cores lack a memory management unit for virtual memory (considered essential for a full-fledged OS like Linux). But can run FreeRTOS on it...memory usages are 236 bytes for the scheduler, 76 bytes + queue storage area for each queue, and 64 bytes plus task stack size for each task, plus 5 to 10 KBytes of ROM.[1] [1] https://freertos.org/FAQMem.html
Damn Small Linux 2024
71–80 of 185 posts
Re: Damn Small Linux 2024
#72Re: Damn Small Linux 2024
#73I used DSL back around when it was released (and 64 MiB flash drives were common) to get around my school's network filtering. I think this was one of the reasons they hired new IT staff the following year, because the technique caught on even with the non-nerdy crowd.
Yes, this brings back such memories for me too! I also used to boot from removable media to use linux on school computers. The librarian assumed I was some kind of computer hacker and reported me to the schools IT admin. I thought I was in trouble. Instead he took me under his wing and had me work with him after school on some fun projects! Really helped me understand that the skills I was learning were valuable and…
Re: Damn Small Linux 2024
#74Earlier quoted context omitted.
Pico is a microcontroller whose Cortex-M0+ cores lack a memory management unit for virtual memory (considered essential for a full-fledged OS like Linux). But can run FreeRTOS on it...memory usages are 236 bytes for the scheduler, 76 bytes + queue storage area for each queue, and 64 bytes plus task stack size for each task, plus 5 to 10 KBytes of ROM.[1] [1] https://freertos.org/FAQMem.html
Yeah I figured there might be a rub somewhere otherwise it would already be a thing, but since it's technically an ARM it sounded vaguely promising. What about a 32 bit build? I think those used to be able to work with without virtual addresses.
Re: Damn Small Linux 2024
#75Re: Damn Small Linux 2024
#76Interesting fact is that DSL used to be 50MB because that’s how big a business-card sized CDs were. And yes, there used to be business-card sized CDs.
Re: Damn Small Linux 2024
#77> keeping otherwise usable hardware out of landfills while i like this idea in theory, in practice the energy efficiency and lower electricity costs of newer hardware mean that in terms of both cost and environmental impact it would probably be better to recycle the old hardware and buy something new in most cases.
Building and shipping new machines requires far more envionmental related costs.
Re: Damn Small Linux 2024
#78Wow, this is crazy. I came across the DSL website last night while trying to figure out how to compile a minimal Linux kernel myself, and now here it is on HN! I used DSL back in high school when it was new. As a side note, why does compiling Linux have to be so... obtuse? It just stops for me after several minutes of building out objects with no explanation.
Are you looking to build just a minimal kernel or also a minimal distribution? (Which is what I happened to be thinking about last night :)) In the latter case, do you know any good resources about that topic?
Re: Damn Small Linux 2024
#79Earlier quoted context omitted.
So uh, who's gonna be first to get it running on a Pi Pico?
Pico is a microcontroller whose Cortex-M0+ cores lack a memory management unit for virtual memory (considered essential for a full-fledged OS like Linux). But can run FreeRTOS on it...memory usages are 236 bytes for the scheduler, 76 bytes + queue storage area for each queue, and 64 bytes plus task stack size for each task, plus 5 to 10 KBytes of ROM.[1] [1] https://freertos.org/FAQMem.html
Re: Damn Small Linux 2024
#80Wow, this is crazy. I came across the DSL website last night while trying to figure out how to compile a minimal Linux kernel myself, and now here it is on HN! I used DSL back in high school when it was new. As a side note, why does compiling Linux have to be so... obtuse? It just stops for me after several minutes of building out objects with no explanation.
That's... odd. Does it break if you just use the default `make defconfig` configuration? Because pruning what's built in without breaking it is hard-ish IME but it shouldn't just fail silently. Or... when you say "It just stops" you don't by any chance mean that it finished and you just need to find the actual binar(y|ies) it produced?