Lines Matching refs:file

20 Inside of the home directory a file `~/.identity` contains the JSON formatted
26 user cannot make modifications to the file on their own (at least not without
39 the user record in the `~/.identity` file.
83 Linux file system inside a LUKS2 volume inside a loopback file (or on removable
101 * Inside of this LUKS2 volume must be a Linux file system, one of `ext4`,
102   `btrfs` and `xfs`. The file system label must be the user name.
104 * This file system should contain a single directory named after the user. This
106   contains a second copy of the user record in the `~/.identity` file, like in
109 The image file should reside in a directory `/home/` on the system,
113 loopback file `/home/waldo.home` is mounted to `/home/waldo` while activated.)
115 file can be directly `dd`'ed onto it; the format is unchanged. The GPT envelope
117 used in a loopback file and on a removable USB stick. (Note that when mounting
130 Linux kernel file system implementations are generally not robust towards
131 maliciously formatted file systems; there's a good chance that file system
140 the contained file system: this way special directories such as `lost+found/`
149 case of the LUKS2 backend a regular block device mount of the file system
164 During activation, the file system checker (`fsck`) appropriate for the
165 selected file system is automatically invoked, ensuring the file system is in a
169 the file system, the home directory is automatically and recursively `chown()`ed
173 loopback file is `fallocate()`ed during activation, or the mounted file system
176 When deactivating a home directory, the file system or block device is trimmed