#1639 Issue closed: remove os.conf creation on rear.spec file

Labels: enhancement, cleanup, fixed / solved / done

gdha opened issue at 2017-12-11 08:12:

  • rear version (/usr/sbin/rear -V): 2.3+
  • OS version (cat /etc/rear/os.conf or lsb_release -a): rhel and sles arch
  • Brief description of the issue: clean up the rear.spec file around the creation of os.conf file
    This is a continuation of issue #731

jsmeix commented at 2018-01-30 11:08:

Via https://github.com/rear/rear/pull/1713
/etc/rear/os.conf gets autocreated in the original sytem (if not already exists).

I wonder why /etc/rear/os.conf is autocreated in the original sytem?

Why not only autocreate a $ROOTFS_DIR/etc/rear/os.conf in the recovery system
e.g. in the same way as $ROOTFS_DIR/etc/rear-release gets autocreated by
build/default/970_add_rear_release.sh ?

In general I do not like it when any "rear WORKFOLW" automatically
changes the original system without an explicit user request.
I think in general the original system should be sacrosanct - except there is
really a very good reason to automatically change the original system.

gdha commented at 2018-02-23 09:53:

@jsmeix Cannot follow your reasoning here - it was like this for a decade. From my point of view this issue may be closed. If you want to change the behaviour then please create a new separate issue.

jsmeix commented at 2018-02-23 10:37:

O.k. for me.

[Export of Github issue for rear/rear.]