From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: none Date: Fri, 05 Dec 2014 00:04:23 +0100 Message-ID: <87wq67qao8.fsf@gnu.org> References: <87a9347gtj.wl%sleep_walker@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwfRl-0008GG-Te for guix-devel@gnu.org; Thu, 04 Dec 2014 18:04:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XwfRh-0002EF-Nw for guix-devel@gnu.org; Thu, 04 Dec 2014 18:04:29 -0500 Received: from hera.aquilenet.fr ([2a01:474::1]:48551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwfRh-0002Du-86 for guix-devel@gnu.org; Thu, 04 Dec 2014 18:04:25 -0500 In-Reply-To: <87a9347gtj.wl%sleep_walker@suse.cz> (Tomas Cech's message of "Wed, 03 Dec 2014 19:02:00 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Tomas Cech Cc: guix-devel@gnu.org Tomas Cech skribis: > 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. OK, but there=E2=80=99s still an open bug on that topic. :-) http://bugs.gnu.org/19220 > 1] if you set device to partition (and not to disk) in your grub-configur= ation like this: > > (bootloader (grub-configuration > (device "/dev/sda4"))) Why would you want to use a partition and not a disk? I didn=E2=80=99t know this was even possible. > `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 informa= tion 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 fail= s. > > 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. OK. I think the conclusion for Guix is to leave the defaults unchanged. Perhaps we could add a =E2=80=98force?=E2=80=99 field to the =E2=80=98grub-= configuration=E2=80=99 data type to allow those who know what they doing to get the effect of =E2=80=98--force=E2=80=99. WDYT? > 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 Strange. I haven=E2=80=99t experienced it. Sounds like a .mod wasn=E2=80= =99t found or something like that? That could be a bug related to separate /boot. > 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=3DLIBRARY_PATH=3D/root/.guix-profile/lib > export CPATH=3D/root/.guix-profile/include > export PATH=3D/run/setuid-programs:/run/current-system/profile/sbin:/root= /.guix-profile/bin:/run/current-system/profile/bin > export INFOPATH=3D/root/.guix-profile/share/info:/run/current-system/prof= ile/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 I suppose this works, right? > 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. I realize =E2=80=98guix package --search-paths=E2=80=99 wouldn=E2=80=99t su= ffice here. You may want to source /etc/profile from within the chroot. > And last thing I wanted to mention, you have kind community around Guix a= nd Guile. It's really motivating! Thanks for your feedback and for the kind words! Ludo=E2=80=99.