https://bugzilla.novell.com/show_bug.cgi?id=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c1 Sankar P <psankar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent --- Comment #1 from Sankar P <psankar@novell.com> 2008-09-15 05:30:06 MDT --- Setting priority as I feel this is an urgent issue that makes my machine unusable. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c3 --- Comment #3 from Sankar P <psankar@novell.com> 2008-09-15 13:24:07 MDT --- (In reply to comment #2 from Robert Vojcik)

Hello,

Please provide the content of /etc/adjtime

0.275542 1221504743 0.000000 1221504743 LOCAL

Is your hardware clock set to localtime or UTC?

Localtime

Right after booting, when you get the wrong system time, can you please check the output of

hwclock --show

Shall restart and provide this.

Thanks

-- 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=426270 User rvojcik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c5 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |psankar@novell.com --- Comment #5 from Robert Vojcik <rvojcik@novell.com> 2008-09-16 04:11:15 MDT --- Ok, try to change in yast2 system clock to UTC instead of local time. -- 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=426270 User chuckwolfe@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c7 chuck wolfe <chuckwolfe@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chuckwolfe@gmail.com Status|NEW |RESOLVED Resolution| |FIXED --- Comment #7 from chuck wolfe <chuckwolfe@gmail.com> 2008-09-18 19:31:50 MDT --- (In reply to comment #5 from Robert Vojcik)

Ok,

try to change in yast2 system clock to UTC instead of local time.

