On 25/03/2023 10:39, Albretch Mueller wrote:
You can't physically alter a DVD[+|-]R once it is burned ...
Do you customize images to change preferences, e.g. to make OS aware
that hardware clock is set to local time? If you do not than OS almost
certainly assumes that system time is in
On 25/03/2023 10:39, Albretch Mueller wrote:
On 3/25/23, Max Nikulin wrote:
- Both Debian and Windows installed on the hard drive ...
Thank you for the steps and the logical elucidations that may
certainly help someone else, but I can't do that "because" all
electronic devices which I use
David Wright composed on 2023-03-24 23:20 (UTC-0500):
> BTW I've only really trusted reading or setting the RTC by means of
> the CMOS screens, and treat it as a one-time only process (upon
> acquisition), assuming the coin-cell battery never needs replacing.
Lucky you. I can only dream of going
On Fri 24 Mar 2023 at 19:10:49 (-0400), Stefan Monnier wrote:
> > That works great for the Live OS, but not for the fixed-disk OS. If
> > the Live OS sets the HW clock to local upon shutdown, but the fixed-disk
> > OS expects the HW clock to be UTC, then the fixed-disk OS is wrong
> > every time
On Fri 24 Mar 2023 at 17:13:31 (+), Albretch Mueller wrote:
> On 3/24/23, Andy Smith wrote:
> > As already pointed out, the hardware clock is used in very limited
> > ways and is not the same thing as the system clock, so your result
> > is as expected.
> > What are you actually trying to do?
On 3/25/23, Max Nikulin wrote:
> - Both Debian and Windows installed on the hard drive ...
Thank you for the steps and the logical elucidations that may
certainly help someone else, but I can't do that "because" all
electronic devices which I use are being kept.
You can't physically alter a
On 25/03/2023 07:07, Albretch Mueller wrote:
I am using right now a DELL laptop which had Windows 11 installed but
I expect that the following should work smoothly enough:
- Hardware clock is in UTC
- Both Debian and Windows installed on the hard drive are configured to
your local time zone
I am using right now a DELL laptop which had Windows 11 installed but
started to give me sh!t which I totally ignored and started to use my
good old friend Debian in order to "keep moving".
By the way, after a while as if for a magical reason the hw time
changed and now it is showing to me the
> That works great for the Live OS, but not for the fixed-disk OS. If
> the Live OS sets the HW clock to local upon shutdown, but the fixed-disk
> OS expects the HW clock to be UTC, then the fixed-disk OS is wrong
> every time it boots after the Live OS.
AFAIK the Linux kernel is pretty careful
On Fri, Mar 24, 2023 at 05:51:30PM -0400, Stefan Monnier wrote:
> > If your policy choice ends up being "set HW clock to local", then you
> > also have to make sure the correct time zone is set on each operating
> > system, each time it boots. I have no idea how one does that on Debian
> > Live,
> If your policy choice ends up being "set HW clock to local", then you
> also have to make sure the correct time zone is set on each operating
> system, each time it boots. I have no idea how one does that on Debian
> Live, since I've never used Debian Live. So, I can hope for your sake
> that
On Fri, Mar 24, 2023 at 05:13:31PM +, Albretch Mueller wrote:
> I should have pointed out that I always go into exposed mode (use the
> Internet) with a live DVD. My laptop was always 6 hours ahead and now
> that they changed to summer time, it is 5 hours ahead.
So, you have at least two
On 3/24/23, Andy Smith wrote:
> As already pointed out, the hardware clock is used in very limited
> ways and is not the same thing as the system clock, so your result
> is as expected.
> What are you actually trying to do?
>
> What "time zone issues" do you refer to?
I should have pointed out
Hello,
On Thu, Mar 23, 2023 at 09:41:40PM +, Albretch Mueller wrote:
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time
On Thu 23 Mar 2023 at 21:41:40 (+), Albretch Mueller wrote:
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time setting?
On 3/23/23, Cindy Sue Causey wrote:
> On 3/23/23, Albretch Mueller wrote:
>> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
>> the time 5 hours. hwclock tells me it worked fine but the terminal
>> windows opened before and after running hwclock still give me the
>> "old"
On 3/23/23, Albretch Mueller wrote:
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time setting?
>
> _HRS_PM=-5
>
> ###
> #
>
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time setting?
The hardware clock is an "external" device which the Linux kernel
I am using this (yes, visually cr@ppy ;-)) code snippet to set back
the time 5 hours. hwclock tells me it worked fine but the terminal
windows opened before and after running hwclock still give me the
"old" time setting?
_HRS_PM=-5
###
#
19 matches
Mail list logo
