Daniel Kahn Gillmor wrote...
> It'd take a bit of thinking about how to handle mac address
> limitations, and the decision about whether to place the symlink or
> not, to bring this up to parity with the current implementation, but
> then this work could be donated directly to the vblade upstream, and
> we could leave it at that.
As you might already have seen, I've suggested a solution for
persistence at upstream. Assuming things go well - I'm fairly certain -
vblade will soon provide persistence on its own and we can RM
vblade-persist in time before the buster release.
This is mostly to inform potential adopters their work will probably be
in vain.
To ease transition for users of vblade-persist, I've already prepared a
migration script to convert configurations into the new format, it will
be part of the vblade for quite some time.
Christoph, wearing the vblade maintainer's hat
Attachment:
signature.asc
Description: PGP signature