From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: create a symlink Date: Sat, 9 Mar 2019 09:22:14 +0100 Message-ID: <20190309092214.2cef348d@scratchpost.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Pfb1Wz3E+cCk0RgA7at7y0x"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54577) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2XFS-0000Rg-OO for guix-devel@gnu.org; Sat, 09 Mar 2019 03:22:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h2XFR-0008MV-RU for guix-devel@gnu.org; Sat, 09 Mar 2019 03:22:26 -0500 Received: from dd26836.kasserver.com ([85.13.145.193]:49710) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h2XFR-0008HU-Ji for guix-devel@gnu.org; Sat, 09 Mar 2019 03:22:25 -0500 In-Reply-To: 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" To: Rene Cc: guix-devel@gnu.org --Sig_/Pfb1Wz3E+cCk0RgA7at7y0x Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Rene, On Fri, 08 Mar 2019 15:13:13 -0600 Rene wrote: > Danny Milosavljevic writes: >=20 > > > > What is supposed to load the "/hurd" that would be created ? > > =20 >=20 > After starting GNU Mach microkernel, the hurd translators are required to= start > the operating system. >=20 > At the moment all components like gnumach, hurd servers point to /hurd. >=20 > Maybe there is a way to avoid links? I see. I ask because usually the part that loads that can be adapted and is also a better place to do the adaption in the first place--instead of hard-coding "/hurd". After all, we want eventually to have the ability to roll back the system by selecting a previous generation in the bootloader menu again. That doesn't work all that well with the "/hurd" link. But as far as I understand, you boot Debian/Hurd or something and then it loads Guix, right? In that case, we can understand the GNU Mach microkernel as a bootloader (from our vantage point) and thus emit the /hurd link in the "bootloader" configuration. It's not that clean, but it works (sans rollback, though). Cleaner would be to also boot Guix's gnumach microkernel. It seems that https://www.gnu.org/software/hurd/grub.html documents how to get grub to boot mach and then hurd--and it seems that there, the paths are specified. It should be easy to adapt gnu/bootloader/grub.scm's grub-configuration-file to emit those and then reconfigure. (Later, we could add "multiboot" and "modules" to in gnu/bootloader.scm) However, it's a dangerous part to modify since this part cannot be rolled back easily. So don't make a typo ;) --Sig_/Pfb1Wz3E+cCk0RgA7at7y0x Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlyDd7YACgkQ5xo1VCww uqWmxAf/X+nE1aDVJriSZRD38Ao+1xI3MLPIc6WCEpzJGISTTtzQ2+Dyqx6Atoxt IVIHLfbA4eotCCsn9bWhmcH32v6/FokzKoheo46xB6E/XHd8Od6TrRGBOLrPtbc4 VU0TUo/Ku47oB26FuYIBrF02nPvanC6TMRELK+Nxp25duazyY8xZVoBVsaMwQoBP lpqYp+56gyQYdpvdSa7VLVSIjfXmPm3wBrKrKR6s/qb4NLJgcTPMXrLatnsEVfar L33evn24F2e1YoFJgKwNpJguLROI4/G86KNPWcdQ2MeaFQa2erEooaLJvIb7wTDQ O3dGSh2EqNE3CJr9w1XnL0noEixEXA== =qem6 -----END PGP SIGNATURE----- --Sig_/Pfb1Wz3E+cCk0RgA7at7y0x--