From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Tom=C3=A1=C5=A1_?= =?UTF-8?Q?=C4=8Cech?= Subject: bug#20024: grub store is not copied to target system Date: Mon, 9 Mar 2015 21:04:21 +0100 Message-ID: <20150309200421.GA1222@venom> References: <20150307000159.GA1292@venom> <87lhj7nor2.fsf@gnu.org> <20150308215719.GB22135@venom> <8761aatx2m.fsf@gnu.org> <20150309103424.GB30937@crashnator.suse.cz> <877fuqkswn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YV3vG-0004i3-CM for bug-guix@gnu.org; Mon, 09 Mar 2015 16:05:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YV3vC-0002yM-AD for bug-guix@gnu.org; Mon, 09 Mar 2015 16:05:06 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:42387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YV3vC-0002y9-7V for bug-guix@gnu.org; Mon, 09 Mar 2015 16:05:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YV3vB-0004uT-Pj for bug-guix@gnu.org; Mon, 09 Mar 2015 16:05:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <877fuqkswn.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 20024@debbugs.gnu.org --9amGYk9869ThD9tj Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 09, 2015 at 06:00:24PM +0100, Ludovic Court=C3=A8s wrote: >Tomas Cech skribis: > >> I'm afraid that I don't understand the relation between `guix system ini= t' and >> `guix system reconfigure' you insist on. My understanding was, that `guix >> system init' will create new system in subdirectory as it is described in >> manual (6.1.4 Proceeding with the Installation). > >=E2=80=98guix system init=E2=80=99 initializes a GuixSD root file system. = It is >typically used from the USB installation image. > >Conversely, =E2=80=98guix system reconfigure=E2=80=99 is used to reconfigu= re an already >installed GuixSD system, with the untold assumption that the root >partition remains the same (which is reasonable, IMO.) Thank you for your verification. It means I understand it correctly. I reread whole bug again and I couldn't find the reason you even consider me using `guix system reconfigure'. My assumption is that you didn't expect me to have Guix on my Gentoo. Guix is (as you have to know the best) non-intrusive for OS so I have standard Gentoo installation and Guix built from GIT and installed to system. Binaries are in /gnu/store so it is not colliding with the rest of my system. I'll keep that in mind to mention it better in future bugs. Sorry for confusion. TL;DR I run `guix system init' from Gentoo to separate partition to _init_ root filesystem and after reboot to boot into GuixSD. >>>Seriously, I don=E2=80=99t think we=E2=80=99d want it to automagically m= igrate the >>>store. >> >> How does it differ from building new VM image? > >=E2=80=98init=E2=80=99 is similar to building a new VM image; =E2=80=98rec= onfigure=E2=80=99 is not. > >Specifically, =E2=80=98reconfigure=E2=80=99 changes things to have immedia= te effect, >such as switching /run/current-system/ to the new (reconfigured) system. >Eventually it will also offer to restart dmd services whose definition >have changed. I hope it is now obvious that I didn't `reconfigure', but `init'. >>>Maybe it could check whether the root partition in the OS declaration is >>>the same as the one that holds the current store, but I=E2=80=99m not su= re if >>>that can be done reliably. Thoughts? >> >> Again, I'm afraid we misunderstood each other. >> >> One thing is that you can expose it to configuration and let user config= ure it >> correctly. I was already thinking that I'm wasting disk space with two c= opies >> of /gnu/store on my computer (on Gentoo and on GuixSD). > >Oh, I see. So you had installed Guix atop Gentoo, and from there you >wanted to install GuixSD while (1) keeping Gentoo, and (2) not >rebuilding a new store, right? Yes. >The solution to is to run, from your Gentoo system: > > # guix system init config.scm / > >The =E2=80=9C/=E2=80=9D here means that you keep the same root file system= , and thus the >same store. > >If you want to still be able to boot into Gentoo, you need to specify >GRUB menu entries in config.scm, like > > (define gentoo-entry > (menu-entry > (label "Gentoo") > (linux "/whatever/bzImage") > (linux-arguments '("answer=3D42")) > (initrd "/something/initrd.gz"))) > > (operating-system > ;; ... > (bootloader (grub-configuration > (device "/dev/sda") > (menu-entries (list gentoo-entry))))) I'm aware of this feature, I'm preparing bug report for that :) >But! Beware that GuixSD wants to own /etc. So in practice, when you >boot GuixSD, it may override most of the files in there with its own (it >might also bork of some of its assumptions do not hold, like if Gentoo >left files in /etc that it doesn=E2=80=99t expect to see.) So the next ti= me you >boot into Gentoo, Gentoo will basically be somewhat broken. > >IOW, using =E2=80=98guix system init=E2=80=99 on the current root should b= e thought of >as a one-way transition. It=E2=80=99s not documented because it=E2=80=99s= brittle and >it=E2=80=99s most likely not what you want. Yes, that would be way to hell. So the better solution can be putting /gnu on separate partition and share it among the systems like you can do for /home, /boot etc. >Does that better answer your questions? Yes and no. I really appreciate your patience here but we diverged =66rom original reported issue. Let me the whole bug rephrase into single simple question: Shouldn't `grub' be in `%base-packages'? Thanks and best regards, S_W --9amGYk9869ThD9tj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlT9/MUACgkQ37XrCapiVCPr1wCeOSCrZanKDkgwZa28++nz8c9B Y+sAoNGOnGDfQdBGWi5Axp+YxqnZTjW8 =Kwj1 -----END PGP SIGNATURE----- --9amGYk9869ThD9tj--