Actually, it looks like boot.clock does _nothing_ on S/390 and zSeries systems. Even on non-mainframe systems, all it really does is issue hwclock commands, which have no effect on what timezone gets used. That is really, truly, only dictated by /etc/localtime.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Wednesday, October 26, 2005 4:05 PM To: [email protected] Subject: Re: Generating and fstab from list of mounted file systems I may not be understanding the problem... But the way I get the timezone to be what I want it to be is to update /etc/sysconfig/clock with the -u and the "US/Pacific". Then /etc/init.d/boot.clock takes care of it at IPL time. Marcy Cortes ---------------------------------------------------------------------- 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
