From mboxrd@z Thu Jan 1 00:00:00 1970 From: Divan Santana Subject: Re: guixsd install questions Date: Sun, 05 Feb 2017 09:25:30 +0200 Message-ID: <8760kpyu8l.fsf@santanas.co.za> References: <87tw8kkisf.fsf@santanas.co.za> <878tpu22mu.fsf@gnu.org> 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]:40112) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1caHfv-0001gQ-9h for help-guix@gnu.org; Sun, 05 Feb 2017 02:55:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1caHfs-0006Jt-7K for help-guix@gnu.org; Sun, 05 Feb 2017 02:55:55 -0500 In-reply-to: <878tpu22mu.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 Ludovic Court=C3=A8s writes: > Hello! > > Divan Santana skribis: > >> Then do the install with this guile code: >> >> #+BEGIN_SRC scheme >> ;; two devices in raid0 striped with LUKS full disk encryption. >> (bootloader (grub-configuration (device "/dev/vdb"))) >> (mapped-devices (list >> (mapped-device >> (source (list "/dev/vdb1" "/dev/vdc1")) >> (target "/dev/md0") >> (type raid-device-mapping)) >> (mapped-device >> (source (uuid "fb29c6f6-b2c0-4c87-8651-4962b7125dc= 0")) >> (target "crypt") >> (type luks-device-mapping)))) >> #+END_SRC >> >> >> And this too: >> >> #+BEGIN_SRC scheme >> (file-systems (cons (file-system >> (device "root") >> (title 'label) >> (mount-point "/") >> (type "ext4")) >> %base-file-systems)) >> #+END_SRC >> >> >> The above fails. So tried another install with device like so > > Do you know how it fails? No unfortunately I didn't document it at the time. Though I'll do a better job of it next time I give it a go and give feedback. > My guess is that you=E2=80=99d need to explicitly mark one of the mappe= d device > as depending on the other; this cannot be guessed. > > If you run =E2=80=9Cguix system shepherd-graph=E2=80=9D on your config = you=E2=80=99ll probably > see that there=E2=80=99s no such dependency. > > Currently dependencies among mapped devices cannot be expressed, but > that=E2=80=99s easy to fix (by providing a =E2=80=98dependencies=E2=80=99= field as in > =E2=80=98file-system=E2=80=99.) I'll give this a try thanks. >> That failed, I then tried the UUID method, via =3Dblkid >> /dev/mapper/crypt=3D, get the UUID and did another install with this >> snippet instead: >> >> #+BEGIN_SRC scheme >> (file-systems (cons (file-system >> (device (uuid "4dab5feb-d176-45de-b287-9b0a6e4c= 01cb")) >> (title 'uuid) >> (mount-point "/") >> (type "ext4")) >> %base-file-systems)) >> #+END_SRC >> >> This fails with waiting for root device. > > Probably same problem as above. > > For now, using just RAID or just LUKS will work; it=E2=80=99s the combi= nation > that=E2=80=99s not supported yet. >> * How to recover a failed install. How to chroot a broken system and >> fix? >> >> You can see why I'm asking this. When my failed crypt install fails, I >> sometimes just want to reconfigure the system to try another method. >> >> Now when I run =3Dguix system init /mnt/etc/config.scm /mnt=3D to reco= ver >> the install to the same preveiously install disk it re-downloads, >> re-compiles and redoes the whole install, instead of just perhaps >> changing grub to (attempt to) fix my crypt issue. >> >> Ideally I want to chroot into the installed (and broken) environment a= nd >> do a =3Dguix system reconfigure /etc/config.scm=3D. >> >> How can one do this? > > I guess you could boot the install image, mount the target file system, > chroot in it, run guix-daemon in there, and run =E2=80=98guix system > reconfigure=E2=80=99 there. > > That should work though that=E2=80=99s inconvenient at best. I'll give it a try and let you know. >> * How to use a proxy to do the install >> >> This is from the boot install media. >> >> I've read the docs on using proxy though it's not working like I expec= t. >> Prob doing something wrong. >> >> I've done the following >> >> On tt1 I did =3Dherd stop guix-daemon=3D >> Then exported proxy like so: >> export http_proxy=3Dhttp://server.domain.co.za:8080/ ; export ftp_prox= y=3D$http_proxy ; export https_proxy=3D$http_proxy >> >> =3Dherd start guix-daemon=3D > > The =E2=80=98http_proxy=E2=80=99 variable needs to be set in the enviro= nment of the > =E2=80=98guix-daemon=E2=80=99 process itself, which is why this doesn=E2= =80=99t work. We should > make it easier to choose a proxy, for instance by having the daemon > honor client-provided proxy settings. Hmm, so what exactly do I need to do to get the http_proxy variable set in the guix-daemon environment? I've tried exporting on command line, then starting the daemon but that didn't work. > Thanks a lot for your detailed feedback! Thanks a lot for the awesome work on GuixSD!