9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] First time 9front start with qemu
Date: Wed, 20 Mar 2024 21:41:46 -0400	[thread overview]
Message-ID: <51d6cdf9-d0a3-4e8c-ac17-f652ea6cbab4@fjrhome.net> (raw)
In-Reply-To: <90183F6B-F40E-4EAF-A081-C372B0FE0CFB@gmail.com>

Not sure why you would do that; I was able to build a native ARM binary 
of drawterm for macOS without issue.


On 3/20/24 11:17, Michael Misch wrote:
> Having ran x86 on my M1, I can attest to it being perfectly usable for a Drawterm host.
>
>> On Mar 20, 2024, at 08:14, Jacob Moody <moody@posixcafe.org> wrote:
>>
>> On 3/20/24 10:07, Bengt Kleberg wrote:
>>> Thank you for the very prompt answer.
>>>
>>> Yes, my host is an ARM computer, Mac Mini with MacOS.
>> In your case then it may be worth the trouble of figuring out the arm64 vm.
>> The kernel that is used was specifically written to work under MacOS arm64
>> accelerated virtualization so it should work. It is just not entirely documented.
>>
>> For what it's worth I doubt that running an x86 VM would be much of an issue either,
>> 9front is not exactly a demanding piece of software compared to a gnome desktop.
>>
>>> To use drawterm I would need a computer/VM with 9front, which I do not have.
>> This is incorrect, drawterm is a program that runs under mac/linux/windows/whatever
>> that acts as a terminal. This is the whole point of having a specific program for it.
>> If you already had a 9front system you could just rcpu and run rio.
>>
>>
>


  reply	other threads:[~2024-03-21  1:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:20 Bengt Kleberg
2024-02-26 18:54 ` Jacob Moody
2024-03-20 10:45   ` Bengt Kleberg
2024-03-20 14:51     ` Jacob Moody
2024-03-20 15:07       ` Bengt Kleberg
2024-03-20 15:14         ` Jacob Moody
2024-03-20 15:17           ` Michael Misch
2024-03-21  1:41             ` Frank D. Engel, Jr. [this message]
2024-03-20 16:00           ` Bengt Kleberg
2024-03-20 16:11             ` Jacob Moody
2024-03-21 11:14               ` Bengt Kleberg
2024-03-23 15:51                 ` Bengt Kleberg
2024-03-26  1:38                   ` Jacob Moody
2024-03-26 14:56                     ` Bengt Kleberg
2024-03-23 16:04               ` Bengt Kleberg
2024-03-23 20:00                 ` hiro
2024-03-24 21:06                 ` Pablo Tesari
2024-04-05  7:05                   ` Bengt Kleberg
2024-03-26  1:54                 ` Jacob Moody
2024-03-26 14:59                   ` Bengt Kleberg
2024-02-26 19:55 ` ori
2024-02-26 21:29   ` Bengt Kleberg

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=51d6cdf9-d0a3-4e8c-ac17-f652ea6cbab4@fjrhome.net \
    --to=fde101@fjrhome.net \
    --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).