Re: Digest for classic-mac-dev@googlegroups.com - 3 Messages in 2 Topics
Christian
classic-mac...@googlegroups.com wrote:
>=============================================================================
>Today's Topic Summary
>=============================================================================
>
>Group: classic...@googlegroups.com
>Url: http://groups.google.com/group/classic-mac-dev/topics
>
> - Digest for classic...@googlegroups.com - 5 Messages in 1 Topic [1 Update]
> http://groups.google.com/group/classic-mac-dev/t/c5899cc506818539
> - nukernel Continued Development [2 Updates]
> http://groups.google.com/group/classic-mac-dev/t/6ff210a138bd2e1a
>
>
>=============================================================================
>Topic: Digest for classic...@googlegroups.com - 5 Messages in 1 Topic
>Url: http://groups.google.com/group/classic-mac-dev/t/c5899cc506818539
>=============================================================================
>
>---------- 1 of 1 ----------
>From: Christian <cco...@gmail.com>
>Date: Jul 19 10:29PM -0400
>Url: http://groups.google.com/group/classic-mac-dev/msg/8727ab16de22478a
>
>I can't tell you the language, as I taught myself using this. The programming environment is the debugger running in Mac OS 7.5.5. My task list is to get NuKernel stabile, then reinsert it into Copland to finish the programming on the OS itself, for release into the mainstream OS market.
>
>
>
>
>=============================================================================
>Topic: nukernel Continued Development
>Url: http://groups.google.com/group/classic-mac-dev/t/6ff210a138bd2e1a
>=============================================================================
>
>---------- 1 of 2 ----------
>From: Joshua Juran <jju...@gmail.com>
>Date: Jul 19 07:01PM -0700
>Url: http://groups.google.com/group/classic-mac-dev/msg/6a491017ee5bff85
>
>On Jul 19, 2011, at 10:15 AM, Copland DeveloperChris Coxe wrote:
>
>> Hi all, I've been working on NuKernel for nearly two years now so the
>> community that uses Classic Mac OS will be able to bost about their
>> amazing version of multitasking.
>
>Holy crap! Really? Do you have the source somehow, or is this from
>scratch?
>
>> If ANYONE is willing to help, please
>> email me. Thanks.
>
>
>I'm definitely interested. I've been developing a POSIX-like
>environment for classic Mac OS called MacRelix. It allows writing
>programs using blocking I/O, though it it's fundamentally
>cooperatively multitasked and its responsiveness depends on programs
>minimizing time spent between system calls. But theoretically it
>should be possible to install some kind of interrupt handler (e.g.
>Time, VBL, etc.) that walks the stack until it reaches user code and
>either munge it to force a preemption or at least terminate the
>offending thread. Another option is to use MPTasks or 68K preemptive
>threads.
>
>http://www.metamage.com/code/MacRelix/
>
>https://github.com/jjuran/metamage_1
>
>I'd love to see what you've done so far.
>
>Josh
>
>
>---------- 2 of 2 ----------
>From: Joshua Juran <jju...@gmail.com>
>Date: Jul 19 07:13PM -0700
>Url: http://groups.google.com/group/classic-mac-dev/msg/cac163d19537aa7a
>
>On Jul 19, 2011, at 10:56 AM, Dean Howell wrote:
>
>> I would be willing to set up a subversion server for you so that
>> you can track changes and allow for people to check-out code. I
>> can install TRAC too so that you can control your bugs.
>
>I'm neutral on bug trackers for now, but is there any reason not to
>use a DVCS like Git?
>
>For what it's worth, I've ported a subset of git to classic Mac OS by
>way of MacRelix. I don't have ssh yet, but git-fetch over the Git-
>native protocol and git-daemon both work.
>
>Josh
>
>
>
>
Joshua Juran
primarily for high-volume lists, and never (I would argue) for those
posting.
On Jul 20, 2011, at 5:35 PM, Christian wrote:
> It's not easy, but yes, all development has been from scratch.
> There's not much I've done so far other than ATTEMPT to make it
> stabile. A proof-of-concept is in the WAY distant future Mr Kaiser.
> Its been two years, but on the whole, this a very confusing kernel,
> which has greatly wounded my efforts to fix it up. The kernel
> itself is separate from the OS only in D9, and was incorporated in
> fully by D7E1. That's how I got the kernel, for those of you
> wondering.
Now I understand (I think). You're making assembly-level patches to
a binary recovered from a Copland installation.
Even if you don't have something working yet, I'd like to see your
source code (even if it's assembler). Also, I'm not sure how people
are supposed to help otherwise.
Josh
Copland DeveloperChris Coxe
Copland DeveloperChris Coxe
what I call "patching " the kernel. As I said, it's been slow, but I
can upload my work (the microkernel itself) to Macintosh Garden if
anyone really is willing to help.