From: nightowl <nightowl@members.fsf.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Guix Pull SSL Cert Invalid Old PC
Date: Mon, 23 Sep 2019 21:36:34 -0500 [thread overview]
Message-ID: <b796e764e242833944054793403c86be@posteo.net> (raw)
In-Reply-To: <87zhiv1w4h.fsf@nckx>
Thanks,
That works! I am really glad to have my old PC back up again. Going to
have more fun with Guix now and see what works well on an old machine.
All the best
On 2019-09-22 11:20 pm, Tobias Geerinckx-Rice wrote:
> Greetings, fellow night owl,
>
> nightowl 写道：
>> Why would the old computer say the certificate is invalid while two of
>> my newer computers say it is ok?
>
> That sounds like your old computer's system clock isn't set to the
> correct time. You can check it with ‘date’, and change it with ‘date
> --set="…"’.
>
> If your clock was off, and you do make changes, it may be necessary to
> save them to the hardware clock (so they survive reboots) with
> ‘hwclock --systohc’. I'm not sure whether that's done automatically
> nowadays.
>
> Kind regards,
>
> T G-R
prev parent reply other threads:[~2019-09-24 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 3:12 Guix Pull SSL Cert Invalid Old PC nightowl
2019-09-23 4:20 ` Tobias Geerinckx-Rice
2019-09-24 2:36 ` nightowl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b796e764e242833944054793403c86be@posteo.net \
--to=nightowl@members.fsf.org \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).