unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: swedebugia@riseup.net
To: 荒井吉則 <kumagusu08@gmail.com>
Cc: Help-Guix@gnu.org,
	Help-Guix <help-guix-bounces+swedebugia=riseup.net@gnu.org>
Subject: Re: My first impression for GuixSD
Date: Sat, 05 Jan 2019 03:14:36 -0800	[thread overview]
Message-ID: <f3e1d99d781865be1ceb090c411e42cb@riseup.net> (raw)
In-Reply-To: <CAH2wgjhkVS02v5d4j1Rn-R+i-jaaLe++eAhne5H2RiY2Qgmc+Q@mail.gmail.com>

Hi :)

On 2019-01-05 11:48, 荒井吉則 wrote:
> I'm installed GuixSD using desktop config.
> Gnome/Xfce desktop is garbled cause of missing Japanese fonts. 
> And missing /etc/grub.d and grub commands.  I edited
> /boot/grub/grub.cfg directly to be enable multiboot.
> 
> Otherwise is OK.  Thank you.

Thanks a lot for your feedback. 

Would you be willing to share your config.scm so we can help debug your
issues?

My knowledge of special fonts in guix is very low but others might have
succeded with getting japanese fonts to work by tweaking their
config.scm.

Regarding multiboot, I tried myself some months ago and it worked fine
after tweaking of my config.scm. Did you specify a custom
bootloader-configuration? (see info guix --search menu-entries).

Here is the example from the manual:
Should you want to list additional boot menu entries via the
menu-entries field above, you will need to create them with the
menu-entry form. For example, imagine you want to be able to boot
another distro (hard to imagine!), you can define a menu entry along
these lines:

(menu-entry
  (label "The Other Distro")
  (linux "/boot/old/vmlinux-2.6.32")
  (linux-arguments '("root=/dev/sda2"))
  (initrd "/boot/old/initrd"))

-- 
Cheers 
Swedebugia

  reply	other threads:[~2019-01-05 11:14 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 [this message]
2019-01-06  4:08   ` 荒井吉則
2019-01-06  9:00     ` Ricardo Wurmus
2019-01-06 10:53       ` 荒井吉則
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=f3e1d99d781865be1ceb090c411e42cb@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=Help-Guix@gnu.org \
    --cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
    --cc=kumagusu08@gmail.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.
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).