No, I don't think so.

If I'm running, say, a TLS listener (an HTTPS web server), there is no way for you to tell if I'm using a FIPS-validated implementation of the algorithms or not. I can be using a cipher suite that is allowed by FIPS, but that doesn't mean my implementation is FIPS-validated. It's not like there's a "FIPS validated and FIPS mode enabled" flag added to the TLS spec, and even if there was, there'd be nothing stopping me from setting it to true even when using a non-validated implementation.

So no, this does not pull all existing routers off the market. Anything that already got FCC approval remains approved and new stock may be imported and sold.

Just to expand on how bonkers this book is... they assume that everyone has easy access to a Forth implementation. So they teach you how to build a Lisp on top of it. Then they use the Lisp you just built to build a Prolog. Then, finally, they do what the topic of the book actually is: build a simple expert system on top of that Prolog.

I love it!

And if you want to go farther back, even if it wasn't called "mmap" or a specific function you had to invoke -- there were operating systems that used a "single-level store" (notably MULTICS and IBM's AS/400..err OS/400... err i5 OS... err today IBM i [seriously, IBM, pick a name and stick with it]) where the interface to disk storage on the platform is that the entire disk storage/filesystem is always mapped into the same address space as the rest of your process's memory. Memory-mapped files were basically the only interface there was, and the operating system "magically" persisted certain areas of your memory to permanent storage.

Really the only thing in my head is my internal monologue. If I'm thinking about something I've seen, it's my internal monologue "saying," with words, physical attributes I remember about it. If a song is stuck in my head, it's my internal monologue (in my own voice) signing the lyrics or my own voice humming the tune in my head. No sensation of it being the original artist or the actual instruments, it's 100% my own voice in my own head.

I have a friend who says she does not have any inner monologue at all, and thinks entirely visually. I can't imagine! We're on the pretty extreme opposite ends of the spectrum of how we think, apparently.

I set up a new mailserver a few years ago and have had no delivery problems whatsoever. All messages get through to gmail and outlook/o365 inboxes I've sent to. Didn't even have to register the IP with O365, it's just worked flawlessly from day one. That was from an IP address/netblock not associated with cloud or VPS providers, so initial reputation may have been higher.

A few months ago I set up a mail server on a VM in Digital Ocean, and have had no delivery problems to gmail/Google Apps recipients.

More recently, for new IPs sending mail into O365, they appear to be blocked by default but the rejection message gives you a URL to go to where you can register your IP(s). After doing that, we haven't seen any problems.

If you end up getting an IP that has been associated with previous spam or abuse, I assume your experience will be different. But in my experience, my handful of servers have not had delivery problems. This is all, of course, with proper reverse DNS records that match what the server advertises in its HELO/EHLO, SPF and DKIM all set up, etc.

I think you're thinking of New Yorker magazine, perhaps?

There was a program a long time ago, classic Mac OS days, and I don't remember the name of it but I think it was " Consistency". I loved it because tasks in it were "loose," in the sense that something like "water the plants" didn't have to happen on a strict 7-day repeating event. It could be defined as "should be done 6-8 days after the last time I did it." So when you hit "done" on the current "water the plants" task, it automatically fuzzy-scheduled the next "water the plants" event with a target date of 6-8 days after when you clicked done. You could have the range prefer some days but be "acceptable" for a wider range of days.

Someone once told me emacs org-mode might be able to schedule recurring tasks somewhat like this. But any time I see a new calendar/to-do manager application, I hope the designers keep this "fuzzy" repeating event idea in mind!

But IBM _does_ have their own mainframe emulator, zPDT (z Personal Development Tool), sold to their customers for dev and testing (under the name zD&T -- z Development and Test), and to ISVs under their ISV program. That's what IBM's own developers would be using if they're doing stuff under emulation instead of LPARs on real hardware.

(And IBM's emulator is significantly faster than Hercules, FWIW, but overall less feature-full and lacks all of the support Hercules has for older architectures, more device types, etc.)

All coconut trees are palm trees, but not all palm trees grow coconuts.

Identity is the only purpose that certificates serve. SSL/TLS wouldn't have needed certificates at all if the goal was purely encryption: key exchange algorithms work just fine without either side needing keys (e.g. the key related to the certificate) ahead of time.

But encryption without authentication is a Very Bad Idea, so SSL was wisely implemented from the start to require authentication of the server, hence why it was designed around using X.509 certificates. The certificates are only there to provide server authentication.

> Smalltalk and another esoteric programming environment I used for a while called Frontier had an idea of a persistent data store environment. Basically, you could set global.x = 1, shut your program down, and start it up again, and it would still be there.

Frontier! I played with that way back when on the Mac. Fun times.

But as for programming language with integrated database... MUMPS! Basically a whole language and environment (and, in the beginning, operating system) built around a built-in global database. Any variable name prefixed with ^ is global and persistent, with a sparse multi-dimensional array structure to be able to organize and access the variables (e.g. ^PEOPLE(45,"firstname") could be "Matthew" for the first name of person ID 45). Lives on today in a commercial implementation from Intersystems, and a couple Free Software implementations (Reference Standard M, GT.M, and the GT.M fork YottaDB). The seamless global storage is really nice, but the language itself is truly awful.

I'm pretty sure that MVS syscalls (that is, the numbers you use with the SVC opcode) have remained backward-compatible at least as far back as MVS 3.8 in the 1970s and those binaries making those "raw" syscalls will still work on the latest z/OS releases.

There are a _lot_ more operating systems than Linux, Windows, and the BSDs... making a statement that the Linux kernel is the only kernel to do something a certain way is a risky proposition :-)

Chapter 16 is named "No Silver Bullet—Essence and Accident in Software Engineering."

I'll type out the beginning of the abstract at the beginning of the chapter here:

"All software construction involves essential tasks, the fashioning of the complex conceptual structures that compose the abstract software entity, and accidental tasks, the representation of these abstract entities in programming languages and the mapping of these onto machine languages within space and speed constraints. Most of the big past gains in software productivity have come from removing artificial barriers that have made the accidental tasks inordinately hard, such as severe hardware constraints, awkward programming languages, lack of machine time. How much of what software engineers now do is still devoted to the accidental, as opposed to the essential? Unless it is more than 9/10 of all effort, shrinking all the accidental activities to zero time will not give an order of magnitude improvement."