Posted: Mon 01 Sep 2008, 18:24
Post deleted because somewhat misleading and incomplete. See my next post.
READ-ONLY Archive
https://oldforum.puppylinux.com/
I did the right thing to set the TZ at Europe/BrusselsIn other words, POSIX counts time offsets negative for zones east of the Greenwich meridian, where time is ahead of GMT. (Source of quote: http://www.twinsun.com/tz/tz-link.htm)
I checked now for Puppy 4.00-k2.6.21.7-seamonkeyBéèm wrote:I did the right thing to set the TZ at Europe/Brussels
You might have found a bug there.erikson wrote:But the timezone GUI still has the older "GMT+-n" entries from previous versions, and these older entries are still just as wrong as they were in previous Puppies. GUI selection of a "GMT+-n" timezone creates a symlink /etc/localtime to /usr/share/zoneinfo/Etc/GMT-+n (i.e. with inverted sign). For instance, the old timezone selection "GMT+1 (Paris, Berlin, Amsterdam, Brussels...)" actually gives localtime one hour behind GMT, whereas the old timezone selection "GMT-2 (Mid-Atlantic)" gives the correct time for CEST, two hours ahead of GMT.
4 series works fine for GMT-5 here. I use the 'old-style "GMT+-n" entries' as well as dual boot XP. Clock is always correct.erikson wrote:My conclusion: in Puppy 4 series, you can safely use the timezone GUI with the new-style "continent/city" entries, but you should avoid the old-style "GMT+-n" entries (or use them with inverse sign, as for Puppy series 2 and 3).
Yes I dual boot to windows and the time stays correct.erikson wrote:Is your machine dual-boot? I just wonder if your Windows time is correct.
No, there's nothing wrong with the timezone GUI in all recent puppies 2 -4. This was worked out ages ago. The sign inversion is correct. Here in Perth Australia my timezone is GMT+8, however the people who designed the GMT timezone files decided in their wizdom to invert the signs. So, I have /etc/localtime linked to /usr/share/timezone/Etc/GMT-8, which is correct. Note, Puppy assumes your hardware clock is set to local time, which is usually what Windows expects also.erikson wrote:But the timezone GUI still has the older "GMT+-n" entries from previous versions, and these older entries are still just as wrong as they were in previous Puppies. GUI selection of a "GMT+-n" timezone creates a symlink /etc/localtime to /usr/share/zoneinfo/Etc/GMT-+n (i.e. with inverted sign). For instance, the old timezone selection "GMT+1 (Paris, Berlin, Amsterdam, Brussels...)" actually gives localtime one hour behind GMT, whereas the old timezone selection "GMT-2 (Mid-Atlantic)" gives the correct time for CEST, two hours ahead of GMT
Code: Select all
1# ls -l /etc/localtime
lrwxrwxrwx 1 root root 25 2008-09-03 18:35 /etc/localtime -> /usr/share/zoneinfo/GMT-2
1#
1# hwclock
Wed 03 Sep 2008 06:39:20 PM GMT-2 -0.376946 seconds
1#
1# date
Wed Sep 3 18:39:27 GMT-2 2008
1#
1# date -u
Wed Sep 3 16:39:35 UTC 2008
1#
You may have wondered about eeelog and tlog in the directory listing that I posted; eeelog is an experimental relic that I forgot to clean up; for tlog see...Bruce B wrote:if I wrote /etc/profile, I'd have to take it up with it's author.
Code: Select all
1# cat /tmp/tlog
2008-09-04 16:21:05.405 (1,,1714) /etc/rc.d/rc.sysinit
2008-09-04 16:21:05.738 (2,,1838) /etc/rc.d/rc.update
2008-09-04 16:21:05.788 (1,,1714) /etc/rc.d/rc.modules
2008-09-04 16:21:08.251 (2,,2567) /etc/rc.d/rc.alsa
2008-09-04 16:21:08.678 (1,,1714) /etc/rc.d/rc.local0
2008-09-04 16:21:08.734 (1,,1714) /etc/rc.d/rc.modules2
2008-09-04 16:21:08.872 (2,,2857) /etc/rc.d/rc.country
2008-09-04 14:21:10.010 (2,,2872) /etc/rc.d/rc.network
2008-09-04 14:21:10.025 (2,,2890) /etc/rc.d/rc.modem
2008-09-04 14:21:11.441 (2,,3050) /etc/rc.d/rc.modem
2008-09-04 14:21:11.492 (1,,1714) /etc/rc.d/rc.local
2008-09-04 14:21:12.474 (1,,3276) /etc/profile
2008-09-04 14:21:12.599 (1,,3276) /etc/profile.d/qt.sh
2008-09-04 14:21:12.602 (1,,3276) added for test... /etc/profile.d/test.sh
2008-09-04 14:21:12.618 (1,,3276) /usr/X11R7/bin/xwin
2008-09-04 14:21:15.321 (2,,3409) /root/.xinitrc
2008-09-04 14:21:23.590 (3,1,3575) /root/.bashrc
1#
Don't worry, I have no Linux reputation to defendBefore erikson stands corrected any more, and my not wanting to see him to have to sit corrected...
... but as an amateur astronomer, I happen to know already which way the earth spins.... I'll explain the best way I know to make a person wonder which way the earth spins.
Actually pcPuppyOS has a time sync utility built in, and I tried it months ago. I never succeeded in letting it sync, however, and it didn't throw anything out of whack either, it just reported failure to sync. That was the case with my earlier timezone setting, and it still is the case with my corrected setting.Install a time sync utility in Puppy and see if it syncs or throws things out of whack.
Code: Select all
#need to set Linux system time/date, from hardware clock...
hwclock --hctosys --localtime
#...--hctosys reads cmos clock to system.
#...--localtime means that cmos clock is set to local-time.
Code: Select all
# cat /tmp/tlog
2008-09-09 16:41:33.748 (,,1) init: Loading kernel drivers needed to access disk drives
2008-09-09 16:41:40.896 (,,1) init: Searching for Puppy files in computer disk drives
2008-09-09 16:41:41.179 (,,1) init: Loading personal storage file /puppOSfin/pup_save-pOSfin.2fs (sda1)
2008-09-09 16:41:43.203 (,,1) init: Loading the 'pup_301.sfs' main file
2008-09-09 16:41:43.882 (,,1) init: Setting up the Unionfs layered filesystem
2008-09-09 16:41:43.964 (,,1) init: Preparing switch_root to the new Unionfs filesystem
2008-09-09 16:41:45.447 (,,1) init: Copying tlog to the new /tmp folder
2008-09-09 16:41:45.458 (,,1) init: Now executing the switch_root
2008-09-09 18:41:45.742 (1,,2282) /etc/rc.d/rc.sysinit
2008-09-09 18:41:46.066 (2,,2406) /etc/rc.d/rc.update
2008-09-09 18:41:51.228 (1,,2282) /etc/rc.d/rc.modules
2008-09-09 18:41:53.700 (2,,11968) /etc/rc.d/rc.alsa
2008-09-09 18:41:54.121 (1,,2282) /etc/rc.d/rc.local0
2008-09-09 18:41:54.175 (1,,2282) /etc/rc.d/rc.modules2
2008-09-09 18:41:54.320 (2,,12258) /etc/rc.d/rc.country
2008-09-09 16:41:55.011 (2,,12273) /etc/rc.d/rc.network
2008-09-09 16:41:55.019 (2,,12280) /etc/rc.d/rc.modem
2008-09-09 16:41:56.450 (2,,12456) /etc/rc.d/rc.modem
2008-09-09 16:41:56.501 (1,,2282) /etc/rc.d/rc.local
2008-09-09 16:41:57.745 (1,,12682) /etc/profile
2008-09-09 16:41:57.853 (1,,12682) /etc/profile.d/qt.sh
2008-09-09 16:41:57.855 (1,,12682) added for test... /etc/profile.d/test.sh
2008-09-09 16:41:57.871 (1,,12682) /usr/X11R7/bin/xwin
2008-09-09 16:42:00.610 (2,,12815) /root/.xinitrc
2008-09-09 16:42:16.607 (3,1,13001) /root/.bashrc
#
In the mean time I've done so (I just forgot to report).erikson wrote:Now it won't be difficult anymore to get rid of those last few timestamp anomalies between switch_root and rc.country. The simplest solution is to move the systemtime reset from the end of /etc/rc.d/rc.country to the very beginning of /etc/rc.d/rc.sysinit that runs immediately after busybox init (as defined in /etc/inittab).
Code: Select all
1# cat /tmp/elog
puppOSfin
2008-12-21 10:11:43.030 (,,1) init: Loading kernel drivers for disk access
2008-12-21 10:11:51.260 (,,1) init: Searching for Puppy files
2008-12-21 10:11:53.471 (,,1) init: Loading /puppOSfin/pup_save-pOSfin.2fs
2008-12-21 10:11:56.533 (,,1) init: Loading pup_301.sfs main file
2008-12-21 10:11:56.589 (,,1) init: Setting up the layered filesystem
2008-12-21 10:11:56.616 (,,1) init: Preparing switch_root
2008-12-21 10:11:56.712 (,,1) init: Now executing the switch_root
2008-12-21 10:11:59.030 (1,,1851) /etc/rc.d/rc.sysinit
2008-12-21 10:11:59.454 (2,,1974) /etc/rc.d/rc.update
2008-12-21 10:11:59.542 (1,,1851) /etc/rc.d/rc.modules
2008-12-21 10:12:02.215 (2,,2703) /etc/rc.d/rc.alsa
2008-12-21 10:12:02.704 (1,,1851) /etc/rc.d/rc.local0
2008-12-21 10:12:02.795 (1,,1851) /etc/rc.d/rc.modules2
2008-12-21 10:12:02.970 (2,,3011) /etc/rc.d/rc.country
2008-12-21 10:12:03.023 (2,,3025) /etc/rc.d/rc.network
2008-12-21 10:12:03.072 (2,,3047) /etc/rc.d/rc.modem
2008-12-21 10:12:04.558 (2,,3208) /etc/rc.d/rc.modem
2008-12-21 10:12:04.620 (1,,1851) /etc/rc.d/rc.local
2008-12-21 10:12:04.946 (1,,3400) /etc/profile
2008-12-21 10:12:05.219 (1,,3400) /etc/profile.d/qt.sh
2008-12-21 10:12:05.232 (1,,3400) /etc/profile.local
2008-12-21 10:12:05.273 (1,,3400) /usr/X11R7/bin/xwin (entry)
2008-12-21 10:12:08.270 (2,,3539) /root/.xinitrc
2008-12-21 10:12:13.036 (3,,3652) /usr/sbin/delayedrun
2008-12-21 10:12:29.943 (2,,3392) /mnt/home/bin/e-startup
2008-12-21 10:12:29.971 (3,,3762) /mnt/home/bin/e-meminfo
2008-12-21 10:12:30.070 (3,,3768) /mnt/home/bin/e-httpd start
2008-12-21 10:12:30.115 (3,,3775) /mnt/home/bin/e-pingd
2008-12-21 10:12:30.137 (3,,3776) /mnt/home/bin/e-myipd: probing router...
2008-12-21 10:12:37.976 (3,,3776) /mnt/home/bin/e-myipd: IP=81.242.106.244
2008-12-21 10:47:09.860 (3,,12812) /usr/sbin/snapmergepuppy
2008-12-21 10:54:43.092 (3,1,15551) /root/.bashrc
2008-12-21 11:17:10.629 (3,,21584) /usr/sbin/snapmergepuppy
2008-12-21 11:47:20.527 (3,,30336) /usr/sbin/snapmergepuppy
2008-12-21 12:17:23.440 (3,,6435) /usr/sbin/snapmergepuppy
2008-12-21 12:47:25.432 (3,,15191) /usr/sbin/snapmergepuppy
2008-12-21 13:17:27.741 (3,,23955) /usr/sbin/snapmergepuppy
2008-12-21 13:47:30.726 (3,,32705) /usr/sbin/snapmergepuppy
2008-12-21 14:17:34.454 (3,,9052) /usr/sbin/snapmergepuppy
1#