unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Why does setting a language in Grub take 1.5 minutes?
Date: Tue, 17 May 2022 06:45:39 -0500	[thread overview]
Message-ID: <871qwsidr0.fsf@gmail.com> (raw)
In-Reply-To: <87czgdi46r.fsf@laura> (Olivier Dion's message of "Mon, 16 May 2022 16:59:56 -0400")

Olivier Dion <olivier.dion@polymtl.ca> writes:

> On Sun, 15 May 2022, Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:
>> At some point, after a long time with no problems, my system began
>> taking an unreasonably long time to boot. I only reboot my system
>> ~1/week for updates, so I never took the time to debug the problem,
>> and therefore, I couldn't really connect the issue with any changes
>> that either I or Guix had made.
>
> I've come across this
> https://lists.gnu.org/archive/html/grub-devel/2022-05/msg00005.html
> today. If it is the problem, perhaps GCing your old kernels would make
> the boot faster.

Thank you for responding.

I think this only impacts running `grub-mkconfig` and not booting, doesn't it? Aside from that, the echo statements I gave suggest that the issue is with setting the language.

Still, I removed some old generations of my system. Things went a little faster, but I'm guessing that's probably a side-effect of shrinking my /gnu/store path.

Thank you for the suggestion.
-- 
Katherine


      reply	other threads:[~2022-05-17 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 23:06 Why does setting a language in Grub take 1.5 minutes? Katherine Cox-Buday
2022-05-16  0:04 ` raingloom
2022-05-16 15:15   ` Katherine Cox-Buday
2022-05-16 20:59 ` Olivier Dion via
2022-05-17 11:45   ` Katherine Cox-Buday [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=871qwsidr0.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).