The process I am trying to implement is the most logical and generalised one, so please suggest something along the line.
Not feasible, since I already have a Debian 6.0.3 system, it resets the bios according to my localisation values set there, aided by ntpdate. So you have to please suggest another alternative. I have tried TZ cheatcode but that does not work either. I had also run tzselect (=asia/kolkata) here in knoppix, but that too does not work.
The process I am trying to implement is the most logical and generalised one, so please suggest something along the line.
Well, I will read up on it and see what you are talking about. Thanks for all of the help. I still have a lot to learn, so, and time to learn it. Wish I had more time to spend reading this stuff, but, I have to do other things too. I really haven't figured out the Micro Re-Mastering, but, I suppose I will eventually. I will be posting other issues as well.
The UNIX/ LINUX way is:
- always BIOS time = UTC
With Debian I use the crontab:
With dual boot Windows installation you have to register:Code:40 10,15,20 * * * /usr/sbin/ntpdate -v de.pool.ntp.org; /sbin/hwclock -u --systohc
Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\↲ Services\W32Time\TimeProviders\NtpClient] "SpecialPollInterval"=dword:00000e10 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\↲ CurrentVersion\DateTime\Servers] @="1" "1"="de.pool.ntp.org" "2"="time.nist.gov" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\↲ TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001
Why configure crontab? My system automatically updates the time when I log in to the internet. The ntpdate client listens to the network time servers by itself.
I don't use windoze, so I would not be interested in its registry codes.
Okay, this is one thing that we have got to look into in Knoppix.
But that the BIOS is updated by ntpdate is absolutely confirmed. In doze, if you change time the BIOS time is affected too.
Why not?Why configure crontab?Why do you think so? From man ntpdate:But that the BIOS is updated by ntpdate is absolutely confirmed.ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to determine the correct time.
.
I have a nice Dell laptop which came equipped with Windows 7.
I rarely use Windows 7, but it allows the laptop to be very close
to 'Observatory time' since it syncs up my hardware clock with an
ntp server every time it IS used. I also corrects for daylight
savings time, if allowed a peek at the internet. The hardware
clock in question is set to local Eastern US time. I also set
my Knoppix desktop to local 12-hour am/pm format.
I don't use ntpdate or any other Knoppix time correction.
The consequences of this are two as far as I can tell.
1. The result of a date command will erroneously append UTC to
the otherwise very nearly correct local time.
2. There is a small error, currently about 15 seconds, which I
observe by occasionally checking against the USNO.
See: http://tycho.usno.navy.mil/simpletime.html.
If I wanted to tweak the small error, I could spend a few
minutes with Window 7.
If I wanted to tweak the erroneous UTC, I could use an alias
date="date | sed 's\UTC\EST\'" or date="date | sed 's\UTC\EDT\'"
I rarely find the need to do either.
Nor do I care to disturb my Windows 7 which works ok for what it is.
I am sorry, I should have been more elaborate. Actually, I have a localised system, as explained earlier. ntpdate sends that process the ntp data( time and date), and it localises the date time according to my settings(Asia/Kolkata) and rewrites the BIOS on that basis.
Please tell us the output fromCode:cat /proc/driver/rtc; date
- from Debian
- from Knoppix
My values are with Debian
with KnoppixCode:rtc_time : 07:38:25 rtc_date : 2013-01-28 alrm_time : 00:00:00 alrm_date : ****-**-** alarm_IRQ : no alrm_pending : no 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes DST_enable : no periodic_freq : 1024 batt_status : okay Mo 28. Jan 08:38:25 CET 2013Timezone for me is "Europe/Berlin"Code:cat /proc/driver/rtc; date rtc_time : 07:41:11 rtc_date : 2013-01-28 alrm_time : 00:00:00 alrm_date : 2013-01-29 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : no BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay Mon Jan 28 08:41:11 CET 2013
Dell PowerEdge R730 Intel Xeon 2x E5-2650v4 12C 2.20GHz 128GB 600GB H730 iDrac8
$600.00
Dell PowerEdge R720XD Xeon E5-2680 V2 2.8GHz 20 Cores 256GB RAM 12x4TB
$510.00
DELL PowerEdge R730 Server 2x E5-2690v3 2.6GHz =24 Cores 32GB H730 4xRJ45
$275.00
Dell PowerEdge R730XD 28 Core Server 2X Xeon E5-2680 V4 H730 128GB RAM No HDD
$389.99
Dell PowerEdge R730, 2 sinks, SystemBoard, 8 trays,H330,Idrac 8 exp, 2x750w Psu
$135.00
Dell PowerEdge R620 Server 2x Xeon E5-2620 @ 2.0GHz 64GB RAM NO HDDs
$108.96
Dell PowerEdge R630 2x Xeon E5-2630 V4 2.20GHZ 128GB DDR4-2133MHZ 2x 750W PSU
$170.95
Dell PowerEdge R620 Server - 256GB RAM, 2x8c CPU, 128Gb SSD/3x600Gb SAS, Proxmox
$320.00
Dell PowerEdge R430 3.5 1U 2x E5-2690 v3 2.6ghz 24-Cores 256gb 4x Trays 2x 550w
$289.99
DELL PowerEdge R630 8SFF Server 2x E5-2690v4 2.6GHz =28 Cores 128GB H730 4xRJ45
$444.00