Yes. that does not make the system time go wrong. -- 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=426270 User ivan.lucchese@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c9 Ivan Lucchese <ivan.lucchese@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.lucchese@gmail.com --- Comment #9 from Ivan Lucchese <ivan.lucchese@gmail.com> 2008-09-27 11:54:13 MDT --- First of all, hello to everybody. I'm a new openSuSE user, but not new at linux, at least as an hobbyst. I was very interested in the "1-click-installation" feature and so I installed openSuSE 11.0 from the live CD. Then I was really annoyed by this same bug: at each reboot, my system time was delayed by two more hours (4 hours after 2 reboots, 6 hours after 3 reboots ...). My hardware clock is set to local time, since once in a while I have to use WindowsXP ... My local time is CEST, so it is GMT+2. With a working ntp server the system time goes good, but sometimes my ADSL connection is quite slow to start up and so it takes several minutes before the ntp server can connect and synchronize. I tried some search in this bugzilla and in the forums and I found out other people with this problem but no complete fix (http://forums.opensuse.org/install-boot-login/388755-wrong-clock-11-0-a-3.ht...). After some tries I found out that probably the problem is due to the fact that /sbin/hwclock, as called by the boot.clock script, needs access to data stored in the /usr/share/zoneinfo directory. Note that my /usr directory is stored in a different partition and that partiton is not mounted till after the boot.localfs script is called and has completed its procedure. Without parallel booting it is sufficient to call boot.clock just after boot.localfs, but with parallel booting boot.clock is still called before the /usr partition is mounted. As I like parallel booting, as a temporary fix I copied /usr/share/zoneinfo in the / directory. BTW, I see in the boot.clock script the line "#X-Start-Before: boot.localfs", so it seems that boot.clock must be called after boot.localfs: can somebody explain why ? And fix the problem that we have found? P.S. I promise to be less verbose next time, but I've been involved for so much time with this bug ... ;-) -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c10 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoenig@novell.com, aj@novell.com, ro@novell.com Severity|Critical |Normal Status|NEW |RESOLVED Priority|P1 - Urgent |P3 - Medium Resolution| |INVALID --- Comment #10 from Dr. Werner Fink <werner@novell.com> 2008-10-01 06:01:39 MDT --- The script boot.clock *must* called before boot.localfs to get the timestamps of the mounts correct in their superblock. Please note: this was and is a request of the developers of e.g. the e2fsprogs to get the fsck counts and times correct. And we have to follow this. On system reboot or system halt the script boot.getclock is used to write the system time back to the CMOS clock. Both scripts *must* be enabled, e.g. by insserv boot.getclock insserv boot.clock please note that the /etc/adjtime makes little sence in case of using local time for CMSO time. This is the reason why the original boot.clock and boot.getclock of openSuSE 11.0 do not use /etc/adjtime in case of not using UTC: [...] USE_ADJFILE=no case "$HWCLOCK" in *-u*) USE_ADJFILE=yes esac test "$USE_ADJFILE" = no && HWCLOCK="$HWCLOCK --noadjfile" [...] please do *not* change this. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c12 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@novell.com, pbaudis@novell.com AssignedTo|werner@novell.com |pbaudis@novell.com Status|REOPENED |NEW Summary|Time resets everytime machine is rebooted |Timezone not in /etc (Was: Time resets everytime | |machine is rebooted) --- Comment #12 from Dr. Werner Fink <werner@novell.com> 2008-10-02 03:52:05 MDT --- Sorry but if I would change this to fix your problem this would open an other bug. Please note that we are *enforced* to set the system time *before* mounting the local file system. Beside this: CMOS Clock != System Clock, that is running the CMOS clock in UTC as reference clock is the common way for a normal system as the local time is hold in System Clock as the later is set by hwclock(8) automatically from the CMOS Clock to the correct local time. T his is very simple and works perfect even with the switch from local Standard Time to Daylight Saving Time and vice versa ... beside this on most hardware out there it also works perfect with adjfile option of hwclock(8). About Windows[tm] I can say nothing but most UNIX and Linux systems I know do have the CMOS clock in UTC and the system time in local time as these two clocks are fully different. Otherwise the adjfile option of hwclock(8) to handle the variance of the CMOS clock would not make any sense. But AFAIK (but never used) it is possible to run the CMOS Clock in local time as long as hwclock(8) knows about(!) but this may cause trouble at the switch from Standard Time to Daylight Saving Time and vice versa is used together with the adjfile option. The problem of not having the informations of /usr/share/zoneinfo and the binary /usr/sbin/zic in the boot system (e.g. /usr not mounted) is a real problem and should be fixed. At least the timezone informations of the local time should be stored in /etc/ and /usr/sbin/zic should become /sbin/zic for e.g. s390. Petr? Any comment about? -- 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=426270 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c14 --- Comment #14 from Petr Baudis <pbaudis@novell.com> 2008-10-02 07:16:03 MDT --- Sankar P, to sum up Werner's post, the main reason CMOS clock should be kept in UCT is correct handling of daylight saving and other timezone changes (yes, that does happen sometimes). I think the main problem is to run this kind of setup with separate /usr and I'm not sure if it is reasonable to support that - why do you want to have separate /usr in the first place? There is really no good place for the timezone data outside of /usr/share - I believe they do not belong to /etc since they are not _configuration_ files, but _data_ files. So the closest would be probably something akin /lib/timezone, but that would be quite an evil hack, and I'm not convinced at all that doing that juts for the sake of supporting separate /usr is reasonable. -- 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=426270 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c16 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |werner@novell.com --- Comment #16 from Petr Baudis <pbaudis@novell.com> 2008-10-02 07:50:05 MDT --- Actually, I now remember that we did already look into this problem in the past and we _did_ change /etc/localtime from symlink to a copy (or a hardlink). So, hwclock should have no problem with this? -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c18 --- Comment #18 from Sankar P <psankar@novell.com> 2008-10-04 10:08:06 MDT --- My machine is a fresh 11.0 installation and I have not customized anything in /usr or anywhere. It is just vanilla 11.0 + updates (with all default options) Single boot linux is not a possible option for a (shared) laptop. And it is not that uncommon to have users not removing their windows OSes and hence the time needs to be in sync with that. I do not mind even if this is a configurable option somewhere in yast. From an user perspective, losing time everytime I boot to a different OS is making my machine unusable. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c20 Sankar P <psankar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|psankar@novell.com | --- Comment #20 from Sankar P <psankar@novell.com> 2008-11-17 00:49:54 MST --- psankar@sandance:~/svn/gnome/evolution> ls -l /etc/localtime -rw-r--r-- 5 root root 265 2008-11-08 02:18 /etc/localtime psankar@sandance:~/svn/gnome/evolution> cat /etc/sysconfig/clock ## Path: System/Environment/Clock ## Description: Information about your timezone and time ## Type: string(-u,--utc,--localtime) ## ServiceRestart: boot.clock # # Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="-u" ## Description: Write back system time to the hardware clock ## Type: yesno ## Default: yes # # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # SYSTOHC="yes" ## Type: string(Europe/Berlin,Europe/London,Europe/Paris) ## ServiceRestart: boot.clock # # Timezone (e.g. CET) # (this will set /usr/lib/zoneinfo/localtime) # TIMEZONE="Asia/Kolkata" DEFAULT_TIMEZONE="US/Eastern" -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c22 --- Comment #22 from Sankar P <psankar@novell.com> 2008-11-18 02:23:15 MST --- What is invalid about this bug ? I don't get it honestly. I did a fresh installation of 11.0 After which, whenever I boot to windows and linux the machine times are different and wrong. What is the solution for this ? Why should they be different at all ? Why, should my machine time reset everytime my machine reboots ? By looking at the number of people facing the issue, I don't think it is just a misunderstanding of one person (me). And there are lots of people who complain about this same time behavior even in IRC. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c24 Sankar P <psankar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Basesystem |Basesystem Product|openSUSE 11.0 |openSUSE 11.1 Resolution|INVALID | Summary|Timezone not in /etc (Was: Time resets everytime|Time becmoes wrong in linux everytime after |machine is rebooted) |booting to windows Version|Final |RC 1 --- Comment #24 from Sankar P <psankar@novell.com> 2008-12-09 00:39:42 MST --- I upgraded to 11.1 and my windows paritition was not reachable then on ( a seperate bug and resolved now). So, I could not verify this earlier. With 11.1 RC fresh installation, Still my system time becomes wrong everytime, I switch between windows and linux . I have not got any option for retaining windows time during installation. None of the settings in YaST fixes the time to be same across windows and linux. Please tell me if one such setting exists. Reopening the bug as it is still happening with vanilla 11.1 RC build as well. -- 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=426270 Lukas Ocilka <locilka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@novell.com |jsuchome@novell.com -- 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=426270 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c27 --- Comment #27 from Jiří­ Suchomel <jsuchome@novell.com> 2008-12-09 06:04:17 MST --- Created an attachment (id=258898) --> (https://bugzilla.novell.com/attachment.cgi?id=258898) screenshot -- 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=426270 User pchenthill@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c29 --- Comment #29 from Chenthill palanisamy <pchenthill@novell.com> 2008-12-10 00:18:45 MST --- I have an issue in setting Hardware clock to UTC. I set the my local time (utc + 5:30) as system time. Since my system time is considered to be in utc with the above option enabled, there is a mismatch of the times between system times in the auto-build machine and my machine. I face problems while building the tarballs scp'ed from my machine to autobuild system since the timestamps in files are ahead of the system time in autobuild system. I now have the system time set in UTC which is -5:30 from timezone Asia/Kolkatta (my local timezone) to workaround this issue. Due to this, the mails which I send out have a wrong time stamp. Considering these problems, is setting "Hardware clock set to UTC" is a right solution ? Please correct me if am wrong. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c31 Sankar P <psankar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical --- Comment #31 from Sankar P <psankar@novell.com> 2008-12-11 03:56:15 MST --- (In reply to comment #30 from Dr. Werner Fink)

