unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@alaskasi.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 40542@debbugs.gnu.org
Subject: bug#40542: wip-hurm-vm build failure
Date: Tue, 14 Apr 2020 07:55:43 -0800	[thread overview]
Message-ID: <65442d61bd47a699b4d90e9fb342d357d4ceee2f.camel@alaskasi.com> (raw)
In-Reply-To: <87ftd6bovr.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Thank you, I'd like to try ssh. Would someone be willing to share what
qemu and ssh commands they are using to establish the connection?


-----Original Message-----
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Christopher Howard <christopher@alaskasi.com>
Cc: Ludovic Courtès <ludo@gnu.org>, 40542@debbugs.gnu.org
Subject: Re: bug#40542: wip-hurm-vm build failure
Date: Tue, 14 Apr 2020 07:46:48 +0200

Christopher Howard writes:
> I'm having some trouble playing around with the VM, because a lot
> ofweird things are happening with keyboard input into the qemuwindow.
> It seems like the meta keys (shift, ctrl, alt, super) arebehaving in
> strange ways, or that terminal state is getting corruptedsomehow.
> E.g., sometimes shift key stops working, or the cursors jumpsup to
> the middle of the screen, or text gets garbled.

Since yesterday I've been seeing that too.  I'm pretty sure that if
youbuild a VM from core-uupdates, the console is fine.
I haven't looked into the details of the console/tty setup, so I
musthave messed-up something.  Sorry!
Meanwhile we do have ssh login :-)
The startup now goes like this
    startup -> runsystem -> init -> runsystem.hurd -> rc -> shepherd
and; i would like to move towards
    -startup -> rc -> shepherd
if that's possible.
Greetings,janneke

-- 
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com

[-- Attachment #2: Type: text/html, Size: 2798 bytes --]

  reply	other threads:[~2020-04-14 16:48 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
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 [this message]
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

  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=65442d61bd47a699b4d90e9fb342d357d4ceee2f.camel@alaskasi.com \
    --to=christopher@alaskasi.com \
    --cc=40542@debbugs.gnu.org \
    --cc=janneke@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).