Notices by Wolf480pl (wolf480pl@mstdn.io), page 14

@ivesen yeah, the cold bug

> When you're throwing a workload at it, you can go to, say, -160C, but when you reboot, there's no more workload, all of a sudden you can't boot anymore. Then you have to increase to -140C to boot."

https://www.pcgamer.com/overclocking-a-cpu-to-7-ghz-with-the-science-of-liquid-nitrogen/

I'm guessing at that point there isn't enough free charges in the silicon for it to (semi)conduct.

But IIRC there is a sweet spot and it's below zero... lemme do some seraching

@ivesen I mean T_die.

The aggregate of the readings of the dozens of temperature sensors built into the CPU silicon.

@ivesen but yeah I guess it can be confusing.

I just opened GamersNexus's last livestream where the AMD guys visited him to do some XOC, skipped to the part when they started running some benchmarks, and they were saying their target with that particular CPU is -120°C, because at -130°C it won't boot, and at -125°C it only sometimes works.

And it wasn't clear if they meant Tdie or Tpot

@Nepiant @quad like, imagine one day you're competing in CTFs or reading up on the latest CPU vulns or some other novel difficult exploits that require immense skill to pull off

And the next day you go do pentests for a customer whose webapp uses outdated libraries with known vulns, and also has a mongodb with default password exposed on the internet, and holds the door open for you despite not knowing you.

And you know that most companies are like that

@domi in theory that should be doable as a Framework extension module...

@lanodan @nytpu @lispi314
oh, in the sense that it's not a single git repo everyone has - yes, that would be a problem.

I wish they were still doing source CDs :/

@lanodan @nytpu @lispi314
also being a debian downstream distro is one of the sanest ways of doing infrastructure-as-code with Debian

@lanodan @nytpu @lispi314
yeah, you typically become a debian downstream instead of forking it

@lanodan @nytpu @lispi314
IIRC (some?) Debian source packages use an upstream source tarball + -debian tarball (containing the debian/ directory, including patches and buildscripts) that gets extracted on top of it, and then patches get applied.

It's not as clean as I would like, but in principle the stuff authored by Debian is separate from upstream code.

You just need pre-compromise build-essential, upsteram tarballs, and audited *-debian tarballs.

@lanodan @nytpu @lispi314
(assuming by compromise you mean "someone tried to put a backdoor in the source packages")

@lispi314 @nytpu I think another way to become resilient against link rot is to have all the source code of the packages you use in one place.

There used to be source CDs but most distros don't fit on a CD or a DVD anymore. So either mirrors like Debian does, or keeping the source code of everything you install on your local disk (or a NAS).

A while ago I was of the opinion that Gentoo users are uniquely well prepared for an apocalypse, but that may've changed recently

I remember my dad's RedHat came on 4 CDs: 2 Binary Discs, one Source Disc and one Documentation Disc.

If it worked the way I think, you could take it to a desert island and rebuild everything from source, with just those 4 CDs and an x86 computer.

Today a Debian mirror has 100+ GB of source packages and 600+ GB of binaries just for amd64.

But at least it's one place, heavily replicated. And IIRC it's supposed to work on a desert island.

2/

@jonty Fiat Punto Door Connector

@lanodan or a fun task for Advanced Operating System students to implement

Silly kernel patch idea:

You know how on Linux you can't kill init?

What if instead, you can kill init, but if you do, you become the pid 1?

You know, the Dutchman needs a captain, and all that?

@Suiseiseki btw @SuperDicq when you said it's easier to become an ISP, what definition of "ISP" did you use?
- someone who provides internet to others
- someone with an ASN
- ...?

@Suiseiseki if you have a (non-private) ASN, you are by definition an ISP

@Suiseiseki also the "you connect to your friends and they commect to the internet" is like Stallman boycotting credit cards by asking his friends to pay by card for him.

It just adds intermediaries, and while it may make things easier for you, it just ouahes the burden onto those around you, and does not provide a solution that could scale and eventually replace the status quo.

@Suiseiseki And if I'm going to be selfish, then me becoming an ISP will easier for me, and less obnoxious for my friends.

@Suiseiseki @SuperDicq
bandwidth isn't an issue, latency is.

Besides, even with satellites, if you want access to the existing Internet (as opposed to a new wide-area network for you and your friends) you need to interconnect with existing ISPs anyway.

Also, if you are your own ISP, you don't rely on a single upstream ISP.
Being an ISP means having an ASN.
That means you can interconnect with multiple ISPs redundantly and participate in BGP.