collapseos VS ZLib

Something like this is probably a lot more realistic than (as fast) "integrated circuits at home" : http://collapseos.org/

http://collapseos.org/

I know the point of it isn't to run on new hardware, but this would be a way to learn it on a stable platform without having to worry about dealing with constant problems from old hardware before trying to implement it on said.

There is something called Collapse OS I read about here on HN:

http://collapseos.org/

I myself am a collector of old devices, having raised three kids plus being a web dev. Hate throwing them away too I was just think about this today could I extract the CPUs or RAM or something to reuse rather than destory for the metals. I'd like to learn more hardware but no time.

Some hope for Colapse OS [1] perhaps?

[1] http://collapseos.org

http://collapseos.org/

Here is a quick guide to the science for those with the brain worms:

Maybe start with sufficient support for a simple OS that allows you to edit and compile programs. Something like FreeDOS or CollapseOs. Once you have that working you can extend it.

During collapse we'll all be using Dusk OS and post collapse we'll be using cobbled together rugged computers running on Collapse OS. I imagine at that point we can probably put the sub name to a vote. Maybe "r/ordinarylife".

Not Linux....but you could just install Kolibri OS for a very light desktop or consider CollapseOS and DuskOS....think Dusk should run bare metal on now and won't be too bloated, but there's always CollapseOS if you prefer to keep things light

A fix has been checked into the upstream git repo: https://github.com/madler/zlib/pull/843 but a release has not yet been made including it.

So the real issue here is that the lack of tree validation before the tree construction, I believe. I'm surprised that this check was not yet implemented (I actually checked libwebp to make sure that I was missing one). Given this blind spot, an automated test based on the domain knowledge is likely useless to catch this bug.

[1] https://github.com/madler/zlib/blob/master/examples/enough.c

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Seeing the text in red got me thinking for a moment, "wow, didn't realize pirates had such love for an open-source compression library"

cd "${srcdir}/zlib-$pkgver/contrib/minizip" make install DESTDIR="${pkgdir}" install -D -m644 "${srcdir}/zlib-$pkgver/LICENSE" "${pkgdir}/usr/share/licenses/minizip/LICENSE" # https://github.com/madler/zlib/pull/229 rm "${pkgdir}/usr/include/minizip/crypt.h"