#569 Issue closed: ISO_FILES are no longer considered in /etc/rear/local.conf¶

Labels: enhancement

domibarton opened issue at 2015-03-26 15:14:¶

Hi

There were some commits a while ago https://github.com/rear/rear/commit/41efc97eb7141c30455df45a871b98cd08e09fa7 to add UEFI integreation support to mkbackup / mkrescue. You've changed several scripts which make use of the ISO_FILES variable, basically by replacing the extension of the ISO_FILES variable to multiple cp commands.

Finally the creation of the ISO image was replaced by using the current directory (which contains all the copied files) instead of the ISO_FILES variable:

    -R -J -volid "$ISO_VOLID" $EFIBOOT -v -iso-level 3 .  >&8
    ##-R -J -volid "$ISO_VOLID" $EFIBOOT  "${ISO_FILES[@]}"  >&8

The problem is, that users will still have some ISO_FILES defined in /etc/rear/local.conf (for example inclexcl files for the dsmc client) and rear dump will still report them.

I think we need to add / copy the files & directories from ISO_FILES to the tmp directory for the ISO creation as well. Do you agree?

Cheers
Domi

gdha commented at 2015-03-30 11:40:¶

@domibarton Thank - are you only missing files you added to the array ISO_FILES manually in local.conf?

domibarton commented at 2015-04-02 22:22:¶

@gdha yeah exactly!

---

[Export of Github issue for rear/rear.]