Adding missing mount options to the parser #1

Open
opened 4 years ago by joepie91 · 0 comments
Owner

Relevant file: https://git.cryto.net/joepie91/cvm/src/feature/node-rewrite/src/parse/mount-options.js

This contains parsing definitions for a lot of different mount options, for different file systems, However, the list is far from complete. Help is needed to make it more complete, in all the places with a TODO comment. Adding new filesystems is welcome too, so long as they are filesystems that are actually observed to exist on a real system.

The 'friendly names' for these mount options (defined on the right-hand side) should be easy to understand and identify, without needing to consult the filesystem's manpage. This can mean that the name should be very different from the real option name, if that option name is unclear.

Sometimes, different filesystems use different option names for what's semantically the same thing. In those cases, you should make an effort to map those options to the same 'friendly name' as is used elsewhere, in the same format - even when the original option name differs.

Sometimes, the same option name is used in different filesystems for different purposes! For example, the mode mount option can map to filesystemPermissions, rootPermissions, or newPTYPermissions, depending on the semantics of the filesystem. Make sure that you pick the appropriate friendly name, inventing one yourself if the semantics don't match any of the existing ones.

Please make sure that you include a link to the documentation you've used as a reference, as a comment in that filesystem's option list.

Relevant file: https://git.cryto.net/joepie91/cvm/src/feature/node-rewrite/src/parse/mount-options.js This contains parsing definitions for a lot of different mount options, for different file systems, However, the list is far from complete. Help is needed to make it more complete, in all the places with a `TODO` comment. Adding new filesystems is welcome too, so long as they are filesystems that are actually observed to exist on a real system. The 'friendly names' for these mount options (defined on the right-hand side) should be easy to understand and identify, without needing to consult the filesystem's manpage. This can mean that the name should be very different from the real option name, if that option name is unclear. Sometimes, different filesystems use different option names for what's semantically the same thing. In those cases, you should make an effort to map those options to the same 'friendly name' as is used elsewhere, in the same format - even when the original option name differs. Sometimes, the same option name is used in different filesystems for different purposes! For example, the `mode` mount option can map to `filesystemPermissions`, `rootPermissions`, or `newPTYPermissions`, depending on the semantics of the filesystem. Make sure that you pick the appropriate friendly name, inventing one yourself if the semantics don't match any of the existing ones. Please make sure that you include a link to the documentation you've used as a reference, as a comment in that filesystem's option list.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: joepie91/cvm#1
Loading…
There is no content yet.