Re: [WORKAROUND]what sets the time at boot?

[Hugo Vanwoerkom <hvw59601@care2.com>]

Sven Joachim wrote:
> On 2009-08-19 20:37 +0200, Hugo Vanwoerkom wrote:
>
> > Sven Joachim wrote:
> > > On 2009-08-19 19:08 +0200, Hugo Vanwoerkom wrote:
> > >
> > > > Hugo Vanwoerkom wrote:
> > > > > So my question is: who at boot time is responsible for realizing
> > > > > that the hwclock is kept in local time and UTC time?
> > > > And the answer is: /etc/init.d/hwclock.sh and
> > > > /etc/init.d/hwclockfirst.sh do that from package util-linux.
> > > They don't do this anymore unless your system is not using udev.
> > >
> > > > It's a bug:
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542443
> > > In which you state that you don't have /dev/rtc.  I'm not sure that
> > > systems without that file are supported.
> > How does one go about getting /dev/rtc?
>
> ,----
> | % grep -i rtc /boot/config-$(uname -r) | grep -v ^#
> | CONFIG_HPET_EMULATE_RTC=y
> | CONFIG_RTC_LIB=y
> | CONFIG_RTC_CLASS=y
> | CONFIG_RTC_HCTOSYS=y
> | CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
> | CONFIG_RTC_INTF_SYSFS=y
> | CONFIG_RTC_INTF_PROC=y
> | CONFIG_RTC_INTF_DEV=y
> | CONFIG_RTC_DRV_CMOS=y
> `----
>
> In the kernel configuration, select "Device Drivers" -> "Real Time Clock"
> and check the options.  Note that udev should create a symlink
> /dev/rtc -> rtc0 automatically for you.

This is what I get:

...
/home/hugoThu Aug 20-10:17:33HDC3# grep -i rtc /boot/config-2.6.30-1-686 
| grep -v ^#
CONFIG_HPET_EMULATE_RTC=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_S35390A=m
CONFIG_RTC_DRV_FM3130=m
CONFIG_RTC_DRV_RX8581=m
CONFIG_RTC_DRV_M41T94=m
CONFIG_RTC_DRV_DS1305=m
CONFIG_RTC_DRV_DS1390=m
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_R9701=m
CONFIG_RTC_DRV_RS5C348=m
CONFIG_RTC_DRV_DS3234=m
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1286=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T35=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_BQ4802=m
CONFIG_RTC_DRV_V3020=m
CONFIG_RTC_DRV_WM8350=m
CONFIG_RTC_DRV_PCF50633=m
...

and that system with the new hwclock command claimed it could not read 
the system clock!

Hugo