Don’t break userspace.

That’s a kernel saying. A bit unfitting to repeat it for the distro that builds said userspace.

Even further: The support is exclusively for the 32bit libraries. The 32bit kernel and therefore cpu support was dropped a long time ago in Fedora. Fedora 31 in 2019.

To be a little more precise, Linux is still available for 32-bit x86, just not from the Fedora distro. The Linux project is just now dropping support for 486 CPUs, because the maintenance burden for a virtually unused system type is too high for the mainline. That still leaves 32-bit Pentiums and newer though.

Is dropping support for 32bit hardware more important than being able to run on everything?

Yes evidently, because they dropped that hardware support in 2019. Specifically they dropped 32-bit x86 kernels in Fedora 31

I wonder how betrayed the people in the Appalachian feel when their supposed “own” Vance stood for this.

They are hardly even in the US market. Only via Murena with their e/OS/.

Those are both way more useful than exploiting a lazy coder’s fuckup

I never said social engineering, physical breaching, exerting force on people, and other ways of compromising systems weren’t useful. They just aren’t hacking to me, otherwise the term is too broad to be very useful.

You’re free to come up with your own definition, I was asked to define it and that’s my best shot for now.

You know my first instinct wast to reply with: “No.”

Maybe I should have stuck with that. I had a feeling this would lead nowhere.

I’d start with the following, and refine if necessary:

“Gaining unauthorized access to a protected computer resource by technical means.”

• Port scanning --> Not hacking because there isn’t any access to resources gained*
• Using default passwords that weren’t changed --> Not hacking because the resource wasn’t protected*
• Sending spam --> Not hacking because there isn’t any access to resources gained
• Beating the admin with a wrench until he tells you the key --> Not hacking because it’s not by technical means.
• Accessing teacher SSN’s published on the state website in the HTML --> Not hacking because the resource wasn’t protected, and on the contrary was actively published**
• Distributed denial of service attack --> Not hacking because there isn’t any access to resources gained

* Those first two actually happened in 2001 here in Switzerland when the WEF visitors list was on a database server with default password, they had to let a guy (David S.) go free
** The governor and his idiot troupe eventually stopped their grandstanding and didn’t file charges against Josh Renaud of the St. Louis Post-Dispatch reporter, luckily

I haven’t heard of a firewall failing open when overwhelmed yet. Usually quite the opposite, a flood disables access to more than just the targeted device, when the state table overflows.

But maybe there is a different mechanism I’m not aware of. How would the DDoS change the properties of ingress?

DDoS is not hacking

They do actually burn gas locally, I wasn’t trying to dispute that part. It has become a political discussion in Memphis. Apparently they wanted to start operations on turbines before the grid access was ready.

The linked video is a bit unclear to me. The don’t explain the modes well. Mostly it seems to just show heat. According to the description it’s a Teledyne FLIR G620, which should be able to detect Methane and other VOCs. But it’s not clear to me how we are supposed to distinguish hot rising CO2 and H2O from any potentially leaking Methane, in those pictures.

Video in question https://www.youtube.com/watch?v=4prazMVylRs

This week I heard from a network group lead of a university hospital, that they have a similar issue. Some medical devices that come with control computers can’t be upgraded, because they were only certified for medical use with the specific software they came with.

They just isolate those devices as much as possible on the network, not much else to do, when there is no official support and recertification for upgrading. And of course nobody wants to spend half a million on a new imaging device when the old one is still fine except for the OS of the control computer.

Sounds like a shitty place to be, I pity those guys.

That said, if you were talking about normal client computers then it’s inexcusable.

We got SSO systems too, unfortunately, there are about 3 of them, lol. The old ADFS, the current Microsoft login (possibly cloud AD, not sure), and our own ID product that we offer to customers.

The E2 drives are 200 millimeters (7.9 inches) in length, measuring 76 mm (3 inches) in height, and just 9.5 mm thick (0.4 inches).

So two of them would be roughly the size of a dual fan GPU. I can definitely see how it would make sense for servers. With that heigh it should just fit in 2U. And then you can probably fit like 30 of them side by side, or more, depending on how much space you need in between for cooling.

In that physical footprint of the E2 drives you could roughly fit 18 M.2 SSD (2280), but they would still have to be 55 TB each to reach the 1 PB headline, or 16.6 TB each to reach the level of their 300 TB prototype. I think the max you get at the moment would be 8 TB for a 2280 form factor, so they still have pretty good density on their prototype.

lol, the “j l’ai lu” domain is pretty funny

Okay that’s fair. I fricked around with some C++ numerics BLAS header library (I think it was Eigen) on Linux before that was complicated and annoying too. The ARM Fast Models simulator was also a pain. Maybe I just don’t like C++ development now that I think about it.

C mostly worked okay for me though. And I agree Rust tooling is nice, but admittedly I have not really worked on a big project in it.

Hm. I’ve always found it harder to compile stuff on Windows.