From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Howard <christopher@alaskasi.com>
Cc: 40542@debbugs.gnu.org
Subject: bug#40542: wip-hurm-vm build failure
Date: Mon, 13 Apr 2020 23:23:14 +0200 [thread overview]
Message-ID: <87tv1n2i7x.fsf@gnu.org> (raw)
In-Reply-To: <15fa028e33810483c427ef20a23dd31c10662ddf.camel@alaskasi.com> (Christopher Howard's message of "Mon, 13 Apr 2020 13:02:21 -0800")
Hi,
Christopher Howard <christopher@alaskasi.com> skribis:
> Okay, I was just about to report that I successfully built the VM using
> commit ef33718a5cc486dd34378e6a8fcfcbb920ff7a8a from wip-hurd-vm. The
> VM started fine and I was able to run the guile shell and the ls shell
> command. Was going to try to install Emacs next.
>
> For screenshots, is there something equivalent to `cat /proc/version`
> to show running kernel version?
I think you can do something like:
settrans -ca /proc /hurd/procfs
cat /proc/version
Or just “uname -a”.
Can’t wait to see the screenshot! :-)
Note: I don’t think janneke has tried building anything as high in the
stack as Emacs, that sounds a bit ambitious for a start.
Ludo’.
next prev parent reply other threads:[~2020-04-13 21:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 15:53 bug#40542: wip-hurm-vm build failure Christopher Howard
2020-04-11 15:46 ` Jan Nieuwenhuizen
2020-04-13 16:59 ` Christopher Howard
2020-04-13 20:40 ` Ludovic Courtès
2020-04-13 21:02 ` Christopher Howard
2020-04-13 21:23 ` Ludovic Courtès [this message]
2020-04-13 21:46 ` Jan Nieuwenhuizen
2020-04-13 22:58 ` Christopher Howard
2020-04-14 5:46 ` Jan Nieuwenhuizen
2020-04-14 15:55 ` Christopher Howard
2020-04-14 17:12 ` Jan Nieuwenhuizen
2020-04-14 16:57 ` Bengt Richter
2020-04-14 17:29 ` Christopher Howard
2020-04-14 19:30 ` Jan Nieuwenhuizen
2020-04-14 23:27 ` Christopher Howard
2021-03-26 0:16 ` Christopher Howard
2021-03-26 0:25 ` Leo Famulari
2021-03-29 16:49 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv1n2i7x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40542@debbugs.gnu.org \
--cc=christopher@alaskasi.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.