Remark: execute as root

insserv /etc/init.d/boot.clock

to make sure that the service of this script is really enabled. This because there was an other bug with a similiar problem and it was detected that boot.clock was never enabled on that system.

This did the trick. After executing this command, I unset "HW clock in UTC" setting in Yast; rebooted to windows changed time to correct time in windows; rebooted to linux. And the time remained correct across windows and linux. However, I consider this bug to be valid, as we cannot expect all muti-boot users to execute this command. Also, I tested this in a 11.1 installation (and not an update from 11.0, after formatting / ) So, I hope it will not be due to any old obsolete data from 11.0 Also, I am raising the severity of this issue, as I think it deserves more than a Normal state. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c33 --- Comment #33 from Dr. Werner Fink <werner@novell.com> 2008-12-11 04:14:45 MST --- The missing start/stop links may happend during the consecutively updates. Nevertheless we can not do a hardcoded insserv of boot.clock because there are users which do not want to run hwclock and had therefore disabled boot.clock. AFAIK the spec file of aaa_base checks if boot.clock was disabled and do honour this (Rudi?). -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c36 Sankar P <psankar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knikanth@novell.com --- Comment #36 from Sankar P <psankar@novell.com> 2008-12-11 06:16:00 MST --- (In reply to comment #35 from Andreas Jaeger)

