Snapshot files are set with the "snapshot" file flag during creation by

mksnap_ffs(8) or mount(8).  The previous statement was incorrect since
it mentions the immutable flag, i.e. "noschg" which is not the case when
one does "ls -lo" in a directory containing snapshot files.

While I am here, mention a way for finding snapshot files on a file
system.

PR: 	docs/80535 (inspired by)

en_US.ISO8859-1/books/handbook/disks/chapter.sgml

@@ -3141,12 +3141,10 @@ Filesystem 1K-blocks Used Avail Capacity  Mounted on
 	however all the used space may not be acquired because another snapshot will
 	possibly claim some of the released blocks.</para>
 
-      <para>During initial creation, the <option>schg</option> flag (see the &man.chflags.1; manual page)
-	is set to ensure that even <username>root</username> cannot write to the snapshot.
+      <para>The un-alterable <option>snapshot</option> file flag is set
+      by &man.mksnap.ffs.8; after initial creation of a snapshot file.
 	The &man.unlink.1; command makes an exception for snapshot files
-	since it allows them to be removed
-	with the <option>schg</option> flag set, so it is not necessary to
-	clear the <option>schg</option> flag before removing a snapshot file.</para>
+	since it allows them to be removed.</para>
 
       <para>Snapshots are created with the &man.mount.8; command.  To place
 	a snapshot of <filename>/var</filename> in the file
@@ -3159,6 +3157,10 @@ Filesystem 1K-blocks Used Avail Capacity  Mounted on
 	a snapshot:</para>
 <screen>&prompt.root; <userinput>mksnap_ffs /var /var/snapshot/snap</userinput></screen>
 
+      <para>One can find snapshot files on a file system (e.g. <filename>/var</filename>)
+      by using the &man.find.1; command:
+<screen>&prompt.root; <userinput>find /var -flags snapshot</userinput></screen>
+
       <para>Once a snapshot has been created, it has several
 	uses:</para>