https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c2 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net Summary|hostname lost while zypper |hostname lost while zypper |dup from 13.1 to Factory |dup from 13.1 to Factory or | |zypper dup of Factory --- Comment #2 from Felix Miata 2014-06-25 22:31:54 EDT --- On Factory installation last dup'd 5 weeks ago, HOSTNAME was replaced with symlink to hostname containing linux.site without regard to original content of HOSTNAME during today's zypper dup (4 bit host hs80e). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c4 Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #4 from Petr Gajdos 2014-06-27 10:27:47 UTC --- Standa Brabec pointed out that there can be various setups according to /etc/{HOSTNAME,hostname} on the original system before the update. I tested %pre/%post from comment 3 like this: (1) There is /etc/HOSTNAME only. -------------------------------- $ ls -l /etc | grep -i hostname -rw-r--r-- 1 root root 11 Jun 26 12:44 HOSTNAME $ echo bleble > /etc/HOSTNAME $ rpm -Uhv netcfg-11.5-0.noarch.rpm --force $ ls -l /etc | grep -i hostname lrwxrwxrwx 1 root root 8 Jun 27 09:50 HOSTNAME -> hostname -rw-r--r-- 1 root root 7 Jun 27 09:47 HOSTNAME.rpmsave -rw-r--r-- 1 root root 7 Jun 27 09:50 hostname $ cat /etc/hostname bleble (2) There is /etc/HOSTNAME and /etc/hostname link to /etc/HOSTNAME. ------------------------------------------------------------------- $ ls -l /etc | grep -i hostname -rw-r--r-- 1 root root 7 Jun 27 10:01 HOSTNAME lrwxrwxrwx 1 root root 13 Jun 27 10:02 hostname -> /etc/HOSTNAME $ echo bleble > /etc/HOSTNAME $ rpm -Uhv netcfg-11.5-0.noarch.rpm --force $ ls -l /etc | grep -i hostname lrwxrwxrwx 1 root root 8 Jun 27 10:04 HOSTNAME -> hostname -rw-r--r-- 1 root root 7 Jun 27 10:02 HOSTNAME.rpmsave -rw-r--r-- 1 root root 7 Jun 27 10:04 hostname -rw-r--r-- 1 root root 11 Jun 27 09:13 hostname.rpmnew lrwxrwxrwx 1 root root 13 Jun 27 10:02 hostname.rpmsave -> /etc/HOSTNAME alef:/> cat /etc/hostname bleble (3) There is /etc/HOSTNAME and /etc/hostname, both regular files. ----------------------------------------------------------------- Unlikely, /etc/HOSTNAME and /etc/hostname can differ but that would mean conflict between them. $ ls -l /etc | grep -i hostname -rw-r--r-- 1 root root 16 Jun 27 10:09 HOSTNAME -rw-r--r-- 1 root root 16 Jun 27 10:09 hostname $ echo bleble.HOSTNAME > /etc/HOSTNAME $ echo bleble.hostname > /etc/hostname $ rpm -Uhv netcfg-11.5-0.noarch.rpm --force $ ls -l /etc | grep -i hostname lrwxrwxrwx 1 root root 8 Jun 27 10:11 HOSTNAME -> hostname -rw-r--r-- 1 root root 16 Jun 27 10:09 HOSTNAME.rpmsave -rw-r--r-- 1 root root 16 Jun 27 10:11 hostname -rw-r--r-- 1 root root 11 Jun 27 09:13 hostname.rpmnew -rw-r--r-- 1 root root 16 Jun 27 10:09 hostname.rpmsave $ cat /etc/hostname bleble.HOSTNAME (4) There is /etc/hostname and /etc/HOSTNAME, link to /etc/hostname. -------------------------------------------------------------------- $ ls -l /etc | grep -i hostname lrwxrwxrwx 1 root root 13 Jun 27 10:18 HOSTNAME -> /etc/hostname -rw-r--r-- 1 root root 11 Jun 26 12:44 hostname $ echo bleble > /etc/hostname $ ls -l /etc | grep -i hostname lrwxrwxrwx 1 root root 8 Jun 27 10:21 HOSTNAME -> hostname lrwxrwxrwx 1 root root 13 Jun 27 10:18 HOSTNAME.rpmsave -> /etc/hostname -rw-r--r-- 1 root root 7 Jun 27 10:19 hostname -rw-r--r-- 1 root root 11 Jun 27 09:13 hostname.rpmnew $ cat /etc/hostname bleble Does that serve our purpose? Or is there another scenario which would fail? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c7 --- Comment #7 from Felix Miata 2014-06-27 06:57:24 EDT --- 1: cf. Bug 872264 2: I don't see the following covered by the proposal: -rw-r--r-- 2 root root 13 Dec 23 2013 HOSTNAME -rw-r--r-- 2 root root 13 Dec 23 2013 hostname 3: Why not a hard link of hostname to existing HOSTNAME? 4: One of my pet peeves routinely violated by zypper and yast activity is any file whose content before touching is identical to that after touching and my finding the original timestamp has not survived along with the original content. This very irritating behavior happens constantly to /etc/fstab and various files in /etc/sysconfig/ among others, mostly in the /etc/ tree. Would the renaming of /etc/HOSTNAME to /etc/hostname be another as a result of the proposal? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c9 --- Comment #9 from Felix Miata 2014-07-03 03:07:35 EDT --- In order to not have a current timestamp polluting either HOSTNAME or hostname, before doing upgrades I set a hard link from HOSTNAME to hostname, then set HOSTNAME immutable. This halts the upgrade process until I tell it to ignore its inability to create a new HOSTNAME with a current timestamp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c11 --- Comment #11 from Petr Gajdos 2014-07-21 07:25:34 UTC --- (In reply to comment #10)

The change /etc/HOSTNAME -> /etc/hostname + symlink /etc/HOSTNAME do not come

not come == not initiated by -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c13 --- Comment #13 from Felix Miata 2014-07-21 04:55:24 EDT --- (In reply to comment #12)

What exactly do you think by 'not covered'? That the hardlink hierarchy is not maintained during the update?

Yes. Given the extent to which various unchanged config files in the /etc tree get new timestamps when various package updates occur, it would not surprise me, hence the question. What bothers me more is absent using a hardlink between the two, HOSTNAME gets a new create date when hostname gets "created" via mv to HOSTNAME. If it was up to me, the update process would hard link instead of moving, creating a soft link, and leaving behind litter in the form of an .rpmsave or .rpmnew. Better still would be to do no more than a rename, period, dispensing with the HOSTNAME that is pointlessly unique among major distros to openSUSE/SLEx. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c15 Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fcrozat@suse.com | --- Comment #15 from Petr Gajdos 2014-07-24 12:12:54 UTC --- Needinfo provided personally. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c17 Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #17 from Petr Gajdos 2014-07-25 10:55:51 UTC --- Package submitted. Please test. If you meet any other problem which I can resolve on netcfg side, please let me know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c20 --- Comment #20 from Felix Miata 2014-07-28 21:12:33 EDT --- Last 2-3 systems upgraded with HOSTNAME and hostname hard linked survived intact, but I just did host g5eas where HOSTNAME and hostname were hard linked to start with, and afterward HOSTNAME was a currently timestamped symlink to hostname. When I deleted the symlink and recreated the hard link, I wound up with 3 links total, the third to hostname.rpmsave, which I've now deleted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=883999#c22 --- Comment #22 from Felix Miata 2014-08-17 02:30:12 EDT --- netcfg-11.5-23.1 refuses to install when hostname exists as immutable hard link to HOSTNAME -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.