summaryrefslogtreecommitdiffstats
path: root/man4/loop.4
diff options
context:
space:
mode:
Diffstat (limited to 'man4/loop.4')
-rw-r--r--man4/loop.418
1 files changed, 10 insertions, 8 deletions
diff --git a/man4/loop.4 b/man4/loop.4
index 71c2e4a..273456c 100644
--- a/man4/loop.4
+++ b/man4/loop.4
@@ -3,7 +3,7 @@
.\"
.\" SPDX-License-Identifier: GPL-2.0-or-later
.\"
-.TH loop 4 2023-05-03 "Linux man-pages 6.05.01"
+.TH loop 4 2023-10-31 "Linux man-pages 6.7"
.SH NAME
loop, loop-control \- loop devices
.SH SYNOPSIS
@@ -20,7 +20,7 @@ image stored in a file, so that it can be mounted with the
.BR mount (8)
command.
You could do
-.PP
+.P
.in +4n
.EX
$ \fBdd if=/dev/zero of=file.img bs=1MiB count=10\fP
@@ -30,14 +30,14 @@ $ \fBsudo mkdir /myloopdev\fP
$ \fBsudo mount /dev/loop4 /myloopdev\fP
.EE
.in
-.PP
+.P
See
.BR losetup (8)
for another example.
-.PP
+.P
A transfer function can be specified for each loop device for
encryption and decryption purposes.
-.PP
+.P
The following
.BR ioctl (2)
operations are provided by the loop block device:
@@ -214,12 +214,14 @@ explicitly request read-only mode by setting
in
.IR loop_config.info.lo_flags .
.RE
-.PP
+.P
Since Linux 2.6, there are two new
.BR ioctl (2)
operations:
.TP
-.BR LOOP_SET_STATUS64 ", " LOOP_GET_STATUS64
+.B LOOP_SET_STATUS64
+.TQ
+.B LOOP_GET_STATUS64
These are similar to
.BR LOOP_SET_STATUS " and " LOOP_GET_STATUS
described above but use the
@@ -293,7 +295,7 @@ device to find a free loop device, opens the loop device,
opens a file to be used as the underlying storage for the device,
and then associates the loop device with the backing store.
The following shell session demonstrates the use of the program:
-.PP
+.P
.in +4n
.EX
$ \fBdd if=/dev/zero of=file.img bs=1MiB count=10\fP