10654 savecore(1M) should be able to work on read-only dump devices
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: John Levon <john.levon@joyent.com>
Reviewed by: Andy Stormont <astormont@racktopsystems.com>
Reviewed by: Gergő Doma <domag02@gmail.com>
Reviewed by: Toomas Soome <tsoome@me.com>

@@ -4,11 +4,11 @@
 
 NAME
        savecore - save a crash dump of the operating system
 
 SYNOPSIS
-       /usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
+       /usr/bin/savecore [-L | -r] [-vd] [-f dumpfile] [directory]
 
 
 DESCRIPTION
        The savecore utility saves a crash dump of the kernel (assuming that
        one was made) and writes a reboot message in the shutdown log. By

@@ -71,10 +71,18 @@
                       of memory continue to change while the dump is saved.
                       This means that live crash dumps are not fully self-
                       consistent.
 
 
+       -r
+                      Open the dump device or file as read-only, and don't
+                      update the dump header or do anything else that might
+                      modify the crash dump. This option can be used to
+                      recover a crash dump from a read-only device. This flag
+                      cannot be used in conjunction with -L.
+
+
        -v
                       Verbose. Enables verbose error messages from savecore.
 
 
 OPERANDS

@@ -134,6 +142,6 @@
        savecore very soon after booting, before the swap space containing the
        crash dump is overwritten by programs currently running.
 
 
 
-                               January 30, 2013                   SAVECORE(1M)
+                               February 22, 2019                  SAVECORE(1M)