3 ms·
That's true when the namespace covers objects that are very similar to access, ideally identical. If that's not the case, I have found the scheme to be helpful
by mpweiher 7y ago
That's true when the namespace covers objects that are very similar to access, ideally identical.
If that's not the case, I have found the scheme to be helpful to indicate what's going on.
- hlandau 7y agoOn *nix, you can always figure out what type of filesystem is mounted at a given prefix by typing `mount`. What the use of schemes does is make things needlessly inflexible, and embeds a dependency on the name of a filesystem provider inside consumers of that filesystem. It's akin to a Unix where filesystems can only be mounted in top-level directories /mnt, but not /mnt/foo, etc.; I don't see the appeal.
- yjftsjthsd-h 7y agoI prefer to use `df -T /path/to/mount`, personally.
- vageli 7y ago> I prefer to use `df -T /path/to/mount`, personally. Why?
- yjftsjthsd-h 7y agoLets me specify a single file system; I don't think `mount` does that (unless I'm blind; possible).
- vageli 7y agoMount lets you do this as well. mount -t type device destination_dir Unless I am missing something in your use case.
- mpweiher 7y ago> schemes make things needlessly inflexible Not so. See file: :-)