The first time I saw that episode, I don’t remember how old I was, but it was one of the first times I was left home alone. And by total coincidence, right when it was at the most intense part of the episode the power went out at my house. It was night time, during a thunderstorm, and no one else was home.
And then I had to brave the basement to check the breaker box. In the dark. Which was a little Home-Alone-evil-furnace-scene for me under normal circumstances.
Very cool. Are there laws about practicing medicine without a license (at least in some jurisdictions) that might need to be navigated carefully when, for instance, making a prosthetic or some such for a human?
I remember looking into the OpenEEG projecct long ago. I remember hearing of folks getting into legal trouble for lending a homemade EEG unit to someone else. Not sure if that applies to 3d-printed “medical … and quality-of-life” devices (for humans.)
Maybe don’t use highlighter markers on your monitor?
(But seriously, it’s no different color than other comments in this thread for me. Maybe it was a “new” post for you when you wrote that and the rest weren’t?)
Glad it was informative! Back when the D&D situation was all happening in realtime, I was so addicted to any and all news about it. I watched all there was to see about it on YouTube constantly. (And there was a lot.)
I’ve never played Magic, but especially given how soon after the D&D debacle it went down, it felt like a continuation of the same story. So I watched a lot about that as well.
It seems like what you’re asking about are more what I’d think of as components of an a Linux “system” or “install.”
First off, it’s definitely worth saying that there aren’t a lot of rules that would apply to “all” Linux systems. Linux is huge in embedded systems, for instance, and it’s not terribly uncommon to find embedded Linux systems with no shells, no DE/WM, and no package manager. (I’m not 100% sure a filesystem is technically necessary. If it is, you can probably get away with something that’s… kinda sorta a filesystem. But I’ll get to that.)
Also, it’s very common to find “headless” systems without any graphical system whatsoever. Just text-mode. These are usually either servers that are intended to be interacted with over a network or embedded systems without screens. But there are a lot of them in the wild.
There’s also Linux From Scratch. You can decide for yourself whether it qualifies as a “distribution”, but it’s a way of running Linux on (typically) a PC (including things like DE’s) without a package manager.
All that I’d say are truly necessary for all Linux systems are 1) a bootloader, 2) a Linux kernel, 3) A PID 1 process which may or may not be an init system. (The “PID 1 process” is just the first process that is run by the Linux kernel after the kernel starts.)
The “bunch of default applications and daemons” feels like three or four different items to me:
Systemd is an example of an “init system.” There are several available. OpenRC, Runit, etc. It’s main job is to manage/supervise the daemons. Ensure they’re running when they’re supposed to be. (I’ll mention quickly here that Systemd has a lot more functionality built in than just for managing daemons and gets a bad rap for it. Network configuration, cron, dbus for communication between processes, etc. But it still probably qualifies as “an init system.” Just not just an init system.)
Daemons are programs that kindof run in the background and handle various things.
Coreutils are probably something I’d list separately from user applications. Coreutils are mostly for interacting with low-ish level things. Formatting filesystems. Basic shell commands. Things like that.
User applications are the programs that you run on demand and interact with. Terminal emulators, browsers compilers, things like that. (I’ll admit the line between coreutils and user applications might be a little fuzzy.)
As for your question about graphical systems, X11 and Wayland work a little differently. X11 is a graphical system that technically can be run without a desktop environment or window manager, but it’s pretty limited without one. The DE/WM runs as one or more separate processes communicating with X11 to add functionality like a taskbar, window decorations, the ability to have two or more separate windows and move them around and switch between them, etc. A Wayland “compositor” is generally the same process handling everything X11 would handle plus everything the DE/WM would handle. (Except for the Weston compositor that uses different “shells” for DE/WM kind of functionality.)
As far as things that might be missing from your list, I’ll mention the initrd/initramfs. Typically, the way things are done, when the Linux kernel is first loaded by the bootloader, it an “initial ramdisk” is also loaded. Basically, it creates a filesystem that lives only in ram and populates it from an archive file called an “initramfs”. (“initrd” is the older way to do the same thing.) Sometimes the initramfs is bundled into the same file as the kernel itself. But, that initial ramdisk provides an initial set of tools necessary to load the “main” root filesystem. The initramfs can also do some cool things like handling full disk encryption.
So, the whole list of typical components for a PC-installed Linux system to be interacted with directly as I’d personally construct it would be something like:
Bootloader
Linux Kernel
Initramfs
Filesystem(s)
Shell(s)
Init system
Daemons
Coreutils
Graphical system (X11 or Wayland potentially with a DE/WM.)
User applications
Package manager
But techinically, you could have a functional, working “Linux system” with just:
Bootloader
Linux Kernel
Either a nonvolatile filesystem or initrd/initramfs (and I’m not 100% sure this one is even strictly necessary)
A PID 1 process
Hopefully this all helps and answers your questions! Never stop learning. :D
So, D&D first. WotC back in 2001 realized something. There are a few books that they sell a ton of copies of and make a lot of money off of. (The Player’s Handbook, The Dungeon Master’s Guide, Monster Manual, etc.) And then there are a ton more books that take a lot of effort to make but that they don’t sell many copies of so they don’t really make much money on them, but they still have to be made in order to ensure that the more profitable books sell. (These are mostly the published adentures.)
They figured that it would be in their best interest to incentivize third parties to write a lot of these published adventures so that WotC itself could focus more on the core books. So they licensed a lot of their core content under a license (The “Open Gaming License version 1.0a” or “OGL 1.0a”) that allowed third parties to use it in their own modules and sell those modules. It created a vibrant ecosystem of publishers.
The OGL 1.0a was intended as a perpetual license. They promised third party publishers that the wording of the license didn’t allow WotC themselves – creators of the OGL 1.0a – to revoke the license. (This was on an official FAQ on WotC’s site.) So you’d be able to sell your module that included verbiage and elements from official D&D materials forever.
Well, in 2022, they changed their tune. They created an “OGL 1.1” (which was not “open” the way the 1.0a was) and started pressuring publishers they partnered with to accept the new license. It basically allowed them to rip off any third party content and include it in official WotC stuff without paying the third party publisher and also ban the publisher from using the material they wrote. It also put ridiculous restrictions on virtual tabletop software (software for playing D&D remotely.) Now, that’s not so catastrophic because they couldn’t revoke the OGL 1.0a and publishers were under no obligation to accept the OGL 1.1, right?
Well, they came up with a legal argument why the language of the OGL 1.0a that they’d been telling everyone couldn’t be revoked on existing works actually was something they could revoke. Basically, if they convinced a court they could do that, every third-party D&D module that relied on the OGL 1.0a would have to accept the OGL 1.1 terms that would let WotC rip off their work or stop sales immediately.
There was massive backlash from the community. D&D players were remarkably unified in their response. And the CEO of WotC was really tone deaf and dismissive and soured WotC’s relationship with the D&D community even further. Enough subscriptions to D&D Beyond (an online service owned by WotC) that shareholders started asking tough questions at shareholder meetings.
So, finally, WotC hired a slick PR firm to smooth things out. And, honestly, I have to admit they did good. They ended up leaving the OGL 1.0a in place (unrevoked it, sorta). But also, WotC had already said “actually, we can revoke it” and nobody trusted the OGL 1.0a any more. So WotC also dual-licensing the same OGL-1.0a-licensed content also under a Creative Commons license that is (more certain to be) unrevokable and is more open than the OGL 1.0a. The upcoming version of D&D will be OGL 1.1 only, but players and third party publishers are pretty unified on the idea of refusing to migrate to the new version and the current version is safer from the evil clutches of WotC than it was before this whole fiasco went down.
Now, the consensus among the D&D players is that WotC isn’t the bad guys so much as Hasbro, WotC’s parent company. When WotC backpeddeled and did the dual licensing thing, I decided to end my boycott of Hasbro. (I was actually DM’ing a D&D campaign at the time.) I looked forward to buying more D&D books. To seeing the latest Transformers movie and the D&D movie. Stuff like that.
And then, very shortly after that all went down, there was the other fiasco started by WotC.
I’m a little less familiar with this one, but some player of Magic: The Gathering purchased packs of MTG cards from a small reseller and the reseller fucked up. The reseller, not knowing the difference, gave the customer packs of a not yet released but similarly-named line of cards that weren’t supposed to be available to customers at all yet.
The customer made an unboxing video of these not-yet-officially-released cards and stuck it on YouTube. And that’s when shit hit the fan. WotC could have DM’d the customer on YouTube and asked if the customer could take down the video and exchange the cards for the ones he’d actually purchased, but instead they sent the actual, literal Pinkertons (a private security/mercinary company known for union busting and lots of illegal quasi-military/quasi-police actions against innocent people) to go harass the customer’s neighbors and intimidate (like while sporting assault rifles and body armor and camo – on the customer’s front porch) and bully the customer.
Now, my understanding is that the customer did nothing legally wrong. The fuck up was the reseller’s. The customer was under no legal obligation to return the cards or take down the video or otherwise cooperate in any way. The customer also said in later videos about the whole situation and the visit he got from the Pinkertons that they would totally have fully cooperated if they’d have just contacted him and asked.
As soon as I heard about WotC sending the Pinkertons after a customer, I recommitted to boycotting Hasbro and I intend never to end that boycott. I really didn’t expect something far worse to follow right on the heels of the OGL 1.1 fiasco.
“Gimp”, aside from being an open source image editor is also a term used in BDSM fetish communities. I think the joke is basically that the developers who work on the image editor must also be into BDSM.
In my experience, if you need to do Linux kind of things on a Windows computer, it’s far less glitchy, buggy and laden with weird caveats and edge cases than the alternatives (like Cygwin and Git Bash).
To be fair, I’ve never used it. But I’ve been the guy people come to when shit doesn’t work. Switching from Cygwin or Git Bash to WSL frequently fixes issues.
For those of you outside the U.S. who don’t know, Thanksgiving is basically a simultaneous celebration and revision of the genocide of the indigenous peoples of North America where people eat turkey and disgusting green bean slop.
Richard M. Stallman. Origin of the whole idea of “Free Software,” founder of the Free Software Foundation and GNU Project, guy who said some of Epstein’s sex trafficking victims probably enjoyed it.
Oh, and ESR is Eric Raymond, cofounder of the Open Source Initiative and rabid Libertarian.