Poorly written code can't.
In this case:
- Load config data
- If data is valid:
- Use config data
- If data is invalid:
- Crash entire OS
Is just poor code.
deadbeef79000
joined 1 year ago
If anything, it's probably calmed P'n'S down a bit...
In future, assume everything is a hostile payload until scanned.
Microsoft provides free VM images of various versions for developers to test with, use one of them, install whatever scanning tool you want, then install your suspicious payload.
Rinse repeat.
Used to be an LVM group using the LVM docker volume driver. So every container volume became its own LV.
Now just a bunch of devices behind a btrfs volume mounted on /var/lib/docker or wherever.
In the past I've tended towards /srv/* as most mounts end up being application specific storage.
Though now it is all mounted as container volume storage.
Eeeh, if anything, systemd is Microsoft's contribution.
/s sort of
... For sufficiently large values of 1.
You put the em-PHA-sis n the wrong syl-A-byl.
I haven't wanted an Intel processor for years. Their "innovation" is driven by marketing rather than technical prowess.
The latest batch of 13900k and again with 14900k power envelope microcode bullshit was the final "last" straw.
They were more interested in something they could brand as a competitor to ryzen. Then left everyone who bought one (and I bought three at work) holding the bag.
We've not made the same mistake again.
Intel dying and its corpse being consumed by its competitors is a fairy tale ending.
Thinking about it, the SoC idea could stop at the southern boundary of the chipset in x86 systems.
Include DDR memory controller, PCI controller, USB controllers, iGPU's etc. most of those have migrated into x86 CPU's now anyway (I remember having north and south bridge chipsets!)
Leave the rest of the system: NIC's, dGPU's, etc on the relevant busses.
NVIDIA spent many many years doing a very very poor job of providing drivers for Linux.
Many people have not forgiven them for that.
Except "freak out" could have various manifestations.
In this case it was "burn down the venue".
It should have been "I'm sorry, there's been an issue, let's move on to the next speaker"