From: Tom Harrington <tph@rmi.net>
To: robin@louis.bidmc.harvard.edu (Robin Colgrove)
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux and Mac together (Was: Re: mac-on-linux project status)
Date: Sun, 24 Jan 1999 17:55:16 -0700 (MST) [thread overview]
Message-ID: <199901250055.RAA20183@shell.rmi.net> (raw)
In-Reply-To: <36AB7411.F40DFF97@louis.bidmc.harvard.edu> from "Robin Colgrove" at Jan 24, 99 02:28:22 pm
> Maybe I am just not understanding this but if both MkLinux and OS X run on
> top of the Mach microkernel, could they both be running simultaneously? If
> so, I could imagine using OS X (not OS X server) as my desktop OS while
> on the same machine MkLinux was taking care of the internet server things
> in the background. I do not need super high performance stuff since I
> only "host" a few dozen pretty low-intensity users. Right now I get by on
> shareware tools (Quid Pro Quo, Rumor Mill, OTChat, NCSATelnet, Eudora
> Internet Mail Server) but I am reaching the limits of what I can do with
> these.
In principle, yes, Mach is capable of running multiple server operating
systems at the same time. I have no idea what's involved in making this
happen, but supposedly one of the advantges of a microkernel-based Linux
(like MkLinux or L4Linux) is that you can run one Linux kernel while
debugging another one simultaneously. You may have trouble, though, if
Apple is using a different version of Mach than MkLinux does, or if Apple
has stuck some MacOS X Server-specific things into their Mach code.
I really can't help you beyond suggesting that the MkLinux mailing lists
might be a better place to ask. If you succeed, though, I'd be very
interested in hearing about it. Good luck. :-)
Depending on how urgent your needs are and how much MacOS you need vs.
server stuff, you might be better off waiting for SheepShaver on Linux.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-25 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-24 3:48 mac-on-linux project status Samuel Rydh
1999-01-24 19:28 ` Linux and Mac together (Was: Re: mac-on-linux project status) Robin Colgrove
1999-01-25 0:55 ` Tom Harrington [this message]
1999-01-25 5:11 ` Ken Roberts
1999-01-25 15:47 ` David A. Gatwood
1999-01-25 1:14 ` mac-on-linux project status Tom Harrington
1999-01-25 15:12 ` Samuel Rydh
1999-01-25 17:44 ` David Edelsohn
1999-01-25 19:21 ` Tom Harrington
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=199901250055.RAA20183@shell.rmi.net \
--to=tph@rmi.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=robin@louis.bidmc.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.