From: Afshin Min <amin@firemail.cc>
To: 9front@9front.org
Subject: [9front] typos in gefs(8)
Date: Mon, 16 Sep 2024 20:18:38 +0300 [thread overview]
Message-ID: <ZuhobrIolC15cqLx@vm3> (raw)
Incomplete phrase here:
> .TP
> .B -S
> Disables automatic snapshots.
> .I old
> and gives it the name
> .IR new .
Others in the diff:
diff 2d63bdbb4416a8328f42db44d3b6d4da04303e17 uncommitted
--- a/sys/man/8/gefs
+++ b/sys/man/8/gefs
@@ -105,7 +105,7 @@
.TP
.BI "-d " snap
Deletes a snapshot, reclaiming whatever space is not shared
-is not shared with other snapshots.
+with other snapshots.
.TP
.B -m
Flags that the newly created snapshot should be mutable.
@@ -130,12 +130,12 @@
Snapshots are independent views of a filesystem hierarchy.
A snapshot may be mutable or immutable.
Mutable snapshots can be mounted and written to,
-Immutable snapshots are a view of a file system hierarchy at a point im time.
+immutable snapshots are a view of a file system hierarchy at a point im time.
They are referred to by name, and are selected at mount time with an attach spec.
When the attach spec starts with the
.B %
sigil, a snapshot is mounted in permissive mode.
-This allows the mounting user to bypass normal file system permission checks.'
+This allows the mounting user to bypass normal file system permission checks.
In order to mount a snapshot in permissive mode, the mounting user must be in the
.I adm
group.
@@ -148,7 +148,7 @@
.I dump:
This is the name used to mount a list of all snapshots.
Each snapshot in the file system will be listed in a directory.
-.IP
+.TP
.I empty:
This is a read-only empty snapshot.
It contains no files or directories.
next reply other threads:[~2024-09-16 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:18 Afshin Min [this message]
2024-09-17 7:13 ` baux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZuhobrIolC15cqLx@vm3 \
--to=amin@firemail.cc \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).