“No, this is Patrick”
“No, this is Patrick”
It’s not paranoia if they really are trying to kill scam you.
IMHO you probably now have the right amount of scepticism.
Banks’ system are probably already compromised and don’t even know it.
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.
I did this until I moved to an ISP that cared about IPv6.
It was almost trivial even with the ISP’s PoS router.
ARM won the mobile/tablet form factor right from the start. Apple popularised ARM on the desktop. Amazon popularised ARM in the cloud.
Intel’s been busy shitting out crap like the 13900K/14900K and pretending that ARM and RISC-V aren’t going to eat their lunch.
The only beef I have with ARM systems is the typical SoC formula, I still want to build systems from off the shelf components.
I can’t wait.
Backup backup backup! If you have btrfs them just take a snapshot first: instantly.
One could do a non-destructive rename first. E.g. prepend deleteme.
to the file name, sanity check it, then ‘rollback’ by renaming back without the prefix or commit and delete anything with the prefix.
ln
creates a hard link, ln -s
creates a symlink.
So, yes, the hardlink tool effectively replaces a file’s duplicates with hard links automatically, as if you’d used ln
manually.
For backup or for file-level reduplication?
If the latter, how?
I have exactly the same problem.
I got as far as using fdupe
to identify duplicates and delete the extras. It was slow.
Thinking about some of the other comments… If you use a tool to create hardlinks first, then one could then traverse the entire tree and deleting a file if it has more than one hardlink. The two phases could be done piecemeal and are cancelable and restartable.
It’s not very typical.
I took far too long trying to figure out why a German would pronounce “ja” as “you”.
El Reg pulls no punches.
Convenience link for people interested in the ligatures:
I, for one, welcome our new AI overlords.
I’m really appreciating your use of &c
.
Are you in the nineteenth century by any chance?
Well. To Java that’s just a string of utf-8 characters, assuming you haven’t bastardised the encoding, and it’s just yanked out of an HTTP entity. So of course they’re different.
If you’re using some json parser and object mapping library (like Jackson) then all bets are off 'cause it could be configured any which way.
On every other language and library it’s whatever the defined behaviour is.
3/10