Can I get a +1 on this?
--matt
Tom Erickson wrote:
I attached an updated case with the following changes:
Dave Pacheco wrote:
> In section A, paragraph 4: I still find the terminology of saying that
> "zfs send -b" is used to "restore properties" from the original
> dataset confusing, since it's really just generating a stream that
> will later be restored. For customers who understand that a NDMP
> backup = "zfs send" and NDMP restore = "zfs restore" (which it is),
> this is an important distinction. I would just change "restore" to
> "backup" in that sentence.
>
I Changed that to
"This case also adds a -b (restore from backup) option to the 'zfs
send'
command to generate a stream that, when received, restores properties
from the original dataset ... "
> The header of section C.1.1 is similarly confusing.
>
I changed that from
C.1.1. Backup with 'receive -o', restore with 'send -b'
to
C.1.1. 'zfs receive -o' and 'zfs send -b'
> Section B.1: For clarification in the first sentence, you might say
> "_subsequent_ incremental 'zfs send' streams".
>
Done.
> You mention the "-t" aliases in sections A, B, and the overview in C,
> but not in the detailed solutions part of C or the manpage diffs.
>
Nice catch. I meant to include that in the manpage diffs, but I had
nothing further to say about them in the detailed solutions part of C.
C.3.5. zfs list -t
-t type
A comma-separated list of types to display, where
type is one of filesystem, snapshot , volume, or
all. For example, specifying -t snapshot displays
- only snapshots.
+ only snapshots. The following aliases can be used in
+ place of the type specifiers: fs (filesystem), snap
+ (snapshot), and vol (volume).
Thanks,
Tom
_______________________________________________
opensolaris-arc mailing list
[email protected]
