#1613 Issue closed: There are use cases for mkrescue/mkbackuponly with BACKUP_URL=iso

Labels: enhancement, fixed / solved / done, minor bug

jsmeix opened issue at 2017-12-01 08:47:

mkrescue/mkbackuponly errors out with BACKUP_URL=iso
because of
indicates that there are (special) use cases for
mkrescue/mkbackuponly with BACKUP_URL=iso
so that the hardcoded Error should be replaced with
a UserInput dialog that errors out by default to be on the safe side
but the user can actively intervene to run mkrescue/mkbackuponly
even with BACKUP_URL=iso when he really wants that.

This follows my general principle that the user must
always have ready-made means of final power to decide
and enforce what ReaR should do and then ReaR must obey.

I consider missing ready-made means of final power
as "minor bug" and adding them as "enhancement".

By the way:
I do not consider "just change the (open source) code"
as a ready-made mean of final power for the user.

jsmeix commented at 2017-12-01 09:50:

I will "just merge" https://github.com/rear/rear/pull/1614
unless there are immediate furious objections against
providing ready to use final power to our users ;-)

jsmeix commented at 2017-12-01 10:43:

With https://github.com/rear/rear/pull/1614 merged
I consider this issue to be fixed.

to provide an automated response run ReaR in debug mode '-d'
so that the UserInput function shows its ID like


Then you can specify a predefined input for that particular
UserInput call e.g. via


or specify that in your local.conf (no 'export' needed there).
For details see the USER_INPUT_ variables in default.conf

N3WWN commented at 2017-12-05 17:04:

Thanks @jsmeix !

jsmeix commented at 2017-12-06 13:08:

could you describe your particular use case for
mkrescue/mkbackuponly with BACKUP_URL=iso
because I still have no idea why that could be useful
and/or how that could actually work.

[Export of Github issue for rear/rear.]