Something I forgot about during the discussion about the diff for dump:
The manpage doesn't mention yet that we can specify the duid on the
command line now.
--- sbin/dump/dump.8.orig Mon Jul 14 23:57:37 2014
+++ sbin/dump/dump.8Mon Jul 14 23:59:09 2014
@@ -288,8 +288,10 @@
is either a
On Fri, 2014-07-11 at 14:22 +0200, Alexander Hall wrote:
> If there are no other objections, I'd like to commit this today.
Just don't forget to get rid of this
> + } else { fprintf(stderr, "duid: %s\n", duid); }
before committing.
On 07/10/14 18:38, Claudio Jeker wrote:
> I was looking for something like this. Manly to make dump -W work with
> DUIDs. Would be nice if it would not introduce a new flag but I think I
> can live with that if the rest works.
How would you decide whether to use the file name or the duid then? I
c
On 07/10/14 16:28, Alexander Hall wrote:
> Anyway, I worked on your diff a bit more:
>
> - keep having -U and -u separate (as discussed)
> - use Uflag instead of duidflag
> - bail out if the duid is all 0.
> - allow specifying the drive to dump by . on the
> command line. Subject to race conditi
Thanks for your feedback!
> I like the idea. I would have liked to read an explanation for the
> selected solution though, or a brief description of it.
I'll add a description below for the benefit of other readers.
> I think adding a check to make sure there is a nonzero duid [...]
> is reasona
Hi!
This diff adds a "-U" flag to dump that allows using disklabel
UIDs in /etc/dumpdates. That makes incremental dumps possible when a
disk is roaming between device files.
I'd be happy to receive comments.
Also, sorry for the noise in misc, and thanks to everyone pointing me
in the right direc
