> I know :) I'm just curious as to why 1) several files aparrently were
> hardlinked to /etc/localtime on the single volume system and 2) what is
> done differently when the sles9 installer is presented with a device vs a
> multi-device install.
See my other note about what SLES might be doing to effect it.
Probably what happened is that /etc/localtime on your single-volume
source was the first file 'tar' encountered. The reality then is
that several files under /usr/share/zoneinfo are hard links giving
multiple names for the same timezone logic. ONE of those was
evidently hard-linked to your /etc/localtime, and 'tar' has
no way to know which end of a hard link is "first".
I see that /usr/share/zoneinfo/US/Central on some of my systems
has a link count of "4". (There are ways to chase down the
other names.) If I hard-link ANY ONE of those to /etc/localtime,
the link count increases to "5", but programs like 'tar' have
no way of knowing that my /etc/localtime was done after the others.
Just a lucky guess here, but since your TAR errors report these:
./usr/share/zoneinfo/America/Chicago
./usr/share/zoneinfo/SystemV/CST6CDT
./usr/share/zoneinfo/US/Central
./usr/share/zoneinfo/CST6CDT
maybe those are the same four names MY system has. ;-)
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
