4 ms·
You can't expect filesystem to behave consistently across filesystem and media types because these exist to solve different issues and involve different design
by gmueckl 6y ago
You can't expect filesystem to behave consistently across filesystem and media types because these exist to solve different issues and involve different design decisions.
The same thing goes for out of memory handling: no size fits all. The kind of handling strategy you need depends on the kind of system you build.
Exactly this kind of flexibility and lack of unification is what made Linux so ubiquitous.
- kreetx 6y agoI think what the OP means is that you can be in any filesystem without needing to put much thought into it (regardless of the very real differences in implementation). Advanced users who want to interface with the details can do that, but for the rest of us consistency can be good.
- robertlagrant 6y agoIsn't the same level of detail needed for init as for different filesystems?
- gmueckl 6y agoExcept that file systems aren't consistent on Linux. FAT and NTFS can't represent Unix permission bits. File systems reorder operations internally in some ways user space programs don't expect. NFS mounts may not be able to guarantee exclusive file locks...
- kreetx 6y agoAbsolutely. What I'm saying is that I personally don't need to know about this. I suspect that OOM's behavior is of similar effect to most developers.
- pjmlp 6y agoIt was more like free beer source code did it.