.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "mount.posixovl 8" .TH mount.posixovl 8 2024-03-20 "mount.posixovl" "User Commands" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME posixovl \-\- FUSE file system that provides POSIX functionality .SH SYNOPSIS .IX Header "SYNOPSIS" .Vb 1 \& mount.posixovl [\-F] [\-S SOURCE_DIR] TARGET_DIR [\-\- fuseopts] .Ve .SH DESCRIPTION .IX Header "DESCRIPTION" If no source directory is given, the TARGET_DIR specifies both source and target (mount point), yielding an "over mount". .PP Supports: chmod, chown, hardlink, mkfifo, mknod, symlink/readlink ACLs/xattrs (only in passthrough mode, no emulation). .SH NOTES .IX Header "NOTES" Using posixovl on an already POSIX-behaving file system (e.g. XFS) incurs some issues, since detecting whether a path is POSIX behaving or not is difficult. Hence, the following decision was made: .PP .Vb 4 \& \- permissions will be set to the default permissions (see below) unless \& a HCB is found that can override these \& \- all lower\-level files will be operated on/created with the user who \& initiated the mount .Ve .PP If no HCB exists for a file or directory, the default permissions are 644 and 755, respectively. The owner and group of the inode will be the owner/group of the real file. .PP Each non-regular, non-directory virtual file will have a zero-size real file. Simplifies handling, and makes it apparent the object exists when using other operating system. .PP Command \fBdf\fR\|(1) will show: .PP .Vb 5 \& $ df \-Tah \& File System Type Size Used Avail Use% Mounted on \& /dev/hda5 vfat 5.9G 2.1G 3.9G 35% /windows/D \& posix\-overlay(/windows/D) \& fuse.posixovl 5.9G 2.1G 3.9G 35% /windows/D .Ve .SH OPTIONS .IX Header "OPTIONS" .IP \fB\-F\fR 4 .IX Item "-F" Option \fB\-F\fR will disable permission and ownership checks that would be required in case you have a POSIX mount over VFAT. For example, where /vfat is vfat, and /vfat/xfs is a POSIX-behaving file system. .SH EXAMPLES .IX Header "EXAMPLES" In general, posixovl does not handle case-insensitivity of the underlying file system (in case of VFAT, for example). If you create a file \fIX0\fR on VFAT, it is usually lowercased to \fIx0\fR, which may break some software, namely X.org. In order to make VFAT behave more POSIX-like, the following mount options are recommended: .PP .Vb 1 \& mount \-t vfat /dev/sda5 /mnt/vfat \-o check=s,shortname=mixed .Ve .SH ENVIRONMENT .IX Header "ENVIRONMENT" None. .SH FILES .IX Header "FILES" None. .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBmount\fR\|(1) \&\fBumount\fR\|(1) .SH AUTHORS .IX Header "AUTHORS" Program was written by Jan Engelhardt . .PP This manual page was written by Jari Aalto , for the Debian GNU system (but may be used by others). Released under license GNU GPL version 2 or (at your option) any later version. For more information about license, visit .