On 2015-06-03 15:57, Elan Ruusamäe wrote:

  the previous code caused permission issues in docker:

[root@localhost] # docker run -i -t pld bash
[root@fee5a8d66c6a /]# echo $HOSTNAME
fee5a8d66c6a
[root@fee5a8d66c6a /]# cat /etc/hostname
fee5a8d66c6a
[root@fee5a8d66c6a /]# poldek -u systemd-units
5:systemd-units ###########################################
mv: cannot move '/etc/hostname' to '/etc/hostname.rpmsave': Device or
resource busy
Operation failed: No such file or directory
[root@fee5a8d66c6a /]# ls -l /etc/sysconfig/network /etc/hostname
ls: cannot access /etc/sysconfig/network: No such file or directory
-rw-r--r-- 1 root root 13 Jun  3 13:52 /etc/hostname
[root@fee5a8d66c6a /]# grep hostname /proc/mounts
/dev/mapper/sys-docker /etc/hostname xfs
rw,relatime,attr2,inode64,noquota 0 0



why set up the file at all if the file already exists and is not-empty?

Exactly! If the file is there, then it must not me touched! That is an important part of the system configuration.

Jacek
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Reply via email to