#342 Issue closed: Properly support site.conf and don't hack local.conf

Labels: bug, fixed / solved / done

schlomo opened issue at 2013-12-05 07:25:

While doing 08387b9ba6c7b374edb56e01bc99ff8d060af440 I realized (grep for local.conf) that there are places where we check local.conf for a configuration setting and there are other places where we write to local.conf.

Example: If users use site.conf to configure the use of DHCP in the rescue system then it won't work.

I think that this is very dangerous. Why not use the rescue.conf which is read after the local.conf for that purpose? Also, instead of greping local.conf for configuration items we should be sourcing in the ReaR configuration and use the value if set.

gdha commented at 2013-12-09 10:58:

I'll improve the ./prep/GNU/Linux/21_include_dhclient.sh script some time later

gdha commented at 2014-12-05 17:14:

@Reiner030 when you enhanced the rules of Debian packaging did you notice if the local.conf file got overwriiten?

gdha commented at 2015-02-16 18:44:

added to the release notes so we can close this issue

[Export of Github issue for rear/rear.]