From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2448 Path: news.gmane.org!.POSTED!not-for-mail From: Guillermo Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: nosh: User-space virtual terminal test and questions Date: Sun, 6 Jan 2019 19:35:50 -0300 Message-ID: References: <1539fe55-162b-ebd3-12c0-a15f5373d78b@NTLWorld.COM> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1546814033 20978 195.159.176.226 (6 Jan 2019 22:33:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 6 Jan 2019 22:33:53 +0000 (UTC) To: Supervision Original-X-From: supervision-return-2038-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Jan 06 23:33:49 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1ggGzN-0005MN-0X for gcsg-supervision@m.gmane.org; Sun, 06 Jan 2019 23:33:49 +0100 Original-Received: (qmail 909 invoked by uid 89); 6 Jan 2019 22:36:25 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 902 invoked from network); 6 Jan 2019 22:36:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=DR85VvQBR9f1TMABbkmx4jF/wL8yLt9JfofZNCP75lg=; b=fy9Wm1OqSkI6CKQWh2yo06FTLBWJ29/Y6VLRpaj7uIbhNuZjgXDCRgjwKoqiPjoh3c zzTQfEVrCiFmormcFTvTMT+7CFvJ89Lg4VVeQ2gvB6jo61bghRarkiFpxqLvpblE4/S3 jlB3N3hqRwru+OlT9aGufR/SccnSWrHwa4U6aF38L0sdJrnFZeCN0J3jEzHbXTDzlcrb NWyiBDk7uGyOApGnQXLH3EFpMqa7sgtaMH5FTD0U9YbByh+dF7UpWZKmpqFX4VTyPOSz u9dr04QtKF6Sm/3MynNao+MaaHOl53IuJTFuyJXQ6hM2UuzxRjHU8Dwsvw0r7qJ4hnOj xraw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=DR85VvQBR9f1TMABbkmx4jF/wL8yLt9JfofZNCP75lg=; b=IPo+jLv6AuYm9N1lVEo1l9WCKBmvrIcW9TN3/Xkuvgo5VIFcZiNpbWyS+3HMx3mkmc v1u7MIO9avfkVt4yfgcQ6sZElxVG7r9rOx7pKaMjlstIqNQ6Ui3kJ1bHLb7W6cecD+m/ ApzqtbvIkhK5yISHlt+un2lY07hyFeuQoSppQRc+xxXgoiqNXRh/39hR8sW0tJ5wWxRy 7n/87yZoTGGPj3LcVbC9OhodPGrGdQz2jei7q8+SC/JIiINotgOsgpcMA3UuMHj9YQfD Fnzhmnvt3NJ7oLJ8KBQw54VdVyP3rZ8oEuh+/NiudiLAKx7af7RbMNPNvvATy30sMoDv DJow== X-Gm-Message-State: AA+aEWZRCANfBCInlOPxo0oSB0nqAuMviLS/GFoA3WpYBQzQkufZA0i4 FoeRai3X0CnxdSesC8C+WakxmtaDyQUwEMikZNGU7w== X-Google-Smtp-Source: AFSGD/XC+dtFYyjZcYssTpP4FFtJFNzYkJy2GZWcC0LVjBckzz53163dsozbHfFxrY7OpbkCbU5ndR5CmUg3FkkZJw0= X-Received: by 2002:a02:9d0:: with SMTP id 77mr39036787jam.14.1546814157032; Sun, 06 Jan 2019 14:35:57 -0800 (PST) In-Reply-To: <1539fe55-162b-ebd3-12c0-a15f5373d78b@NTLWorld.COM> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2448 Archived-At: El dom., 6 ene. 2019 a las 8:27, Jonathan de Boyne Pollard escribi=C3=B3: > > > The combination of vboxvideo with |console-fb-realizer| was explosive, > > I got a (guest) kernel panic. > > > [...] > so I'm initially going to lay that one at the door of the driver. Yeah, I'm suspicious about the kernel module too. I didn't spend too much time with this, I just blacklisted the module for the console-fb-realizer tests, which gave me the VESA framebuffer device. But I thought I should mention that it happened in case anyone else wanted to try that, or had not experienced it. > Try the --80-columns option > (which prevents console-fb-realizer trying to switch to some of the > more exciting high-resolution modes) The option is not present if console-fb-realizer is built on [GNU/]Linux, right? 'console-fb-realizer --help' doesn't show it, and the C++ source file seems to have the relevant code contained inside an #if defined(__FreeBSD__) || defined(__DragonFly__) || defined(__OpenBSD__) - #endif block. > > I [...] managed to deal with the BSDness of the requirements on font > > and keyboard map files with the help of FreeBSD's SVN repository :) > > > For those reading this, there is a whole chapter in the Guide on the > multiplicity of places whence one can obtain fonts, keyboard maps, and > input methods. The toolset does not come with them for two major > reasons. Oh, I don't expect nosh to ship font and keyboard map files. That was a humorous remark about them either having to be in a BSD-specific format, or in a format that a BSD program (vtfontcvt) outputs. > First, it is a deliberate design decision to use existing > formats and not require new ones be created from scratch. That's fine. > > 3) More strangely, Ctrl + x (e.g. to exit from GNU nano) did not work > > with |console-termio-realizer|, but did with |console-fb-realizer|. > > > Control+X is =E2=90=98 (cancel, U+0018) which cancels an in-progress ECMA= -48 > escape or control sequence. > [...] > console-termio-realizer decodes its input with a fully-fledged ECMA-48 > decoder, [...] So, how does one get the control character delivered to the application? Is it possible with console-termio-realizer? > > 4) With console-termio-realizer, green is blue and blue is green :D > > > Part of my usual Z shell prompt is green, so I am confident that I would > have noticed it being blue in error. (-: I noticed it with GNU ls's colorized output (directories showed up green and executable files showed up blue), and Bash's prompt, which also happens to be green and blue, and looked reversed. This is the value of PS1: \[\033[01;32m\]\u@\h\[\033[01;34m\] w $\[\033[00m\] > What terminal type is console-termio-realizer outputting to? Is this > a GUI terminal emulator with a colour palette that has been altered from > the standard colour set? Straight to a kernel VT, and I don't think the color palette is changed from the default. This is how I lauhched console-termio-realizer: /etc/inittab: us2:3:respawn:/home/guillermo/bin/start-termio-realizer /home/guillermo/bin/start-termio-realizer: #!/bin/nosh foreground sleep 1 ; vc-get-tty tty8 open-controlling-tty vc-reset-tty /lib/nosh/setuidgid -s user-vt-realizer console-termio-realizer /run/dev/vc1 (Yeah, that's van Smoorenburg init. Minimal setup for ease of troubleshooting, remember :) ) I didn't see a console-termio-realizer (or console-ncurses-realizer) example in nosh-bundles, maybe simple file descriptor redirections would have sufficed, but that worked, so... > Is it a 24-bit-colour-capable terminal? Use > console-control-sequence --foreground blue|console-decode-ecma48 from > version 1.39 on that terminal. What do you see? SGR 34? SGR 38;5;4? > Or SGR 38;2;... ? I'd have to build in-development 1.39 for that. I'll post the result when I do that. Thanks, G.