pcn

u/pcn@lemmy.world
2 posts · 22 comments

Recent posts

Recent comments

You're talking about phones and Internet, but to extend your thought a bit, checks don't work at the scale we run financial transactions anymore, they are scanned and recorded, then data about them is used for settlement, and they have been doing this for decades. But your point stands about phones and the Internet.

Or chagas. Or chikungunya. Or any of a number of other aegyptus-spread diseases. A species that is not native to most of the world, is not a natural pet of most ecosystems, and which doesn't contribute in any meaningful way to almost any ecosystem in the world.

It's not entirely outsourced by any means. There is a lot of it. The article is discussing one department that was outsourced, many others are not.

Regarding running their own Linux distro, that probably would be neither cheap or really helpful (which of their vendors would support that vs. some other distro in practice?) but yes, there is a sizeable IT footprint required for such a large place.

on linux rm · c/linuxmemes · 5 pts · 328d

I'm not windows expert, but as far as I know, the way to get snapshots on NTFS is via VSS, which is usually going to work by making a block level snapshot that can be mounted independently and used read only. I don't believe NTFS was designed or has been updated to implement the kind of filesystem features that I was describing.

And yes, NTFS is usually slower at a lot of day to day things. It's very sophisticated in some respects, but it's traditionally not strong at dealing with lots of small file operations across lots of files, something that Linux filesystems tend to be good at, especially as e.g. got was written to support kernel development and if there is something that would speed up git that required a filesystem change due to git showing a performance weakness, well, I believe that had precedent

on linux rm · c/linuxmemes · 34 pts · 328d

Filesystems are either pretty simple or really complex. The old dos FAT filesystem just overwrote the first character of a file name with an omega, and so usually you could just undelete by having a utility that would change the name back, as long as nothing used the blocks.

Modern filesystems are an absolute wonder of spinning wheels inside of spinning wheels allocating ranges of blocks, and then doing bookkeeping to reorganize linked data structures as fast as an SSD can write or as efficiently as possible on spinning rust.

Some log structured filesystems can do special snapshotting either automatically like NetApp ontap or manually like zfs so that when you take a snapshot any further changes preserve a view of that snapshot at a point in time that you can treat like a special directory where you can cd to and copy back out data as it was as long as you have space. Windows supports this kind of functionality with the VSS API if the underlying FS tech supports it.

The downside to these approaches is that they tend to cause fragmentation, can cause a lot of extra space to be used (after all, if you delete a tb, it may be because you meant to and you needed to, so if you mean it, why hasn't it gone away, etc.,) and are a lot of complexity that 99% of the time 99% of the people don't want to think about it or pay for it (pay as in it's slower, uses more space, the complexity leads to more failure modes, etc )