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.
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.
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.
I don’t care if this is “fake” nor “gay”, it is wholesome.
I’m really appreciating your use of &c
.
Are you in the nineteenth century by any chance?
Yet.
As IPv4 blocks get scarcer and ISP’s get more customers, they’ll all eventually have to move to IPv4 CGNAT.
And that’s completely fine for most people.
If you’re not one of those people, then IPv6 is your saviour.
Remember: in most cases the c-suite consider you merely as resources(human) a source of labour.
To them employees are things.
Customers are just a revenue source, they are also just things.
CEO’s are just chasing their next quarterly performance bonus.
I read that in Agent Smith’s voice.
Fucking LOL while scrolling next to sleeping wife. You bastard.
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.