nineteen999

I use an SDwire device - connect the USB end to your build host, and the SD card end to the DUT.

Pfft. You just need more robot arms to hose down the ones that are catching fire.

Definitely helped my RSI as well. Another anecdotal point.

Getting a job in a mom-and-pop ISP back in 1999. Our uplinks were so constrained that with 40 dial-in lines, we needed to run our own bandwidth-throttled NNTP cache to prevent one or two customers relentlessly trawling Usenet making life horrible for the others. Fun times.

toast0's answer below is the correct one. Plus in Australia, gaming/gambling is heavily regulated - my state government didn't even allow poker machines until 1991.

So we never started with a network of disconnected poker machines, the whole thing was built from the ground up with a centralised jackpot system. I don't know what hardware the original jackpot platform ran on but I know it used hardware RNG units. By the time I started there ~2003 it had been migrated to Stratus.

We were lucky on our site, our team leader was a Stratus guru, and was a great teacher, so we had plenty of time on there if we wanted to practice. We were lucky enough to do just about everything in midrange - Solaris, OpenVMS, Stratus and a bit of Linux here and there in the latter days.

And some ancient lottery processing machines the size of fridges that ran some ancient V7 UNIX variant.

We use to run Stratus VOS on Continuum series hardware at a lottery/poker machine company I worked at in the mid 2000's. It handled the jackpot system which decided which of 13,500 poker machines in our state would jackpot at any given time.

A reliable beast - never failed once in the entire time I worked there. Based on PA-RISC if I recall correctly.

Yes you could do this, from Sun Microelectronics back in the 1990's. We purchased an Ultra-10 motherboard with 250 MHz Ultrasparc II in 1998/1999, fitted it out with compatible third party SVGA, Ethernet and SCSI adapters and ran Solaris on it. Was our production LDAP, Mail and database server for a small ISP for many years.

I later worked for a systems builder that built and sold Sparc/Ultrasparc systems for government (eg. Hong Kong Mass Transit). We were the only vendor in the Southern Hemisphere doing it. So it wasn't common. But yes you could order parts from Sun Microelectronics and build your own systems, and it became easier use certain standard PC compatible parts once they standardised on PCI. We had shelves full of the older incompatible MBus compatible systems and boards as well.

Until Fuzix of course.

Not written in assembly, mostly Javascript and HTML/CSS.

Strong disagree. Appropriate levels of humility is not something that Lisp weenies suffer from.

It's a Lisp programmer thing.

> 3. Designed for the Elite Let’s be honest: Lisp is a language designed by and for elite hackers

... it took them up to item #3 this time? Usually i see this quoted as item #1

Ive been throwing z80, 6502, 68000, 8086, i386 and x86_64 asm at it lately. Haven't seen it get stuck on any of them.

The downside is after all that, is you end up with an running Ubuntu system, and you realise you're running a shitty NIH Debian fork.

Beginning with ME (Management Engine) firmware version 11 (found on Skylake CPUs and newer), Intel utilizes a customized version of the MINIX 3 microkernel operating system.

Somewhat ironic Postfix has a record of no root/RCE in the default install, where opensmptd hasn't (CVE-2020-7247). Time will tell if it stays that way.

Or Bach.

I didn't say I was any good at them! Just like my text editor.

That's actually funny, because I play both.

I consider my vi/vim skills to be extremely minimalist subset, and probably horribly inefficient, since they were developed to work accross a broad range of UNIX systems (SCO, Solaris, HP-UX, OSF, AIX) and I rarely add anything to my vim configs on top of that other than syntax highlighting.

But I'd still rather use it than just about any other text editor, just for the simplicity of that muscle memory alone. I have way more stuff to keep in my head than I have room for and I can't afford to expend more than about 0.0001% of context on a text editor.

Back in the 1990's I was fond of it for the community spirit, the attention to detail, the way things "just worked" even it had a particular take on some things. Over time it felt like it became burderned with design-by-committee decisions, maintainers leaving and abandoning packages faster than they could replace them, and just a bit too political.

Fedora is upstream for RHEL, which is absolutely dominant in the server space some sectors that require enterprise support.

Yeah perhaps learning UNIX API's and Rust at the same time doesn't lead to a drop in replacement ready to be shipped in major distributions. Who whould have thunk it.

This is obvious within about 3 seconds of opening the article, noticing it's filled with coloured M&M's, and closing it again.

A different "network-aware" concept of this was "aide", that allowed the checksums to be stored on a server, for mutiple clients. [1]

Had some drawbacks compared to using offline media of course, but in day to day operation on an air-gapped network it had its uses.

Also worth knowing is the "-V" (for very parameter) of rpm.

[1] https://docs.redhat.com/en/documentation/red_hat_enterprise_...

Oh. My. God. Will the LISP community ever stop MOANING? It is the consistently most depressing, woe-is-me wailing in the entire IT segment.

You guys are depressing.

Once you've taken most all of the other subsystems out of NT (which they pretty much have), all you're left with is is the crapload in the Windows subsystem.

Im a 3D artist not a pixel artist but I've had these Saint11 tutorial series bookmarked for a while:

https://saint11.art/blog/pixel-art-tutorials/