You’re right that it was power-related - one of the options was an ASPM modification - but the issue seemed to be common to this chipset accross laptop brands.

The fix I used came from this post: https://bbs.archlinux.org/viewtopic.php?id=286109

My machine was a Thinkpad, but this article was also talking about problems on HP, Asus, etcetera. I think the 8852BE might just be cursed

To be fair, I was using an E series Thinkpad, but in my defense, the E series seems to have improved a lot in the past few years - this was luckily the only issue I’ve had. I’ve had much more difficult times with Linux on other laptops. Heck, even my desktop had more setup than this when I was first starting out, though it was because I was using a Broadcom Wi-Fi card, as I also dual-booted with a Hackintosh and macOS only supports Broadcom Wi-Fi chipsets.

Otherwise agree, but I did run into pain with Realtek on my Thinkpad - the module would sometimes crash and disconnect entirely (on a PCI-e level) from the system.

I did manage to find a fix, but I would not recommend Realtek to someone.

Vulnerabilities certainly do exist, but I’m pretty sure the attacker has to be well-equipped

I’d call it a protection against data getting cracked in a petty theft, but if your attack vector is much more than that, there are other measures you should probably take. I think Clevis also works with Yubikeys and similar, meaning the system won’t decrypt without it plugged in.

Heck, I think I know someone who just keeps their boot partition with the keys on it on a flash drive and hide it on their person.

In my case, no; it’s all a single machine - it is in the initramfs and uses the system’s TPM to (relatively) securely store the keys.

It can be set up with an attestation server, but you certainly don’t have to do it. The Arch wiki has a really good article on getting it set up.

I use Clevis to auto-unlock my encrypted root partition with my TPM; this means when my boot partition is updated (E.G a kernel update), I have to update the PCR register values in my TPM. I do it with my little script /usr/bin/update_pcr:

#!/bin/bash
clevis luks regen -d /dev/nvme1n1p3 -s 1 tpm2

I run it with sudo and this handles it for me. The only issue is I can’t regenerate the binding immediately after the update; I have to reboot, manually enter my password to decrypt the drive, and then do it.

Now, if I were really fancy and could get it to correctly update the TPM binding immediately after the update, I would have something like an apt package shim with a hook that does it seamlessly. Honestly, I’m surprised that distributions haven’t developed robust support for this; the technology is clearly available (I’m using it), but no one seems to have made a user-friendly way for the common user to have TPM encryption in the installer.

I’m pretty sure by default, virtual networks are not enabled automatically if you’re not using virt-manager GUI.

To make it run automatically, run the following: virsh net-autostart default

If it’s not that, just to make it easier to find information, what’s your host distro? I’m guessing by mention of Kickstart files that it’s something Red Hat related, possibly Rocky 9 based on your choice of guest.

I got midway through season 4 of Disco, though I plan on finishing eventually. I think season 3 had its ups and downs, but the setting it introduced could have been really interesting. I was just underwhelmed by what they were doing in season 4 instead of the natural plot threads the 32nd century opened.

I agree on SNW, and LD and PRO have earned a special place in my heart.

You must be quite behind on Trek. They sort of just gave up on Kelvin and returned to the prime timeline with Star Trek: Discovery back in 2017. They eventually canonized that the Kelvin timeline is just an alternate reality existing in parallel to the main timeline.

I booted Buildroot with kernel 5.17 on a Pentium II laptop off a CD I burned once - I needed to dump a drive once and that was the only hardware I had on hand that could dump 2.5” IDE drives and had a working CD drive so I could boot something other than the operating system installed on the drive.

Honestly, I rather like the default XFCE terminal. In fact, I was using it even before I used XFCE back when I was just playing with the default GNOME in VMs before I daily-drove Linux.

Is this xfce-winxp-tc? I ‘ve played with it before and it’s awesome.

However, I don’t use it because while the XP start menu replica is cool, I need a Win7-style search bar, and Whiskermenu sticks pit like a sore thumb here.

I think a 7 replica would be awesome, but I think some parts of Aero can only truly be replicated with a new WM and DE, such as the color changes in the taskbar for different applications. Many themes just fall short - proportions and effects are slightly off and such.

Not really, but I switched from Qwerty to Workman years ago, though I can live with Qwerty if I have to when it’s on someone else’s machine.

I use Workman because I found Colemak rather hard to learn, mostly because of the position of S being one over from where it was on Qwerty.

It’s not just packages. Ubuntu performance is terrible - it runs so much worse than other distros in VM. I don’t know about spins, but main Ubuntu takes 30 seconds to respond to some button presses whereas it’s nearly instant in other GNOME-using distros given equal or less resources.

I think this works. I was in fact one of them, although honestly, at a certain point, they trusted me and weren’t even watching all that hard.

I mean, today, we use shuttle pretty broadly, to refer to anything from buses to a space vehicle that went to the ISS.

Not everyone works in Starfleet, so civilians might have a different definition of shuttle.

TLDR; Daystrom did bad stuff but under mental collapse, and it’s very much in part Starfleet Command’s fault.

I think also, as much as Daystrom had much responsibility for those deaths, it was not as intentional as something like slavery, genocide, or sexual assault. He was fundamentally in a state of psychological distress partially beyond his control. Depending on when Daystrom Institute was founded (touched on above), he may have had decades for rehabilitation and redemption.

Additionally, Starfleet command probably had ample opportunity to avoid this very early on, like:

• Looking over Daystrom’s reports to consider potential risks of using engram imprints in a manner similar to a university’s Institutional Review Board - (Though perhaps Daystrom was rather secretive about it and kept it from reviewers.)
• Running the M-5 in simulations. We know the Kobiyashi Moru existed, so we could probably create a wide range.
• Not running the test on the Federation flagship, literally one of Starfleet’s most powerful weapons.

While it’s possible Starfleet took more precautions than we see onscreen, Commodore Wesley’s enthusiasm in “The Ultimate Computer” almost suggests an over-enthusiasm in Command, possibly one that caused them to skip necessary precautions. In fact, we had almost this exact scenario happen in Lower Decks “Trusted Sources”/“The Stars at Night” with the Texas class a century later. Ultimately, Starfleet Command likely bears a non-negligible amount of responsibility in the M-5 affair.

Of course, the above does not reduce the wrongness of Daystrom’s actions and perhaps only serves to deflect from the OP’s question. However, I feel Starfleet’s potential role combined with Daystrom’s mental condition may be mitigating factors that would make Richard Daystrom less unworthy of having an institution bear his name.

I would agree calling it a web crawler is inaccurate, but disagree with the reasoning; I think it’s more in the sense that calling an LLM a web crawler is akin to calling a search index a web crawler; in other words, an LLM could be considered a weird version of a search index.

It looks like this rulebook was released 2 months before the Discovery episode.

Honestly, I think I’d personally consider the Disco naming a canon goof up - Daystrom was only 37 years old at that point. While he’d certainly done a lot in his career by then, it still feels weird to name such a major part of Starfleet after him when he’s still relatively young.

I think my headcannon, and a reasonable retcon in my opinion, is that there was a predecessor organization to Daystrom, somewhat like how there was NACA before there was NASA. When Discovery mentions Daystrom, they should actually be mentioning the predecessor organization.

This is firmly Memory Beta canon, but this bit from the Star Trek Adventures Core Rulebook still feels like an interesting addition to this conversation:

I view satirical voice impression and speech synthesis of a real person as two different ethical issues entirely.

I find impressions intended for satire fall within the real of the first amendment, while the latter can be an unwelcome appropriation of identity when done wrong.