9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sml@firstpost.pub
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9legacy under OpenBSD's vmm
Date: Thu, 3 Feb 2022 02:51:29 -0500	[thread overview]
Message-ID: <16438746890.d9D2104Be.391213@composer.9fans.topicbox.com> (raw)
In-Reply-To: <A5E395A6-E6A0-42C5-9A71-F692E0DC6372@gmx.com>

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

I would like to run 9legacy on OpenBSD as well. Unfortunately, I'm still learning and even though finding and ideally contributing solutions to such bugs is a distant goal of mine, my only current option is to run on 9front.

In the wiki (https://wiki.9front.org/openbsd-vmm) it says: 
"Since VMM doesn’t provide any display functionality, 9front’s console has to be redirected to virtual serial port by adding console=0 to plan9.ini. It makes sense to also use display=none while at it.

Note that even though you might not have a chance to modify plan9.ini before booting, stopping boot process with an early hit of a key, typing an additional configuration in, and then boot<ENTER> is ought to work."

Unfortunately, the only way I know to start a VM under OpenBSD is to set up the vm in /etc/vm.conf, enable and start vmd via rcctl and then connect via SSH or vmctl console. 

Could someone possibly help me out and explain how I can edit the plan9.ini during the boot process, please?

Thank you very much in advance!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te13afbfe31e87665-M8fd548688b12d7af925e6fa9
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2022-02-03  7:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 23:30 Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11  5:21 ` Conor Williams
2022-01-11 11:16 ` David du Colombier
2022-01-14 12:03   ` cinap_lenrek
2022-01-15 22:13     ` David du Colombier
2022-01-16  3:12       ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-16  3:35         ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-16 20:23           ` David du Colombier
2022-01-17 18:12             ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-17 18:29               ` David du Colombier
2022-01-17 18:35                 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-24 14:11                   ` B. Atticus Grobe
2022-01-24 16:58                     ` cinap_lenrek
2022-01-24 17:43                       ` Duke Normandin
2022-02-03  7:51                         ` sml [this message]
2022-02-03 15:26                           ` ori
2022-02-03 17:21                           ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-02-03 17:26                             ` elviz.ismayilov
2022-01-17  2:49           ` Lucio De Re
2022-01-17  6:06             ` David du Colombier
2022-02-03 10:52 mkf9

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=16438746890.d9D2104Be.391213@composer.9fans.topicbox.com \
    --to=sml@firstpost.pub \
    --cc=9fans@9fans.net \
    /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.
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 NNTP newsgroup(s).