From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front]
Date: Mon, 10 Jan 2022 09:25:59 -0800 [thread overview]
Message-ID: <2E841EE539B7EC7B2BF4E16664A7DFA3@gmail.com> (raw)
In-Reply-To: <3cd7037b-6fa3-4ebd-b602-e65f6989872e@sirjofri.de>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Okay this is where it get confusing. So I suspect I mount the 9front-xxxx=i386.iso. Which is generally in read only mode. Copy the contents into another directory and edit the plan9.ini file. Then
repackage the iso with the altered .ini file and reset the boot
record? Now I have a new but modified iso that has console=0. I can
then try to install it on my target remote system via ssh/
[-- Attachment #2: Type: message/rfc822, Size: 4319 bytes --]
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front]
Date: Mon, 10 Jan 2022 10:21:56 +0000 (UTC)
Message-ID: <3cd7037b-6fa3-4ebd-b602-e65f6989872e@sirjofri.de>
10.01.2022 09:44:51 thinktankworkspaces@gmail.com:
> Trying to do an install on a remote server via ssh that has qemu.
>
> I suppose i'm doing this with -nographic
>
> kind of like qemu-system-x86_64 -serial stdio 9front.img -boot d
> 9front-xxxx-i386.iso -m 1024
>
> With pipes such as /tmp/guest.in /tmp/guest.out
>
> I'm receiving data.
>
> Booting from DVD/CD... *e820 ..... ... ... cdboot=yes
> mouseport=ask monitor=ask vgasize=ask bootfile=/386/9pc
>
>
> But it stops at that last line and nothing. Any thoughts or
> recommendations? Is it possible? Or do I have to build the image
> local then copy the 9front.img to remote system. I worry that I will
> run into same situation where it gets stuck.
Please check plan9.ini(8) man page and look for console=. I believe
that's what you want/need.
I can't give more advise since I didn't use it (yet).
sirjofri
next prev parent reply other threads:[~2022-01-10 17:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 8:44 [9front] thinktankworkspaces
2022-01-10 10:21 ` [9front] sirjofri
2022-01-10 17:25 ` thinktankworkspaces [this message]
2022-01-10 23:33 ` [9front] sirjofri
2022-01-12 1:16 ` [9front] thinktankworkspaces
2022-01-12 8:30 ` [9front] sirjofri
2022-01-12 9:29 ` [9front] Eckard Brauer
2022-01-12 13:09 ` [9front] sirjofri
2022-01-12 13:40 ` [9front] hiro
2022-01-12 14:59 ` [9front] thinktankworkspaces
2022-01-12 16:56 ` [9front] hiro
2022-01-14 11:45 ` [9front] cinap_lenrek
2022-01-12 14:40 ` [9front] thinktankworkspaces
2022-01-12 14:18 ` [9front] Stanley Lieber
2022-01-12 15:04 ` [9front] thinktankworkspaces
2022-01-10 12:10 ` [9front] mkf
-- strict thread matches above, loose matches on Subject: below --
2022-06-22 12:28 [9front] roy niang
2022-06-22 12:32 ` [9front] stefncb
2021-09-16 22:17 [9front] Drew Fargo
2021-08-24 19:25 [9front] Jonas
2021-06-09 14:33 [9front] adr
2021-03-31 16:32 [9front] cinap_lenrek
2021-04-01 18:33 ` [9front] Romano
2021-04-01 18:54 ` [9front] Romano
2021-04-01 19:03 ` [9front] cinap_lenrek
2021-04-01 23:16 ` [9front] Romano
2021-04-02 14:31 ` [9front] cinap_lenrek
2021-04-02 18:31 ` [9front] cinap_lenrek
2021-04-03 0:41 ` [9front] Romano
2021-04-02 21:24 ` [9front] Romano
2021-04-02 21:54 ` [9front] cinap_lenrek
2021-01-22 16:32 [9front] Марко М. Костић
2021-01-22 23:41 ` [9front] Tanami Muller
2021-01-23 0:29 ` [9front] Stuart Morrow
2021-01-23 13:38 ` [9front] Thaddeus Woskowiak
2021-01-23 14:12 ` [9front] hiro
2018-08-20 19:42 [9front] umbraticus
2018-08-20 12:11 [9front] Alex Musolino
2018-06-06 12:30 Stanislav Paskalev
2018-06-06 15:50 ` [9front] Kurt H Maier
2018-02-17 4:53 [9front] kokamoto
2016-12-28 23:31 sl
2016-12-28 23:33 ` [9front] cinap_lenrek
2015-10-02 11:43 Holger Sebert
2015-10-02 14:32 ` [9front] Kurt H Maier
2015-10-04 21:18 ` [9front] Stanley Lieber
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=2E841EE539B7EC7B2BF4E16664A7DFA3@gmail.com \
--to=thinktankworkspaces@gmail.com \
--cc=9front@9front.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.
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).