New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lib/vfscore: Introduce ukopts
, a new vfs.fstab
option and mkmp
, a ukopts
option
#1145
lib/vfscore: Introduce ukopts
, a new vfs.fstab
option and mkmp
, a ukopts
option
#1145
Conversation
0080305
to
6cc4aef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested my side, this works. :) Thanks!
Reviewed-by: Alexander Jung alex@unikraft.io
a0a8f2d
to
19c4e54
Compare
Sorry, I know, lots of pushes, I messed up some rebasing 🙃 |
198bf42
to
8f42060
Compare
ukopts
, a new vfs.fstab
option and mkpath
, a ukopts
optionukopts
, a new vfs.fstab
option and mkmp
, a ukopts
option
ee07fe8
to
71f9074
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mogasergiu, thanks a lot for your work. I just noticed some little things with the update but overall looks very good already!
The Unikraft Core supports, following the merge of [0], the ability to specify Unikraft-specific options as part of the `vfstab` list of options. This commit accommodates for that basic change. [0]: unikraft/unikraft#1145 Signed-off-by: Alexander Jung <alex@unikraft.io>
Allow the `vfs.fstab` option arguments to receive an additional option that is Unikraft specific and that enables one to change a volume's mount behavior depending on the passed option. Thus, now the `vfs.fstab` syntax is as follows: ``` vfs.fstab=[ "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" ... ] ``` The `ukopts` options will have the same separator as `fstab`, that being `:`. Signed-off-by: Sergiu Moga <sergiu@unikraft.io>
In case someone may want to mount a filesystem to a directory that does not currently exist in the rootfs, allow them to do so without having to rebuild the rootfs by exposing a `ukopts` option called `mkmp`. This option will let `fstab` know that it must ensure that the mount path exists before attempting to mount. Signed-off-by: Sergiu Moga <sergiu@unikraft.io>
71f9074
to
65926f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your work and updates!
Reviewed-by: Simon Kuenzer simon@unikraft.io
Approved-by: Simon Kuenzer simon@unikraft.io
Allow the `vfs.fstab` option arguments to receive an additional option that is Unikraft specific and that enables one to change a volume's mount behavior depending on the passed option. Thus, now the `vfs.fstab` syntax is as follows: ``` vfs.fstab=[ "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" ... ] ``` The `ukopts` options will have the same separator as `fstab`, that being `:`. Signed-off-by: Sergiu Moga <sergiu@unikraft.io> Reviewed-by: Simon Kuenzer <simon@unikraft.io> Approved-by: Simon Kuenzer <simon@unikraft.io> GitHub-Closes: unikraft#1145
In case someone may want to mount a filesystem to a directory that does not currently exist in the rootfs, allow them to do so without having to rebuild the rootfs by exposing a `ukopts` option called `mkmp`. This option will let `fstab` know that it must ensure that the mount path exists before attempting to mount. Signed-off-by: Sergiu Moga <sergiu@unikraft.io> Reviewed-by: Simon Kuenzer <simon@unikraft.io> Approved-by: Simon Kuenzer <simon@unikraft.io> GitHub-Closes: unikraft#1145
Following the merge of [0], the name of the Unikraft-specific VFSTAB cli option for creating a non-existing directory is called `mkmp` and not `mkpath`. The latter was the original name which was changed during the review process of [0]. [0]: unikraft/unikraft#1145 Signed-off-by: Alexander Jung <alex@unikraft.io>
Allow the `vfs.fstab` option arguments to receive an additional option that is Unikraft specific and that enables one to change a volume's mount behavior depending on the passed option. Thus, now the `vfs.fstab` syntax is as follows: ``` vfs.fstab=[ "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" "<src_dev>:<mntpoint>:<fsdriver>[:<flags>:<opts>:<ukopts>]" ... ] ``` The `ukopts` options will have the same separator as `fstab`, that being `:`. Signed-off-by: Sergiu Moga <sergiu@unikraft.io> Reviewed-by: Simon Kuenzer <simon@unikraft.io> Approved-by: Simon Kuenzer <simon@unikraft.io> GitHub-Closes: unikraft#1145
In case someone may want to mount a filesystem to a directory that does not currently exist in the rootfs, allow them to do so without having to rebuild the rootfs by exposing a `ukopts` option called `mkmp`. This option will let `fstab` know that it must ensure that the mount path exists before attempting to mount. Signed-off-by: Sergiu Moga <sergiu@unikraft.io> Reviewed-by: Simon Kuenzer <simon@unikraft.io> Approved-by: Simon Kuenzer <simon@unikraft.io> GitHub-Closes: unikraft#1145
Prerequisite checklist
checkpatch.uk
on your commit series before opening this PR;Base target
Additional configuration
Description of changes
Allow the
vfs.fstab
option arguments to receive an additionaloption that is Unikraft specific and that enables one to change
a volume's mount behavior depending on the passed option.
Thus, now the
vfs.fstab
syntax is as follows:The
ukopts
options will have the same separator asfstab
, thatbeing
:
.Furthermore, in case someone may want to mount a filesystem to a directory
that does not currently exist in the rootfs, allow them to do so
without having to rebuild the rootfs by exposing a
ukopts
option called
mkpath
. This option will letfstab
know thatit must ensure that the mount path exists before attempting to
mount.