On Fri, Aug 6, 2010 at 8:26 AM, Greg Troxel <[email protected]> wrote:
>
> Olemis Lang <[email protected]> writes:
>
>>
>> Mac OS X is (AFAIK) a full FreeBSD system with a proprietary kernel
>> and Cocoa & other Mac specific libs working somewhere on top of it .
>
> That's not true. Mac OS X is Darwin plus mac UI on top.
That was what I was trying to say , FreeBSD subsystem lives **mostly**
in userland and all (most of ?) its commands are available so as to be
«compatible» with (and be able to use) *NIX applications (freshports
et al. with some persuasive whispering in their ears ;o) on the Mac .
Probably are not compatible at byte-code level but the command line
interface is the same (so similar that makes little difference ;o). In
Apple's dev site [1]_ I found
{{{
Darwin consists of the Mac OS X kernel environment, BSD libraries, and
BSD command environment. For more information about Darwin and what it
contains, see “Kernel and Drivers.” For detailed information about the
kernel environment, see Kernel Programming Guide.
}}}
... and also [2]_
{{{
Darwin layer of Mac OS X comprises the kernel, drivers, and BSD
portions of the system [...] The kernel environment is built on top of
Mach 3.0
}}}
... AFAIK , the Mach kernel is proprietary (I might be wrong, 'cause
it seems sources are in public servers ...). This was what I was
trying to say (even if I didn't say it exactly that way ...)
Anyway, this image illustrates all the details [3]_ , see how there
are parts of BSD in both the kernel & in user space ;o)
> Darwin is sort
> of a cross between mach and some freebsd code and I think some netbsd
> (network stack), with a userland that's been done oddly.
Major parts of the kernel is substantially different from FreeBSD.
> In particular
> shared libraries are totally different from how they are on *BSD (and
> *BSD and Linux are pretty much the same for shlibs). And other things
> are gratuitously different. Building a program that works on linux and
> *bsd on mac is often a small bit of work.
>
+1
>> Since you shouldn't be using Mac-specific soft (i.e. Apache should
>> only use FreeBSD components, AFAIK) any tutorial for
>> (Free|Open|...)BSD , Unix , or Linux should be very similar (unless
>> you're using some Mac-specific install package, doing Mac-specific
>> magic under-the-hood ... BTW, how did you install Trac ?) just be
>> aware of path translations between OS ...
>
> But this is mostly true - apache config may need something special, but
> I know 'bmake package-install' in www/apache22 in pkgsrc works just
> fine. The issues are mostly solved by libtool. Once you have apache,
> python mod_wsgi running, trac is easy.
>
PS: Depending on the way you install Python and Trac , e.g. paths may
be different ...
.. [1] Darwin and Open Source Development
(http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/OSX_Technology_Overview/About/About.html)
.. [2] Darwin and Core Technologies
(http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemTechnology/SystemTechnology.html#//apple_ref/doc/uid/TP40001067-CH207-TPXREF172)
.. [3] Mac OS X system components
(http://upload.wikimedia.org/wikipedia/commons/thumb/f/f2/Diagram_of_Mac_OS_X_architecture.svg/556px-Diagram_of_Mac_OS_X_architecture.svg.png)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
