From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: sirgazil@zoho.com, 39089@debbugs.gnu.org
Subject: bug#39089: Guix System: Very long, scary boot time
Date: Fri, 17 Jan 2020 22:39:06 +0100 [thread overview]
Message-ID: <87lfq5yd8l.fsf@gnu.org> (raw)
In-Reply-To: <20200111160505.77327dc3@scratchpost.org> (Danny Milosavljevic's message of "Sat, 11 Jan 2020 16:05:31 +0100")
Hello!
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I think it's our job as a distribution to integrate the components properly into
> the system so that confusing stuff like that doesn't happen.
>
> As a first step, we could just not start a getty on tty1 when gdm is configured
> to start (see tty1 in %base-services in (gnu services base)). Then the thing
> above wouldn't appear.
>
> The usual fix a lot of other distributions (and BIOSes) have is to display a
> splash screen on top.
I think that would be the better fix: add the splash screen thing (I
forgot the name) to ‘%desktop-services’, but keep functional TTYs.
> Because of long boot times (15 s is ALSO too long) I almost never reboot
Heh same here.
We should do some profiling with “bootchart” I think it’s called. I’m
sure systemd does a better job that the Shepherd, in particular by
starting more things on demand and doing others in parallel. We’ll get there.
> I've tried booting Guix now and I took note of the following points in time:
>
> t = 0 s: I press the power button
> t = 8 s: Grub asks for my system password
> t = 45 s: Console login prompt appears
> t = 55 s: GDM login prompt appears
That’s roughly what I get on my laptop. (Note: Guix cannot be blamed
for what happens until the kernel has booted. :-))
Ludo’.
next prev parent reply other threads:[~2020-01-17 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 14:36 bug#39089: Guix System: Very long, scary boot time sirgazil via Bug reports for GNU Guix
2020-01-11 15:05 ` Danny Milosavljevic
2020-01-11 22:54 ` sirgazil via Bug reports for GNU Guix
2020-01-17 21:39 ` Ludovic Courtès [this message]
2020-05-03 17:15 ` Ricardo Wurmus
2020-05-03 17:18 ` Ricardo Wurmus
2020-01-11 15:07 ` sirgazil via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfq5yd8l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39089@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=sirgazil@zoho.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.