From: Reza Alizadeh Majd <r.majd@pantherx.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Hide boot process logs
Date: Tue, 18 Aug 2020 22:12:15 +0430 [thread overview]
Message-ID: <20200818221215.2e32ac1e@panther-arch.localdomain> (raw)
In-Reply-To: <87y2mceya2.fsf@nckx>
Hi Tobias!
Thanks for your response.
On Tue, 18 Aug 2020 18:04:05 +0200
Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Hi Reza!
>
> Reza Alizadeh Majd 写道:
> > I want to hide the boot process logs in Guix, having a quick
> > search I
> > found that I can use following options in grub configuration
> > file:
> >
> >
> > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
>
> Forget this line. No part of it makes sense on Guix (except
> ‘quiet’, which is handled by the kernel itself, and see below for
> that).
>
> GRUB_CMDLINE_LINUX_DEFAULT (and similar-looking variables) is used
> only by the ‘update-grub’ utility on some distributions that uses
> a bash configuration file to configure a bash script that creates
> the final (bash-like) grub.cfg.
so as I understand, `update-grub` utility generate entries in a way to
perform a quiet boot using `GRUB_CMDLINE_LINUX_DEFAULT` parameter.
do you think if it's possible to perform these changes manually to menu
entries?
I also find that we can redirect kernel logs to a separated TTY using
`GRUB_CMDLINE_LINUX="console=tty...`. I assume this parameter is also
processed by `update-grub` utility. is it possible to perform same
action using `kernel-arguments` or some other modification in menu
entries?
--
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/
prev parent reply other threads:[~2020-08-18 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:56 Hide boot process logs Reza Alizadeh Majd
2020-08-18 16:04 ` Tobias Geerinckx-Rice
2020-08-18 16:54 ` John Soo
2020-08-18 17:51 ` Reza Alizadeh Majd
2020-08-18 17:42 ` Reza Alizadeh Majd [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=20200818221215.2e32ac1e@panther-arch.localdomain \
--to=r.majd@pantherx.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).