F7 general question about livecd-creator and timezones

[Skunk Worx]

My ks scripts have the timezone set to PDT (America/Los_Angeles).

Installation to a hard drive works as expected. PDT in startup and in 
shells, etc.

Creating a livecd-creator iso with the same tz setting, then booting, 
shows A/L_A in the /etc/sysconfig/clock file, as expected.

However the date is always EDT in the boot messages, shells, etc.

During startup I see :

(lvm)
Press I to enter interactive startup
Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007
(udev)

I'm not clear on what is happening between lvm and udev in the Linux 
startup sequence.

If someone could give me a hint about what to look for and where to look 
for it I would appreciate the help.

---
John

[Forrest Taylor]

On Wed, 2007-06-06 at 20:04 -0700, Skunk Worx wrote:
>  My ks scripts have the timezone set to PDT (America/Los_Angeles).
>  
>  Installation to a hard drive works as expected. PDT in startup and in 
>  shells, etc.
>  
>  Creating a livecd-creator iso with the same tz setting, then booting, 
>  shows A/L_A in the /etc/sysconfig/clock file, as expected.
>  
>  However the date is always EDT in the boot messages, shells, etc.
>  
>  During startup I see :
>  
>  (lvm)
>  Press I to enter interactive startup
>  Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007
>  (udev)
>  
>  I'm not clear on what is happening between lvm and udev in the Linux 
>  startup sequence. 
It is probably using the /etc/localtime to determine the time zone.
Replace that with /usr/share/zoneinfo/America/Los_Angeles.

For the above entry, search for "Setting clock" in /etc/rc.sysinit.

Forrest

[Skunk Worx]

Forrest Taylor wrote:
>  On Wed, 2007-06-06 at 20:04 -0700, Skunk Worx wrote:
> > My ks scripts have the timezone set to PDT (America/Los_Angeles).
> >
> > Installation to a hard drive works as expected. PDT in startup and in 
> > shells, etc.
> >
> > Creating a livecd-creator iso with the same tz setting, then booting, 
> > shows A/L_A in the /etc/sysconfig/clock file, as expected.
> >
> > However the date is always EDT in the boot messages, shells, etc.
> >
> > During startup I see :
> >
> > (lvm)
> > Press I to enter interactive startup
> > Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007
> > (udev)
> >
> > I'm not clear on what is happening between lvm and udev in the Linux 
> > startup sequence.
>  
>  It is probably using the /etc/localtime to determine the time zone.
>  Replace that with /usr/share/zoneinfo/America/Los_Angeles.
>  
>  For the above entry, search for "Setting clock" in /etc/rc.sysinit.
>  
>  Forrest
>   
Yes, it's the binary file /etc/localtime.

It appears livecd-creator doesn't trigger a code path into 
"tzdata-update" (directly) or via "build-locale-archive" (indirectly)

whereas a kickstart or "normal" anaconda install does.

For now I'm going to dynamically update it during startup with 
"tzdata-update".

Thanks,
John

F10 general question about livecd-creator and timezones

[Marc Herbert]

Wow, Same time zone bug 2 years later, and same "tzdata-update" workaround!

I love email archives :-)


Skunk Worx <skunkworx(a)verizon.net&gt; writes:

>  Forrest Taylor wrote:
> > On Wed, 2007-06-06 at 20:04 -0700, Skunk Worx wrote:
> >> My ks scripts have the timezone set to PDT (America/Los_Angeles).
> >>
> >> Installation to a hard drive works as expected. PDT in startup and
> >> in shells, etc.
> >>
> >> Creating a livecd-creator iso with the same tz setting, then
> >> booting, shows A/L_A in the /etc/sysconfig/clock file, as expected.
> >>
> >> However the date is always EDT in the boot messages, shells, etc.
> >>
> >> During startup I see :
> >>
> >> (lvm)
> >> Press I to enter interactive startup
> >> Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007
> >> (udev)
> >>
> >> I'm not clear on what is happening between lvm and udev in the
> >> Linux startup sequence.
> >
> > It is probably using the /etc/localtime to determine the time zone.
> > Replace that with /usr/share/zoneinfo/America/Los_Angeles.
> >
> > For the above entry, search for "Setting clock" in /etc/rc.sysinit.
> >
> > Forrest
> >
>
>  Yes, it's the binary file /etc/localtime.
>
>  It appears livecd-creator doesn't trigger a code path into
>  "tzdata-update" (directly) or via "build-locale-archive"
> (indirectly)
>  whereas a kickstart or "normal" anaconda install does.
>
>  For now I'm going to dynamically update it during startup with
>  "tzdata-update".