Bug#48866: Time-Zone still wrong
In <[🔎] NDBBLJECCLJCBKMIKBPBCEABFAAA.firstname.lastname@example.org>,
at Date: Tue, 1 Feb 2000 09:52:17 -0800,
on Subject: RE: Bug#48866: Time-Zone still wrong,
"Ross Boylan" <email@example.com> writes:
> I'm concerned there is more to the problem than this. As I reported, when I
> manually changed /etc/default/rcS to UTC=no my system clock was reset when I
Have you "manually changed" it in boot-floppies alternative console (Alt+F2)
during initial install stage (boot from root floppy) ?
I think the problem of "reseting the hardware (cmos) clock on shutdown,
and adjust /etc/adjtime" is another problem than this "boot-floppies can
not change /etc/default/rcS when specified to use localtime in CMOS clock"
> That was with 2.2.4 boot-floppies. Was this just an artifact of
> changing the setting after the initial install?
In initial install, /etc/default/rcS is set by dbootstrap in boot-floppies.
This is done by asking user with the prompt of "Use UTC in CMOS clock ?"
If user answer "yes", then /etc/default/rcS is left untouched, and if user
answer "No", then it is changed from "UTC=yes" to "UTC=no".
This part is the work for boot-floppies.
Then, after rebooting the installed system, system clock and hareware (CMOS)
clock is controlled by /etc/init.d/hwclock.sh using /sbin/hwclock from
This script (/etc/init.d/hwclock.sh) takes the part of "reseting the clock"
problem, and boot-floppies can not do for that.
> Also, if someone could combine this and bug 53808, that would be great. I'm
> now convinced that the two refer to the same problem (I submitted 53808).
If 53808 is for the problem of "resetting the clock on reboot", then
it may be different problem. I think 48866 is initially reported for
the problem of "b-f (boot-floppies) can not change the setting in
Taketoshi Sano: <firstname.lastname@example.org>,<email@example.com>,<firstname.lastname@example.org>