unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: guix-devel@gnu.org
Subject: Progress on the Hurd; new state of wip-hurd-vm
Date: Sun, 19 Apr 2020 16:50:26 +0200	[thread overview]
Message-ID: <87ftczttql.fsf@gnu.org> (raw)

Hello,

I just reset wip-hurd-vm to ba6bdb0d0b gnu: guix: Run `make update-guix-package'.

Like before, you should be able to run

    ./pre-inst-env guix build -f gnu/system/hurd.scm

on it to get a VM and start it doing something like

    guix environment --ad-hoc qemu -- qemu-system-i386 -enable-kvm \
     -snapshot -hda $(./pre-inst-env guix build -f gnu/system/hurd.scm) -m 2G \
     -device rtl8139,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:10022-:2222

The VM now starts the Shepherd which starts the guix-daemon as well as
an openssh daemon.

root shares the system profile, which has been setup for minimalistic
Guix development.  You can build our first package

    ssh root@localhost -p 10022
    guix build --no-offload -e '(@@ (gnu packages commencement) gnu-make-boot0)'

and now also do that from git

    git clone gnu:guix
    cd guix
    ./bootstrap
    ./configure --localstatedir=/var --sysconfdir=/etc --with-courage
    make -j2
    ./pre-inst-env guix build --no-offload -e '(@@ (gnu packages commencement) gnu-make-boot0)'

Being able to build packages from git greatly reduces the round-trip
time :-)

The Shepherd integration needs more work.  Also, the tip of that branch
shows some troublesome commits that hack around cross-compiling guix to
the Hurd.

Greetings,
janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

             reply	other threads:[~2020-04-19 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 14:50 Jan Nieuwenhuizen [this message]
2020-04-19 15:32 ` Progress on the Hurd; new state of wip-hurd-vm Vincent Legoll
2020-04-20  5:39   ` Jan Nieuwenhuizen
2020-04-20  7:50     ` Vincent Legoll
2020-04-22  7:35 ` Jan Nieuwenhuizen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftczttql.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).