I'll stuff it into an e-mail in a sec here - Quick question however, going
back to the problem I had with these files not copying.

tar: ./usr/share/zoneinfo/America/Chicago: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/SystemV/CST6CDT: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/US/Central: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/CST6CDT: Cannot hard link to `./etc/localtime':
No such file or directory

Makes sense as they're trying to be created as cross device hard links.
What I don't understand is this:

On an otherwsie identically configured SLES-9 system (mutliple HFS) that
was created using the SLES-9 installer, the file /etc/localtime exists. So,
they cannot be hard-linking to it during install cuz /usr is already
mounted before the install begins. This is vexing because a symbolic link
to any of the target files is vanishing after IPL. I've had many symbolic
links not go away after an IPL - We use them to expose WebSphere log data
from serveral servers in one place.

Until I can solve this time zone file stuff, my cloned guest is reporting
time as UTC which is unacceptable. Any ideas on how to fix this?



             Rick Troth
             <[EMAIL PROTECTED]>
             Sent by: Linux on                                          To
             390 Port                  [email protected]
             <[EMAIL PROTECTED]                                          cc
             IST.EDU>
                                                                   Subject
                                       Re: Generating and fstab from list
             10/26/2005 10:43          of mounted file systems
             AM


             Please respond to
             Linux on 390 Port
             <[EMAIL PROTECTED]
                 IST.EDU>






On Wed, 26 Oct 2005, James Melin wrote:
> While the script I have to do this is crude by most people's standards,
I'd
> be happy to share. Just be gentle. My bash script skills are still on a
> learning curve.

Share it!
We could all learn from what you've done.

Also,  learn shell,  not BASH.   If you need BASH-specific
functions or capability,  externalize those steps.   (I omit
the details of this for now.)   But remember in all cases,  shell is
a write-only language.   That is,  whatever you code in shell script
will be nigh unto impossible for others to read.   ;-)

-- 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

----------------------------------------------------------------------
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

Reply via email to