On Sun 14 Oct 2018 at 21:29:57 +0300, Reco wrote:
> On Sun, Oct 14, 2018 at 07:18:12PM +0100, Brian wrote:
>
> > At present there is an effort to update documentation for buster. Get
> > your bug report in. Don't delay!
>
> I'll consider your suggestion.
Striking. Iron. Hot.
#911020.
--
Bria
Hi.
On Sun, Oct 14, 2018 at 07:18:12PM +0100, Brian wrote:
> On Sun 14 Oct 2018 at 17:21:43 +0300, Reco wrote:
>
> > Hi.
> >
> > On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote:
> > > On 10/14/18, to...@tuxteam.de wrote:
> > > > On Sat, Oct 13, 2018 at 07:11:07AM +0
On Sun 14 Oct 2018 at 17:21:43 +0300, Reco wrote:
> Hi.
>
> On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote:
> > On 10/14/18, to...@tuxteam.de wrote:
> > > On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote:
> > >> Thank tomas!
> > >>
> > >> i run "cat /etc/adjtime"
Hi.
On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote:
> On 10/14/18, to...@tuxteam.de wrote:
> > On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote:
> >> Thank tomas!
> >>
> >> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch
> >> /etc/adjtime does
On 10/14/18, to...@tuxteam.de wrote:
> On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote:
>> Thank tomas!
>>
>> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch
>> /etc/adjtime doesn't seem to exist
>
> I see. Perhaps this is the root of the problem. On the other
> hand,
On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote:
> Thank tomas!
>
> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch
> /etc/adjtime doesn't seem to exist
I see. Perhaps this is the root of the problem. On the other
hand, perhaps, systemd is taking care of time in str
On Sat 13 Oct 2018 at 19:51:07 (+), Curt wrote:
> On 2018-10-13, Brian wrote:
> > On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote:
> >> On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote:
> >> > Thank Teemu Likonen!
> >> > You are right. My stretch and jessie think differently ab
On 2018-10-13, Brian wrote:
> On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote:
>
>> On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote:
>> > Thank Teemu Likonen!
>> > You are right. My stretch and jessie think differently about hardware
>> > clock.
>> > i run "timedatectl set-local-
On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote:
> On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote:
> > Thank Teemu Likonen!
> > You are right. My stretch and jessie think differently about hardware clock.
> > i run "timedatectl set-local-rtc 1", it should be ok for both now.
> >
On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote:
> Thank Teemu Likonen!
> You are right. My stretch and jessie think differently about hardware clock.
> i run "timedatectl set-local-rtc 1", it should be ok for both now.
> though there's warning, i think it's ok
Because China doesn't use Da
Long Wind [2018-10-12 21:59:40Z] wrote:
> jessie and stretch are installed on same PCtime of jessie is wrong:
> Fri Oct 12 21:51:05 CST 2018then i reboot and enter stretch time of
> stretch is right: Sat Oct 13 05:55:30 CST 2018 tzdata of both are
> reconfig to same place
As others have pointed o
On Fri, Oct 12, 2018 at 10:32:16PM +, Long Wind wrote:
> Thanks! How could I find out if debian thinks bios clock is set to local
> time or universal time?
This is one way to do it:
tomas@trotzki:~$ cat /etc/adjtime
0.00 1539378883 0.00
1539378883
UTC
The last line will te
On Fri, Oct 12, 2018 at 6:32 PM Long Wind wrote:
> Thanks! How could I find out if debian thinks bios clock is set to local
> time or universal time?
>
I looked it up. Even though Arch Linux isn't Debian, I respect them, for
giving good, technical details about Linux Concepts. Here's a Link:
On Fri, Oct 12, 2018 at 6:01 PM Long Wind wrote:
> jessie and stretch are installed on same PC
> time of jessie is wrong: Fri Oct 12 21:51:05 CST 2018
> then i reboot and enter stretch
> time of stretch is right: Sat Oct 13 05:55:30 CST 2018
>
> tzdata of both are reconfig to same place
>
Is it
14 matches
Mail list logo