mirror of
https://github.com/lkl/linux.git
synced 2025-12-18 23:53:03 +09:00
29e4402a82
This lock-while-mounted behaviour is similar to what QEMU does, and can help avoid duplicate mounts. Allowing for an explicit lock path that differs from the filesystem image / block device path was intentional, to ensure non-flock supporting filesystems can still be used. Also, there are cases where a block device and partition (e.g. sda and sda1) can both provide access to the same filesystem image, in which case an FS-ID based lock would make sense. Signed-off-by: David Disseldorp <ddiss@suse.de>
49 lines
1.2 KiB
ReStructuredText
49 lines
1.2 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
=========
|
|
lklfuse
|
|
=========
|
|
|
|
-----------------------------------------
|
|
access LKL mounted block devices via FUSE
|
|
-----------------------------------------
|
|
|
|
:Date: 2025-06-23
|
|
:Manual section: 8
|
|
|
|
SYNOPSIS
|
|
========
|
|
|
|
lklfuse block-device mountpoint [options]
|
|
|
|
DESCRIPTION
|
|
===========
|
|
|
|
lklfuse uses the Linux Kernel Library (LKL) to mount a block-device or
|
|
filesystem image, and provides access to the host system via FUSE.
|
|
lklfuse can run as an unprivileged user-space process, while reusing entire
|
|
Linux kernel filesystem driver implementations.
|
|
|
|
Udev rules and systemd service files are available for automatically mounting
|
|
USB storage devices via an unprivileged lklfuse sandbox; see 61-lklfuse.rules
|
|
and lklfuse-mount@.service.
|
|
|
|
OPTIONS
|
|
=======
|
|
|
|
-o log=<file> log to <file>.
|
|
|
|
-o type=fstype mount with filesystem type <fstype>.
|
|
|
|
-o mb=memory allocate <memory> in MB for LKL (default: 64).
|
|
|
|
-o part=parition mount <partition>.
|
|
|
|
-o ro open block-device read-only.
|
|
|
|
-o lock=<file> only mount after taking an exclusive lock on <file>.
|
|
|
|
-o opts=options Linux kernel mount <options> (use \\ to escape , and =).
|
|
|
|
See `lklfuse --help` for additional FUSE specific options.
|