From: Finn Thain <fthain@telegraphics.com.au>
To: Josh Juran <jjuran@gmail.com>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: penguin (was Re: Linux-mac68k project account maintenance)
Date: Mon, 15 Jun 2020 14:21:25 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.22.394.2006151336260.34@nippy.intranet> (raw)
In-Reply-To: <0A4C54D6-956E-4E46-90DB-BA89B0ED66EB@gmail.com>
On Sun, 14 Jun 2020, Josh Juran wrote:
>
> As my most recent participation was co-developing Penguin, I probably
> don't need to be an admin. :-)
>
If your sourceforge account is still a going concern I'll leave the commit
bit as-is -- I'd hate to discourage possible future contributions!
> Let me know if there's any other information or action you need from me.
> I'd also be interested in any hearing about efforts to virtualize Mac OS
> or Mac applications on Linux/m68k, as I might be able to assist with
> those.
>
I don't know of any MacOS virtualization efforts (kvm for linux-m68k?)
Personally, I'd love to see EMILE ported to MacRelix, as a replacement for
Penguin. Reason being, there are several Penguin bugs that result in boot
crashes and some other bugs besides. Almost all have workarounds, but you
have to read the docs to find out about them (and go out of your way to
apply them).
next prev parent reply other threads:[~2020-06-15 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.22.394.2006151113030.17@nippy.intranet>
2020-06-15 3:29 ` Linux-mac68k project account maintenance (fwd) Josh Juran
2020-06-15 4:21 ` Finn Thain [this message]
2020-06-18 7:11 ` penguin (was Re: Linux-mac68k project account maintenance) Josh Juran
2020-06-19 1:39 ` Finn Thain
2020-06-19 6:33 ` Brad Boyer
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=alpine.LNX.2.22.394.2006151336260.34@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=jjuran@gmail.com \
--cc=linux-m68k@lists.linux-m68k.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