From: 荒井吉則 <kumagusu08@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Help-Guix@gnu.org,
Help-Guix <help-guix-bounces+swedebugia=riseup.net@gnu.org>
Subject: Re: My first impression for GuixSD
Date: Sun, 6 Jan 2019 19:53:21 +0900 [thread overview]
Message-ID: <CAH2wgjjns2PSWQYo-fEQNpUVXTxgq2s-imXMC8GBN=XV+6Bk+g@mail.gmail.com> (raw)
In-Reply-To: <874lamrwii.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
Ok, thanks.
2019年1月6日(日) 18:00 Ricardo Wurmus <rekado@elephly.net>:
>
> 荒井吉則 <kumagusu08@gmail.com> writes:
>
> > My knowladge of guixsd configuration is not enogh to make my own
> > configuration yet. but my expectation is that I could ajdust system
> > configuration according to ordinal way of postinstallation.
> >
> > For instance, locale setting at config.scm is to install additional fonts
> > according to locale or config of multiboot is that I could edit
> > /etc/grub.d/40_custom for postinstallation.
>
> This won’t work on a Guix system, because it does not generally consult
> files in /etc. Most system configuration files are generated when
> running “guix system init” (or “guix system reconfigure”) using the
> information provided in the system configuration file.
>
> --
> Ricardo
>
>
[-- Attachment #2: Type: text/html, Size: 1288 bytes --]
next prev parent reply other threads:[~2019-01-06 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 10:48 My first impression for GuixSD 荒井吉則
2019-01-05 11:14 ` swedebugia
2019-01-06 4:08 ` 荒井吉則
2019-01-06 9:00 ` Ricardo Wurmus
2019-01-06 10:53 ` 荒井吉則 [this message]
2019-01-06 21:14 ` Chris Marusich
2019-01-07 0:30 ` 荒井吉則
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='CAH2wgjjns2PSWQYo-fEQNpUVXTxgq2s-imXMC8GBN=XV+6Bk+g@mail.gmail.com' \
--to=kumagusu08@gmail.com \
--cc=Help-Guix@gnu.org \
--cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
--cc=rekado@elephly.net \
/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).