From: Tomas Cech <sleep_walker@suse.cz>
To: guix-devel@gnu.org
Subject: (unknown)
Date: Wed, 03 Dec 2014 19:02:00 +0100 [thread overview]
Message-ID: <87a9347gtj.wl%sleep_walker@suse.cz> (raw)
Hello,
I'd like to share with you some experiences with using Guix.
I tried to install Guix as alternative OS to my Gentoo and openSUSE
installations to give a try. I tried unsupported scenario -
installation on LVM volume and separate /boot partition until I was
told it is unsupported. Separate boot wasn't hard as I had to just
copy generated files so they are loaded. But eventually I gave up
preparing it manually or automating it and I had rather put another
Grub in the same partition and set up chainloading.
I met then two problems:
1] if you set device to partition (and not to disk) in your grub-configuration like this:
(bootloader (grub-configuration
(device "/dev/sda4")))
`guix system init' will fail on grub installation. By default Grub
tries to fit in the beginning of partition and fails if it can't fit
in. I asked about this behaviour on Grub mailing list and it seems
that there are two options:
a] add `--force' to command line and use block list for keeping information about position of Grub's core.img
b] use filesystem which allows embedding - BtrFS or ZFS
I verified both options (a] and then b] with BtrFS) and it no longer fails.
But,
ad a] - I don't feel safe passing `--force' to grub-install every
time. So if installation fails on this point and you'd like to use
your FS anyway, you can pass `--no-grub' to `guix system init' and
then rung grub-install manually.
ad b] - I don't feel safe using still experimental BtrFS.
2] current Grub version in Guix during boots generated this error:
error: symbol 'grub_term_highlight_color' not found
and started rescue shell.
It seems to be a bit mystic bug:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977
I used my Gentoo's version of Grub to fix it and then it worked.
I'm also interested in running chroot in Guix. This is something I
like about all Linux distribution I use - I can run Linux and at the
same time I prepare another Linux root filesystem for use. It seems
that chrooting into Guix may be tricky.
I prepared this script to be placed somewhere into Guix:
----------%<---------
#!/run/current-system/profile/bin/bash
export LIBRARY_PATH=LIBRARY_PATH=/root/.guix-profile/lib
export CPATH=/root/.guix-profile/include
export PATH=/run/setuid-programs:/run/current-system/profile/sbin:/root/.guix-profile/bin:/run/current-system/profile/bin
export INFOPATH=/root/.guix-profile/share/info:/run/current-system/profile/share/info
exec bash -i
----------%<--------
for i in dev proc sys; do mount -R /$i /guix_mountpoint/$i; done
chroot /guix_mountpoint/ /helper_script.sh
Ludovic said that `guix packages --search-paths' should generate similar path configuration so it may be the right way, but it didn't work for me.
And last thing I wanted to mention, you have kind community around Guix and Guile. It's really motivating!
Best regards,
Tomas Cech
Sleep_Walker
next reply other threads:[~2014-12-03 18:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 18:02 Tomas Cech [this message]
2014-12-04 23:04 ` none Ludovic Courtès
2014-12-05 8:35 ` none Tomas Cech
2014-12-06 14:06 ` none Ludovic Courtès
2015-03-10 11:59 ` bug#20071: none Tomáš Čech
-- strict thread matches above, loose matches on Subject: below --
2020-04-13 9:53 (unknown) elaexuotee
2019-05-02 16:19 (unknown) znavko
2018-04-27 15:05 (unknown), Catonano
2017-01-02 19:22 (unknown), manolis837
2016-12-19 17:50 (unknown), John Darrington
2016-12-05 18:20 (unknown), ng0
2016-10-06 6:16 (unknown), Leo Famulari
2016-07-21 1:39 (unknown) Unknown, Pjotr Prins
2016-07-20 3:46 (unknown) Pjotr Prins
2016-06-30 0:27 (unknown), ng0
2016-06-08 12:55 (unknown), Ben Woodcroft
2016-05-30 19:24 [PATCH] gnu: Add py3status Tomáš Čech
2016-05-30 20:01 ` (unknown), Tomáš Čech
2015-09-15 14:35 (unknown) Pjotr Prins
2015-07-13 13:01 (unknown) Pjotr Prins
2015-07-08 14:30 [PATCH 2/2] gnu: Update pumpa to 0.9.1 Mathieu Lirzin
2015-07-08 14:39 ` (unknown), Claes Wallin (韋嘉誠)
2015-03-25 22:49 (unknown), Tomáš Čech
2014-02-11 22:17 Gnunet-0.10.0 recipe Sree Harsha Totakura
2014-02-12 15:15 ` (unknown), Sree Harsha Totakura
2014-02-04 15:12 (unknown), John Darrington
2014-01-26 7:38 [PATCH 3/3] gnu: Add octave and dependencies John Darrington
2014-01-26 9:09 ` (unknown), John Darrington
2014-01-25 7:00 [PATCH 2/2] gnu: fltk: New module John Darrington
2014-01-25 8:27 ` (unknown), John Darrington
2014-01-23 13:30 [PATCH] Doc: Introduction: rewrite for style and clarity Ludovic Courtès
2014-01-23 18:00 ` (unknown), Alex Sassmannshausen
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=87a9347gtj.wl%sleep_walker@suse.cz \
--to=sleep_walker@suse.cz \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).