Werner, you say this happens only during update. I think Sankar is saying this happens on a fresh install as well - where it should not at all. Sankar, is that correct? In that case we do have a regression which means this is MAJOR.

Yes. When I (and a lot of other students) tried it, it was a fresh install and not an update. In fact most of us my peers got new laptops, a few weeks after 11.0 release and we installed afresh on these new laptops. The problem existed for all of them. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c38 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@novell.com, coolo@novell.com --- Comment #38 from Dr. Werner Fink <werner@novell.com> 2008-12-11 07:25:59 MST --- Add Stephan to CC list. Beside this it could also an error in yast2-country, therefore Jiri should stay at least in CC list. @ Jiri : Does yast2-country something with boot.clock? Maybe enabling or disabling boot.clock? @ All of those which see the problem : Is one of the files which should be enabled by aaa_base not enabled. The list includes boot.proc, boot.localfs, boot.swap, boot.clock, boot.ldconfig, boot.ipconfig, boot.klog, boot.localnet, halt, random, reboot, and single. -- 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=426270 User pchenthill@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c40 --- Comment #40 from Chenthill palanisamy <pchenthill@novell.com> 2008-12-11 22:59:19 MST --- (In reply to comment #36 from Sankar P)

(In reply to comment #35 from Andreas Jaeger)

...

Werner, you say this happens only during update. I think Sankar is saying this happens on a fresh install as well - where it should not at all. Sankar, is that correct? In that case we do have a regression which means this is MAJOR.

Yes. When I (and a lot of other students) tried it, it was a fresh install and not an update. In fact most of us my peers got new laptops, a few weeks after 11.0 release and we installed afresh on these new laptops. The problem existed for all of them.

Right. I too have a fresh install. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c42 --- Comment #42 from Sankar P <psankar@novell.com> 2008-12-12 00:50:04 MST --- Okay Captain Magnus helped me out in irc. As root I tried chkconfig with all these options. For: boot.proc, boot.localfs, boot.swap, boot.clock, boot.ldconfig, boot.ipconfig, boot.klog, boot.localnet , I got "on" for boot.halt I got 0 for reboot I got off for single I got 1S -- 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=426270 User markus.kossmann@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c44 Markus Koßmann <markus.kossmann@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markuskossmann@gmx.de --- Comment #44 from Markus Koßmann <markus.kossmann@gmx.de> 2008-12-29 13:11:12 MST --- Unfortunately this bug has made it into 11.1 final. I've seen it on two fresh installations (not updates) : The system is definitely set to localtime: --------------------------------[/etc/sysconfig/clock]-------------------------- Path: System/Environment/Clock ## Description: Information about your timezone and time ## Type: string(-u,--utc,--localtime) ## ServiceRestart: boot.clock # # Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime" ## Type: yesno ## Default: yes ## Description: Write back system time to the hardware clock # # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # SYSTOHC="yes" ## Type: string(Europe/Berlin,Europe/London,Europe/Paris) ## ServiceRestart: boot.clock # # Timezone (e.g. CET) # (this will set /usr/lib/zoneinfo/localtime) # TIMEZONE="Europe/Berlin" DEFAULT_TIMEZONE="Europe/Berlin" -------------------------------------------------[snip]------------------------- -------------------------------------------[/etc/adjtime]----------------------- 0.000000 1229879064 0.000000 1229879064 LOCAL ---------------------------------------[snip]----------------------------------- But after after setting clock and rebooting the system you will see:

hwclock -r So 21 Dez 2008 19:34:08 CET -0.473655 Sekunden date So 21. Dez 20:33:43 CET 2008

-- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c46 --- Comment #46 from Sankar P <psankar@novell.com> 2008-12-30 23:14:03 MST --- this problem exists even if there is no seperate /usr. I have jsut / and /home even then the problem appears. -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c48 --- Comment #48 from Sankar P <psankar@novell.com> 2008-12-30 23:18:38 MST --- psankar@sandance:~/Desktop> rpm -qa --triggers --scripts | grep -B3 -A14 boot.clock test -n "$FIRST_ARG" || FIRST_ARG=$1 FORCE_YES=0 set -- boot.proc boot.localfs boot.swap boot.clock boot.ldconfig boot.ipconfig boot.klog boot.localnet halt random reboot single PNAME=aaa_base INSSRV_ARRAY="" while [ ${#*} -gt 0 ] ; do SCRIPTNAME=$1 shift SV_B='^### BEGIN INIT INFO' SV_E='^### END INIT INFO' SV_KW=Default-Enabled SV_VALUE=`sed -n -e "/$SV_B/,/$SV_E/{/^# [^[:space:]]*$SV_KW:[[:space:]]*\([^[:space:]]*\).*/s//\1/p;}" < etc/init.d/$SCRIPTNAME` test "$FORCE_YES" = "1" && SV_VALUE="yes" test -n "$SV_VALUE" || SV_VALUE="yes" INSSRV_ARRAY="$INSSRV_ARRAY $SCRIPTNAME $SV_VALUE" done -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c50 --- Comment #50 from Dr. Werner Fink <werner@novell.com> 2009-01-07 05:25:26 MST --- Now the question is: Why we do not see this error here around with fresh installations of openSuSE 11.1 ... it is very hard to debug a problem without reproducing the problem its self :( -- 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=426270 User psankar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c52 --- Comment #52 from Sankar P <psankar@novell.com> 2009-01-07 10:37:16 MST --- .... and of course in a machine with a multi-boot option (windows) -- 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=426270 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c54 --- Comment #54 from Petr Baudis <pbaudis@novell.com> 2009-01-07 10:51:48 MST --- (I have actually done just this last weekend, but I did not check time consistency in Windows and Linux - I can do that this weekend if I remember.) -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c56 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|coolo@novell.com |psankar@novell.com --- Comment #56 from Dr. Werner Fink <werner@novell.com> 2009-01-12 01:44:38 MST --- @iantos_hal: In english please ... or is here a russian native speaker around which is able to translate this into english . -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c59 --- Comment #59 from Dr. Werner Fink <werner@novell.com> 2009-01-12 03:42:27 MST --- OK ... with tanslate.google.com I see:

I write in English and not very worried about me, whether I understand the developer. Well, once he was over 4 months and did not understand the problem. And in general, cool to see the developer OSes, which is not seen and knows nothing about Windows (TM). Moreover, the system which takes in the market about 1 percent of (and all the assembly) is trying to dictate the terms of "how to work with time " Incidentally, this was one of the reasons that I have version 11.0, I did not exploit. It was a small entry. Bagh number 423697 has been led by me. I realized that this is a problem in the near future can be resolved unless Developer Windows (TM), ie They perepishut their systems under the "correct" work with time. Therefore, their problems, I decided myself to read as follows: after the initial boot put on the stage 3 and 5 of the following: /etc/init.d/boot.clock restart Now I am being shown correctly.

Which leads me to the assumption that the start/stop links are missed of /etc/init.d/boot.clock in that case ... therefore please try out insserv /etc/init.d/boot.clock before next reboot/halt. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c61 --- Comment #61 from Dr. Werner Fink <werner@novell.com> 2009-01-12 04:05:51 MST --- Petr? After your installation is there a file /etc/adjtime around? -- 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=426270 User iantos_hal@mail.ru added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c63 --- Comment #63 from Игорь Антошин <iantos_hal@mail.ru> 2009-01-19 08:27:24 MST --- (In reply to comment #59)

OK ... with tanslate.google.com I see:

Excuse. Further I will write in english.

Which leads me to the assumption that the start/stop links are missed of /etc/init.d/boot.clock in that case ... therefore please try out

insserv /etc/init.d/boot.clock

before next reboot/halt.

After the given command has been fulfilled I has received too as was before.. i.e. has exchanged nothing. I return in loading on runlevels 3 and 5 a command /etc/init.d/boot.clock restart -- 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=426270 User varkoly@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c65 Peter Varkoly <varkoly@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Joseph.Comfort@asu.edu --- Comment #65 from Peter Varkoly <varkoly@novell.com> 2009-01-21 08:34:27 MST --- *** Bug 465850 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=465850 -- 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=426270 Ruediger Oertel <ro@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- 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=426270 User Joseph.Comfort@asu.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c68 --- Comment #68 from Joseph Comfort <Joseph.Comfort@asu.edu> 2009-01-24 14:37:27 MST --- The mod in #66 does not work for me. Although marked as a duplicate, my bug #465850 may be something else. If SuSE wants to put out a fix as in #68, that is fine with me, but it does not fix my case. Here are 2 situations: 1) On my desktop, which runs essentially continuously, a reboot starts up with the time 7 hours behind (not ahead). (I am in the Phoenix time zone.) At the 'bootsplash' in the /var/log/messages file, it then jumps to the correct time. This behavior did not change with the mod in #66. Some log files are written with the wrong time information. 2) My laptop is usually off. When I turned it on, the time was 14 hours behind. I made the mod, set the correct date and time manually, and rebooted. Unlike the desktop, the time was 7 hours behind -- it was not even the correct time. Upon a second reboot, the time was again 14 hours behind. I set my clock to be for local time. The behaviors here do not happen on SuSE 10.3 or earlier versions. It is something new. I did not understand all the discussion on this issue. Are the file system people demanding a change so they can avoid the "time in the future" error messages on reboots? If so, I would prefer the messages to the new behavior. In any case, the issues here are pointing to a weakness in the development of linux (or other open source) software. There are too many independent entities, with little or no overall guiding management to ensure consistency. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c70 --- Comment #70 from Dr. Werner Fink <werner@novell.com> 2009-01-26 03:34:13 MST --- (In reply to comment #69)

Neither computer has a /etc/adjtime file. There is no boot.getclock in 11.1 (apparently handled through boot.clock stop). chkconfig shows boot.getclock is 'on.' The installation was clean and new from the offical release DVD iso.

A file which does not exist can not provide a service and therefore chkconfig can not report `boot.getclock on'. Please do rm /etc/init.d/boot.getclock rm /etc/init.d/*.d/*boot.getclock insserv -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c72 --- Comment #72 from Dr. Werner Fink <werner@novell.com> 2009-01-28 09:23:48 MST --- Fix may be available with update for bug #466484 -- 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=426270 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c74 --- Comment #74 from Jim Omura <jimomura@pathcom.com> 2009-02-03 15:08:05 MST --- I am thinking about what was said in Comments #9 and #10. I do not like the idea of adding more directories directly in "/" but it makes sense that this stuff in particular would go in "/etc/init.d" since it is important for system initialization. In fact, if it is considered critical for the early part of the boot process it could be argued that it should be in "/boot", but I think too many traditionalists would scream if that was done. So how about this: The RPM should install everything in "/usr/share/zoneinfo" into "/etc/init.d/zoneinfo" and this latter directory should be soft-linked back to "/usr/share/zoneinfo" for the sake of programs that might actually need it there later. The only other changes necessary would be for programs actually running before the local file systems are mounted actually during the boot process, which should not be very many changes. Everything else could use the soft-link. Is this feasible? -- 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=426270 User Joseph.Comfort@asu.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c76 Joseph Comfort <Joseph.Comfort@asu.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pbaudis@novell.com | --- Comment #76 from Joseph Comfort <Joseph.Comfort@asu.edu> 2009-02-07 12:51:01 MST --- 3 computers: 1) Desktop, openSuSE 10.3 2) Desktop, openSuSE 11.1 3) Laptop, openSuSE 11.1 Facts: Computer 1 has /etc/localtime as a real file (copy of /usr/share... Computers 2 & 3 have /etc/localtime as a soft link to ..//usr/share/zoneinfo/America/Phoenix [note //] Computers 1 and 2 do not have /etc/adjtime Computer 3 has /etc/adjtime [a comment below] None of the computers have /etc/UTC / and /usr are separate partitions (along with some others). My laptop had been off a few days. When started up, the log file showed the time as 7 hours earlier (behind the actual time), and it never corrected. I manually reset the time. The /etc/adjtime file was created at that time, and the /etc/localtime also showed that time. A change that fixes my problems: Instead of having a soft link, I copied /usr/share/zoneinfo/America/Phoenix to /etc/localtime. Now, on boot and all reboots, the time is continuous and correct in /var/log/messages and in the display clock. (!) Of course, the hard copy is not the way things are installed in 11.1, although it is that way in 10.3. So the problem seems to be the install procedures. The rpms, or whatever, must also ensure that the /etc/localtime file is a hard copy whenever an update is installed. If the system people want to patch and update boot.clock, that would be fine. But an update to make /etc/localtime a real file is also needed, and should be pushed out very soon. Then 11.1 will behave correctly as does 10.3. -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c78 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jsuchome@novell.com --- Comment #78 from Dr. Werner Fink <werner@novell.com> 2009-02-09 02:16:08 MST --- AFAIK the /etc/localtime is always a hard copy done by YaST since several years. The question is *why* this is not true on your systems. Which package replace the hard copy done by YaST with a sysmbolic link? Jiri? Do you have any idea? -- 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=426270 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c80 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |pbaudis@novell.com --- Comment #80 from Dr. Werner Fink <werner@novell.com> 2009-02-09 03:55:14 MST --- OK then let's ask Petr. Petr? Does `zic -l <timezone>' create a hard copy of the specific timezone in /etc/localtime or does it create a soft link pointing to /usr/share/zoneinfo/<timezone>? -- 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=426270 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c81 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |lnussel@novell.com Info Provider|pbaudis@novell.com | --- Comment #81 from Ludwig Nussel <lnussel@novell.com> 2009-02-09 06:09:17 MST --- yes, see bug 473743 -- 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=426270 User gfarrell@netspeed.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c83 Geoff Farrell <gfarrell@netspeed.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gfarrell@netspeed.com.au --- Comment #83 from Geoff Farrell <gfarrell@netspeed.com.au> 2009-02-23 03:27:48 MST --- My machine boots with localtime set, then part way through the boot process, the time is set to 11 hours ahead of localtime. It is then set back to localtime when boot.clock runs. The timezone is set to Australia/Sydney, using a copy of /usr/share/zoneinfo/Australia/Sydney at /etc/localtime, not a link: # ll /usr/share/zoneinfo/Australia/Sydney -rw-r--r-- 8 root root 2183 Feb 8 00:00 /usr/share/zoneinfo/Australia/Sydney # ll /etc/localtime -rw-r--r-- 1 root root 2183 Feb 8 00:00 /etc/localtime /etc/sysconfig/clock has the correct settings: HWCLOCK="--localtime" SYSTOHC="yes" TIMEZONE="Australia/Sydney" DEFAULT_TIMEZONE="US/Eastern" (comments stripped out) This timezone is UTC +11 hours (daylight saving active). The version of /etc/init.d/boot.clock has the patch referred to at Comment #66. The computer was booted at approximately 2009-02-23 16:53. The correct localtime was confirmed in the BIOS during the boot process. This is an excerpt from /var/log/boot.msg: ... Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/tty1(/dev/console) at Mon Feb 23 16:54:09 2009 Trying manual resume from /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part5 Invoking userspace resume from /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part5 resume: libgcrypt version: 1.4.1 Trying manual resume from /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part5 Invoking in-kernel resume from /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part5 Waiting for device /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part6 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part6 /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part6: clean, 6681/131648 files, 67574/526120 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part6 Boot logging started on /dev/tty1(/dev/console (deleted)) at Tue Feb 24 03:54:11 2009 done Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... doneEntering boot.clock at date: Tue Feb 24 03:54:14 EST 2009 Setting up the hardware clockdone Leaving boot.clock at date: Mon Feb 23 16:54:16 EST 2009 Activating device mapper... done Checking file systems... fsck 1.41.1 (01-Sep-2008) ... Notice the two lines starting with 'Boot logging started on /dev/tty1'. The first one, just after the 'Kernel log daemon terminating' message, is showing the time from the Hardware Clock as localtime (Mon Feb 23 16:54:09 2009). The second one, just after the root device is mounted read-write, has been set to 11 hours ahead (Tue Feb 24 03:54:11 2009). Later, when boot.clock is run, (with extra 'echo' and 'date' commands added to it) the entry time to it can be seen as +11 hours, then set to the correct localtime on exiting boot.clock. Somewhere between the two 'Boot logging started' messages, something is setting the System Time, is assuming it is based on UTC, and is applying the localtime offset as +11 hours. This has to be a bug, since if it could find the timezone setting, it should also be able to find the 'HWCLOCK="--localtime"' setting in /etc/sysconfig/clock, and work out that the time is Not based on UTC, and just leave System Time alone. boot.clock eventually fixes the time, but a lot of files and devices have their date-time stamps set 11 hours in the future. Potentially, at least these are affected: ... Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... ... After login, the system files with a date-time stamp in the future were captured in the attached file 'future-files'. They are mainly /dev and /sys files. 'boot.msg' is also attached. -- 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=426270 User gfarrell@netspeed.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c85 --- Comment #85 from Geoff Farrell <gfarrell@netspeed.com.au> 2009-02-23 03:31:56 MST --- Created an attachment (id=274613) --> (https://bugzilla.novell.com/attachment.cgi?id=274613) /var/log/boot.msg -- 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=426270 User gfarrell@netspeed.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c87 --- Comment #87 from Geoff Farrell <gfarrell@netspeed.com.au> 2009-03-14 17:32:54 MST --- Re Comment #75: I think too much emphasis is being placed on UTC as a timezone. UTC is a standard, and doesn't require any entry in /etc to know what it is. The installer asks two pieces of information from the user: 1. Is the Hardware Clock set to UTC? (checkbox with prompt: 'Hardware clock set to UTC') 2. What timezone is the computer in? (GUI of world, where user clicks on a city) In answer to 1, /etc/sysconfig/clock will have either HWCLOCK="-u" or HWCLOCK="--localtime". In answer to 2, /etc/sysconfig/clock will have the timezone registered as, for example, TIMEZONE="Australia/Sydney", or TIMEZONE="US/Eastern". As well, /etc/localtime will contain the same information recorded for the /etc/sysconfig/clock 'TIMEZONE=' setting. (For consistency, maybe a new file could be created to hold the second vital piece of information. It could be /etc/hwclock, whose contents would be either '-u' or '--localtime'.) Therefore, enough information is already available in /etc for the System Time to be calculated from the Hardware Clock. No extra specification for UTC is needed in /etc. For example, if someone were in London, their answers would provide: 1. HWCLOCK="-u" 2. TIMEZONE="Europe/London" Both these pieces of information are enough to calculate that System Time = Hardware Clock. (Ie, don't adjust the Hardware Clock time to derive System Time.) Similarly, for me, my answers provide: 1. HWCLOCK="--localtime" 2. TIMEZONE="Australia/Sydney" Again, enough is provided to know that System Time = Hardware Clock. (Ie, don't adjust.) If someone was in New York, and their answers were: 1. HWCLOCK="-u" 2. TIMEZONE="US/Eastern" then enough information is available to know that System Time = Hardware Clock - 4 hours. Re Comment #86:

we are required to set the correct time before accessing the real file system, e.g. running the first fsck and mount on root and that is within initrd.

I agree that this course of action will eliminate all the problems reported in this bug. If you mean the correct time must be set before running the first fsck and mount of root, then /etc will be an unsuitable location for the timezone info (as will any other filesystem which is yet to be mounted). In that case, an extra task will most likely be required of GRUB, which is the only function that can currently access information on a partition without it being mounted on a filesystem. Maybe the information could be stored in /boot/grub/hwclock and /boot/grub/localtime, and passed as parameters to initrd by way of a GRUB menu.lst entry like this: title openSUSE 11.1 - 2.6.27.19-3.2 root (hd0,0) kernel /vmlinuz root=/dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part6 resume=/dev/disk/by-id/ata-ST3200827AS_4ND1N6BB-part5 splash=silent showopts vga=0x31a initrd /initrd hwclock=/grub/hwclock localtime=/grub/localtime (where sda1 is a separate /boot partition) This would require the bootloader program to extract the information from /etc/localtime (and perhaps /etc/hwclock?) and install it the files in /boot/grub/ and in the GRUB 'initrd' line. As an example, my data would be stored as: 1. /boot/grub/hwclock: contents = "--localtime" (the other option would be = "-u") 2. /boot/grub/localtime: contents = "Australia/Sydney" It would also require initrd to be able to accept parameters passed to it, and to apply them to the correct System Time at the appropriate opportunity. Following that, the current function provided by /etc/init.d/boot.clock would need to be modified to remove the 'start' staza, as this would be superfluous. The 'stop' function would still be required. In addition, the bug that is incorrectly setting System Time as UTC-based (between the two 'Boot logging started on' messages in boot.msg - as reported in Comment #83) needs to be identified and eliminated. -- 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.