From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: boot the Hurd with Guix Date: Mon, 13 Nov 2017 11:42:01 +0100 Message-ID: <87fu9iv4sm.fsf@gnu.org> References: <20171112210310.80B0E4E0031@mta-1.openmailbox.og> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20171112210310.80B0E4E0031@mta-1.openmailbox.og> (rennes@openmailbox.org's message of "Sun, 12 Nov 2017 21:03:07 -0000") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-hurd-bounces+gnu-bug-hurd=m.gmane.org@gnu.org Sender: "Bug-hurd" To: rennes@openmailbox.org Cc: guix-devel , bug-hurd@gnu.org List-Id: guix-devel.gnu.org Hi rennes, (Something went wrong with your message headers.) rennes@openmailbox.org skribis: >>> Finally I was able to start the Hurd with the binaries generated with t= he guix package manager. >>=20 >> Woohoo! Does that mean you were able to run packages cross-compiled >> with Guix, or packages built natively with Guix? >>=20 > > the packages were built on top of Debian/Hurd. At this moment I am copyin= g everything that is compiled into /gnu/store to the image,=20 > and then create symbolic links so that grub, Mach and Hurd can locate the= binaries. Neat. >>> At the moment the image of Hurd I have built it manually and does not y= et have any functionality like GuixSD / Linux. >>=20 >> =E2=80=A6 or did you build a VM image of GNU/Hurd? >>=20 > > Yes, I have built the VM image according to your notes [1]. Oh, awesome! I can=E2=80=99t wait to fiddle with this image! Please make sure to send us a recap of what needs to be done in Guix proper to make this happen. We=E2=80=99ll think about ways to incorporate = those changes. Congrats! Ludo=E2=80=99. PS: guix-daemon no longer depends on =E2=80=98lsof=E2=80=99, but it still d= epends on /proc.