The "utc=no timezone=America/Chicago" boot options worked with 2.1.2-43-amd64,
but do not work with versions 2.2.0-16-amd64 or later.
I could not find any test versions between those two stable versions, so I could not narrow down when these boot options stopped working any further than that. I guess I need to make backups more often, or I would have noticed this sooner.
Since nobody else has mentioned this, maybe I am the only person who uses these boot options. Of course, you get to decide if this is worth the effort to address it.
The ocs_prerun of hwclock that I used in the previous topic still works around the problem.
The "utc=no timezone=America/Chicago" boot options also worked with gparted-live-0.16.2-1b-amd64,
but fail to work with gparted-live-0.16.2-11-amd64 or later.
If you would like for me to create a bug report (or would this be a feature request) for gparted-live, then I will do so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the bug report.
On Clonezilla live 2.2.0 we started to use newer live-boot and live-config (version 3) from Debian. Therefore I believe it's broken, I will fix that.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did a test, and it looks working in Clonezilla live 2.2.2-32.
1) Boot clonezilla-live-2.2.2-32-amd64.iso, without changing any boot parameters:
root@debian:~# cat /proc/cmdline
BOOT_IMAGE=/live/vmlinuz initrd=/live/initrd.img boot=live username=user config quiet noswap edd=on nomodeset locales= keyboard-layouts= ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch=no vga=788 ip= nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=no
root@debian:~# date
Wed Apr 2 02:44:37 UTC 2014
The utc=no option does not work for Hong Kong: "utc=no timezone=Asia/Hong_Kong" only changes the timezone code but the time is stil utc, i.e. off by 8 hours. I have to use "date -s -8hours" to correct it.
This happened in version 2.1.x.
Since I saw your discussion, I tried the 2.2.2-32-i686 version but it still doesn't work.
Vincent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried clonezilla-live-2.2.2-32-amd64, and the same utc=no problem showed up.
As VincentHK wrote, the "timezone=" boot parameter is working correctly.
The problem is that the "utc=no" boot parameter doesn't take into account that my hwclock is set to localtime instead of utc.
Your test had two variables, "utc" and "timezone". Try just changing one of them at a time to show the problem.
Booting with "timezone=America/Chicago" versus booting with "utc=no timezone=America/Chicago" produces the same time plus the difference in minutes between booting. The "utc=no" should change the time by five hours.
Or, booting without "utc=no" and with "utc=no" also produces the same time plus the difference in minutes between booting.
Last edit: rja 2014-04-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "utc=no" boot option has stopped working again, just like in
https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/141181cd/#7be2
The "utc=no timezone=America/Chicago" boot options worked with 2.1.2-43-amd64,
but do not work with versions 2.2.0-16-amd64 or later.
I could not find any test versions between those two stable versions, so I could not narrow down when these boot options stopped working any further than that. I guess I need to make backups more often, or I would have noticed this sooner.
Since nobody else has mentioned this, maybe I am the only person who uses these boot options. Of course, you get to decide if this is worth the effort to address it.
The ocs_prerun of hwclock that I used in the previous topic still works around the problem.
The "utc=no timezone=America/Chicago" boot options also worked with gparted-live-0.16.2-1b-amd64,
but fail to work with gparted-live-0.16.2-11-amd64 or later.
If you would like for me to create a bug report (or would this be a feature request) for gparted-live, then I will do so.
Thanks for the bug report.
On Clonezilla live 2.2.0 we started to use newer live-boot and live-config (version 3) from Debian. Therefore I believe it's broken, I will fix that.
Steven.
I did a test, and it looks working in Clonezilla live 2.2.2-32.
1) Boot clonezilla-live-2.2.2-32-amd64.iso, without changing any boot parameters:
root@debian:~# cat /proc/cmdline
BOOT_IMAGE=/live/vmlinuz initrd=/live/initrd.img boot=live username=user config quiet noswap edd=on nomodeset locales= keyboard-layouts= ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch=no vga=788 ip= nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=no
root@debian:~# date
Wed Apr 2 02:44:37 UTC 2014
2) Boot clonezilla-live-2.2.2-32-amd64.iso, adding "utc=no timezone=America/Chicago"
root@debian:~# cat /proc/cmdline
BOOT_IMAGE=/live/vmlinuz initrd=/live/initrd.img boot=live username=user config quiet noswap edd=on nomodeset locales= keyboard-layouts= ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch=no vga=788 ip= nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=no utc=no timezone=America/Chicago
root@debian:~# date
Tue Apr 1 21:47:17 CDT 2014
So to me it looks like working. Or maybe I am wrong?
Steven.
The utc=no option does not work for Hong Kong: "utc=no timezone=Asia/Hong_Kong" only changes the timezone code but the time is stil utc, i.e. off by 8 hours. I have to use "date -s -8hours" to correct it.
This happened in version 2.1.x.
Since I saw your discussion, I tried the 2.2.2-32-i686 version but it still doesn't work.
Vincent.
I just tried clonezilla-live-2.2.2-32-amd64, and the same utc=no problem showed up.
As VincentHK wrote, the "timezone=" boot parameter is working correctly.
The problem is that the "utc=no" boot parameter doesn't take into account that my hwclock is set to localtime instead of utc.
Your test had two variables, "utc" and "timezone". Try just changing one of them at a time to show the problem.
Booting with "timezone=America/Chicago" versus booting with "utc=no timezone=America/Chicago" produces the same time plus the difference in minutes between booting. The "utc=no" should change the time by five hours.
Or, booting without "utc=no" and with "utc=no" also produces the same time plus the difference in minutes between booting.
Last edit: rja 2014-04-03
Could you give Clonezilla live 2.2.2-35 a try?
From my test, "utc=no" should work.
Please let me know the results.
Thanks.
Steven.
2.2.2-35-amd64 fixes the "utc=no" problem.
Thanks for the quick update.
Cool! Thanks for the confirmation.
Steven.
clonezilla-live-20140708-trusty-i386.zip
It doesn't work for me. Tried:
timezone=Europe/Andorra
utc=no timezone=Europe/Andorra
At shell, date command shows correct localtime. But when I create an image allways has UTC time.
Here is my custom menu option:
append initrd=/live/initrd.img boot=live username=user hostname=trusty config quiet union=overlayfs noswap edd=on nomodeset noeject timezone=Europe/Andorra locales=ca_ES.UTF-8 keyboard-layouts=es ocs_prerun="mount /dev/sdb2 /home/partimag" ocs_live_run="ocs-sr -q2 -j2 -z1p -i 2000 -fsck-src-part -p poweroff savedisk ImatgeBellera sda" ocs_live_extra_param="" ocs_live_batch=no video=uvesafb:mode_option=800x600-16 ip= nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=no
Could you add
ocs_prerun1="date" ocs_prerun2="sleep 10"
to see the output of date and compare that in the command line?
Steven.