From owner-freebsd-questions Thu Jul 23 15:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15034 for freebsd-questions-outgoing; Thu, 23 Jul 1998 15:15:54 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smople.thehub.com.au (smople.thehub.com.au [203.143.240.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15012 for ; Thu, 23 Jul 1998 15:15:33 -0700 (PDT) (envelope-from bradyt@choiceconnect.com.au) Received: from choice3.thehub.com.au (choice3.thehub.com.au [203.24.135.3]) by smople.thehub.com.au (8.9.1/8.9.1) with ESMTP id IAA10901; Fri, 24 Jul 1998 08:14:55 +1000 (EST) Message-Id: <199807232214.IAA10901@smople.thehub.com.au> Received: from 203.24.135.4 by choice3.thehub.com.au with SMTP (QuickMail Pro Server for MacOS 1.0.3); 24 JUL 98 08:15:00 UT Date: 24 Jul 98 08:14:44 +1000 From: Terry Brady Subject: Re: Apples and oranges? FreeBSD and MacOSX To: Sue Blake , Sean Harding , Jamie Lawrence CC: "freebsd-questions" X-Mailer: QuickMail Pro 1.5.3 (Mac) X-Priority: 3 MIME-Version: 1.0 Reply-To: Terry Brady Content-Type: multipart/alternative; boundary="====56575455545548545049===1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --====56575455545548545049===1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="US-Ascii" Reply to: Re: Apples and oranges? FreeBSD and MacOSX Jamie Lawrence wrote: >At 07:05 PM 7/22/98 -0700, Sean Harding wrote: >>On Thu, 23 Jul 1998, Sue Blake wrote: >> >>> If you are going to install some unix system now, you couldn't get = anything >>> closer than FreeBSD to do the task well. Some parts of your learning = will be >> >>This is true of free distributions, but if you go commercial, >>OPENSTEP/NeXTSTEP is *far* closer to Rhapsody/MacOS X Server than FreeBSD= >>is ever likely to be. > >Um, forgive me if I'm clue-deprived here, but I thought MacOS X >was a strategy for backing away from Rhapsody for desktop machines. >From my reading, it was to be a revved up MacOS on which developers >could count on a subset of the former APIs being executed in a = >preemptive multitasking, memory protected environment. Basically, >most of what Copeland was to have been. I didn't think there was >any Unix involved, although it would make sense to use what they >have. Does anyone know for sure that I'm wrong? > >-j Jamie, here's one topic I *do* have the answers for: MacOSX is esentially the same thing as Rhapsody which is esentially the = same thing as NeXTStep/OpenStep... they all have a Mach kernel, all have = BSD Unix implementation. It's the higher level services and (graphical) = user interface which differentiate between them. As far as we know, even the "consumer-level" Mac OS X will have the = ability (perhaps not by default but through an install option) to work via = the unix command line - even over a telnet connection. Just like a real = unix, because it is one. Mac OS X Server is just a renamed Rhapsody Customer Release 1.0. The big deal with Carbon - which is just a subset of the existing Mac OS = API's plus a few new ones - is that developers will only have to modify a = small portion of their existing applications in order to take advantage of = protected memory and pre-emptive multitasking... which is what Copland was = supposed to have delivered some years ago. So we will have an OS which is unix at heart, with an advanced Mac OS GUI = for those who like that, command line facilities for the more hands-on = types, capable of running legacy Mac OS apps, updated "Carbon-based" apps, = apps written to the updated NeXTStep API's (aka Yellow Box), 100% Java = implementation, and last but not least the wealth of existing unix = software through the BSD and POSIX implementation. To keep this post somewhere near the FreeBSD list topic: seems like a = knowledge of FreeBSD would give you a good foundation for running a Mac OS = X box. Regards, Terry --====56575455545548545049===1 Content-Type: text/html; charset="US-Ascii" Content-Transfer-Encoding: quoted-printable 
         Reply to:   Re: Apples and oranges? FreeBSD and MacOSX

Jamie Lawrence wrote:
>At 07:05 PM 7/22/98 -0700, = Sean Harding wrote:
>>On Thu, 23 = Jul 1998, Sue Blake wrote:
>>
>>> = If you are going to install some unix system = now, you couldn't get anything
>>> = closer than FreeBSD to do the task well. = Some parts of your learning will be
>>
>>This = is true of free distributions, but if you = go commercial,
>>OPENSTEP/NeXTSTEP = is *far* closer to Rhapsody/MacOS X Server = than FreeBSD
>>is ever likely to = be.
>
>Um, forgive me if I'm clue-deprived = here, but I thought MacOS X
>was a = strategy for backing away from Rhapsody for = desktop machines.
>From my reading, = it was to be a revved up MacOS on which = developers
>could count on a subset = of the former APIs being executed in a
>preemptive = multitasking, memory protected environment. = Basically,
>most of what Copeland was = to have been. I didn't think there was
>any = Unix involved, although it would make sense = to use what they
>have. Does anyone = know for sure that I'm wrong?
>
>-j

Jamie, = here's one topic I *do* have the answers = for:

MacOSX is esentially the same = thing as Rhapsody which is esentially the = same thing as NeXTStep/OpenStep... they = all have a Mach kernel, all have BSD Unix = implementation. It's the higher level services = and (graphical) user interface which differentiate = between them.

As far as we know, even = the "consumer-level" Mac OS X = will have the ability (perhaps not by default = but through an install option) to work via = the unix command line - even over a telnet = connection. Just like a real unix, because = it is one.

Mac OS X Server is just = a renamed Rhapsody Customer Release 1.0.

The = big deal with Carbon - which is just a subset = of the existing Mac OS API's plus a few = new ones - is that developers will only have = to modify a small portion of their existing = applications in order to take advantage = of protected memory and pre-emptive multitasking... = which is what Copland was supposed to have = delivered some years ago.

So we will = have an OS which is unix at heart, with = an advanced Mac OS GUI for those who like = that, command line facilities for the more = hands-on types, capable of running legacy = Mac OS apps, updated "Carbon-based" = apps, apps written to the updated NeXTStep = API's (aka Yellow Box), 100% Java implementation, = and last but not least the wealth of existing = unix software through the BSD and POSIX = implementation.

To keep this post somewhere = near the FreeBSD list topic: seems like = a knowledge of FreeBSD would give you a good = foundation for running a Mac OS X box.

Regards,

Terry --====56575455545548545049===1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message