oso2k

My favorite trick with this feature is pairing it a timeout

   # Connection successful:
   $ timeout 1 bash -c 'cat < /dev/null > /dev/tcp/google.com/80'
   $ echo $?
   0

There is also git-bash which usually doesn’t need to have administrator to be installed.

https://git-scm.com/install/windows

Thanks for finding this!

I have one those Librex as well. It was fun to play with when it came into my hands back in 1997.

I agree. It's also the evil that created the need and improvements like SSL/TLS, ssh, gzip, bzip2, lz4, Linux, etc. and so many other worthwhile innovations.

I'd presume we're almost all using the Web primarily on some employer's dime (except where we are self-employed but it still applies). Prior to the Web 1.0, I remember interacting with people/managers that discouraged reading email or news or forums or other casual/non-work uses of the Web. I remember articles about employers allowing their programmers to read their email "up to" 2 hours per day. Now we're expected to have rapid response/access to email, slack, SMS, etc.

I believe this is because the commercialization/monetization of Web usage is beneficial to commercial entities. If that isn't possible, then the few who build the Web aren't able to build it in the first place. It's akin OSS and concepts of commercialization in the GPL. You can't create equity if there is no method to transfer value.

Flash succeeding is subjective. There were many who were hostile to Flash (and Java) for a long time. I actively disabled the Flash plugin except when necessary.

HTML not passing the criteria doesn't negate it from being the current leading technology. All it indicates is that there could be a technology that does more (most) of these things better. And, it sets a certain benchmark for the next technology to aspire to.

I think accepting input from anyone is a resiliency feature. Imagine if only Governments drove the Web? Or Multi-national Megacorps? Billionaires? Choice and freedom helps to democratize and enable usage by participants who are diadvantaged.

Content-neutrality is experiential. That is to say, gopher is well known to be more organizationally efficient at transimitting data than http. However, it was primarily aimed at text transmission and was very poor at supporting applications (like banking, commerce sites or email). These were huge boons to the current Web.

I think we could learn from an old (gone?!) Google+ post from Ian Hickson on what could possibly replace HTML but a lot of the criteria applies to Web/Internet as a whole (https://www.sitepoint.com/will-html-ever-be-replaced/).

   Ian Hickson (“Hixie” — WHATWG specification editor, CSS2.1 co-editor and Google’s W3C representative) recently published an interesting post on Google+. He’s occasionally contacted by people suggesting a better alternative to HTML but, in all cases, none have come close. Ian states that any technology would need to satisfy at least five objectives to displace existing web technologies:

   Be devoid of licensing requirements.
   Be vendor-neutral and accept input from everyone.
   Be device and media-neutral; it should work on PCs, TVs, mobiles, tablets, screen readers and any future hardware.
   Be content-neutral and not restrict itself to types of document or application.
   Be radically better than the existing web in every way; faster, more usable, more features, easier to develop, easier to monetize, etc.


   HTML can fail objectives two and three. Technologies such as XHTML2 and XForms only satisfied one and three. Java and Flash struggle in all areas — and I’d also add Google’s Dart to that list.

I remember way back when, there were ports of SDL 1.x to djgpp. Glad to see someone still cares.

I say this as someone who likes and use TinyCoreLinux and PiCore, there are some mind numbing ways TCL makes immutability work. I chalk this up to Linux and immutability being sometimes in contention with each other. Lots of Linux code make assumptions paths being writable.

This looks interesting. Thanks for sharing.

I had the same inclination back in the 90s when I upgraded my Cyrix 486 SLC2 50MHz without a heat sink (which seems like a no-no in retrospect) to Cyrix MediaGX 133MHz. The stocker fan was immediately noticeable. I thought I had done something wrong.

There’s several other (well) known examples of the use of mujs.

There’s Artifex’s interpreter from muPDF. It’s also the basis of several JS related projects: https://mujs.com/

There’s also a lesser known interpreter: https://github.com/ccxvii/mujs

And IIRC, there was a CommonJS library of the same name.

Maybe you’re misremembering or referring to Doom (2016). The original Doom was developed for DOS and id had to build a lot of its own network stack. BSD style socket based networking wasn’t a given in DOS.

Still, zclaw is an impressive achievement.

   I don't feel like RedHat had to do anything to sell support contracts in this case, because that was already their business. All they had to do was say they'll include container support as part of their contracts.

   What they did do, AIUI based on feedback in the oss docker repos, is those contracts stipulated that you must run RHEL in the container and the host, and use systemd in the container in order to be "in support". So that's kind of a self-feeding thing.

https://access.redhat.com/articles/2726611

I think STL was the intent.

On aliexpress, there’s Pi Pico Dev dev boards featuring the RP2350 in the Pi Zero form factor.

https://www.aliexpress.us/item/3256807163052616.html

Yes. 486 with 26MB for MicroCore (cli) or 46MB for TinyCore (gui).

https://en.wikipedia.org/wiki/Tiny_Core_Linux#System_require...

VGA color palette was 18-bits/256K, but input into the palette was 8-bit per channel. (63,63,63) is visibly different from (255,255,255).

http://qzx.com/pc-gpe/tut2.txt

http://qzx.com/pc-gpe/

Not true. You can enable “Mount Mode of Operation: TCE/Install” where packages will be mounted off disk. See:

http://www.tinycorelinux.net/concepts.html

I don't know about CSI cameras. My use case for TCL doesn't require a CSI camera. But it looks like others have made a CSI camera work:

https://forum.tinycorelinux.net/index.php/topic,26713.0.html

I recommend asking on that forum. Folks are helpful.

There’s an installation option to run apps off disk. It’s called “The Mount Mode of Operation: TCE/Install”.

With some modifications, yes. Boot2docker and boot2podman were based on tinycorelinux.

With CorePlus, you have the the choice of some 10 GUI environments. I prefer openbox or jwm.

I love Tiny Core Linux for use cases where I need fast boot times or have few resources. Testing old PCs, Pi Zero and Pi Zero 2W are great use cases.

Wake-on-LAN not available to you?

Only if they never call DOS or the BIOS or execute a Real Mode Software Interrupt. When they do, they ask the DPMI server (which could be an OS like Windows 9x or CWSDPIM) to make the call on their behalf. In doing so, the DPMI server will temporarily enter into a VM86 Virtual Machine to do execute the Real Mode code being requested.

http://www.delorie.com/djgpp//doc/libc-2.02/libc_220.html

VM does not mean Virtual Memory in this context. VM does mean Virtual Machine. When an OS/DPMI Server/Supervisor/Monitor provides an OS or program a virtual interface to HW interrupts, IO ports, SW interrupts, we say that OS or program is being executed in a Virtual Machine.

For things like Windows 3.x, 9x, OS/2, CWSDPMI, DOS/4G (DPMI & VCPI), Paging & Virtual Memory was an optional feature. In fact, CWSDPMI/djgpp programs had flags (using `CWSDPR0` or `CWSDPMI -s-` or programmatic calls) to disable Paging & Virtual Memory. Also, djgpp’s first DPMI server (a DOS extender called `go32`) didn’t support Virtual Memory either but could sub-execute Real Mode DOS programs in VM86 mode.

http://www.delorie.com/djgpp/v2faq/faq15_2.html

There were loadlin and grub4dos back in the day. A more recent development is doslinux (https://github.com/lpsantil/doslinux) but it is far less complete. But more hackable if you just want to see something work.

I went smallwall after m0n0wall was shutdown. I recall the smallwall & smoothwall maintainers briefly considered joining forces.