From: sirgazil <sirgazil@zoho.com>
To: "Leo Famulari" <leo@famulari.name>
Cc: "christophe.pisteur" <christophe.pisteur@posteo.net>,
"help-guix" <help-guix@gnu.org>
Subject: Re: guix system boot time
Date: Sat, 02 May 2020 21:06:03 +0000 [thread overview]
Message-ID: <171d735ddcb.da4398a74605.5227154174590577874@zoho.com> (raw)
In-Reply-To: <20200502203233.GA29000@jasmine.lan>
---- On Sun, 03 May 2020 03:32:33 +0000 Leo Famulari <leo@famulari.name> wrote ----
> Welcome and thanks for trying Guix!
>
> On Sat, May 02, 2020 at 10:09:10PM +0200, christophe.pisteur@posteo.net wrote:
> > The only small problem is the system startup, which takes a long time (3
> > minutes from grub to GDM user login). It is probably due to a problem with
> > the system clock (I get somes warnings: ntpd clock unsynchronized). I don't
> > know where the boot log is on guix system and I don't know if it has to do
> > with GNU bug report logs - #22274.
>
> I have Guix on an X200 (basically the same as yours) and I can confirm,
> it's slow.
>
> I don't think it's related to ntpd. I see the same warnings but the
> system displays the login prompt before they are resolved.
>
> Generally, the issue is that the Shepherd is not optimized to the degree
> that systemd is, and that these old Thinkpads (sold in 2008) are really
> slow by contemporary standards.
>
> One of the early selling points of systemd was that it reduced boot
> times from being measured in minutes, which used to be typical, to
> seconds. Now systemd is the standard, and minutes-long booting seems
> incredibly and unreasonably slow.
>
>
Guix System: Very long, scary boot time: http://issues.guix.gnu.org/issue/39089
next prev parent reply other threads:[~2020-05-02 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 20:09 guix system boot time christophe.pisteur
2020-05-02 20:32 ` Leo Famulari
2020-05-02 21:06 ` sirgazil [this message]
2020-05-02 21:48 ` christophe.pisteur
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=171d735ddcb.da4398a74605.5227154174590577874@zoho.com \
--to=sirgazil@zoho.com \
--cc=christophe.pisteur@posteo.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).