On Sat, Dec 17, 2005 at 07:45:42PM -0500, Theodore Ts'o wrote:
> Sigh, I see what's going on. Unfortunately S22hwclockfirst.sh gets
> done *after* S10checkroot. So the system time is still incorrect when
> we check the root filesystem; it doesn't get adjusted to account for
> the fact that you're using a non-GMT time until afterwards. I run
> with my hardware clock set to UTC, so I didn't notice this problem.
>
> Could you try renaming /etc/rcS.d/S22hwclockfirst.sh to
> /etc/rcS.d/S09hwclockfirst.sh and see if this addresses your problem?
>
Oops, I just realized, this won't work if /usr is a separately mounted
filesystem, since /etc/localtime is a typically a symlink to
/usr/share/zoneinfo/<timezome>, and at the time when the root
filesystem is checked, any other filesystems (such as possibly /usr)
won't be mounted yet.
On Sat, Dec 17, 2005 at 07:45:42PM -0500, Theodore Ts'o wrote: d/S22hwclockfir st.sh to d/S09hwclockfir st.sh and see if this addresses your problem?
> Sigh, I see what's going on. Unfortunately S22hwclockfirst.sh gets
> done *after* S10checkroot. So the system time is still incorrect when
> we check the root filesystem; it doesn't get adjusted to account for
> the fact that you're using a non-GMT time until afterwards. I run
> with my hardware clock set to UTC, so I didn't notice this problem.
>
> Could you try renaming /etc/rcS.
> /etc/rcS.
>
Oops, I just realized, this won't work if /usr is a separately mounted zoneinfo/ <timezome> , and at the time when the root
filesystem, since /etc/localtime is a typically a symlink to
/usr/share/
filesystem is checked, any other filesystems (such as possibly /usr)
won't be mounted yet.
- Ted