From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mikhail Kryshen Subject: Re: ~/.config/guix/current Date: Wed, 11 Jul 2018 18:46:55 +0300 Message-ID: <87d0vt3hcg.fsf@eta.cs.prv> References: <87o9foz7f4.fsf@eta.cs.prv> <877em4iq1g.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdHKb-0007ve-U3 for help-guix@gnu.org; Wed, 11 Jul 2018 11:47:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fdHKa-00021L-L4 for help-guix@gnu.org; Wed, 11 Jul 2018 11:47:05 -0400 Received: from mail.kryshen.net ([2a01:6f0:ffff:302::de2b]:48796) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fdHKa-000200-A7 for help-guix@gnu.org; Wed, 11 Jul 2018 11:47:04 -0400 In-Reply-To: <877em4iq1g.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: help-guix@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: >> a) master node running guix-daemon [1] >> - will "guix gc" destroy guix/current profiles if /home is not >> mounted on the master node? What if some users have local >> home directories and some are on nfs? > >> [1] https://guix-hpc.bordeaux.inria.fr/blog/2017/11/installing-guix-on-a= -cluster/ > > This is what I would recommend, and as the post suggests, you=E2=80=99ll = have to > make sure home directories are visible to guix-daemon, which means > having them mounted on the master node. > > If you don=E2=80=99t do that, there=E2=80=99s a risk that user-pulled Gui= xes will be > reclaimed prematurely, simply because the GC won=E2=80=99t see that they = are > still =E2=80=9Clive.=E2=80=9D But ~root is local on each machine, so root-pulled Guix will still not be protected from gc. Btw, is option a) possible on GuixSD? >> b) guix-daemon on every computer >> - then /gnu/store and /var/guix/profiles will by local and user >> profiles can be different on every computer, but >> ~/.config/guix/current will link to nonexistent store item if >> "guix pull" was invoked by the same user on a different machine. > > If this is a cluster, I would definitely recommend option a), which > provides a single world view, shared storage, etc. It's for GNU/Linux workstations in university labs. I want to use Guix to provide additional software that is not available in required configuration in the host distro, and also give students an interesting environment to experiment. I decided for now to go with the option b) for performance and reliability. My previous attempts to deploy large software packages on NFS (even with FS-Cache enabled) didn't work well. Also, it may be possible to somehow exploit immutability of the store items to share and cache them more efficiently. The computers periodically run "guix pull" as root and I want to make the updated Guix automatically available to all users, but /usr/local/bin/guix can't be linked to /root/.config/guix/current/bin/guix as the /root directory is normally not searchable by other users =E2=80=94 another reason to keep pulled Guix profiles in /var. I workaround this by having the script that runs "guix pull" to symlink /usr/local/bin/guix directly into the new profile in /gnu/store. > I agree it would be useful (the way we do it on GuixSD is by having > /etc/profile define INFOPATH systematically, for instance), but there=E2= =80=99s > no clear way to have ~/.config/guix/current/etc/profile define them > directly. It would be useful to have a similar script included in the guix package to be symlinked into host distro's /etc/profile.d Thank you,=20 Mikhail --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEEw6yVFU/UQfkLWikDzxz0c4HWsG4FAltGJm8ACgkQzxz0c4HW sG5+Wwv+M7AaWJstG5/te08b7hlBAq2PJCkLJviQpwfs9YybdH+sBnBt6WaiWVod bgysjrPE+VRp3seBQToaoDYPYRQ6jJOEJkcX8Tb1+dzGVMdkBPMRcB4OU/UQWM+B fDz8Vy5IDHin59DXVbvfwXl5150BzPn04XSkqhfazc0Ze/opWI3mf1ul9KhDawIA FlOMy/poMasbB+1b6LJYfvT/MMeXlq5i7Ti/QXcZE88s6bX1Ffjl0MdIw4Op5cs7 EoS2oAFakhiUWSMjnVsyrJZDX6hX/TcyRNlj1HtcXpyDNcB8JI7osUIFiSp35OAj Hv0B5AkLqAMbRrOcC9Z8LqNCS5poGRRtcPiJxl9M1Ev6wOpLO7sPvpzE5fd8BDiA K3+mrvAdJ58KdX3ZtycLGZ7aO87omS3dCkMNXz9aiZFYxURcx1eYY4APCv3e2Dli e3XwaqOBEwehXbiaseqMiETS1y0XQJzJUgt7yUUHdnveKZI1/S60ZXfgh7VQqQRV gs54gg74 =lxhD -----END PGP SIGNATURE----- --=-=-=--