RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 02:37:36 +00:00
Code Issues Activity Actions

Kernel & Userland: Allow to mount image files formatted with Ext2FS

Browse source
This commit is contained in:
Liav A 2020-04-06 11:55:08 +03:00 • committed by Andreas Kling
parent ecee76b741
commit 23fb985f02
8 changed files with 96 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

23
Base/usr/share/man/man2/mount.md
View file

@ -7,12 +7,13 @@ mount - mount a filesystem
```**c++
#include <unistd.h>
int mount(const char* source, const char* target, const char* fs_type, int flags);
int mount(int source_fd, const char* target, const char* fs_type, int flags);
```
## Description
`mount()` mounts a filesystem stored at `source` by overlaying its contents over `target`.
`mount()` mounts a filesystem stored at `source_fd` by overlaying its contents
over `target`.
`fs_type` must be one of the following supported filesystems:
@ -21,9 +22,10 @@ int mount(const char* source, const char* target, const char* fs_type, int flags
* `DevPtsFS` (or `devpts`): The pseudoterminal pseudo-filesystem (normally mounted at `/dev/pts`).
* `TmpFS` (or `tmp`): A non-persistent filesystem that stores all its data in RAM. An instance of this filesystem is normally mounted at `/tmp`.
For Ext2FS, `source` must be a path to a block device storing the filesystem contents. All
the other filesystems ignore the `source` argument (by convention, it should have the same
value as `fs_type`).
For Ext2FS, `source_fd` must refer to an open file descriptor to a file containing
the filesystem image. This may be a device file or any other seekable file. All
the other filesystems ignore the `source_fd` — you can even pass an invalid file
descriptor such as -1.
The following `flags` are supported:
@ -37,14 +39,17 @@ mounted file system.
### Bind mounts
If `MS_BIND` is specified in `flags`, `fs_type` is ignored and a bind mount is performed
instead. In this case `source` is treated as a path to a file or directory whose contents
are overlayed over `target`. This can be used as an alternative to symlinks or hardlinks.
If `MS_BIND` is specified in `flags`, `fs_type` is ignored and a bind mount is
performed instead. In this case, the file or directory specified by `source_fd`
is overlayed over `target` — the target appears to be replaced by a copy of the
source. This can be used as an alternative to symlinks or hardlinks.
## Errors
* `EFAULT`: The `fs_type` or `target` are invalid strings.
* `EPERM`: The current process does not have superuser privileges.
* `ENODEV`: The `fs_type` is unrecognized, or the device is not found, or the device doesn't contain a valid filesystem image.
* `ENODEV`: The `fs_type` is unrecognized, or the file descriptor to source is not found, or the source doesn't contain a valid filesystem image. Also, this error occurs if `fs_type` is valid, but the file descriptor from `source_fd` is not seekable.
* `EBADF`: If the `source_fd` is not valid, and either `fs_type` specifies a file-backed filesystem (and not a pseudo filesystem), or `MS_BIND` is specified in flags.
All of the usual path resolution errors may also occur.