unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [BLOG] Childhurds and GNU/Hurd substitutes
Date: Wed, 14 Oct 2020 16:15:07 +0200	[thread overview]
Message-ID: <87lfg8evx0.fsf@gnu.org> (raw)
In-Reply-To: <86eem1jg0i.fsf@gmail.com> (zimoun's message of "Wed, 14 Oct 2020 11:47:25 +0200")

zimoun writes:

Dear Simon,

> On Thu, 08 Oct 2020 at 15:34, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
>> We have just published a blog post on building your own Guix System with
>> GNU/Hurd and running it in a virtual machine; the road we traveled since
>> beginning of April and what is possible right now.  Read it here:
>>
>>     https://guix.gnu.org/en/blog/2020/childhurds-and-substitutes/
>
> Amazing!

Thanks!

> On foreign distro, I have missed how to setup the “childhurd“.  The
> “guix system” is still a bit mysterious to me…

Yeah, guix system in essence "just" builds a disk-image (aka vm-image).
Then, qemu can start that image.

> Using this command line (from gnu/system/examples/bare-hurd.tmpl):
>
>     guix environment --ad-hoc qemu \
>          -- qemu-system-i386 -enable-kvm -m 512  \
>           -device rtl8139,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:10022-:2222 \
>          -snapshot -hda \
>          $(guix system disk-image -t hurd-raw bare-hurd.tmpl)
>
> it is telling me that the ’ssh’ service is not started.  Therefore,
>
>     ssh -p 10022 root@localhost
>     ssh: connect to host localhost port 10022: Connection refused
>
> What do I miss?

I have no idea.  This exact command works for me.  Maybe you had bad
luck/try again?  Does `herd start ssh' work after you login as root?

It could be that your "bad luck" comes from qemu networking -- maybe you
could try running your foreign distro's qemu instead of guix's?

> Then,
>
>     login> login root RET RET
>     root@guixygnu ~# $(guix build hello)/bin/hello
>
> downloads, builds, and displays as expected “Hello, world!”. \o/

\o/

> Last, I am confused:
>
>    debian$ guix build hello --target=586-pc-gnu hello
>    /gnu/store/09sz4qsqp3zgnbaxhzppspaxihwmfzll-hello-2.10
>
>    root@guixygnu ~# guix build hello
>    /gnu/store/<other-hash>-hello-2.10
>
> What do I miss?

It's tricky; --target is != --system: --target is a cross-build.  IOW,
--system => (%current-system), --target => (%current-target-system).

So,

    guix build hello --system=i586-gnu hello

should give the identical hash.

> (Sorry for these naive questions.)

You're welcome.  Thanks for looking at this!

> Thank you!  All is really neat!

Hehe, that's what we are doing it for;

Have fun!
Janneke

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


  reply	other threads:[~2020-10-14 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 13:34 [BLOG] Childhurds and GNU/Hurd substitutes Jan Nieuwenhuizen
2020-10-08 15:27 ` Tanguy Le Carrour
2020-10-14  9:47 ` zimoun
2020-10-14 14:15   ` Jan Nieuwenhuizen [this message]
2020-10-14 20:31     ` zimoun
2020-10-14 20:57       ` Jan Nieuwenhuizen
2020-10-14 21:17         ` zimoun
2020-10-15  7:13       ` Tanguy Le Carrour

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=87lfg8evx0.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).