Home

    <div class="row">
      <div class="col-10 col-lg-8 mx-auto mb-4 text-center">
        <p>
          The PureDarwin project, which aims to make Apple's open-source Darwin OS more usable, is still actively
          maintained as of 2024. While development has been relatively slow, the project continues to progress
          through
          community contributions. PureDarwin focuses on creating a usable bootable system that is independent of
          macOS
          components, relying solely on Darwin and other open-source tools.</p>
        <p>The project's main focus is providing useful documentation and making it easier for developers and
          open-source enthusiasts to engage with Darwin.
        </p>
      </div>
    </div>
  </div>
</div>

Test Build

The PD-17.4 Test Build is a minimal system, unlike previous versions like PureDarwin Xmas with a graphical interface. It’s distributed as a virtual machine disk (VMDK) and runs via software like QEMU.

          <br><br>Due to the lack of proprietary macOS components, the community must develop alternatives, leaving
          elements like
          network drivers and hardware support incomplete. This build is intended for developers and open-source
          enthusiasts to explore Darwin development outside of macOS​.
          <br><br><small><i>Based on Darwin 17, which corresponds to macOS High Sierra (10.13.x).</i>
          </small>
        </p>
        <a href="/news/PD17-4-released.html" class="btn btn-primary rounded-pill">PD-17.4 Test Build</a>
        <br>

      </div>
      <div class="col-12 col-lg-7 col-xl-6 pb-4">
        <img src="img/homepage/screenshot-hexley.png" class="img-fluid">
      </div>
    </div>
  </div>
</div>

Archive

The PureDarwin Archive contains documentation material and news articles from prior to 2020.

Archive

Code

We have a GitHub org, and encourage visitors to use it for both contribution, and for checking out the latest build sources.

PureDarwin GitHub

News

Jan. 3, 2026
Remembering Cliff Sekel

Nov. 3, 2024
A New Direction

Jul. 1, 2018
Release: PD 17.4 Test Build

News

Community

Join in on the conversation, talk and watch development, ask questions, chip in, and so much more on our Discord server.

Discord Server

            <br>
            <a href="https://discord.gg/9kz8XXRRcT" target="_blank" class="text-decoration-none">
              <img src="img/social-discord.svg" height="26" width="26" alt="Discord" class="mx-1">
            </a>
            <a href="https://t.me/puredarwin" target="_blank" class="text-decoration-none">
              <img src="img/social-telegram.svg" height="24" width="24" alt="Telegram" class="mx-1">
            </a>
            <a href="https://x.com/puredarwin" target="_blank" class="text-decoration-none">
              <img src="img/social-x.svg" height="22" width="22" alt="X (Previously Twitter)" class="mx-1">
            </a>
        </div>
      </div>
      <div class="col-12 col-lg-4 pb-4">
        <div class="bg-white px-4 py-3 rounded feature-card">
          <img src="img/homepage/preferences-desktop-locale.png" height="80px;">
          <h3>Status</h3>
          <p>PureDarwin is progressing steadily, with ongoing research behind the scenes. There's no GUI yet, and
            the system remains minimal, but key foundations are being built for future updates.</p>
        </div>
      </div>
      <div class="col-12 col-lg-4 pb-4">
        <div class="bg-white px-4 py-3 rounded feature-card">
          <img src="img/homepage/utilities-sdk.png" height="80px;">
          <h3>Native SDK</h3>
          <p>An SDK that is native of an Apple release modified to target PureDarwin. We are working on a modified
            XNU kernel with additional BSD/POSIX features that don’t require us to rely on Apple’s closed sources.
          </p>
          <button type="button" class="btn btn-outline-secondary rounded-pill btn-sm mb-2" disabled>Coming
            Later</button>
        </div>
      </div>
    </div>
  </div>
</div>

News

This category contains the latest news and an archive of old news.

Remembering Cliff Sekel

January 3, 2026 — “The PureDarwin project has lost its leader.”

Support Cliff Sekel

February 24, 2025 — “PureDarwin’s Lead Developer; A Passionate Cybersecurity Architect and Open Source Champion”

A New Direction

November 3, 2024 — “Short Term and Long Term Goals”

Release: PD 17.4 Test Build

July 1, 2018 — “This is not a full OS like PureDarwin Xmas was, as Apple have closed down a lot of core components, we the community have to pick up the slack.”

News Archive

Looking for older news? You’ll find it here.

Remembering Cliff Sekel (InsaneDarwin)

January 3, 2026 - PD-Team

The PureDarwin project has lost its leader.

Cliff Sekel, known throughout the community as InsaneDarwin, passed away in November 2025. For many years, and unequivocally in its most recent era, Cliff was the leader of the PureDarwin project and the steward of its community. He was the person who kept the project alive when it would have been easy (and understandable) to let it quietly disappear.

PureDarwin exists today because Cliff refused to let it die.

Leadership Through Action

Cliff did not lead by title alone. He led by doing the hardest work in the project: untangling incomplete source releases, understanding undocumented system behavior, and pushing forward despite the reality that modern Darwin is no longer fully open.

Under Cliff’s leadership, PureDarwin produced its first real, bootable build in many years — PureDarwin 17.4 — marking a turning point from archival effort to living system. That build was not the result of a single patch or workaround, but of sustained, system-level understanding and careful integration across kernel and build tooling. It was by no means ready to use by end-users, but proof to the FOSS community that the last open-source remnants of Darwin could still be turned into a functional operating system.

Direct Engagement with Apple

Cliff was not advocating from the sidelines. For years until his passing he engaged directly with Apple engineers and developers to try and get Apple to open-source important components to make Darwin viable again.

His advocacy around missing components, particularly in networking and system libraries, came from firsthand knowledge, not speculation. While not all of those components were ultimately open-sourced, his efforts helped define the boundaries PureDarwin had to navigate and influenced how the project approached re-implementation and long-term viability.

A Champion of Free and Open Systems

At his core, Cliff was a Free and Open Source Software advocate. He believed deeply that systems should be understandable, inspectable, and buildable by the people who run them. PureDarwin was a challenge to him, although not in the sense of an academic exercise or nostalgia project. It was the belief that Darwin deserved to exist outside of proprietary walls.

He was drawn to hard problems. The harder the system, the more motivated he became to understand it fully. Missing sources, opaque binaries, and shifting interfaces were challenges to be solved, not excuses to stop.

A Community Held Together by One Person

Beyond code, Cliff held the PureDarwin community together. He answered questions, mentored contributors, curated repositories, and kept institutional knowledge alive. For many, he was the first point of contact and the final authority — not because he demanded it, but because he earned trust through competence and consistency.

PureDarwin was not just something he worked on. It was something he carried.

Continuing His Work

Cliff Sekel leaves behind more than repositories and build scripts. He leaves behind a revived project, a working system, and a community that once again believes PureDarwin is possible.

Honoring his legacy means continuing the work with the same care, patience, and insistence on understanding that defined his leadership.

Thank you, Cliff. For the project you rebuilt, for the community you led, and for showing us that even the hardest problems are worth facing.

— The PureDarwin Project

Support Cliff Sekel: PureDarwin’s Lead Developer

February 24, 2025 - PD-Team

Meet Cliff

Meet Cliff Sekel aka InSaneDarwin on most platforms, a Senior Cybersecurity Architect with a deep passion for open-source software, security, and innovation. By day, Cliff works full-time in the cybersecurity industry, ensuring systems remain safe and resilient. By night (and often in the precious moments in between), he dedicates himself to PureDarwin, an open-source OS project that brings the power of Apple’s Darwin to the broader community.

But beyond his professional and open-source contributions, Cliff is also a devoted husband and a loving father of three young children. Every moment outside of work and coding is spent with his beautiful wife Kaitlynn and their little ones (Alex, Nick and Mateo) cherishing the time they have together.

Tragically, Cliff is also facing one of the toughest battles of his life—Stage 4 Colon Cancer. Despite this, he remains committed to his health, his family, his work, and his contributions to the open-source world. However, as treatments become more intensive and time becomes more precious, he needs support.

Why Support Cliff?

Every contribution helps alleviate the burden of medical expenses and gives him more time to focus on what he loves: spending time with his family and advancing the PureDarwin project. His work has already pushed the boundaries of what’s possible in the open-source community, and with your help, he can continue making a lasting impact.

Your donation isn’t just about supporting one person—it’s about helping an entire community thrive. PureDarwin is a labor of love, and every dollar gives Cliff the freedom to continue building, innovating, and leaving behind a legacy that will inspire future generations of developers and open-source enthusiasts.

How You Can Help

If you believe in the power of open-source software, cybersecurity, or just want to support a brilliant mind in his fight, please consider donating through Cliff’s GitHub account. No amount is too small, and every contribution makes a difference.

Donate/Sponsor here: https://github.com/sponsors/csekel
Share this message to spread awareness

Thank You

From the bottom of our hearts, thank you for your support. Let’s help Cliff keep doing what he loves and continue making the open-source world a better place.

A New Direction: Short Term and Long Term Goals

November 3, 2024 - KevDoy and InSaneDarwin (csekel)

The PureDarwin project, originally created to bring Apple’s open-source Darwin OS to more people, is heading in a fresh new direction with some clear short-term and long-term goals. These new plans are all about breathing new life into PureDarwin. In the short term, we’re focused on getting some solid basics in place with graphical interfaces using MATE Desktop and LightDM, so users can get a functional and accessible experience sooner rather than later. Looking further down the line, the long-term goals—shown in some early wireframes—are about creating a fully featured, polished desktop experience that’s easy to use and visually appealing. Plus, a new versioning system will make it clear how PureDarwin is progressing independently from Apple’s Darwin updates, making it easier for everyone to keep track. This refreshed direction sets PureDarwin up to grow from its roots into a user-centered operating system.

Update to Versioning Approach

To distinguish PureDarwin’s progression from Darwin’s, a new versioning system has been proposed:

• Old Format: PureDarwin Test Build 17.2

  • Structure: PureDarwin [Type of Build] [Darwin Version]

• New Format: PureDarwin 0.3.0 Alpha (Darwin 24)

  • Structure: PureDarwin [PureDarwin Version] [State (Alpha, Beta, Stable)] (Darwin [Darwin Version])

This update allows the team to communicate PureDarwin’s independent progress while providing users clarity on release maturity. This approach avoids confusion with outdated versions, like the “Xmas release” (based on Darwin 9 from 2007), which some users still request over more recent builds.

Short-Term Goals (S.T.)

Main Project Organization

• Identify additional community volunteers that would like to focus on a specific area of the project
• Clean and reorganize PureDarwin Repositories where required.
• Update Darwinbuild to work with Github and Meta’s xcbuild that was forked to PureDarwin to update and allow PureDarwin to build on itself.

Core OS - Kexts and Userland

• Build All Core Kexts that are required to allow PureDarwin to boot. (IONVMeFamily, DarwinACPIPlatform, etc)
• Finish updating CoreFoundation from the Swift 5.10 source code (the last true framework for CoreFoundation)
• Add Swift Core/Foundation to PureDarwin’s Base Image.

Design Focus:

• PureDarwin’s current focus is expanding support for graphical user interfaces, aiming for Wayland compatibility.
• The short-term goal concepts (attached below) target a familiar setup with MATE Desktop and LightDM for login management.
• The initial experience will be similar to a vanilla MATE installation, prioritizing usability and functionality to reach as many users as possible. This target allows the team to focus on foundational tasks needed to achieve a functional graphical environment.

Long-Term Goals (L.T.)

Core OS

• Build a proper installer that will integrate with Darwinbuild for continuous CI build and test process.
• Build PureDarwin on BSD/linux.
• More to add from Community!

Design Focus - Our Own Vision for UI Elements

• The long-term wireframes and mockups (attached below) illustrate a “blue sky” vision of a fully realized PureDarwin desktop environment.
• These designs outline the UI elements intended for a cohesive user experience, though specifics are not finalized.
• The wireframes reflect the aspirations for PureDarwin, showcasing what the user interface might eventually look like when developed. However, these are conceptually ambitious, not yet in development.

Note: The current focus remains on short-term objectives. While the wireframes serve as a guide for PureDarwin’s future, queries regarding these long-term goals or their completion timeline are discouraged at this stage.

Additional Goals

These goals may not be something in scope right at this time, but should be kept in mind for the distant future:

• API compatibility with macOS?
  • e.g. CoreGraphics, CoreDisplay, reimplementing public APIs and trying to cover for ones we don’t have headers for, so there’s some compatibility with macOS Apps.

Conclusion

With these new targets, the PureDarwin project is heading in an exciting direction, finally giving us the foundation to start building a roadmap for the future. These short-term goals and big-picture aspirations give us something solid to aim for and help shape where we’re going next. While it’s not perfect yet, we’re laying the groundwork and setting a clear direction that’s flexible enough to evolve as we go. The updated versioning system also makes it easier for everyone to follow along with PureDarwin’s progress. Altogether, this new focus brings a sense of purpose to the project and sets us up for a promising future.

Release: PureDarwin 17.4 Test Build for Developers

July 1, 2018 - InSaneDarwin (csekel) Clifford Sekel

Download

• This Test Build can be downloaded from here GitHub (vmdk).

VMDK

• To run this, first extract the image with xz (xz -d pd_17_4.vmdk.xz).

• Then, start the VMDK with QEMU: qemu-system-x86_64 -m 8192 -cpu Penryn -smp 2 -netdev user,id=network0 -device rtl8139,netdev=network0 -serial stdio -drive format=vmdk,file=pd_17_4.vmdk

ISO

• To run this, first extract the image with xz (xz -d pd_17_4.vmdk.xz).

• Then convert to VDMK to ISO qemu-img convert -f vmdk pd_17_4.vmdk -O raw pd_17_4.iso.

• Then, start the ISO with QEMU: qemu-system-x86_64 -m 8192 -cpu Penryn -smp 2 -netdev user,id=network0 -device rtl8139,netdev=network0 -serial stdio -drive format=raw,file=pd_17_4.iso

Notes

• This is not a full OS like PureDarwin Xmas was, as Apple have closed down a lot of core components, we the community have to pick up the slack.

• There is still a lot of work to be done but it can be completed if we band together. If you would like to view what’s on this VM please use Paragon VMDK mounter for macOS users, all other please see what you need to do to mount and read an hfs filesystem on your OS. You may also use this qemu-img convert -f vmdk pd_17_4.vmdk -O raw pd_17_4.iso

• Please do not ask us questions on how to run macOS applications and non-open source software on PureDarwin. If you want something to hack on, then this is it.

• We have not finished all the system/network_cmds. We built as much as we could without pulling headers from Apple’s Xcode SDK’s.

Projects

Libxpc/Launchd

PureFoundation

CoreFoundation

ddisnoted

DarwinBuild

Enoch Bootloader

To Do

• Finish out Family Driver Support(USB/SATA/NVME/AHCI/PD-APCIPlatform)
• Finish out System Commands(Reboot/Shutdown)
• Finish out the Networking
• Finish out the Multi-User

Credits

We would like to thank:

• Apple, Inc. for releasing Darwin as Open Source
• David Elliott for his work on boot-132
• The Chameleon team for their work on boot-132
• The xnu-dev team for their work on the XNU kernel
• Stuart Crook for his work on PureFoundation, ddisnoted and libxpc/launchd work
• Ethan Sheriff for his work on the libsystem-plaform and libxpc/launchd work
• William Kent for his work on the DarwinBuild upgrade
• Rafirafi for his work on Generic Platform and PDCrypto kexts
• Mac OS Forge for The DarwinBuild project

Contact Us!

Admins

• Ferdinand Klinzer - bart@pd-devs.org
• Clifford Sekel - insanedarwin@pd-devs.org

Core Dev’s

• Avi Saven - avisaven@pd-devs.org
• Ethan Sherriff - libsystem_ethan@pd-devs.org
• Stuart Cook - sjc@pd-devs.org
• William Kent - wjk@pd-devs.org

Documentation

Darwin is the open source operating system from Apple that forms the base for macOS, iOS, tvOS, etc.

PureDarwin is a community project to make Darwin more usable on its own (some people think of it as the informal successor to OpenDarwin).

One current goal of this project is to provide a useful bootable ISO of Darwin. Another goal of this project is to provide additional documentation. More…

Documentation Categories

• About
• Developers
• Users
• News

Regarding broken, outdated, or incomplete documentation content, we are in the process of fixing this as of October 2024. If you would like to contribute to documentation content please see the Wiki page.

Getting the code

Please visit the GitHub repository.

Credits

There are too many to thank, but here are some highlights:

• Apple, Inc. for releasing Darwin as Open Source 
• kvv and _wms for their continuing help
• Adam Baxter for finding a Gold Sponsor to provide a hosted Mac mini from MacStadium
• David Elliott for his work on boot-132
• The Chameleon team for their work on boot-132
• The xnu-dev team for their work on the XNU kernel
• Stuart Crook for his work on PureFoundation
• Guillaume Verdeau for his work on X.Org
• Rafirafi for his work on Generic Platform kexts
• Mac OS Forge 
• The DarwinBuild project 
• The MacPorts project
• The folks at #macosforge, #macports, #macdev, #opendarwin, #puredarwin, 
• Everyone else contributing to Darwin 

Notice

PureDarwin and the PureDarwin website are independent resources and are not affiliated with, endorsed by, or sponsored by Apple Inc. Apple, Macintosh, macOS, and related trademarks and logos are the property of Apple Inc., registered in the U.S. and other countries. Darwin (operating system) is licensed under the Apple Public Source License (APSL). All other trademarks are the property of their respective owners.

About

This page describes some part of the PureDarwin project and the motivation behind it, as well as how it relates to other projects.

Goals

The goal of the PureDarwin project is to make Darwin more usable for open source enthusiasts and developers by providing documentation and by enabling them to retrieve, understand, modify, build, and distribute Darwin.

Organization

The PureDarwin project is organized very informally at this stage. There are no official boards and committees. We are not interested in politics and personal agendas, just in smart concepts and quality code. Our team is loosely coupled by a common interest in Darwin and by upholding true Open Source spirit.

Status

As of 2024, PureDarwin remains an active open-source project aimed at making Darwin, the core of macOS, into a standalone operating system. The community is working on PureDarwin PD-17.4, a minimal system distributed primarily as a virtual machine disk (VMDK) that can run in environments like QEMU. This release focuses on providing a development platform independent of macOS components, but it lacks a GUI and has limited hardware and network driver support due to the absence of proprietary macOS parts.

While progress is steady, PureDarwin continues to depend on community contributions to address missing components and improve system usability. Documentation efforts are ongoing, and developers are encouraged to contribute on GitHub. A community discussion space on Discord is also available for support and collaboration.

Contributing

Like other open source projects, PureDarwin is looking for contributors for all aspects of the project.

The PureDarwin project is always looking for talented individuals to contribute to and join the project. To contribute to the PureDarwin project, you should first familiarize yourself with the contents of this wiki. You can also join the IRC discussion on the #puredarwin channel on irc.freenode.net or the Discord server and help each other. Contributions to the project can take various forms, from adding documentation to sending in patches and constructive feedback in the Issues section.

A non-exhaustive list of the fields where investigation has still not been done is available here.

Sponsors

Special thanks to MacStadium for sponsoring a hosted Mac mini. We would also like to thank GitHub for hosting this site and repository and, last but not least, Apple, Inc. for making Darwin available and especially for maintaining the DarwinBuild project.

Frequently asked questions

Why spend time on Darwin?

For learning and fun.

How does PureDarwin relate to the former OpenDarwin project?

Although some people have been seeing PureDarwin as the informal successor to OpenDarwin, there is no official relationship other than the fact that OpenDarwin and PureDarwin are both downstream Darwin projects. Also, it is no secret that PureDarwin would not exist if OpenDarwin had not closed down. Coming later in time, PureDarwin is in the fortunate position to be able to benefit from the valuable contributions that were rooted in the OpenDarwin project.

How does PureDarwin relate to the DarwinBuild project?

DarwinBuild is one of PureDarwin’s main upstream projects. 

What does the “Pure” in PureDarwin stand for?

Pure as in beer! It means that we just use components specifically released by Apple for use with Darwin, as well as other Open Source components (collectively called “upstream code”). Specifically, it means that we do not use any components from Mac OS X. It also means that we try to stay as close as possible to the “outside world” as in Mac OS X (e.g., regarding the choice of compilers, options, etc.). It does not mean, however, that we do not modify and add to the upstream code, to the extent that the respective licenses allow.

Where can I find an ISO image?

A ready-made VMware virtual machine is available from the LegacyDownloads page. This virtual machine contains an ISO that could be used on real hardware as well. It is a proof-of-concept of a minimal Darwin 9 system built from the DarwinBuild project. Please note that you need the latest VMware (Player 2.5, Fusion 2).

When do you plan to release a full ISO image?

Probably when the DarwinBuild project and the MacPorts project will be able to run on a mature PureDarwin release without any “impurities”.

PureDarwin Mascot

Read more: Hexley

APSL

Please obtain, read, and make sure you understand the full text of the APSL. For a quick first glance, here is an excerpt (emphasis added):

2. (...) Apple hereby grants You, (...) a world-wide, royalty-free, non-exclusive license (...) to do the following:
	2.1 Unmodified Code. 
	*You may (...) Externally Deploy verbatim, unmodified copies* of the Original Code, for commercial or non-commercial purposes, provided that in each instance:
		(a) You must retain (...) the *copyright and other proprietary notices* (...)
		(b) You must *include a copy of this License* (...) and You may not (...) alter or restrict this License (...)
	2.2 Modified Code. 
	*You may modify (...) and Externally Deploy Your Modifications* and Covered Code, for commercial or non-commercial purposes, provided that (...):
		(a) You must *satisfy all the conditions of Section 2.1* (...)
		(b) You must duplicate (...) the *notice in Exhibit A* in each file of the Source Code of all Your Modifications, and cause the modified files to carry prominent *notices stating that You changed the files and the date of any change*; and
		(c) If You Externally Deploy Your Modifications, You must *make Source Code* (...) *available* (...) under the terms set forth in this License, including the license grants set forth in Section 3 below (...).
	2.3 Distribution of Executable Versions. 
	(...) must include a prominent notice, in the code itself as well as in related documentation, stating that Source Code of the Covered Code is available under the terms of this License with *information on how and where to obtain* (...) *Source Code*.

3. Your Grants.
(...) You hereby *grant* (...) a non-exclusive, royalty-free, perpetual, irrevocable *license*, (...) of the same scope and extent as Apple's licenses under Sections 2.1 and 2.2 above.

4. Larger Works.
You *may create a Larger Work* by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. (...)

BinaryDrivers

Apple has been making available certain drivers in binary form under the Apple Binary License. Without these, Darwin as coming from Apple in its current form would not be usable (in fact, not even the XNU kernel could boot). However, third parties have been developing replacements for some of the key binary components, e.g., GenericPlatform-darwin10.zip.

Here is an incomplete list of such drivers. This is for quick reference only, please refer to official Apple documentation for authoritative information.

Darwin 10: MacOSForge

1. AppleUSBAudio.root.tar.gz

All found here! http://src.macosforge.org/Roots/10A432/

Darwin 9: MacOSForge

1. AppleACPIPlatform.root.tar.gz
2. AppleRTC.root.tar.gz
3. efiboot.root.tar.gz
4. GraphicsDrivers.root.tar.gz

Darwin 8: darwinx86-801.iso

1. ACard62xxM-4.tar.bz2
2. ACard67162-2.tar.bz2
3. ACard671xSCSI-4.tar.bz2
4. ACard6885M-2.tar.bz2
5. ACard68xxM-4.tar.bz2
6. ATTOExpressPCI-204.tar.bz2
7. Adaptec78XXSCSI-7.tar.bz2
8. AdaptecBuiltDrivers-6.tar.bz2
9. AirPortDriver2-350.5.tar.bz2
10. AppleACPIPlatform-39.tar.bz2
11. AppleBlower-104.0.1.tar.bz2
12. AppleBroadcom570X-200.2.11.tar.bz2
13. AppleCPUThermo-200.0.0.tar.bz2
14. AppleFCU-132.2.0.tar.bz2
15. AppleFPButton-105.0.1.tar.bz2
16. AppleFWAudio-113.4.2.tar.bz2
17. AppleFWOHCI-244.4.0.tar.bz2
18. AppleGossamerPE-202.0.1.tar.bz2
19. AppleHWClock-142.2.1.tar.bz2
20. AppleI2SModemFamily-112.3.2.tar.bz2
21. AppleIntel8254XEthernet-4.tar.bz2
22. AppleLED-200.0.2.tar.bz2
23. AppleLM87-105.0.1.tar.bz2
24. AppleLMUController-121.3.2.tar.bz2
25. AppleLynx-162.4.0.tar.bz2
26. AppleMacRISC2PE-170.2.1.tar.bz2
27. AppleMacRISC4PE-160.0.9.tar.bz2
28. ApplePMU-220.0.1.tar.bz2
29. AppleRTL8169Ethernet-1.tar.bz2
30. AppleSEP-101.0.1.tar.bz2
31. AppleSMU-106.0.3.tar.bz2
32. AppleStorageDrivers-140.1.3.tar.bz2
33. Apple_DEC21x4Ethernet-131.4.2.tar.bz2
34. GraphicsDrivers-4.0.24.tar.bz2
35. IOATABlockStorage-141.0.3.tar.bz2
36. IOSCSIArchitectureModelFamily-140.1.7.tar.bz2

Darwin 6: darwinx86-602.iso

ls /Volumes/Darwinx86/System/Installation/apple_binary

1. ACard62xxM.kext.tar.gz
2. ACard671xSCSI.kext.tar.gz
3. ACard68xxM.kext.tar.gz
4. ATIRadeon.kext.tar.gz
5. ATIRadeon8500.kext.tar.gz
6. ATIRadeon8500DVDDriver.bundle.tar.gz
7. ATIRadeon8500GA.plugin.tar.gz
8. ATIRadeon8500GLDriver.bundle.tar.gz
9. ATIRadeonDVDDriver.bundle.tar.gz
10. ATIRadeonGA.plugin.tar.gz
11. ATIRadeonGLDriver.bundle.tar.gz
12. ATIRage128.kext.tar.gz
13. ATIRage128DVDDriver.bundle.tar.gz
14. ATIRage128GA.plugin.tar.gz
15. ATIRage128GLDriver.bundle.tar.gz
16. ATIRagePro.kext.tar.gz
17. ATIRageProGA.plugin.tar.gz
18. ATTOExpressPCI.kext.tar.gz
19. Adaptec290X-2930.kext.tar.gz
20. Adaptec29160x.kext.tar.gz
21. Adaptec39160.kext.tar.gz
22. Adaptec78XXSCSI.kext.tar.gz
23. AppleAirPort.kext.tar.gz
24. AppleAirPortFW.kext.tar.gz
25. AppleAltiVecDVDDriver.bundle.tar.gz
26. AppleBCM5701Ethernet.kext.tar.gz
27. AppleCPUThermo.kext.tar.gz
28. AppleCarolina.kext.tar.gz
29. AppleCuda.kext.tar.gz
30. AppleFPButton.kext.tar.gz
31. AppleFWAudio.kext.tar.gz
32. AppleFWOHCI.kext.tar.gz
33. AppleFan.kext.tar.gz
34. AppleGPIO.kext.tar.gz
35. AppleGossamerPE.kext.tar.gz
36. AppleHWClock.kext.tar.gz
37. AppleKauaiATA.kext.tar.gz
38. AppleKeyswitch.kext.tar.gz
39. AppleKiwiATA.kext.tar.gz
40. AppleKiwiRoot.kext.tar.gz
41. AppleLED.kext.tar.gz
42. AppleLM87.kext.tar.gz
43. AppleLynx.kext.tar.gz
44. AppleMIDIFWDriver.plugin.tar.gz
45. AppleMIDISerialDriver.plugin.tar.gz
46. AppleMIDIUSBDriver.plugin.tar.gz
47. AppleMLANAudio.kext.tar.gz
48. AppleNDRV.tar.gz
49. AppleOnboardDisplay.kext.tar.gz
50. ApplePCCard16ATA.kext.tar.gz
51. ApplePCCardATA.kext.tar.gz
52. ApplePMU.kext.tar.gz
53. AppleRAID.kext.tar.gz
54. AppleRS574Serial.kext.tar.gz
55. AppleSCCIrDA.kext.tar.gz
56. AppleStorageDrivers.kext.tar.gz
57. AppleThermal.kext.tar.gz
58. AppleUSBDisplays.kext.tar.gz
59. AppleUSBIrDA.kext.tar.gz
60. Apple_DEC21x4Ethernet.kext.tar.gz
61. DCPModemSupport.kext.tar.gz
62. GeForce2MX.kext.tar.gz
63. GeForce2MXGA.plugin.tar.gz
64. GeForce2MXGLDriver.bundle.tar.gz
65. GeForce3.kext.tar.gz
66. GeForce3GA.plugin.tar.gz
67. GeForce3GLDriver.bundle.tar.gz
68. I2CGPIO.kext.tar.gz
69. ICAClassicNotSeizeDriver.kext.tar.gz
70. ICAFWKodakProDriver.kext.tar.gz
71. IOBluetoothFamily.kext.tar.gz
72. IOHDIXController.kext.tar.gz
73. IOSCSIParallelFamily.kext.tar.gz
74. InternalModemSupport.kext.tar.gz
75. InternalUSBModem.kext.tar.gz
76. MacIOGPIO.kext.tar.gz
77. NVDANV10Hal.kext.tar.gz
78. NVDANV20Hal.kext.tar.gz
79. NVDAResman.kext.tar.gz
80. TRANS.TBL
81. UltraTek100.kext.tar.gz
82. UltraTek133.kext.tar.gz
83. UltraTek33.kext.tar.gz
84. UltraTek66.kext.tar.gz
85. cddafs.kext.tar.gz
86. udf.kext.tar.gz

Contact us

This PureDarwin wiki is a community effort. The PureDarwin team can best be reached at 

• GitHub issues is the preferred way of communication
• The Discord server has many active members, and 100+ total members
• #puredarwinon irc.freenode.net

Downloads

To the best of our knowledge, we followed all licenses that apply. Please contact us if you believe otherwise and we will work immediately to correct the situation.

See the PureDarwin download page on SourceForge for mirrors.

See the GitHub repository for source code, stuff and scripts.

Also see PureDarwin Xmas and PureDarwin Nano.

Hexley

Hexley is not Huxley but the Darwin’s unofficial mascot.

*Hexley DarwinOS Mascot Copyright 2000 by Jon Hooper. * All Rights Reserved.

Visit http://www.hexley.com/ for the full story.

Hexley has also appeared in supertuxkart.

Legal

This part is as complex as the technical one. The PureDarwin project tries and tends to respect as much as possible the legal aspects involved and avoid conflicts, however this process must be at least improved, and at best maintained. Feel free to contact us if you would like to give advice or contribute.

Community project

Please understand that PureDarwin is a community project. It is not affiliated with Apple, Inc.

Licensed material

Substantial parts of this project are bound to the following licenses. Please make sure that you fully understand them and comply with them before you begin to use or contribute to any software or information provided by the PureDarwin project. Please check the documentation that comes with each individual part.

• Apple Public Source License (APSL) (excerpt)
• Apple Binary Driver Software License Agreement
• VMware General Terms
• Other licensed Open Source material, see /usr/local/OpenSourceLicenses for license information

Original material

Material originally engineered within the PureDarwin project is licensed under the BSD license as follows, unless specifically stated otherwise in the respective files or directories:

/*-
 * Copyright (c) 2007-2009 The PureDarwin Project.
 * All rights reserved.
 *
 * @LICENSE_HEADER_START@
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
 * IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
 * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
 * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
 * NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 * @LICENSE_HEADER_END@
*/

We kindly suggest (but do not require) that you contribute any modifications back to the project.

Hexley

The Hexley mascot for Darwin is Jon Hooper’s copyright since 2000. It is used with permission from Jon Hooper.

Being “open”

Please feel free to contribute and discuss.

What openness means to us…

• We follow any licenses imposed on the upstream software we use
• The code and patches we produce (our “original contributions”) are Open Source, using the BSD license wherever possible
• We do not accept any patches or contributions that do not meet the above criteria
• From Wiktionary
  • (computing, education) degree of accessibility to view, use, and modify in a shared environment with legal rights generally held in common and preventing proprietary restrictions on the right of others to continue viewing, using, modifying and sharing.
  • (systems theory) The degree to which a system operates with distinct boundaries across which exchange occurs capable of inducing change in the system while maintaining the boundaries themselves.

And what it doesn’t mean to us…

• We don’t think that every piece of closed-source software is evil in all cases (read: as long as it works, we are fine with using small portions of licensed Apple closed-source software if no alternative exists)
• Open Source is not “the” solution, but “a” solution or at least “a part of the” solution.

Screenshots

PureDarwin 9 running XFCE from MacPorts

PureDarwin Nano running on a MacBook Pro

PureDarwin Nano running on a PC

PureDarwin Nano running on a MacBook

Enlightenment 17 (0.16.999.037) on PureDarwin on VMware Fusion 2.0b

Fluxbox 1.1.0.1 on PureDarwin running on VMware Fusion 2.02b

Window Maker 0.92.0 on PureDarwin running on VMware Fusion 2.02b

wmii 3.1 on PureDarwin running on VMware Fusion 2.02b

PureDarwin Nano running on VMware Player 2.5 on Ubuntu

PureDarwin Nano running on VMware Player 2.5.1 on Windows

PureDarwin Nano running on VMware Fusion 2.02b on Leopard 10.5.5

PureDarwin Nano running on VMware Player 2.5 on Fedora 8

PureDarwin 9F_20081219 on VMware Fusion 2

PureDarwin 9 running gtk-demo via TightVNC

Status

See the changelog for the history of commits made on Github.

PureDarwin is currently working on AHCI/NVMe and eMMC family/drivers for Darwin, only they will not support/work on Apple’s macOS. We have a PoC (Proof of Concept) of a PureDarwin 17.6 QEMU image that’s based on Apple’s open source code of macOS 10.13.3 that’s only currently available to devs who join our IRC channel (#puredarwin on Freenode).

Update: Hey, guys, we’re still moving along. We’ll be providing an SDK that is native of an Apple release on opensource.apple.com and a modified version that is PureDarwin targeted, as we are working on a modified XNU kernel with some other BSD/POSIX features that don’t require us to rely on Apple’s closed sources that they’ll never release.

We are looking for supporters/coders that can help bring about faster development of PureDarwin while showing Apple that there is still a community of open source Darwin supporters that would like to see more open-ness from them, whether it be from them releasing binary drivers for our use as they once did, or open source projects like libxpc/launchd again.

PureDarwin Progress and Research

We’ve just moved to Apple’s latest code of 10.12.4

This is a living Document that is always being updated!

Currently the project is still moving forward

Current Projects being actively worked on

Working on ACHI Family and Kext work for Darwin use only it will have private headers that will be built into the Kext. Working on CoreFoundation code pulled from latest https://github.com/apple/swift-corelibs-foundation/tree/master/CoreFoundation

Completed Lib’s

Thanks to Ethan we have dyld, libdispatch and libsystem patches along with libplatform project code and built Roots.

Projects Still to be worked on

Port/Upgrade Mac OSX 10.8.4 UsbFamily to macOS 10.12.4 as UsbFamily no longer open sourced (Unless we know some apple people to talk too)

Example of command to compile libfirehose_kernel.a needed for XNU building on OSX

Using Darwinbuild

sudo darwinbuild -nochroot -target=libfirehose_kernel libdispatch

** INSTALL SUCCEEDED **

 BUILD TIME: 0h 0m 1s
EXIT STATUS: 0
libdispatch - 4 files registered.
                                         40755 0 0 0 ./usr
                                         40755 0 0 0 ./usr/local
                                         40755 0 0 0 ./usr/local/include
                                         40755 0 0 0 ./usr/local/include/kernel
                                         40755 0 0 0 ./usr/local/include/kernel/os
ee27353e97833d9a61d67724b5330e74634f7fce 100644 0 0 3273 ./usr/local/include/kernel/os/firehose_buffer_private.h
                                         40755 0 0 0 ./usr/local/lib
                                         40755 0 0 0 ./usr/local/lib/kernel
a99bc86fe2a3a0b967c9da72102ea6dc2ad7b2a1 100644 0 0 36184 ./usr/local/lib/kernel/libfirehose_kernel.a
5829603c6ba1eecb57e05272440364ab63712aad 100644 0 0 37464 ./usr/local/lib/kernel/libfirehose_kernel_debug.a
a99bc86fe2a3a0b967c9da72102ea6dc2ad7b2a1 100644 0 0 36184 ./usr/local/lib/kernel/libfirehose_kernel_profile.a

Using Xcodebuild

xcodebuild -sdk macosx10.12 install -target=libfirehose_kernel -project=libdispatch.xcodeproj
The following build commands
	build/Release/libfirehose_server.a
	build/Release/libfirehose_server_profile.a
	build/Release/libfirehose_server_debug.a

Built Roots with OpenSource Headers added into the macosx10.12.sdk under Xcode This plist https://github.com/PureDarwin/PureDarwin-System-Plist/blob/master/16D32pd1.plist This Modified Darwinbuild for macOS(Database code sqlite changes) https://github.com/PureDarwin/darwinbuild

libplatform has been built Ethan rocks!

** INSTALL SUCCEEDED **

 BUILD TIME: 0h 0m 2s
EXIT STATUS: 0
libplatform - 27 files registered.
                                         40755 0 0 0 ./usr
                                         40755 0 0 0 ./usr/include
3de726adedb1c184243d04eee2528368742fb51f 100644 0 0 5682 ./usr/include/_simple.h
                                         40755 0 0 0 ./usr/include/libkern
d699b626d16c8271fdef328f1da84f95946bb2f2 100644 0 0 1651 ./usr/include/libkern/OSAtomic.h
58481d3f98392795650329fc456e51f087edfb91 100644 0 0 43094 ./usr/include/libkern/OSAtomicDeprecated.h
c260f5ba655dc7c1b6ee5e11f7bf7a9cc29923ed 100644 0 0 6662 ./usr/include/libkern/OSAtomicQueue.h
cfe2e5f61f05eced206eaab55aa1e6dcd8b9a4f0 100644 0 0 2344 ./usr/include/libkern/OSCacheControl.h
3a1e10e4fcb8781e68dc30001a1ed51017c37437 100644 0 0 6632 ./usr/include/libkern/OSSpinLockDeprecated.h
                                         40755 0 0 0 ./usr/include/os
29ae8f4a130f58f1eba6ab291c738fcb6133d67e 100644 0 0 2614 ./usr/include/os/alloc_once_impl.h
8d0493ad759089903983797cd90b2b41172491be 100644 0 0 7167 ./usr/include/os/base.h
254ca8737698de8ffcb9b64a9497d9eee2b41d07 100644 0 0 1138 ./usr/include/os/base_private.h
                                         40755 0 0 0 ./usr/include/os/internal
da4bc957cdea68419e06953574bc25d65641d4b7 100644 0 0 9987 ./usr/include/os/internal/atomic.h
6f069e852ff3d00bfaf31628e2bc2d5e89303096 100644 0 0 1678 ./usr/include/os/internal/crashlog.h
3cc65922de5049d8345bb504553bf3661f0db1fb 100644 0 0 1785 ./usr/include/os/internal/internal_shared.h
17e697b9c6e75dd650cdaa2965e82939ad0b94e1 100644 0 0 4382 ./usr/include/os/lock.h
6dd615291abe72e916ff06bce4de199a9b52f100 100644 0 0 20651 ./usr/include/os/lock_private.h
77b1c40e6004be6fdef3bd29eae6e0e4af888944 100644 0 0 1851 ./usr/include/os/once_private.h
3dde0d4b8cef814c45bcdf34bd1a6ff548abb679 100644 0 0 2401 ./usr/include/os/semaphore_private.h
                                         40755 0 0 0 ./usr/include/platform
5e3181377f01dc0b30b366d4ba3019703e1e2566 100644 0 0 2368 ./usr/include/platform/compat.h
69e27b55c2d1de6aeb5a852cddb230f849701b3a 100644 0 0 12484 ./usr/include/platform/introspection_private.h
b108c703fa83cf3145743844646ea977dd2dd732 100644 0 0 3127 ./usr/include/platform/string.h
79d7c60b7fe04d405d6b053e357dad4e8915e59d 100644 0 0 3139 ./usr/include/setjmp.h
2b808d6255928e200b4e7a15a105ee63b09bf658 100644 0 0 2054 ./usr/include/ucontext.h
                                         40755 0 0 0 ./usr/lib
                                         40755 0 0 0 ./usr/lib/system
da39a3ee5e6b4b0d3255bfef95601890afd80709 100755 0 0 38548 ./usr/lib/system/libsystem_platform.dylib
                                         40755 0 0 0 ./usr/local
                                         40755 0 0 0 ./usr/local/include
                                         40755 0 0 0 ./usr/local/include/libkern
d00e308ffee156e164dd5c76f63f2f8fa77647a3 100644 0 0 1410 ./usr/local/include/libkern/OSAtomic.h
e7ad001908cbd437e48a9fd347a4399bd12e1f84 100644 0 0 123 ./usr/local/include/libkern/module.modulemap
                                         40755 0 0 0 ./usr/local/include/os
cec7efca5a198fc2f1cb06ca7201c678be33d1e5 100644 0 0 3892 ./usr/local/include/os/internal.h
fdb5862c640f6d779e8bb91c2546378714bebbdf 100644 0 0 2712 ./usr/local/include/os/internal_asm.h
f86466e8cb0ee71de4173b8ef15b3786024d9eb9 100644 0 0 2486 ./usr/local/include/os/yield.h

#Roots built so far being updated daily*

InSanes-iMac:InSaneDarwin insane$ ls -alh Packages/ | grep .root.tar.gz
-rw-r--r--    1 root    admin   9.2K Apr 18 11:46 AppleAPIC.root.tar.gz
-rw-r--r--    1 root    admin   8.4K Apr 11 16:38 AppleFileSystemDriver.root.tar.gz
-rw-r--r--    1 root    admin    27K Apr 18 11:46 AppleIntelPIIXATA.root.tar.gz
-rw-r--r--    1 root    admin   814B Apr 11 16:38 AvailabilityVersions.root.tar.gz
-rw-r--r--    1 root    admin    24M Apr 11 16:38 BerkeleyDB.root.tar.gz
-rw-r--r--    1 root    admin   605K Apr 11 16:38 CrackLib.root.tar.gz
-rw-r--r--    1 root    admin   3.9K Apr 11 16:38 Csu.root.tar.gz
-rw-r--r--    1 root    admin    12M Apr 11 16:38 ICU.root.tar.gz
-rw-r--r--    1 root    admin    17K Apr 18 11:46 IOACPIFamily.root.tar.gz
-rw-r--r--    1 root    admin    58K Apr 11 16:38 IOATAFamily.root.tar.gz
-rw-r--r--    1 root    admin   141K Apr 11 16:38 IOAudioFamily.root.tar.gz
-rw-r--r--    1 root    admin    26K Apr 11 16:38 IOBDStorageFamily.root.tar.gz
-rw-r--r--    1 root    admin    38K Apr 11 16:38 IOCDStorageFamily.root.tar.gz
-rw-r--r--    1 root    admin    28K Apr 11 16:38 IODVDStorageFamily.root.tar.gz
-rw-r--r--    1 root    admin    74K Apr 11 16:38 IOFireWireAVC.root.tar.gz
-rw-r--r--    1 root    admin   324K Apr 11 16:38 IOFireWireFamily.root.tar.gz
-rw-r--r--    1 root    admin    58K Apr 11 16:38 IOFireWireIP.root.tar.gz
-rw-r--r--    1 root    admin    87K Apr 11 16:38 IOFireWireSBP2.root.tar.gz
-rw-r--r--    1 root    admin   163K Apr 11 16:38 IONetworkingFamily.root.tar.gz
-rw-r--r--    1 root    admin   122K Apr 11 16:38 IOPCIFamily.root.tar.gz
-rw-r--r--    1 root    admin    33K Apr 11 16:38 IOSerialFamily.root.tar.gz
-rw-r--r--    1 root    admin   109K Apr 11 16:38 IOStorageFamily.root.tar.gz
-rw-r--r--    1 root    admin    61K Apr 20 01:31 Libc.root.tar.gz
-rw-r--r--    1 root    admin   378K Apr 21 13:03 Libinfo.root.tar.gz
-rw-r--r--    1 root    admin    34K Apr 11 16:38 Librpcsvc.root.tar.gz
-rw-r--r--    1 root    admin   1.4K Apr 11 16:38 Liby.root.tar.gz
-rw-r--r--    1 root    admin    40K Apr 11 16:38 OpenPAM.root.tar.gz
-rw-r--r--    1 root    admin    91K Apr 11 16:38 SmartcardCCID.root.tar.gz
-rw-r--r--    1 root    admin   1.2M Apr 11 16:38 TimeZoneData.root.tar.gz
-rw-r--r--    1 root    admin   2.0K Apr 11 16:38 UserNotification.root.tar.gz
-rw-r--r--    1 root    admin   905K Apr 11 16:38 WebInspectorUI.root.tar.gz
-rw-r--r--    1 root    admin   160K Apr 11 16:38 adv_cmds.root.tar.gz
-rw-r--r--    1 root    admin   389K Apr 11 16:38 apr.root.tar.gz
-rw-r--r--    1 root    admin    18K Apr 11 16:38 architecture.root.tar.gz
-rw-r--r--    1 root    admin    51K Apr 11 16:38 awk.root.tar.gz
-rw-r--r--    1 root    admin   2.2M Apr 19 22:27 bash.root.tar.gz
-rw-r--r--    1 root    admin    17K Apr 11 16:38 basic_cmds.root.tar.gz
-rw-r--r--    1 root    admin   5.7M Apr 11 16:39 bind9.root.tar.gz
-rw-r--r--    1 root    admin   271K Apr 11 16:39 bmalloc.root.tar.gz
-rw-r--r--    1 root    admin    74K Apr 11 16:39 bootstrap_cmds.root.tar.gz
-rw-r--r--    1 root    admin    60K Apr 11 16:39 bzip2.root.tar.gz
-rw-r--r--    1 root    admin    53K Apr 11 16:39 copyfile.root.tar.gz
-rw-r--r--    1 root    admin   4.6K Apr 11 16:39 coreTLS.root.tar.gz
-rw-r--r--    1 root    admin   6.8M Apr 11 16:39 cups.root.tar.gz
-rw-r--r--    1 root    admin   568K Apr 11 16:39 curl.root.tar.gz
-rw-r--r--    1 root    admin   213K Apr 11 16:39 cxxfilt.root.tar.gz
-rw-r--r--    1 root    admin    84K Apr 11 16:39 diskdev_cmds.root.tar.gz
-rw-r--r--    1 root    admin    11K Apr 11 16:39 disklabel.root.tar.gz
-rw-r--r--    1 root    admin    23K Apr 11 16:39 doc_cmds.root.tar.gz
-rw-r--r--    1 root    admin   193K Apr 19 22:27 dyld.root.tar.gz
-rw-r--r--    1 root    admin    32M Apr 11 16:39 emacs.root.tar.gz
-rw-r--r--    1 root    admin    66K Apr 11 16:39 expat.root.tar.gz
-rw-r--r--    1 root    admin   606K Apr 11 16:39 file.root.tar.gz
-rw-r--r--    1 root    admin   254K Apr 11 16:39 file_cmds.root.tar.gz
-rw-r--r--    1 root    admin   1.4M Apr 11 16:39 files.root.tar.gz
-rw-r--r--    1 root    admin   148K Apr 11 16:39 gnudiff.root.tar.gz
-rw-r--r--    1 root    admin    49K Apr 11 16:39 gnuserv.root.tar.gz
-rw-r--r--    1 root    admin   155K Apr 11 16:39 gnutar.root.tar.gz
-rw-r--r--    1 root    admin    60K Apr 11 16:39 gpatch.root.tar.gz
-rw-r--r--    1 root    admin    18K Apr 11 16:39 gpt.root.tar.gz
-rw-r--r--    1 root    admin   2.5M Apr 11 16:39 groff.root.tar.gz
-rw-r--r--    1 root    admin   544K Apr 11 16:39 hfs.root.tar.gz
-rw-r--r--    1 root    admin   148K Apr 11 16:39 hunspell.root.tar.gz
-rw-r--r--    1 root    admin   2.8K Apr 11 16:39 keymgr.root.tar.gz
-rw-r--r--    1 root    admin   696K Apr 11 16:39 ksh.root.tar.gz
-rw-r--r--    1 root    admin    85K Apr 11 16:39 less.root.tar.gz
-rw-r--r--    1 root    admin   7.2K Apr 11 16:39 libauto.root.tar.gz
-rw-r--r--    1 root    admin   5.7K Apr 20 20:25 libcoreservices.root.tar.gz
-rw-r--r--    1 root    admin   1.3M Apr 21 13:03 libdispatch.root.tar.gz
-rw-r--r--    1 root    admin    92K Apr 11 16:39 libedit.root.tar.gz
-rw-r--r--    1 root    admin   369K Apr 11 16:39 libevent.root.tar.gz
-rw-r--r--    1 root    admin    15K Apr 11 16:39 libffi.root.tar.gz
-rw-r--r--    1 root    admin    40K Apr 12 06:17 libfirehose_kernel.root.tar.gz
-rw-r--r--    1 root    admin   147K Apr 12 06:17 libfirehose_server.root.tar.gz
-rw-r--r--    1 root    admin   4.4K Apr 11 16:39 libgcc.root.tar.gz
-rw-r--r--    1 root    admin   747K Apr 11 16:39 libiconv.root.tar.gz
-rw-r--r--    1 root    admin    33K Apr 19 22:27 libkxld.root.tar.gz
-rw-r--r--    1 root    admin   405K Apr 21 00:58 libmalloc.root.tar.gz
-rw-r--r--    1 root    admin    44K Apr 18 13:11 libplatform.root.tar.gz
-rw-r--r--    1 root    admin   104K Apr 12 01:49 libplatform_dyld.root.tar.gz
-rw-r--r--    1 root    admin   104K Apr 12 01:49 libplatform_static.root.tar.gz
-rw-r--r--    1 root    admin    27K Apr 12 08:35 libpthread.root.tar.gz
-rw-r--r--    1 root    admin    33K Apr 12 08:45 libpthread_dyld_static.root.tar.gz
-rw-r--r--    1 root    admin    83K Apr 12 08:45 libpthread_eOS_static.root.tar.gz
-rw-r--r--    1 root    admin    83K Apr 12 08:45 libpthread_generic_static.root.tar.gz
-rw-r--r--    1 root    admin    98K Apr 11 16:39 libresolv.root.tar.gz
-rw-r--r--    1 root    admin   871K Apr 11 16:39 libstdcxx.root.tar.gz
-rw-r--r--    1 root    admin    20K Apr 11 16:39 libtelnet.root.tar.gz
-rw-r--r--    1 root    admin    31K Apr 11 16:39 libutil.root.tar.gz
-rw-r--r--    1 root    admin   648K Apr 11 16:39 libxml2.root.tar.gz
-rw-r--r--    1 root    admin   165K Apr 11 16:39 libxslt.root.tar.gz
-rw-r--r--    1 root    admin    89K Apr 11 16:39 lukemftp.root.tar.gz
-rw-r--r--    1 root    admin    83K Apr 11 16:39 lukemftpd.root.tar.gz
-rw-r--r--    1 root    admin    69K Apr 11 16:39 mail_cmds.root.tar.gz
-rw-r--r--    1 root    admin   122K Apr 11 16:39 misc_cmds.root.tar.gz
-rw-r--r--    1 root    admin    30K Apr 11 16:39 modemccl.root.tar.gz
-rw-r--r--    1 root    admin    78K Apr 11 16:39 msdosfs.root.tar.gz
-rw-r--r--    1 root    admin    82K Apr 11 16:39 nano.root.tar.gz
-rw-r--r--    1 root    admin   822K Apr 11 16:39 ncurses.root.tar.gz
-rw-r--r--    1 root    admin   237K Apr 11 16:39 ntfs.root.tar.gz
-rw-r--r--    1 root    admin    20K Apr 11 16:39 patch_cmds.root.tar.gz
-rw-r--r--    1 root    admin   507K Apr 11 16:39 pcre.root.tar.gz
-rw-r--r--    1 root    admin    27K Apr 11 16:39 pdisk.root.tar.gz
-rw-r--r--    1 root    admin    27K Apr 12 08:35 pthread_kext.root.tar.gz
-rw-r--r--    1 root    admin    16K Apr 11 16:39 removefile.root.tar.gz
-rw-r--r--    1 root    admin   208K Apr 11 16:39 rsync.root.tar.gz
-rw-r--r--    1 root    admin   307K Apr 11 16:39 sudo.root.tar.gz
-rw-r--r--    1 root    admin   899K Apr 11 16:39 swig.root.tar.gz
-rw-r--r--    1 root    admin   135K Apr 19 22:27 syslog.root.tar.gz
-rw-r--r--    1 root    admin   2.8K Apr 11 16:39 system_config.root.tar.gz
-rw-r--r--    1 root    admin   245K Apr 11 16:39 tcsh.root.tar.gz
-rw-r--r--    1 root    admin   912K Apr 11 16:39 texinfo.root.tar.gz
-rw-r--r--    1 root    admin   251K Apr 11 16:39 text_cmds.root.tar.gz
-rw-r--r--    1 root    admin    56K Apr 11 16:39 top.root.tar.gz
-rw-r--r--    1 root    admin   7.1K Apr 11 16:39 usertemplate.root.tar.gz
-rw-r--r--    1 root    admin   581K Apr 11 16:39 uucp.root.tar.gz
-rw-r--r--    1 root    admin   7.3M Apr 11 16:39 vim.root.tar.gz
-rw-r--r--    1 root    admin   115K Apr 18 11:46 xar.root.tar.gz
-rw-r--r--    1 root    admin   8.1M Apr 19 22:27 xnu.root.tar.gz
-rw-r--r--    1 root    admin    75K Apr 12 06:28 zlib.root.tar.gz
-rw-r--r--    1 root    admin   2.1M Apr 11 16:39 zsh.root.tar.gz

Todos:

port libktrace and few others to Darwin.

Projects to look forward to on PureDarwin:

SwiftFoundation for Darwin

Darwin’s Own AHCI Family OpenSource

Darwin’s eMMC Family for both arm and x86_64 (great for those smaller embedded internal SSD’s)

Darwin’s XNU Arm port

Team

We are a welcoming community of open source enthusiasts and developers. Everyone is invited to join the PureDarwin project, as long as you agree to promote true open source spirit and abide by any licenses that apply. Unix knowledge is a must at this point.

If you would like to get a puredarwin.org account, please visit #puredarwin on irc.freenode.net. Also, send an e-mail, including your full name, contact information and your desired PureDarwin username (ideally the same as your IRC nickname) to admin@puredarwin.org. 

If you like, you can also include information about your hardware so that we can coordinate testing better.

TODO

Would you like to help out with PureDarwin? Don’t know where to start? 

This page lists (from higher to lower layers, but non exhaustively) some of the areas where work is needed to make Darwin the truly world-class OS it should be.

Feedback

Feedback is crucial, in whatever form it takes; from the container to the content including the way of sending it.

Catalogue compatible hardware

If you’ve got PureDarwin to run somewhere - either in a VM we don’t know about, or on a real piece of hardware - then please let us know so that we can add it to our compatible hardware page.

Test other applications

With the X window system up and running, PureDarwin becomes a very compatible BSD clone, meaning that it should run any of the wide range of software available for that platform. As an example, most of the pure binaries compiled through the MacPorts project can easily be copied into and used in a PureDarwin release. Let us know what you got running.

Complaints

It would be much appreciated if criticism is constructive.

Legal aspects

Help us to improve several legal aspects, including, non-exhaustively, how to handle intellectual property, trademarks, patents, copyright and licenses. What to provide? Where? How?

Packages and binary roots

Test available packages

The basic Darwin system as provided by Apple is made up of over 400 different packages. Many of these have been included in releases of PureDarwin (Xmas and Nano). Many more are available from http://src.macosforge.org. And they all need testing. We know this method is empiric but we simply need to know what works, and (more importantly) what doesn’t, so that we can focus our efforts there.

A particular interest at the moment is per example the high level web application stack: Apache, MySQL, and PHP (or lighttpd, rrdtool and postgresql, etc..). That also could be the other scripting languages as Python, Perl, Ruby… or also some more low level behavior via the use of DTrace per example. We haven’t had a chance to put them through their paces yet, so maybe you could try them and let us know.

Build missing packages

Not every Darwin project is available as a pre-built binary root. There’s a list of these ‘missing’ packages (about 80 in all) in the git repository (under projects/PureDarwinPackageDatabase/PackageLists in the file missing.txt). Some of these are known not to build.

Others are untested. If you succeed in building them, let us know so we can host a copy of the binary root for others and make them available for testing.

Device drivers

Locate and list available device drivers

Like all operating systems, Darwin will live or die by its hardware support.

There are a great many IOKit device drivers created by Apple and 3rd parties available. We first need to collect a list together, so that they can be tested and then bundled with future versions of PureDarwin. 

Notes: See the Network page, the KEXTs page, the Graphics page, the Binary drivers page, the ZFS page, etc…

Write device drivers

This is a crucial mission. Even pulling together all of the 3rd party drivers available, there will still be plenty of unsupported hardware. And we also have the problem of device drivers which are available in OS X but which haven’t been made available for free redistribution in any form by Apple (e.g., the e1000 support via AppleIntel82454XEthernet driver springs instantly to mind).

So if you have the skills in this area, why not roll up your sleeves and get stuck in?

Wiki

State

This wiki originated as a Google Site, then was migrated to a GitHub Wiki, and then ported to this website.

In the migration to GitHub, and therefore conversion to Markdown from HTML, a lot of formatting and many images were lost. The efforts of nekename have restored almost all of the images, fixed grammatical and formatting issues in the About and News categories, and removed most of the junk HTML tags lying around in pages. Additionally, many pages are more than a decade old, so many links are broken - please try to relocate them instead before removing them!

Style guide

This is the style guide you should follow when editing or creating wiki pages, or cleaning up broken ones.

Headers

Headers should only be created using proper # syntax. No ====== or —— should be used at all, and any existing occurences should be removed. All headers should be both preceded and followed by a newline.

H1s (single #) should be used only at the very start of a page. These should not be preceded by a newline.

Links to other pages

Always include the .md suffix. For pages in the same category, provide only the page name in the link. For pages in other categories, provide the full path from the root (e.g. /developers/Bochs.md).

Lists

For lists with no particular order, use - as the item prefix. Otherwise, use an ordered list, with 123. as the item prefix.

HTML

HTML should be avoided at all costs. Any Google Sites HTML remnants should be replaced with proper Markdown syntax.

Trailing newline

All files should end with a single trailing newline.

For developers

Prerequisites

In order to do any serious PureDarwin development, please familiarize yourself with the DarwinBuild project and the MacPorts project, as these are the key components of building software for Darwin.

PureDarwin releases

See PureDarwin Xmas. If you want to have a look at a minimalistic bootable Darwin 9 system, check out PureDarwin nano.

Testers wanted

To qualify as a tester for the current PureDarwin installer, you’ll need

• An Intel Mac with Leopard (to run the installer and to test whether the PureDarwin USB drive can be booted)
• A USB drive, 1GB or larger (will be completely erased)
• Latest VMware or VirtualBox release
• Fast Internet connection (to download Darwin 9 packages)
• A good backup since there are absolutely no guarantees

Please contact us in irc #puredarwin if you want to be a tester.

Useful tools

A utility for browsing through the contents of binary roots is available. It currently covers Darwin build 9F33, and provides links to relevant source code, and binaries.

Darwin mailing lists

Have a look at the Darwin mailing lists.

Documentation

This wiki is a place for users and developers alike to document and discuss Darwin. See below for some pages we have already started.

Audio

This page is about a future audio support in PureDarwin. draft. Status.

IOAudioFamily.kext (patched) and VoodooHDA.kext can be loaded. We heard great progress from Cooper previously, also extending our knowledge to the fact that “audio support” does not only rely on the kext side but also in the user-land. IOAudioFamily and VoodooHDA

High Definition Audio (HDA) driver for Mac OS X

VoodooHDA is an open source audio driver for devices compliant with the Intel High Definition Audio (HDA) specification, based primarily on code from the FreeBSD hdac driver. It is intended as an Intel-only replacement for AppleHDA on Mac OS X with support for a wide range of audio controllers and codecs.

VoodooHDA cannot be loaded, because one of its dependencies (IOAudioFamily.kext) is not satisifed. http://code.google.com/p/voodoohda/issues/detail?id=38

Since IOAudioFamily has been patched for purity purpose, IOAudioFamily.kext can now be loaded without OSvKernDSPLib.kext. See http://darwinbuild.macosforge.org/trac/ticket/89. Consequently, VoodooHDA can also be loaded, its Info.plist has been modified in order to match the virtual devices of VMware but the “start” method doesn’t seem to succeed.

No sound nor good symptoms.

Blockers:

• OSvKernDSPLib.kext
• AppleAC97Audio.kext Please let us know if you have more information and/or solutions.

Cooper sent us the following information in March 2010: OSvKernDSPLib.kext: We don’t have the source but the functions that we need are all well documented in the ADC and simple (each perform a single mathematical operation).  It would be easy for someone to implement these and patch them directly into whatever needs them or, better still, create a kext which exports them called OSvKernDSPLib.kext.

Usermode access: If you use shark to do a trace (on OSX) of a program recording audio you’ll find LOTS of references to HP_ funcs, in particular HP_IOThread.  Now if you search over a full XCode install you’ll find you actually have that code. Turns out that a huge amount of the usermode Coreaudio code is shipped with XCode to allow the development/testing of CoreAudioPlugins; go look in the folders called HPBase, PublicUtility etc.  These classes etc call down to the lower level audio interface functions, header files: AudioHardware.h etc (we don’t have the source) and these then communicate with the audio drivers IOUserClient in the kernel. So, where does that leave us.  Thankfully by trawling over the HP_ code you can find out whats important for the user code (the key thing it realtime priority), and by trawling through the kernel source (IOKit) you can find out what interface the code in AudioHardware.h uses (http://lists.apple.com/archives/Darwin-dev/2009/Aug/msg00000.html). What I posted back in August on the Darwin-dev list is basically correct and the answers to my questions are:

Q. Is there a mechanism to tell me when its safe to use this data, or is it, as I suspect, volatile and you use it “as it”. A. Sort of.  You basically need a realtime usermode thread which polls the kernel for the correct data.  The generic, kernel, audio stuff then gives you a copy of the samples your expecting.

Q. My key question is how do I get intelligible audio from the driver? I’ve tried putting a sleep in, but to no avail. A. IIRC, I did do this over 6 months ago; it all starts working once you get your io thread working correctly. To help illustrate all this I thought I’d attach my test program.  I know its a mess, but it does (or did last time I used it) read audio directly from the kernel on OSX and save it into a file.  What I did was pull out all the key things from the HP_IOThread func, combine that which what I’d learnt about the raw IOKIt interface and put it all together.  You should be able to load the output audio into something like Audacity and then play it.  Simples, see :)

Credits

• Cooper

Bochs, the Open Source IA-32 emulation project

Boot sequence

The Plex86/Bochs VGABios

DFE bootloader

Decompressing extensions

CPU:FSB multiplier detection fails

Please, let us know if you have a solution.

Chameleon bootloader

Kernel Panic

far..

Then it stalls.

Resources

• http://bochs.sourceforge.net/
• http://code.google.com/p/xnu-dev (Voodoo, A fork of the XNU kernel)

Build server

Special thanks to MacStadium for sponsoring a hosted Mac mini, and for voltagex for organizing and setting it up.

Usage

The machine is intended as a build server, possibly with continuous build and integration hooks to GitHub. Ideally, developers can see the impact of every change they make in near-real time. We are still working on setting this up.

Also, we would like to build and host binary packages of and for PureDarwin.

Machine specs

system_profiler SPHardwareDataType
Hardware:

    Hardware Overview:

      Model Name: Mac mini
      Model Identifier: Macmini7,1
      Processor Name: Intel Core i5
      Processor Speed: 2.8 GHz
      Number of Processors: 1
      Total Number of Cores: 2
      L2 Cache (per Core): 256 KB
      L3 Cache: 3 MB
      Memory: 16 GB

Access

Access to this machine can be granted to longstanding contributors of the PureDarwin project who have a proven track record of useful contributions to the project on GitHub. Do not apply for access before having contributed to the project in a meaningful way on GitHub. Contact voltagex in #puredarwin on irc.freenode.net if you think you qualify.

CFLite

This page covers the differences between CoreFoundation as found on Mac OS X (“CF”) and CoreFoundation as found on Darwin (“CFLite”). 

Versions discussed

At the time of this writing, the latest CF on Mac OS X is version 6.5.4 (CFBundleVersion 476.15, CFBundleShortVersionString 6.5.4, SourceVersion 4761500).

The latest published CFLite source is CF-476.15.tar.gz (CFBundleVersion 476, CFBundleShortVersionString 6.5). A binary root compiled through DarwinBuild is available from http://src.macosforge.org/Roots/9C31/CF.root.tar.gz. 

An experimental binary root of CFLite also compiled through DarwinBuild (but includes patches from 9F33pd1.plist) can be found here.

The PureFoundation project also provides patched binaries of CFLite. These combine patches necessary to fix some short-comings with CFLite with those needed by the cloned Foundation.framework, and as a result require the presence of that framework.

Notes: Please, read Apple CFLite page for more information.

There is also OpenCFLite, a version of CFLite maintained by an couple of independent developers (blog) which aims to port it to Windows and Linux. As well as the platform-specific changes, this also includes a number of bug-fixes and feature enhancements. There is a good chance that in the near future the version of CFLite bundled for use with PureFoundation will be based on OpenCFLite rather than directly on Apple’s CFLite.

Exported symbols

Let’s compare the number of symbols exported by CF and CF-Lite with nm.

Number of exported symbols

nm -g CoreFoundation | grep -v  "U " | cut -d " " -f 3 > CF.symbols
nm -g CoreFoundation | grep -v  "U " | cut -d " " -f 3 > CF-Lite.symbols

wc -l CF*.symbols 
    1287 CF-Lite.symbols
    1654 CF.symbols

diff CF.symbols CF-Lite.symbols | grep "^< " |  wc -l
     394

This shows that CF exports 1654 symbols.

The same test with CF-Lite shows that CF-Lite exports 1287 symbols.

Hence, CF-Lite contains about 78% of the symbols of the full CF, and about 22% were stripped away.

It is probably fair to assume that the Darwin sources should either not make use of the 28% of symbols that are missing from CF-Lite, or Apple should release the source for the missing symbols. See Current Blockers for a short list of some of the projects where these missing symbols (and the functions they represent) are causing us problems.

Symbols

In this example, _NSInvalidArgumentException should be exported by CF. (Please note: using the latest PureDarwin darwinbuild patch will automatically build a version of CFLite which now exports this and other NS-domain exceptions.)

nm -an /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation | grep _NSInvalidArgumentException `` 0013b444 **S** _NSInvalidArgumentException nm -an /System/Library/Frameworks/Foundation.framework/Foundation | grep _NSInvalidArgumentException           U _NSInvalidArgumentException 00272c70 S $ld$add$os10.4$_NSInvalidArgumentException

• U means “it is somewhere else”
• S means “it exports it”

Missing exported symbols

Here is a list of the 22% exported symbols that are missing from CF-Lite when compared to the full CF:

diff CF.symbols CF-Lite.symbols | grep “^< “ 

Whenever you encounter a message that includes one of the follwing symbol names, then it might well be due to the difference between CF and CF-Lite.

1. $ld$hide$os10.4$.objc_class_name_NSArray
2. $ld$hide$os10.4$.objc_class_name_NSCalendar
3. $ld$hide$os10.4$.objc_class_name_NSData
4. $ld$hide$os10.4$.objc_class_name_NSDate
5. $ld$hide$os10.4$.objc_class_name_NSDateComponents
6. $ld$hide$os10.4$.objc_class_name_NSDictionary
7. $ld$hide$os10.4$.objc_class_name_NSEnumerator
8. $ld$hide$os10.4$.objc_class_name_NSException
9. $ld$hide$os10.4$.objc_class_name_NSInputStream
10. $ld$hide$os10.4$.objc_class_name_NSInvocation
11. $ld$hide$os10.4$.objc_class_name_NSLocale
12. $ld$hide$os10.4$.objc_class_name_NSMethodSignature
13. $ld$hide$os10.4$.objc_class_name_NSMutableArray
14. $ld$hide$os10.4$.objc_class_name_NSMutableData
15. $ld$hide$os10.4$.objc_class_name_NSMutableDictionary
16. $ld$hide$os10.4$.objc_class_name_NSMutableSet
17. $ld$hide$os10.4$.objc_class_name_NSNull
18. $ld$hide$os10.4$.objc_class_name_NSObject
19. $ld$hide$os10.4$.objc_class_name_NSOutputStream
20. $ld$hide$os10.4$.objc_class_name_NSRunLoop
21. $ld$hide$os10.4$.objc_class_name_NSSet
22. $ld$hide$os10.4$.objc_class_name_NSStream
23. $ld$hide$os10.4$.objc_class_name_NSTimeZone
24. $ld$hide$os10.4$.objc_class_name_NSTimer
25. $ld$hide$os10.4$.objc_class_name_NSUserDefaults
26. $ld$hide$os10.4$_NSBuddhistCalendar
27. $ld$hide$os10.4$_NSChineseCalendar
28. $ld$hide$os10.4$_NSCurrentLocaleDidChangeNotification
29. $ld$hide$os10.4$_NSDefaultRunLoopMode
30. $ld$hide$os10.4$_NSGenericException
31. $ld$hide$os10.4$_NSGetSizeAndAlignment
32. $ld$hide$os10.4$_NSGregorianCalendar
33. $ld$hide$os10.4$_NSHebrewCalendar
34. $ld$hide$os10.4$_NSInternalInconsistencyException
35. $ld$hide$os10.4$_NSInvalidArgumentException
36. $ld$hide$os10.4$_NSIslamicCalendar
37. $ld$hide$os10.4$_NSIslamicCivilCalendar
38. $ld$hide$os10.4$_NSJapaneseCalendar
39. $ld$hide$os10.4$_NSLocaleCalendar
40. $ld$hide$os10.4$_NSLocaleCollationIdentifier
41. $ld$hide$os10.4$_NSLocaleCountryCode
42. $ld$hide$os10.4$_NSLocaleCurrencyCode
43. $ld$hide$os10.4$_NSLocaleCurrencySymbol
44. $ld$hide$os10.4$_NSLocaleDecimalSeparator
45. $ld$hide$os10.4$_NSLocaleExemplarCharacterSet
46. $ld$hide$os10.4$_NSLocaleGroupingSeparator
47. $ld$hide$os10.4$_NSLocaleIdentifier
48. $ld$hide$os10.4$_NSLocaleLanguageCode
49. $ld$hide$os10.4$_NSLocaleMeasurementSystem
50. $ld$hide$os10.4$_NSLocaleScriptCode
51. $ld$hide$os10.4$_NSLocaleUsesMetricSystem
52. $ld$hide$os10.4$_NSLocaleVariantCode
53. $ld$hide$os10.4$_NSMallocException
54. $ld$hide$os10.4$_NSRangeException
55. $ld$hide$os10.4$_NSRunLoopCommonModes
56. $ld$hide$os10.4$_NSStreamDataWrittenToMemoryStreamKey
57. $ld$hide$os10.4$_NSStreamFileCurrentOffsetKey
58. $ld$hide$os10.4$_NSStreamSOCKSProxyConfigurationKey
59. $ld$hide$os10.4$_NSStreamSOCKSProxyHostKey
60. $ld$hide$os10.4$_NSStreamSOCKSProxyPasswordKey
61. $ld$hide$os10.4$_NSStreamSOCKSProxyPortKey
62. $ld$hide$os10.4$_NSStreamSOCKSProxyUserKey
63. $ld$hide$os10.4$_NSStreamSOCKSProxyVersion4
64. $ld$hide$os10.4$_NSStreamSOCKSProxyVersion5
65. $ld$hide$os10.4$_NSStreamSOCKSProxyVersionKey
66. $ld$hide$os10.4$_NSStreamSocketSecurityLevelKey
67. $ld$hide$os10.4$_NSStreamSocketSecurityLevelNegotiatedSSL
68. $ld$hide$os10.4$_NSStreamSocketSecurityLevelNone
69. $ld$hide$os10.4$_NSStreamSocketSecurityLevelSSLv2
70. $ld$hide$os10.4$_NSStreamSocketSecurityLevelSSLv3
71. $ld$hide$os10.4$_NSStreamSocketSecurityLevelTLSv1
72. $ld$hide$os10.4$_NSSystemTimeZoneDidChangeNotification
73. .objc_category_name_CFXPreferencesPropertyListSource_CFXPreferencesSPIAdditions
74. .objc_class_name_CFXPreferencesCompatibilitySource
75. .objc_class_name_CFXPreferencesManagedSource
76. .objc_class_name_CFXPreferencesPropertyListSource
77. .objc_class_name_CFXPreferencesSearchListSource
78. .objc_class_name_CFXPreferencesSource
79. .objc_class_name_NSArray
80. .objc_class_name_NSCalendar
81. .objc_class_name_NSData
82. .objc_class_name_NSDate
83. .objc_class_name_NSDateComponents
84. .objc_class_name_NSDictionary
85. .objc_class_name_NSEnumerator
86. .objc_class_name_NSException
87. .objc_class_name_NSInputStream
88. .objc_class_name_NSInvocation
89. .objc_class_name_NSLocale
90. .objc_class_name_NSMessageBuilder
91. .objc_class_name_NSMethodSignature
92. .objc_class_name_NSMutableArray
93. .objc_class_name_NSMutableData
94. .objc_class_name_NSMutableDictionary
95. .objc_class_name_NSMutableOrderedSet
96. .objc_class_name_NSMutableSet
97. .objc_class_name_NSNull
98. .objc_class_name_NSObject
99. .objc_class_name_NSOrderedSet
100. .objc_class_name_NSOutputStream
101. .objc_class_name_NSRunLoop
102. .objc_class_name_NSSet
103. .objc_class_name_NSStream
104. .objc_class_name_NSTimeZone
105. .objc_class_name_NSTimer
106. .objc_class_name_NSUserDefaults
107. .objc_class_name__NSZombie_
108. .objc_class_name___NSArrayReverseEnumerator
109. .objc_class_name___NSCFArray
110. .objc_class_name___NSCFDate
111. .objc_class_name___NSCFDictionary
112. .objc_class_name___NSCFOrderedSet
113. .objc_class_name___NSCFSet
114. .objc_class_name___NSDictionaryObjectEnumerator
115. .objc_class_name___NSFastEnumerationEnumerator
116. .objc_class_name___NSOrderedSetReverseEnumerator
117. .objc_class_name___NSPlaceholderArray
118. .objc_class_name___NSPlaceholderDate
119. .objc_class_name___NSPlaceholderDictionary
120. .objc_class_name___NSPlaceholderOrderedSet
121. .objc_class_name___NSPlaceholderSet
122. _CFAttributedStringBeginEditing
123. _CFAttributedStringCreate
124. _CFAttributedStringCreateCopy
125. _CFAttributedStringCreateMutable
126. _CFAttributedStringCreateMutableCopy
127. _CFAttributedStringCreateWithSubstring
128. _CFAttributedStringEndEditing
129. _CFAttributedStringGetAttribute
130. _CFAttributedStringGetAttributeAndLongestEffectiveRange
131. _CFAttributedStringGetAttributes
132. _CFAttributedStringGetAttributesAndLongestEffectiveRange
133. _CFAttributedStringGetLength
134. _CFAttributedStringGetMutableString
135. _CFAttributedStringGetString
136. _CFAttributedStringGetTypeID
137. _CFAttributedStringOpenUText
138. _CFAttributedStringRemoveAttribute
139. _CFAttributedStringReplaceAttributedString
140. _CFAttributedStringReplaceString
141. _CFAttributedStringSetAttribute
142. _CFAttributedStringSetAttributes
143. _CFBundleCloseBundleResourceMap
144. _CFBundleOpenBundleResourceFiles
145. _CFBundleOpenBundleResourceMap
146. _CFFileDescriptorCreate
147. _CFFileDescriptorCreateRunLoopSource
148. _CFFileDescriptorDisableCallBacks
149. _CFFileDescriptorEnableCallBacks
150. _CFFileDescriptorGetContext
151. _CFFileDescriptorGetNativeDescriptor
152. _CFFileDescriptorGetTypeID
153. _CFFileDescriptorInvalidate
154. _CFFileDescriptorIsValid
155. _CFGetExecutableLinkedLibraryVersion
156. _CFGetExecutingLibraryVersion
157. _CFLocaleGetLanguageRegionEncodingForLocaleIdentifier
158. _CFLogTest
159. _CFMutableAttributedStringOpenUText
160. _CFMutableStringOpenUText
161. _CFNotificationCenterAddObserver
162. _CFNotificationCenterGetDarwinNotifyCenter
163. _CFNotificationCenterGetDistributedCenter
164. _CFNotificationCenterGetLocalCenter
165. _CFNotificationCenterGetTypeID
166. _CFNotificationCenterIsSuspended
167. _CFNotificationCenterPostNotification
168. _CFNotificationCenterPostNotificationWithOptions
169. _CFNotificationCenterRemoveEveryObserver
170. _CFNotificationCenterRemoveObserver
171. _CFNotificationCenterSetSuspended
172. _CFPasteboardApplyFunction
173. _CFPasteboardBeginGeneration
174. _CFPasteboardCopyData
175. _CFPasteboardCopyFlavorsForItem
176. _CFPasteboardCopyItemsAndFlavors
177. _CFPasteboardCopyName
178. _CFPasteboardCreate
179. _CFPasteboardCreateDataForString
180. _CFPasteboardCreateStringFromData
181. _CFPasteboardCreateUnique
182. _CFPasteboardGetChangeCount
183. _CFPasteboardGetDataFlags
184. _CFPasteboardGetFlavorCount
185. _CFPasteboardGetGenerationCount
186. _CFPasteboardGetItemAtIndex
187. _CFPasteboardGetItemCount
188. _CFPasteboardGetTypeID
189. _CFPasteboardIsDataPromised
190. _CFPasteboardPromiseData
191. _CFPasteboardResolveAllPromisedData
192. _CFPasteboardResolvePromisedData
193. _CFPasteboardSetData
194. _CFPasteboardSetDataFlags
195. _CFPasteboardSetPasteLocation
196. _CFPreferencesAppValueIsForced
197. _CFRunArrayCreate
198. _CFRunArrayDelete
199. _CFRunArrayGetCount
200. _CFRunArrayGetTypeID
201. _CFRunArrayGetValueAtIndex
202. _CFRunArrayGetValueAtRunArrayIndex
203. _CFRunArrayInsert
204. _CFRunArrayReplace
205. _CFServiceControllerCanConnect
206. _CFServiceControllerCopyServicesEntries
207. _CFServiceControllerGetRegisteredProvider
208. _CFServiceControllerPerformService
209. _CFServiceControllerPromiseServiceEntries
210. _CFServiceControllerRegisterProvider
211. _CFServiceControllerSetServicesEntries
212. _CFStreamCreateBoundPair
213. _CFStringOpenUText
214. _CFStringTokenizerAdvanceToNextToken
215. _CFStringTokenizerCopyBestStringLanguage
216. _CFStringTokenizerCopyCurrentTokenAttribute
217. _CFStringTokenizerCreate
218. _CFStringTokenizerGetCurrentSubTokens
219. _CFStringTokenizerGetCurrentTokenRange
220. _CFStringTokenizerGetTypeID
221. _CFStringTokenizerGoToTokenAtIndex
222. _CFStringTokenizerSetString
223. _CFStringTransform
224. _CFURLCreateFromFSRef
225. _CFURLGetFSRef
226. _CFUniCharApplyUnicodeBidiAlgorithm
227. _CFUniCharGetBidiCategory
228. _CFUniCharGetFirstBidiParagraphLength
229. _NSBuddhistCalendar
230. _NSChineseCalendar
231. _NSCurrentLocaleDidChangeNotification
232. _NSDefaultRunLoopMode
233. _NSGenericException
234. _NSGetSizeAndAlignment
235. _NSGregorianCalendar
236. _NSHebrewCalendar
237. _NSInternalInconsistencyException
238. _NSInvalidArgumentException
239. _NSIslamicCalendar
240. _NSIslamicCivilCalendar
241. _NSJapaneseCalendar
242. _NSLocaleCalendar
243. _NSLocaleCollationIdentifier
244. _NSLocaleCountryCode
245. _NSLocaleCurrencyCode
246. _NSLocaleCurrencySymbol
247. _NSLocaleDecimalSeparator
248. _NSLocaleExemplarCharacterSet
249. _NSLocaleGroupingSeparator
250. _NSLocaleIdentifier
251. _NSLocaleLanguageCode
252. _NSLocaleMeasurementSystem
253. _NSLocaleScriptCode
254. _NSLocaleUsesMetricSystem
255. _NSLocaleVariantCode
256. _NSMallocException
257. _NSRangeException
258. _NSRunLoopCommonModes
259. _NSStreamDataWrittenToMemoryStreamKey
260. _NSStreamFileCurrentOffsetKey
261. _NSStreamSOCKSProxyConfigurationKey
262. _NSStreamSOCKSProxyHostKey
263. _NSStreamSOCKSProxyPasswordKey
264. _NSStreamSOCKSProxyPortKey
265. _NSStreamSOCKSProxyUserKey
266. _NSStreamSOCKSProxyVersion4
267. _NSStreamSOCKSProxyVersion5
268. _NSStreamSOCKSProxyVersionKey
269. _NSStreamSocketSecurityLevelKey
270. _NSStreamSocketSecurityLevelNegotiatedSSL
271. _NSStreamSocketSecurityLevelNone
272. _NSStreamSocketSecurityLevelSSLv2
273. _NSStreamSocketSecurityLevelSSLv3
274. _NSStreamSocketSecurityLevelTLSv1
275. _NSSystemTimeZoneDidChangeNotification
276. __CFAppVersionCheck
277. __CFAppVersionCheckLessThan
278. __CFArrayIsMutable
279. __CFAttributedStringCheckAndReplace
280. __CFAttributedStringCheckAndReplaceAttributed
281. __CFAttributedStringCheckAndSetAttribute
282. __CFAttributedStringCheckAndSetAttributes
283. __CFAttributedStringCreateWithRuns
284. __CFAttributedStringGetLength
285. __CFAttributedStringGetNumberOfRuns
286. __CFAttributedStringGetRuns
287. __CFAttributedStringIsMutable
288. __CFBagIsMutable
289. __CFBundleCloseBundleResourceFork
290. __CFBundleCopyInfoDictionaryInResourceFork
291. __CFBundleCreateIfMightBeBundle
292. __CFBundleCreateWithExecutableURLIfMightBeBundle
293. __CFBundleOpenBundleResourceFork
294. __CFCharacterSetIsMutable
295. __CFCreateURLFromFSSpec
296. __CFDNStart
297. __CFDictionaryIsMutable
298. __CFDoExceptionOperation
299. __CFGetFSSpecFromURL
300. __CFLocaleGetNoteCount
301. __CFLogvEx
302. __CFNotificationCenterForLocalNotifications
303. __CFPreferencesCopyValueNoCache
304. __CFPreferencesCreatePathToUsersManagedPrefsDirectory
305. __CFPreferencesIsManaged
306. __CFPreferencesManagementStatusChangedForDomains
307. __CFPreferencesPostValuesChangedInDomains
308. __CFPreferencesWriteDomainDictionaryToPath
309. __CFPreferencesWriteManagedDomainForUser
310. __CFPropertListCreateFromFrozen
311. __CFPropertyListCopyShared
312. __CFPropertyListCreateFrozen
313. __CFPropertyListShare
314. __CFRunArrayCreateWithGuts
315. __CFSetIsMutable
316. __CFStringTokenizerGetDerivedTokens
317. __CFStringTokenizerTokenize
318. __CFStringTokenizerTokenizeCompoundWord
319. __CFURLCopyAliasFromPropertyListRepresentation
320. __CFURLCopyExtendedPropertyListPrimitive
321. __CFURLCopyExtendedPropertyListRepresentation
322. __CFUserNotificationSetWarningThread
323. __CFXNotificationCenterCreate
324. __CFXNotificationCenterIsEmpty
325. __CFXNotificationGetHostCenter
326. __CFXNotificationGetSuspended
327. __CFXNotificationGetTaskCenter
328. __CFXNotificationPost
329. __CFXNotificationPostNotification
330. __CFXNotificationRegister
331. __CFXNotificationResetSessionForTask
332. __CFXNotificationSetSuspended
333. __CFXNotificationUnregister
334. __CFXPreferencesCopyDictionaryForApplicationPreferences
335. __CFXPreferencesCopyDictionaryForNamedVolatileSource
336. __CFXPreferencesCopyDictionaryForSourceWithBundleID
337. __CFXPreferencesCopyLanguageList
338. __CFXPreferencesCopyVolatileSourceNames
339. __CFXPreferencesRegisterDefaultValues
340. __CFXPreferencesRemoveNamedVolatileSource
341. __CFXPreferencesReplaceValuesInNamedVolatileSource
342. __CFXPreferencesReplaceValuesInSourceWithBundleID
343. __CFXPreferencesSetUserDefaultsPointer
344. __CF_forwarding_prep_0
345. __NSExceptionGetRubyToken
346. __NSExceptionSetRubyToken
347. __NSMessageBuilder
348. ___CFAttributedStringCreateMutableWithSubstring
349. ___CFAttributedStringMtbl
350. ___CFDoExternRefOperation
351. ___CFOAInitialize
352. ___CFOASafe
353. ___CFPBStart
354. ___CFRecordAllocationEvent
355. ___CFRuntimeObjCClassTable
356. ___CFSetLastAllocationEventName
357. ___CFStringIsMutable
358. ___CFStringMtbl
359. ____CFA2UC
360. _crashreporter_info
361. __kCFBundleResourceSpecificationKey
362. _kCFErrorDomainCoreFoundation
363. _kCFManagedPreferencesMCXNotificationName
364. _kCFManagedPreferencesMCXObjectName
365. _kCFNotificationAnyName
366. _kCFNotificationAnyObject
367. _kCFPasteboardFind
368. _kCFPasteboardGeneral
369. _kCFPreferencesDidChangeNotificationName
370. _kCFPreferencesDidChangeObject
371. _kCFServiceControllerActivateKey
372. _kCFServiceControllerErrorKey
373. _kCFServiceControllerMessageKey
374. _kCFServiceControllerPasteboardKey
375. _kCFServiceControllerProviderKey
376. _kCFServiceControllerResultKey
377. _kCFServiceControllerServicesChangedNotification
378. _kCFServiceControllerUserDataKey
379. _kCFStringTransformFullwidthHalfwidth
380. _kCFStringTransformHiraganaKatakana
381. _kCFStringTransformLatinArabic
382. _kCFStringTransformLatinCyrillic
383. _kCFStringTransformLatinGreek
384. _kCFStringTransformLatinHangul
385. _kCFStringTransformLatinHebrew
386. _kCFStringTransformLatinHiragana
387. _kCFStringTransformLatinKatakana
388. _kCFStringTransformLatinThai
389. _kCFStringTransformMandarinLatin
390. _kCFStringTransformStripCombiningMarks
391. _kCFStringTransformStripDiacritics
392. _kCFStringTransformToLatin
393. _kCFStringTransformToUnicodeName
394. _kCFStringTransformToXMLHex

Symbols vanished from CF-Lite

An old CF-Lite, CoreFoundation-262.tar.gz (source CoreFoundation-262-src.tar.gz) from 2002, exported the following symbols which the recent version of CF-Lite does no longer appear to export:

1. _CFArrayGetTypeID
2. _CFArrayCreateMutable
3. __CFArrayCreate_ex
4. _CFArrayContainsValue
5. _CFArrayGetValueAtIndex
6. _CFArrayGetValues
7. _CFArrayApplyFunction
8. _CFArrayAppendValue
9. _CFArraySetValueAtIndex
10. _CFArrayExchangeValuesAtIndices
11. _CFArrayRemoveValueAtIndex
12. __CFArraySetCapacity
13. __CFArrayIsMutable
14. _CFArrayBSearchValues
15. _CFArrayAppendArray
16. _CFBagGetTypeID
17. _CFBagCreateMutable
18. __CFBagSetContext
19. _CFBagContainsValue
20. _CFBagApplyFunction
21. __CFBagSetCapacity
22. _CFBagAddValue
23. _CFBagRemoveValue
24. _CFBagRemoveAllValues
25. ___CFRangeMake
26. _CFNullGetTypeID
27. _CFAllocatorGetTypeID
28. _CFAllocatorGetDefault
29. _CFAllocatorSetDefault
30. _CFAllocatorCreate
31. _CFAllocatorAllocate
32. _CFAllocatorReallocate
33. _CFAllocatorDeallocate
34. _CFAllocatorGetPreferredSizeForSize
35. _CFAllocatorGetContext
36. __CFRuntimeSetCFMPresent
37. _CFBinaryHeapGetTypeID
38. _CFBinaryHeapContainsValue
39. _CFBinaryHeapApplyFunction
40. _CFBinaryHeapAddValue
41. _CFBinaryHeapRemoveMinimumValue
42. __CFKeyedArchiverUIDGetTypeID
43. __CFKeyedArchiverUIDCreate
44. __CFKeyedArchiverUIDGetValue
45. ___CFBinaryPlistWriteToStream
46. ___CFBinaryPlistGetTopLevelInfo
47. ___CFBinaryPlistGetOffsetForValueFromArray
48. ___CFBinaryPlistGetOffsetForValueFromDictionary
49. ___CFBinaryPlistCreateObject
50. _CFBitVectorGetTypeID
51. _CFBitVectorCreateMutable
52. _CFBitVectorGetCount
53. _CFBitVectorGetCountOfBit
54. _CFBitVectorContainsBit
55. _CFBitVectorSetCount
56. _CFBitVectorFlipBitAtIndex
57. _CFBitVectorFlipBits
58. _CFBitVectorSetAllBits
59. _CFStringEncodingIsValidCombiningCharacterForLatin1
60. _CFStringEncodingPrecomposeLatinCharacter
61. __CFBundleCopyBundleURLForExecutableURL
62. __CFBundleCreateIfLooksLikeBundle
63. __CFBundleGetMainBundleIfLooksLikeBundle
64. __CFBundleCreateWithExecutableURLIfLooksLikeBundle
65. _CFBundleGetMainBundle
66. _CFBundleGetBundleWithIdentifier
67. _CFBundleGetTypeID
68. _CFBundleCreate
69. _CFBundleCreateBundlesFromDirectory
70. __CFBundleSetDefaultLocalization
71. _CFBundleCopyInfoDictionaryInDirectory
72. _CFBundleGetInfoDictionary
73. __CFBundleGetLocalInfoDictionary
74. _CFBundleGetLocalInfoDictionary
75. __CFBundleGetValueForInfoKey
76. _CFBundleGetValueForInfoDictionaryKey
77. _CFBundleGetIdentifier
78. _CFBundleGetVersionNumber
79. _CFBundleGetDevelopmentRegion
80. __CFBundleGetHasChanged
81. _CFBundleCopySupportFilesDirectoryURL
82. _CFBundleCopyResourcesDirectoryURL
83. __CFBundleCopyResourceForkURL
84. __CFBundleCopyExecutableURLInDirectory
85. __CFBundleCopyOtherExecutableURLInDirectory
86. _CFBundleCopyAuxiliaryExecutableURL
87. _CFBundleIsExecutableLoaded
88. __CFBundleCopyFileTypeForFileURL
89. __CFBundleSetCFMConnectionID
90. _CFBundleLoadExecutable
91. _CFBundleUnloadExecutable
92. _CFBundleGetFunctionPointerForName
93. __CFBundleGetCFMFunctionPointerForName
94. _CFBundleGetFunctionPointersForNames
95. __CFBundleGetCFMFunctionPointersForNames
96. _CFBundleGetDataPointerForName
97. _CFBundleGetDataPointersForNames
98. _CFBundleGetPlugIn
99. _CFBundleGetAllBundles
100. __CFBundleLayoutVersion
101. __CFBundleCopyInfoPlistURL
102. __CFBundleCopyPrivateFrameworksURL
103. __CFBundleCopySharedFrameworksURL
104. _CFBundleCopySharedFrameworksURL
105. __CFBundleCopySharedSupportURL
106. _CFBundleCopySharedSupportURL
107. _CFBundleCopyBuiltInPlugInsURL
108. __CFBundleFlushCaches
109. __CFFindBundleResources
110. _CFBundleCopyResourceURLsOfType
111. __CFBundleCopyResourceURLForLanguage
112. __CFBundleCopyResourceURLsOfTypeForLanguage
113. _CFBundleCopyResourceURLsOfTypeForLocalization
114. _CFBundleCopyLocalizedString
115. _CFBundleCopyLocalizationForLocalizationInfo
116. __CFBundleGetLanguageAndRegionCodes
117. _CFBundleCopyLocalizationsForPreferences
118. _CFBundleCopyPreferredLocalizationsFromArray
119. __CFBundleURLLooksLikeBundle
120. __CFBundleGetPackageInfoInDirectory
121. _CFBundleCopyBundleLocalizations
122. _CFBundleCopyInfoDictionaryForURL
123. _CFBundleCopyLocalizationsForURL
124. _CFCharacterSetGetTypeID
125. _CFCharacterSetGetPredefined
126. _CFCharacterSetCreateWithCharactersInRange
127. _CFCharacterSetCreateWithCharactersInString
128. _CFCharacterSetCreateWithBitmapRepresentation
129. _CFCharacterSetIsSurrogatePairMember
130. _CFCharacterSetHasMemberInPlane
131. _CFCharacterSetCreateBitmapRepresentation
132. _CFCharacterSetAddCharactersInRange
133. _CFCharacterSetAddCharactersInString
134. _CFCharacterSetIntersect
135. _CFCharacterSetInvert
136. _CFCharacterSetCompact
137. _CFCharacterSetFast
138. __CFCharacterSetGetKeyedCodingType
139. __CFCharacterSetIsMutable
140. __CFCharacterSetGetKeyedCodingBuiltinType
141. __CFCharacterSetGetKeyedCodingRange
142. __CFCharacterSetCreateKeyedCodingString
143. __CFCharacterSetIsInverted
144. __CFCharacterSetSetIsInverted
145. _CFDataGetTypeID
146. _CFDataCreateWithBytesNoCopy
147. _CFDataGetLength
148. _CFDataGetMutableBytePtr
149. _CFDataSetLength
150. _CFDataAppendBytes
151. _CFDataDeleteBytes
152. _CFAbsoluteTimeGetCurrent
153. _CFDateGetTypeID
154. _CFDateCompare
155. _CFGregorianDateIsValid
156. _CFGregorianDateGetAbsoluteTime
157. _CFAbsoluteTimeGetGregorianDate
158. _CFAbsoluteTimeAddGregorianUnits
159. _CFAbsoluteTimeGetDifferenceAsGregorianUnits
160. _CFAbsoluteTimeGetDayOfWeek
161. _CFAbsoluteTimeGetDayOfYear
162. _CFAbsoluteTimeGetWeekOfYear
163. _CFDictionaryGetTypeID
164. _CFDictionaryCreateMutable
165. __CFDictionaryCreate_ex
166. __CFDictionarySetContext
167. _CFDictionaryContainsKey
168. _CFDictionaryContainsValue
169. _CFDictionaryGetValue
170. _CFDictionaryGetValueIfPresent
171. _CFDictionaryApplyFunction
172. __CFDictionarySetCapacity
173. __CFDictionaryIsMutable
174. _CFDictionaryAddValue
175. _CFDictionaryRemoveValue
176. _CFDictionaryRemoveAllValues
177. __CFMachPortInstallNotifyPort
178. _CFMachPortGetTypeID
179. _CFMachPortGetPort
180. _CFMachPortGetInvalidationCallBack
181. _CFMachPortGetQueuedMessageCount
182. _CFMachPortInvalidateAll
183. _CFMachPortCreateRunLoopSource
184. _CFMessagePortGetTypeID
185. _CFMessagePortIsRemote
186. _CFMessagePortGetName
187. _CFMessagePortSetName
188. _CFMessagePortGetInvalidationCallBack
189. _CFMessagePortSetInvalidationCallBack
190. _CFMessagePortCreateRunLoopSource
191. _CFNotificationCenterGetTypeID
192. _CFNotificationCenterGetDistributedCenter
193. _CFNotificationCenterAddObserver
194. _CFNotificationCenterRemoveObserver
195. _CFNotificationCenterRemoveEveryObserver
196. _CFNotificationCenterPostNotification
197. _CFBooleanGetTypeID
198. _CFBooleanGetValue
199. _CFNumberGetTypeID
200. _CFNumberGetType
201. _CFNumberIsFloatType
202. _CFNumberCompare
203. __CFArgv
204. __CFArgc
205. __CFGetProgname
206. __CFProcessPath
207. __CFCreateHomeDirectoryURLForUser
208. _CFGetUserName
209. _CFCopyHomeDirectoryURLForUser
210. _CFPlugInUnregisterFactory
211. _CFPlugInUnregisterPlugInType
212. _CFPlugInAddInstanceForFactory
213. _CFPlugInInstanceGetTypeID
214. _CFPlugInInstanceCreateWithInstanceDataSize
215. _CFPlugInInstanceGetInterfaceFunctionTable
216. _CFPlugInInstanceGetFactoryName
217. _CFPlugInInstanceGetInstanceData
218. _CFPlugInGetTypeID
219. _CFPlugInCreate
220. _CFPlugInGetBundle
221. _CFPlugInIsLoadOnDemand
222. _CFPreferencesSetAppValue
223. _CFPreferencesAddSuitePreferencesToApp
224. _CFPreferencesAppSynchronize
225. _CFPreferencesCopyValue
226. _CFPreferencesCopyMultiple
227. _CFPreferencesSetValue
228. _CFPreferencesCopyApplicationList
229. _CFPreferencesCopyKeyList
230. _CFPreferencesAppValueIsForced
231. __CFDoOperation
232. _CFPropertyListIsValid
233. _CFPropertyListCreateXMLData
234. __CFPropertyListCreateXMLDataWithExtras
235. ___CFSetNastyFile
236. _CFPropertyListCreateFromXMLData
237. _CFRunLoopGetTypeID
238. __CFRunLoopSetCurrent
239. __CFRunLoopSetMain
240. _CFRunLoopCopyCurrentMode
241. _CFRunLoopCopyAllModes
242. _CFRunLoopAddCommonMode
243. __CFRunLoopFinished
244. _CFRunLoopRun
245. _CFRunLoopRunSpecific
246. _CFRunLoopRunInMode
247. _CFRunLoopWakeUp
248. _CFRunLoopStop
249. __CFRunLoopStopMode
250. __CFRunLoopModeContainsMode
251. __CFRunLoopAddModeToMode
252. __CFRunLoopRemoveModeFromMode
253. _CFRunLoopContainsSource
254. _CFRunLoopAddSource
255. _CFRunLoopRemoveSource
256. _CFRunLoopContainsObserver
257. _CFRunLoopAddObserver
258. _CFRunLoopContainsTimer
259. _CFRunLoopAddTimer
260. _CFRunLoopSourceGetTypeID
261. _CFRunLoopSourceGetContext
262. _CFRunLoopObserverGetTypeID
263. _CFRunLoopObserverCreate
264. _CFRunLoopObserverGetActivities
265. _CFRunLoopObserverGetOrder
266. _CFRunLoopObserverDoesRepeat
267. _CFRunLoopObserverInvalidate
268. _CFRunLoopObserverIsValid
269. _CFRunLoopObserverGetContext
270. _CFRunLoopTimerGetTypeID
271. _CFRunLoopTimerGetNextFireDate
272. _CFRunLoopTimerSetNextFireDate
273. _CFRunLoopTimerGetInterval
274. _CFRunLoopTimerGetContext
275. ___CFOAInitialize
276. ___CFRecordAllocationEvent
277. ___CFSetLastAllocationEventName
278. __CFRuntimeRegisterClass
279. __CFRuntimeGetClassWithTypeID
280. __CFRuntimeUnregisterClassWithTypeID
281. __CFRuntimeCreateInstance
282. __CFRuntimeSetInstanceTypeID
283. _CFTypeGetTypeID
284. _CFGetTypeID
285. _CFCopyTypeIDDescription
286. _CFRetain
287. _CFRelease
288. _CFGetRetainCount
289. _CFEqual
290. _CFHash
291. _CFCopyDescription
292. _CFGetAllocator
293. ___CFInitialize
294. _CFSetGetTypeID
295. _CFSetCreateMutable
296. __CFSetSetContext
297. _CFSetContainsValue
298. _CFSetApplyFunction
299. __CFSetSetCapacity
300. __CFSetIsMutable
301. _CFSetAddValue
302. _CFSetRemoveValue
303. _CFSetRemoveAllValues
304. _CFSocketGetTypeID
305. _CFSocketSetAddress
306. _CFSocketCreateConnectedToSocketSignature
307. _CFSocketInvalidate
308. _CFSocketIsValid
309. _CFSocketGetNative
310. _CFSocketCopyAddress
311. _CFSocketCopyPeerAddress
312. _CFSocketGetContext
313. _CFSocketGetSocketFlags
314. _CFSocketSetSocketFlags
315. _CFSocketCreateRunLoopSource
316. _CFSocketSendData
317. _CFSocketRegisterValue
318. _CFSocketCopyRegisteredValue
319. _CFSocketCopyRegisteredSocketSignature
320. _CFSocketUnregister
321. _CFSocketGetDefaultNameRegistryPortNumber
322. _CFMergeSortArray
323. _CFQSortArray
324. ___CFStorageGetCapacity
325. ___CFStorageGetValueSize
326. _CFStorageGetTypeID
327. _CFStorageInsertValues
328. _CFStorageDeleteValues
329. _CFStorageApplyFunction
330. __CFStringSetCompatibility
331. ___CFStringIsMutable
332. ___CFStringIsEightBit
333. _CFStringGetSystemEncoding
334. _CFStringFileSystemEncoding
335. _CFStringGetMaximumSizeForEncoding
336. ___CFStringComputeEightBitStringEncoding
337. ___CFStringHash
338. _CFStringGetTypeID
339. ___CFStringCreateImmutableFunnel2
340. _CFStringCreateWithPascalString
341. _CFStringCreateWithPascalStringNoCopy
342. _CFStringCreateWithBytes
343. __CFStringCreateWithBytesNoCopy
344. _CFStringCreateWithFormatAndArguments
345. __CFStringCreateWithFormatAndArgumentsAux
346. _CFStringCreateCopy
347. ___CFStringMakeConstantString
348. _CFStringCreateMutableWithExternalCharactersNoCopy
349. _CFStringCreateMutable
350. _CFStringCreateMutableCopy
351. _CFStringGetLength
352. __CFStringGetLength2
353. _CFStringGetCharacterAtIndex
354. __CFStringCheckAndGetCharacterAtIndex
355. _CFStringGetCharacters
356. __CFStringCheckAndGetCharacters
357. _CFStringGetPascalStringPtr
358. _CFStringGetCString
359. _CFStringCompareWithOptions
360. _CFStringCompare
361. _CFStringFindWithOptions
362. _CFStringCreateArrayWithFindResults
363. _CFStringFind
364. _CFStringHasPrefix
365. _CFStringHasSuffix
366. _CFStringFindCharacterFromSet
367. _CFStringGetLineBounds
368. _CFStringCreateByCombiningStrings
369. _CFStringCreateArrayBySeparatingStrings
370. _CFStringCreateFromExternalRepresentation
371. _CFStringCreateExternalRepresentation
372. _CFStringGetFastestEncoding
373. _CFStringGetIntValue
374. _CFStringGetDoubleValue
375. _CFStringSetExternalCharactersNoCopy
376. _CFStringDelete
377. _CFStringAppend
378. _CFStringAppendCharacters
379. _CFStringAppendPascalString
380. _CFStringAppendCString
381. _CFStringAppendFormat
382. _CFStringFindAndReplace
383. ___CFStringCheckAndReplace
384. ___CFStringNoteErrors
385. _CFStringPad
386. _CFStringLowercase
387. _CFStringCapitalize
388. _CFStringNormalize
389. _CFStringAppendFormatAndArguments
390. __CFStringAppendFormatAndArgumentsAux
391. _CFShowStr
392. _CFStringEncodingUnicodeToBytes
393. _CFStringEncodingBytesToUnicode
394. __CFStringEncodingSetForceASCIICompatibility
395. ___CFStringDecodeByteStream2
396. ___CFStringDecodeByteStream3
397. ___CFStringEncodeByteStream
398. __CFStringGetFileSystemRepresentation
399. _CFStringIsEncodingAvailable
400. _CFStringGetListOfAvailableEncodings
401. _CFStringGetNameOfEncoding
402. _CFStringConvertIANACharSetNameToEncoding
403. _CFStringConvertEncodingToIANACharSetName
404. _CFStringConvertEncodingToNSStringEncoding
405. _CFStringConvertNSStringEncodingToEncoding
406. _CFStringConvertEncodingToWindowsCodepage
407. _CFStringConvertWindowsCodepageToEncoding
408. _CFStringGetMostCompatibleMacStringEncoding
409. _CFTimeZoneGetTypeID
410. _CFTimeZoneCopySystem
411. _CFTimeZoneResetSystem
412. _CFTimeZoneSetDefault
413. _CFTimeZoneCopyAbbreviationDictionary
414. _CFTimeZoneSetAbbreviationDictionary
415. _CFTimeZoneCreateWithTimeIntervalFromGMT
416. _CFTimeZoneGetName
417. _CFTimeZoneCopyAbbreviation
418. _CFTreeGetTypeID
419. _CFTreeGetChildCount
420. _CFTreeGetParent
421. _CFTreeGetNextSibling
422. _CFTreeGetFirstChild
423. _CFTreeGetContext
424. _CFTreeSetContext
425. _CFTreeApplyFunctionToChildren
426. _CFTreePrependChild
427. _CFTreeAppendChild
428. __CFURLCreateOnlyUTF8CompatibleURLs
429. _CFURLCreateStringByReplacingPercentEscapes
430. _CFURLCreateStringByAddingPercentEscapes
431. _CFURLGetTypeID
432. __CFURLAlloc
433. __CFStringIsLegalURLString
434. __CFURLInitWithString
435. _CFURLCreateWithBytes
436. _CFURLCreateData
437. _CFURLCreateWithString
438. _CFURLCopyAbsoluteURL
439. _CFURLGetString
440. _CFURLGetBaseURL
441. _CFURLCopyScheme
442. _CFURLCopyStrictPath
443. _CFURLHasDirectoryPath
444. _CFURLCopyHostName
445. _CFURLGetPortNumber
446. _CFURLCopyPassword
447. _CFURLCopyParameterString
448. _CFURLCopyQueryString
449. _CFURLCopyFragment
450. _CFURLCopyComponents
451. _CFURLCreateFromComponents
452. ___CFURLReservedPtr
453. ___CFURLSetReservedPtr
454. __CFURLCreateCurrentDirectoryURL
455. _CFURLCreateWithFileSystemPath
456. _CFURLCreateWithFileSystemPathRelativeToBase
457. _CFURLCopyFileSystemPath
458. _CFURLCreateStringWithFileSystemPath
459. _CFURLGetFileSystemRepresentation
460. _CFURLCreateFromFileSystemRepresentation
461. _CFURLCreateFromFileSystemRepresentationRelativeToBase
462. _CFURLCopyLastPathComponent
463. _CFURLCopyPathExtension
464. _CFURLCreateCopyDeletingLastPathComponent
465. __CFGetFSSpecFromURL
466. __CFCreateURLFromFSSpec
467. _CFURLCreateFromFSRef
468. _CFURLGetFSRef
469. _CFURLWriteDataAndPropertiesToResource
470. _CFUUIDGetTypeID
471. _CFUUIDCreateWithBytes
472. _CFUUIDCreateFromUUIDBytes
473. _CFUniCharIsMemberOf
474. _CFUniCharGetUnicodePropertyDataForPlane
475. _CFUniCharDecomposeCharacter
476. _CFUniCharDecompose
477. _CFUniCharPrioritySort
478. _CFUserNotificationGetTypeID
479. _CFUserNotificationCreate
480. _CFUserNotificationReceiveResponse
481. _CFUserNotificationGetResponseValue
482. _CFUserNotificationGetResponseDictionary
483. _CFUserNotificationUpdate
484. _CFUserNotificationDisplayNotice
485. _CFLog2
486. _CFHashBytes
487. _CFCopySystemVersionString
488. __CFCopySystemVersionDictionary
489. __CFCopyServerVersionDictionary
490. _CFGetExecutableLinkedLibraryVersion
491. _CFGetExecutingLibraryVersion
492. __CFExecutableLinkedOnOrAfter
493. _CFShow
494. _CFLog
495. _CFXMLNodeGetTypeID
496. _CFXMLNodeCreateCopy
497. _CFXMLNodeGetTypeCode
498. _CFXMLNodeGetString
499. _CFXMLParserGetTypeID
500. _CFXMLParserGetContext
501. _CFXMLParserGetSourceURL
502. _CFXMLParserGetLocation
503. _CFXMLParserGetLineNumber
504. _CFXMLParserCopyErrorDescription
505. _CFXMLParserAbort
506. _CFXMLParserCreate
507. _CFXMLTreeGetNode
508. _kCFCoreFoundationVersionString
509. _kCFAllocatorDefault
510. _kCFAllocatorUseContext
511. ___CFBundleMagicNumbersArray
512. _kCFAbsoluteTimeIntervalSince1970
513. _kCFAbsoluteTimeIntervalSince1904
514. _kCFCoreFoundationVersionNumber
515. ___CFBundleExtensionsArray
516. ___CFBundleLocaleAbbreviationsArray
517. ___CFBundleLanguageAbbreviationsArray
518. _CFNastyFile
519. ___CFOASafe
520. ___CFConstantStringClassReference
521. ___CFDefaultEightBitStringEncoding
522. _kCFTypeArrayCallBacks
523. _kCFTypeBagCallBacks
524. _kCFCopyStringBagCallBacks
525. _kCFNull
526. _kCFAllocatorSystemDefault
527. _kCFAllocatorMalloc
528. _kCFAllocatorNull
529. _kCFStringBinaryHeapCallBacks
530. _kCFBundleInfoDictionaryVersionKey
531. _kCFBundleExecutableKey
532. _kCFBundleIdentifierKey
533. _kCFBundleVersionKey
534. _kCFBundleDevelopmentRegionKey
535. _kCFBundleLocalizationsKey
536. __kCFBundlePackageTypeKey
537. __kCFBundleSignatureKey
538. __kCFBundleIconFileKey
539. __kCFBundleDocumentTypesKey
540. __kCFBundleURLTypesKey
541. _kCFBundleNameKey
542. __kCFBundleShortVersionStringKey
543. __kCFBundleGetInfoStringKey
544. __kCFBundleTypeNameKey
545. __kCFBundleTypeRoleKey
546. __kCFBundleTypeIconFileKey
547. __kCFBundleTypeOSTypesKey
548. __kCFBundleTypeExtensionsKey
549. __kCFBundleTypeMIMETypesKey
550. __kCFBundleURLNameKey
551. __kCFBundleURLIconFileKey
552. __kCFBundleURLSchemesKey
553. __kCFBundleOldIconFileKey
554. __kCFBundleOldDocumentTypesKey
555. __kCFBundleOldTypeNameKey
556. __kCFBundleOldTypeRoleKey
557. __kCFBundleOldTypeIconFileKey
558. __kCFBundleInfoPlistURLKey
559. __kCFBundleNumericVersionKey
560. __kCFBundleExecutablePathKey
561. __kCFBundleCFMLoadAsBundleKey
562. __kCFBundleAllowMixedLocalizationsKey
563. ___kCFCSetNameControl
564. ___kCFCSetNameWhitespace
565. ___kCFCSetNameWhitespaceAndNewline
566. ___kCFCSetNameDecimalDigit
567. ___kCFCSetNameLetter
568. ___kCFCSetNameLowercaseLetter
569. ___kCFCSetNameUppercaseLetter
570. ___kCFCSetNameNonBase
571. ___kCFCSetNameDecomposable
572. ___kCFCSetNameAlphaNumeric
573. ___kCFCSetNamePunctuation
574. ___kCFCSetNameIllegal
575. ___kCFCSetNameCapitalizedLetter
576. ___kCFCSetNameStringTypeFormat
577. _kCFTypeDictionaryKeyCallBacks
578. _kCFCopyStringDictionaryKeyCallBacks
579. _kCFTypeDictionaryValueCallBacks
580. _kCFBooleanTrue
581. _kCFPlugInDynamicRegistrationKey
582. _kCFPlugInUnloadFunctionKey
583. _kCFPreferencesCurrentApplication
584. _kCFPreferencesCurrentHost
585. _kCFRunLoopDefaultMode
586. _kCFTypeSetCallBacks
587. _kCFCopyStringSetCallBacks
588. _kCFSocketNameKey
589. _kCFSocketValueKey
590. _kCFSocketResultKey
591. ___kCFSocketRegistryRequestRunLoopMode
592. _kCFEmptyString
593. _kCFNSDecimalSeparatorKey
594. _kCFURLFileScheme
595. _kCFURLLocalhost
596. _kCFURLFileExists
597. _kCFURLFilePOSIXMode
598. _kCFURLFileLength
599. _kCFFileURLExists
600. _kCFFileURLPOSIXMode
601. _kCFFileURLDirectoryContents
602. _kCFFileURLSize
603. _kCFFileURLLastModificationTime
604. _kCFHTTPURLStatusCode
605. _kCFHTTPURLStatusLine
606. _kCFUserNotificationTokenKey
607. _kCFUserNotificationTimeoutKey
608. _kCFUserNotificationFlagsKey
609. _kCFUserNotificationIconPathKey
610. _kCFUserNotificationSoundPathKey
611. _kCFUserNotificationLocalizationPathKey
612. _kCFUserNotificationTextFieldLabelsKey
613. _kCFUserNotificationSoundURLKey
614. _kCFUserNotificationAlertHeaderKey
615. _kCFUserNotificationAlertMessageKey
616. _kCFUserNotificationDefaultButtonTitleKey
617. _kCFUserNotificationAlternateButtonTitleKey
618. _kCFUserNotificationProgressIndicatorValueKey
619. _kCFUserNotificationCheckBoxTitlesKey
620. __kCFSystemVersionProductNameKey
621. __kCFSystemVersionProductCopyrightKey
622. __kCFSystemVersionProductVersionKey
623. __kCFSystemVersionProductVersionExtraKey
624. __kCFSystemVersionBuildVersionKey
625. __kCFSystemVersionProductVersionStringKey
626. __kCFSystemVersionBuildStringKey

CFNetwork

CFNetwork is a companion to CoreFoundation, and provides key networking features to applications.

While it was available as part of Darwin 8 (OS X 10.4), with the release of Darwin 9 (OS X 10.5) it became closed source. However, the source code for the last version released under Darwin 8 is still available from Apple, and with minor patching can be made to compile in the darwinbuild chroot.

CFNetwork is part of the CoreServices umbrella framework. CoreServices itself is a basic stub, existing solely to link to the framework under it.

Below as an attachement is a binary version of CFNetwork.framework, wrapped inside a CoreServices.framework. Also included is the CarbonCore.framework, which contains only header files.

Status and testing to date

Code written, compiled and linked to CoreServices on OS X will run successfully on PureDarwinXmas. The CFNetService type (the only part tested so far) operates correctly.

This software is covered by the APSL.

Resources

Apple Introduction to CFNetwork Programming Guide

Code Signing

This page is about binary signature.

Background

As of Mac OS X and Darwin, a Mach-O code signature system (similar in concept to Microsoft AuthentiCode for PE binaries on Windows, and Solaris ELF signing) has been implemented. At least on Darwin, this system is not “formally” used, and no binaries are signed.

On Mac OS X, the code signature system forms part of the basis of the “Seatbelt” GPC (Granular Process Control)/RBAC (Role Based Access Control) mechanism (an implementation detail of the Parental Control feature), and most binaries shipped are signed.

I’ve got a binary, is it signed?

There are probably many ways of checking if a binary is signed on Darwin (although some techniques could also be possible on other operating systems), and Mac OS X ships with tools for checking code signatures.

The otool Way

On Darwin, you can quickly check for the presence of a code signature with otool -l /YourBinaryOfChoice | grep LC_CODE_SIGNATURE. You’re looking for the “cmd LC_CODE_SIGNATURE” line (regardless of whether or not you decided to grep). Without grepping, output similar to the following is produced:

Load command 13``cmd LC_CODE_SIGNATURE``cmdsize 16``dataoff 574704`` `` ``datasize 7968`` The binary used in the example above was (naturally) otool from Mac OS X Leopard.

Other ways

strings YourBinaryOfChoice | grep “Apple Code Signing Certification Authority”

or

grep -b “Apple Code Signing Certification Authority” YourBinaryOfChoice

Examples on Mac OS X

Inspecting otool

codesign -dvvvv /usr/bin/otool  Executable=/usr/bin/otool Identifier=com.apple.otool Format=Mach-O universal (i386 ppc7400) CodeDirectory v=20001 size=2920 flags=0x0(none) hashes=141+2 location=embedded CDHash=ea392676d34975966fcc4471c3d85dee70978255 Signature size=4064 Authority=Software Signing Authority=Apple Code Signing Certification Authority Authority=Apple Root CA Info.plist=not bound Sealed Resources=none Internal requirements count=0 size=12

The Apple object file utility shipped with Mac OS X is signed, in the contrary of the one built from DarwinBuild.

codesign -dvvvv /Volumes/Builds/9F33/BuildRoot/usr/bin/otool  /Volumes/Builds/9F33/BuildRoot/usr/bin/otool: code object is not signed

Note: No “impurity” detected at ‘codesign’ inspection with ‘otool’, so perhaps it could be build with the DarwinBuild project and be available in PureDarwin.

Verifying the dynamic validity of a process

In this example, we will take ‘launchd’ process, which also run as an ‘init’ replacement.

ps ux -p1 USER   PID %CPU %MEM      VSZ    RSS   TT  STAT STARTED      TIME COMMAND root     1   0.0  0.0   600820    552   ??  Ss    9:46PM   0:00.42 /sbin/launchd

codesign -vvvv 1 1: dynamically valid 1: satisfies its Designated Requirement

Note: The “-h” options seems not (yet) documented but remains functional:

codesign -h 1 /sbin/launchd /mach_kernel

Miscellaneous

Related fields found in Xcode:

Resources

Apple Technical Note TN2206: Mac OS X Code Signing In Depth The Apple Mac OS X 10.5 codesign Manual Page is attached to this page (PDF) Sun Solaris 10 elfsign(1) Manual Page

man codesign man csreq

Current Blockers

This page lists the current issues we are having that prevent us from making a Darwin 9 ISO. The contents of this page are subject to change.

1. Problems to be solved

1.1 CFOpenDirectory missing in CFOpenDirectory binary root

OpenDirectory framework depends on CFOpenDirectory framework, for which there is both a project and a binary root. However, the binary root does not contain the actual CFOpenDirectory file (http://darwinbuild.macosforge.org/trac/ticket/50):

otool -L OpenDirectory.root/System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/OpenDirectory | grep CFO
/System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
(compatibility version 1.0.0, current version 1.0.0)

The sources cannot be built without being patched because it depends on missing CoreFoundation headers (e.g., CoreFoundation/CFBridgingPriv.h) and on DirectoryServiceCore (part of DirectoryService which cannot yet be built too).

1.2 IOHDIXController.kext needed (image boot support)

BinaryDriver IOHDIXController.kext is missing (used to be available under Apple Driver License) in order to use imageboot. Please let us know if you know a solution.

1.3 OSvKernDSPLib.kext needed (audio support)

BinaryDriver OSvKernDSPLib.kext is missing, consequently IOAudioFamily.kext cannot be loaded resulting in no audio support.

Please let us know if you know a solution.

1.4 Shortage of network drivers

There is a shortage of network drivers (and of other drivers in general) for Darwin. Of particular concern, the Intel e1000 driver AppleIntel8254XEthernet.kext, needed to run networking under VMWare, while available in OS X are not available for general distribution nor redistributable. Open source drivers for a vast number of network cards (and hardware of every type) are available for other platforms (e.g., BSD and GNU/Linux). See the Network page for more information. It would be great if someone skilled in driver programming could port some of these to Darwin (we are told that writing drivers for IOKit is really a rather nice experience).

1.5 SystemConfiguration.framework is incomplete

SystemConfiguration.framework (in the configd package) does not compile, and the binary root made available is incomplete. While some components can be made to compile individually (see the Network page for a download), there are still important components (ATConfig and KernelEventMonitor) missing. KernelEventMonitor can be built (part of configd_plugins which not build because it depends on configd which not build without patch and code sacrifice):

file BuildRoot/private/var/tmp/configd_plugins/configd_plugins-
91.root/System/Library/SystemConfiguration/KernelEventMonitor.bundle/Contents/MacOS/KernelEventMonitor
BuildRoot/private/var/tmp/configd_plugins/configd_plugins-
91.root/System/Library/SystemConfiguration/KernelEventMonitor.bundle/Contents/MacOS/KernelEventMonitor: Mach-O universal binary with 2
architectures
BuildRoot/private/var/tmp/configd_plugins/configd_plugins-
91.root/System/Library/SystemConfiguration/KernelEventMonitor.bundle/Contents/MacOS/KernelEventMonitor (for architecture i386): Mach-O
bundle i386
BuildRoot/private/var/tmp/configd_plugins/configd_plugins-
91.root/System/Library/SystemConfiguration/KernelEventMonitor.bundle/Contents/MacOS/KernelEventMonitor (for architecture ppc7400): Mach-O
bundle ppc

1.6 gdb does not compile

Software development (for example, of PureFoundation or device drivers) is hampered by the lack of a native debugged for Darwin. gdb uses parts of the old Carbon runtime in a single component. However, this is preventing the package as a whole from compiling. Non-Apple gdb cannot be used because it does not understand Darwin’s Mach-O binary format. (You only need to install DebugSymbols.framework and CoreServices.framework into PureDarwin Xmas to get gdb running, but since these are closed-source and non-distributable you wouldn’t want to do that, would you?)

1.7 DirectoryService daemon depends on missing CFLite functions

DirectoryServices, the daemon responsible for (surprise surprise) Directory Services, makes use of CFFileDescriptors and CFNotificationCenters, neither of which are present in the current release of CFLite. The latest patched CFLite produced as part of the PureFoundation project includes basic implementations of these functions which allows DirectoryService to run.

2. Problems with partial workarounds

2.1 OpenDirectory depends on Foundation

OpenDirectory depends on Foundation which is not available in Darwin. This is a vital component of Darwin linked implicitly to the login infrastructure, consequently multi-user mode fails.

passwd
dyld: Library not loaded: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
  Referenced from: /System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/OpenDirectory

The dependency of the OpenDirectory project on Foundation should be removed. http://darwinbuild.macosforge.org/trac/ticket/49 See Foundation replacement called PureFoundation.

2.2 launchd does not build

This is a mission critical component of Darwin. http://darwinbuild.macosforge.org/trac/ticket/9 Maybe related: “Logged as radar 5802196: Unable to build TOT launchd from macosforge.org” (source)

Patched its sources. Please let us know if you know a cleaner solution.

2.3 IOKitUser does not build

Patched its sources. Please let us know if you know a cleaner solution.

3. Problems that are problems no more

3.1 diskarbitrationd fails with “_SCSerialize() failure” errors

This was caused by CFLite not supporting a certain mode of operation of a particular CF function. Building CFLite with the latest PureDarwin patch will restore this functionality and allow diskarbitrationd to run correctly.

3.2 CF missing symbols

__kCFBundleResourceSpecificationKey referenced by some dependents (e.g., Security framework) is expected in CF but missing. Patching the source code to restore this symbol and others (for example, exception names) has proved successful. To apply these patches, follows the instructions for initialising the darwinbuild environment as described in Using DarwinBuild.

3.3 libauto.dylib missing

Apple has released autozone-77 under the Apache License 2.0. Thanks, Apple!

Darwin mailing lists

darwin-dev

darwinbuild-dev

Example of how to build a plist for Darwinbuild if a project requires it and it’s not in the default SDK from Xcode.

<key>AppleI386PCI</key>
	<dict>
		<key>dependencies</key>
		<dict>
			<key>build</key>
			<array>
				<string>bash</string>
				<string>distcc</string>
				<string>file_cmds</string>
				<string>gcc</string>
				<string>gcc_os</string>
				<string>gcc_select</string>
				<string>jam</string>
				<string>shell_cmds</string>
				<string>system_cmds</string>
				<string>text_cmds</string>
			</array>
			<key>header</key>
			<array>
				<string>xnu</string>
				<string>IOPCIFamily</string>
			</array>
			<key>staticlib</key>
			<array>
				<string>Libcpp_kext</string>
				<string>xnu</string>
			</array>
		</dict>
		<key>environment</key>
		<dict>
			<key>RC_ARCHS</key>
			<string>i386</string>
			<key>SYSTEM_LIBRARY_DIR</key>
			<string>/System/Library</string>
		</dict>
		<key>version</key>
		<string>6.1</string>
	</dict>

Development environments

draft.

Status

Most of libraries, headers and developer tools (e.g. a compiler) comes from the Darwinbuild project and/or the MacPorts project.

gcc

gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /Volumes/One/darwin-build-testing/9A581/BuildRoot/private/var/tmp/gcc/gcc-5465.obj/src/configure –disable-checking -enable-werror –prefix=/usr –mandir=/share/man –enable-languages=c,objc,c++,obj-c++ –program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ –with-gxx-include-dir=/include/c++/4.0.0 –with-slibdir=/usr/lib –build=i686-apple-darwin9 –with-arch=apple –with-tune=generic –host=i686-apple-darwin9 –target=i686-apple-darwin9 Thread model: posix gcc version 4.0.1 (Apple Inc. build 5465)

llvm

llvmc –version Low Level Virtual Machine (http://llvm.org/):   llvm version 2.5   Optimized build with assertions.   Built Jul 30 2009(19:01:55).

llvm (Low Level Virtual Machine) from http://llvm.org/ can be built and installed in a chroot at this time:

[…] llvm[4]: ======= Finished Linking Release Executable Sample (without symbols) make[1]: Nothing to be done for `all’. llvm[0]: ***** Completed Release Build

Disk images

This page describes various formats for disk images used in Darwin, Mac OS X, and Linux. This is a work in progress. Please add to the table.

Note that this page might mention tools that are only available in Mac OS X, but not in PureDarwin.

Hard disk images

.dmg (disk image)

.dmg files can contain either an image of one volume (partition) or of an entire disk (device; including the MBR).

These files are used on the Mac. They can be created by Disk Utility, for example. file reports “VAX COFF executable - version 8122” for compressed images. To mount these on a PureDarwin system, they need to be uncompressed first using the dmg2img utility. Here is an example:

URL="http://macfuse.googlecode.com/files/MacFUSE-2.0.3%2C2.dmg"
DMG="MacFUSE-2.0.3,2.dmg"
MOUNTPOINT=/Volumes/test/
VN=/dev/vn0
set +v # be verbose
set +e # exit on errors
wget -c "${URL}" # download compressed DMG
IMG=$(echo "${DMG}" | sed -e "s|.dmg$|.img|g" ) # get name of IMG
dmg2img "${DMG}" -o "/tmp/${IMG}" -v # uncompress to IMG, http://trac.macports.org/ticket/23489
vndevice attach /dev/vn0 "/tmp/${IMG}" # attach IMG to device
mkdir "${MOUNTPOINT}" # create mount point
mount -t hfs "${VN}" "${MOUNTPOINT}" # mount
find "${MOUNTPOINT}" -iname Archive.pax.gz # do something
# install (to be written)...
umount "${MOUNTPOINT}" && rm -r "${MOUNTPOINT}" # unmount
vndevice detach "${VN}" # detach device
rm "/tmp/${IMG}" # delete IMG

The dmg2img utility can be compiled on a PureDarwin system using MacPorts (see #23489).

.dd/.cdr (raw image)

These files are raw dumps, as the dd program uses them. You can convert .dmg files to these on the Mac, using the following command:

hdiutil convert some.dmg -format UDTO -o some.dd

hdiutil uses the suffix “.cdr” for these files, but in fact the result is a raw dump that can be used with standard, cross-platform tools such as dd. This is why we prefer the “.dd” suffix. 

To write a raw dump to a physical disk:

CAUTION: the following commands are dangerous. You might accidentially wipe your hard disk. Do not use this if you do not know what you are doing.

• On the Mac, it can be written with

   dd if=some.dd of=/dev/rdiskX bs=2048

• On Linux, it can be written with

    dd if=some.dd of=/dev/sdaX bs=2048

.vmdk (Virtual Machine Disk Format)

In this case we use qemu-img.

qemu-img convert -O vmdk PureDarwin.iso PureDarwin.vmdk

CD/DVD images

These are .isos (ISO 9660 CD-ROM filesystem data)

First, you need to populate a temporary directory that contains the boot-132 files and that has cdboot as its El Torito boot image (this allows BIOS-based machines to boot).

ELTORITOISO=/tmp/eltorito.iso
cp cdboot ... /tmp/i386/
cd /tmp/i386

From the temporary directory, run mkisofs:

mkisofs -quiet -V "PureDarwin" -no-emul-boot -boot-load-size 4 -c boot.cat -b cdboot -o "$ELTORITOISO"

In order to retreive the sector count:

sectors=$(du "$ELTORITOISO" | tail -1 | awk '{print $1}')
size_mb=$(du -h "$ELTORITOISO" | tail -1 | awk '{print $1}')

Then create, initialize and mount a HFS+ disk image (dmg)

hdiutil create -fs HFS+J -o "$CDDMG" -size 256M -layout NONE -type UDIF -nospotlight

Partitioning with pdisk + newfs_hfs

(please add text)

The tricky way is to “injects” parts of the temporary El Torito ISO into the dmg using

dd if="$ELTORITOISO" of=$rdev skip=64 seek=64 bs=512

Dump a CD/DVD to an iso image

(please add text)

hdiutil create -srcdevice /dev/disk1s0 -format UDTO some.iso # create the image
mv some.iso.cdr some.iso # manually remove the forced .cdr extension

Hybrid media

Up to four file systems supported: HFS+, ISO-9660, Joliet and/or UDF.

   -hfs Generate an HFS+ filesystem    -iso Generate an ISO9660 filesystem    -joliet Generate Joliet extensions to ISO9660    -udf Generate a UDF filesystem

(Please write some text)

hdiutil makehybrid -o ... ...

Bootable CDs

For bootable CDs, see here.

Mounting DMGs on PureDarwin

It looks like compressed DMGs (UDIF) cannot readily be mounted on PureDarwin since Darwin lacks the neccessary frameworks (e.g., DiskImages.framework) and/or kernel extensions (e.g., IOHDIXController.kext and its plug-ins) that Mac OS X uses for this purpose.

IOHDIXController.kext used to be distributed with Darwin under the Apple Binary License. Perhaps that’s what we need to do for PureDarwin as well.

vndevice

Using the raw BSD vndevice would mean that we cannot seemingly use compressed DMGs (UDIF). Since we want to use a compressed filesystem, it appears that the raw vndevice approach is not an option for PureDarwin.

hdik

Mac OS X comes with a little tool called hdik. Its description reads like it could exactly do what we need in PureDarwin:

   hdik is a lightweight tool that can be used to attach disk images in-kernel (i.e. not using a user-land process to providing the backing store).    Only a subset of disk images can be mounted in this manner including      read/write disk images, UDIF disk images that use zlib compression, shadowed disk images, and sparse disk images.

  hdik is intended for use in situations where linking against the DiskIm-    ages framework is problematic or an extremely lightweight mechanism for    attaching a disk image is needed.

And it looks like it has no “impure” dependencies. However, it apparently calls /usr/libexec/load_hdi which, according to its man page, “is used to load the disk image driver.  load_hdi is invoked by the DiskImages framework when it needs to attach images and the user client in IOHDIXController.kext is not available”.

Besides, it looks like the source for hdik is not available. Apparently, hdik is part of the closed-source project DiskImages-195. So it appears that it is not an option for PureDarwin either.

Source code as starting point for own developments

For compressed DMGs (UDIF) see here (sample code in Java) and here (C) Also have a look at this: https://svn.greensocs.com/public/packages/qemu_systemc/qemu-0.9.1/block-dmg.c

Conversion of disk images using LibDMG’s HFS+ implementation

This log should be cleaned up, when I (Tyson) get around to it:

(11:04:38 AM) errordeveloper: hi

(11:05:56 AM) errordeveloper: I just had a bit of experience with getting a dmg image converted into a raw disk image with 1 partion

(11:06:12 AM) errordeveloper: so poweriso and dmg2img didn’t work for me

(11:06:30 AM) errordeveloper: both produced a wrong kind of image

(11:06:46 AM) errordeveloper: which I couldn’t validate with fdisk/parted

(11:06:59 AM) errordeveloper: then I found this:

(11:07:02 AM) errordeveloper: https://github.com/planetbeing/libdmg-hfsplus/>

(11:07:13 AM) errordeveloper: commit d4a253cae40fb4b38377273eb1f89f21c4cb224a

(11:08:13 AM) errordeveloper: ^ current state of the master branch is a bit broken, but all I had to do was just to add one variable which was not defined for some reason

(11:08:53 AM) errordeveloper: after it compiled, I got the ‘dmg’ util to convert the image

(11:09:19 AM) errordeveloper: and the result turned out to be valid in parted

(11:09:29 AM) errordeveloper: now

(11:09:53 AM) errordeveloper: the problem is that http://www.puredarwin.org/developers/diskimages is not a wiki page

(11:10:10 AM) errordeveloper: and I cannot simpy add this info there, so other might find it usefull

DTrace

This page is about the DTrace facility in “Darwin-land”.

What is DTrace?

According to man dtrace:

The dtrace command is a generic front-end to the DTrace facility. The
command  implements  a  simple  interface to invoke the D language com-
piler, the ability to retrieve buffered trace data from the DTrace ker-
nel  facility,  and  a set of basic routines to format and print traced
data.

Simply, DTrace is:

• a dynamic debugger and analysis tool (first appeared in Solaris 10 and OpenSolaris, then in Mac OS X 10.5)
• a D programming language interpreter 
• a monitoring tool (ie: Observing devices, such as disk or network activity) 
• a profiling tool (performance analysis) 
• a process, library, user function, (some) kernel function, the operating system (itself) inspector tool 
• a bug finder
• scalable 

DTrace may also be used as (or be a part of) 

• a malware investigation tool 
• a process deciphering tool 
• a Troubleshooting software bugs 
• a partial intrusion detection system 
• an educative software (in order to explore, and understand how this operating system works) Notes: Although PureDarwin is focused on i386, DTrace supports most of common architectures (-arch i386|x86_64|ppc|ppc64). In Mac OS X 10.5, Instruments.app found in developer tools is another front-end to the DTrace facility. Warning:

Pros

• Every process, or specific processes, can be traced “simultaneously”.
• Output is fully flexible.
• Nanosecond timestamp for function execution measurements.
• Minimum performance impact when used smartly.
• No need to restart anything in order to trace.
• Relatively safe.

Cons

• Partially supported (around 20K probes available instead of 60K) on Darwin (
• DTrace cannot fetch low levels hardware data.
• Performance impact when probe count goes under 36,000 probes (every kernel function entry/return) and 100,000 probes function in user-land. Consequently, not really suited for security auditing, because DTrace may drop events if the system is really busy or simply (but dramatically in this case) abort.
• Need to be run as root (not sure it should belong to “cons” part).

Examples

A real world example: show missing files

On Linux systems, “strace -eopen -f … 2>&1 | grep ENOENT” can be used to see which files a process tries to open. Using dtrace, the equivalent is:

1. Open two terminals
2. In the first terminal, run: opensnoop -ex
3. In the second terminal, run the command that you want to inspect In the first terminal, you will see the files that are tried to be opened but fail to open (e.g., ENOENT).

A cliché example: “Hello world!”

Inline

dtrace -n “BEGIN { trace(“Hello World!”); exit(0);}“ dtrace: description ’BEGIN ’ matched 1 probe CPU     ID                    FUNCTION:NAME   0      1                           :BEGIN   Hello World!

In a file

Edit and save Hello.d: BEGIN  {  trace(“Hello World!”);  exit(0);  } Then run the script: dtrace -s Hello.d 

dtrace: script ‘Hello.d’ matched 1 probe CPU     ID                    FUNCTION:NAME   0      1                           :BEGIN   Hello World!

Detect new process (successfully started)

proc:::exec-success { printf("%s(pid=%d) started by uid - %dn",execname, pid, uid); }

Detect sigkill

proc:::signal-send /args[2] == SIGKILL/ {   printf(“to %s”,args[1]->pr_fname);   printf(“ at %d“, timestamp);   printf(“ by (%d)“, uid);   printf(” from %sn“, execname); }

Detect promiscuous mode changes

fbt:mach_kernel:ifnet_set_promiscuous:* {    printf("%s", execname); }

Watch setuid/setgid calls

/* '*' == {entry|return} */ fbt:mach_kernel:setuid:* {    printf("%s", execname); } fbt:mach_kernel:setgid:* {    printf("%s", execname); }

Classic examples

DTrace one-liners The DTraceToolkit (~100 scripts) D Programming language

It seems to have been based on C language for some parts. (please add text)

1. D programs are compiled in user-land
2. And sent to the DTrace virtual machine in the kernel-land
3. Then run inside the kernel’s address space (not in the DTrace process, nor in the target process)

     copyin()      Copies len bytes of data from the user-space address uaddr                    to the kernel-space address kaddr.

     copyinstr()   Copies a NUL-terminated string, at most len bytes long,                    from user-space address uaddr to kernel-space address                    kaddr.  The number of bytes actually copied, including the                    terminating NUL, is returned in *done.

A generic D script example

probe description /predicate/ {    action }{style=“font-family:courier new,monospace”}

Probes and providers

A provider is a collection of probe.

Probe syntax

Four fields describe a probe: provider:module:function:name Examples: fbt:mach_kernel:setuid:entry syscall::open*:entry Notes: Some special characters *, ?, [, and ] are allowed. * is the well known wildcard extension.  ? character is for any single character in the name.  [ and ] characters are used to specify a set of specific characters in the name.

Listing probes

dtrace -l lists all available probes.

   ID   PROVIDER            MODULE                          FUNCTION NAME     1     dtrace                                                     BEGIN     2     dtrace                                                     END     3     dtrace                                                     ERROR     4   lockstat       mach_kernel                      lck_mtx_lock adaptive-acquire [...]

22527 plockstat1 libSystem.B.dylib    pthread_rwlock_unlock$UNIX2003 rw-release

Available providers

Some providers (non exhaustive list):

 Probe name  Description  fbt  Function boundary tracing

 io  Physical I/O requests/events  mach_trap  Kernel traps

 proc  Process functions

 profile  Sample count activity?

 syscall  Kernel system calls

 vminfo  

Default variables

FIXME

** Variable name**  Description

 arg0…argN  Function arguments and return value  curpsinfo  Structure of current process information  errno  Error code  execname  Processname  pid  Process id  probefunc  Probe function name  probename  Probe name  tid  Thread id  timestamp  Nanoseconds since boot

Macro variables

FIXME

+--------------------------------------+--------------------------------------+
| <span                                | <span                                |
| style="font-weight:bold"> Macro     | style="font-weight:bold"> Descripti |
| name                                | on</span>                            |
| </span>                              |                                      |
+--------------------------------------+--------------------------------------+
|  $[0-9]+                         |  macro arguments                    |
+--------------------------------------+--------------------------------------+
|  $egid                             |  effective group id                 |
+--------------------------------------+--------------------------------------+
|  $euid                             |  effective user id                  |
+--------------------------------------+--------------------------------------+
|  $gid                              |  real group id                      |
+--------------------------------------+--------------------------------------+
|  $pid                              |  process id                         |
+--------------------------------------+--------------------------------------+
|  $pgid                             |  process group id                   |
+--------------------------------------+--------------------------------------+
|  $ppid                             |  parent process id                  |
+--------------------------------------+--------------------------------------+
|  $projid                           |  project id                         |
+--------------------------------------+--------------------------------------+
|  $sid                              |  session id                         |
+--------------------------------------+--------------------------------------+
|  $target                           |  target process id                  |
+--------------------------------------+--------------------------------------+
|  $taskid                           |  task id                            |
+--------------------------------------+--------------------------------------+
|  $uid                              |  real user id                       |
+--------------------------------------+--------------------------------------+

Predicate (optional)

When the predicate evaluates to true, “action” is executed.

** Predicate Name** ** Description**

 cpu == 0  true if the probe executes on cpu0  ppid !=0  true if the parent process id is not 0

 arg0 == 0  true if first argument is 0  ppid !=0 && arg0 == 0  …

Action (optional)

C-style functions and semicolon (;) separation for the “body”. Examples: printf(), ustack(), trace, …

Kernel destructive actions

Understand “destructive for the running OS”.

“-w” flag required for…

-w  permit destructive actions

• void stop()
• voir raise()
• void breakpoint(void)
• void chill(int nanoseconds)
• void panic(void) panic: We are hanging here…  It can force a kernel crash dump. FIXME

References

man dtrace man dtruss man procsystime

Jon Haslam. http://wikis.sun.com/display/DTrace/Security, Sun Microsystems, 2008. Glenn Brunette & Jon Haslam. Enhancing Security Awareness with DTrace, Sun Microsystems, 2006. How To Use DTrace. http://www.sun.com/software/solaris/howtoguides/dtracehowto.jsp, Sun Microsystems, 2005. Solaris Dynamic Tracing Guide. http://docs.sun.com/app/docs/doc/817-6223, Sun Microsystems, 2005.

GNUstep

GNUstep is a cross-platform environment that provides partially Cocoa-compatible frameworks. This page is a work in progress and is currently just a placeholder and space for collecting all things related to GNUstep.

About GNUstep

GNUstep is a cross-platform environment loosely compatible with Cocoa. It is available for Linux, for example, and also for PureDarwin (via MacPorts). By the way, WindowMaker and GNUstep are different things and are often confused by people.

Building GNUstep for PureDarwin

Follow the instructions on the MacPorts page (important) and https://trac.macports.org/ticket/14176, https://trac.macports.org/ticket/16425, then do

sudo /opt/local/bin/port archive gnustep +puredarwin

(This is a work in progress.)

Compiling a “Cocoa” hello world on Ubuntu

apt-get install gnustep build-essential libfoundation1.0-dev gnustep-devel gnustep-make libgnustep-base-dev gobjc # maybe too much

source.m

#import <Foundation/Foundation.h>
int
main (void)
{
  NSLog (@"Executing");
  return 0;
}

GNUmakefile

include $(GNUSTEP_MAKEFILES)/common.make
TOOL_NAME = LogTest
LogTest_OBJC_FILES = source.m
include $(GNUSTEP_MAKEFILES)/tool.make

Compile

export GNUSTEP_MAKEFILES=/usr/share/GNUstep/Makefiles # needed?
. /usr/share/GNUstep/Makefiles/GNUstep.sh
make
obj/LogTest # runs
make clean
make

References

• http://wiki.gnustep.org/
• http://www.cocoabuilder.com/archive/message/cocoa/2007/12/10/194725
• http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/WritingMakefiles.html

Graphics

This page describes the graphics infrastructure on both Darwin and Mac OS X.

Sections marked with the “X” logo only apply to Mac OS X and not to Darwin. They are included here to increase the understanding of the differences between PureDarwin and Mac OS X only. 

This page is a work in progress, please contribute.

Overview

While Darwin is the operating system underlying Mac OS X, the graphical environments of PureDarwin and Mac OS X are very different. This is because most graphical aspects of Mac OS X (especially Quartz and Aqua) are proprietary, closed-source software and are not available for PureDarwin. Hence, PureDarwin uses a more traditional UNIX-like graphics system (X server), waiting a better alternative.

PureDarwin

What follows is an overview about the various terms and components that make up the graphical infrastructure of PureDarwin.

IOGraphics

The IOGraphics project consists of

• IOGraphicsFamily.kext
• IONDRVSupport.kext (legacy; apparently for very old graphics chips such as  ATI Rage series cards from around 1997, Chips and Technologies Asiliant 65550 from around 1997, used in PowerBook 2400/3400)

It is open source.

GraphicsDrivers

GraphicsDrivers is a proprietary, closed-source project that consists (or doesn’t yet include) of the following drivers: ATI

• Radeon: Drivers for a series of ATI R100-based graphics cards from 2001  (ATIRadeon.kext, ATIRadeonDVDDriver.bundle, ATIRadeonGA.plugin, ATIRadeonGLDriver.bundle)
• Radeon 8500:** **Drivers for a series of ATI R200-based graphics cards from 2001  (ATIRadeon8500.kext, ATIRadeon8500DVDDriver.bundle, ATIRadeon8500GA.plugin, ATIRadeon8500GLDriver.bundle, ATIRadeon8500VADriver.bundle)
• Radeon 9700: Drivers for a series of ATI R300-based graphics cards from 2002  (ATIRadeon9700.kext, ATIRadeon9700DVDDriver.bundle, ATIRadeon9700GA.plugin,  ATIRadeon9700GLDriver.bundle, ATIRadeon9700VADriver.bundle)
• Radeon X1000 (missing): Drivers for a series of ATI R520-based graphics cards from 2005 (ATIRadeonX1000.kext, ATIRadeonX1000GA.plugin, ATIRadeonX1000GLDriver.bundle, ATIRadeonX1000VADriver.bundle)
• Radeon X2000 (missing): Drivers for a series of ATI R600-based graphics cards from 2006 (ATIRadeonX2000.kext, ATIRadeonX2000GA.plugin, ATIRadeonX2000GLDriver.bundle, ATIRadeonX2000VADriver.bundle) Intel
• AppleIntel830: Drivers for a series of Intel 82830M-based on-board graphics found in 830M, 830MG, and 830MP chipsets from 2003 (AppleIntel830.kext, AppleIntel830GA.plugin, AppleIntel830GLDriver.bundle)
• AppleIntel915: Drivers for a series of Intel 82915G/82910GL-based on-board graphics found in the Intel 915 Express Chipset family from 2004 (AppleIntel915GA.plugin, AppleIntel915GLDriver.bundle)
• ****: Drivers for a series of Intel GMA 950-based on-board graphics from 2005  found in the Mac mini and early MacBook  (AppleIntelIntegratedFramebuffer.kext, AppleIntelGMA950.kext, AppleIntelGMA950GA.plugin,  AppleIntelGMA950GLDriver.bundle, AppleIntelGMA950VADriver.bundle)
• AppleIntelGMAX3100 (missing): Drivers for a series of Intel GMA X3100-based on-board graphics from 2007 found in the MacBook (AppleIntelGMAX3100.kext, AppleIntelGMAX3100FB.kext, AppleIntelGMAX3100GA.plugin,  AppleIntelGMAX3100GLDriver.bundle, AppleIntelGMAX3100VADriver.bundle) Legacy
• AppleAltiVecDVDDriver.bundle (relevant on PPC only)
• AppleNDRV/ATIDriver.bundle
• AppleNDRV/ATIRuntime.bundle NVidia
• GeForce.kext
• GeForce2MXGLDriver.bundle
• GeForce3GLDriver.bundle
• GeForceFXGLDriver.bundle
• GeForceGA.plugin
• NVDANV10Hal.kext: Driver for a series of NV10-based graphics cards from 1999 known as “GeForce 256”
• NVDANV20Hal.kext: Driver for a series of NV20-based graphics cards from 2001 known as “GeForce 3 Series”
• NVDANV30Hal.kext: Driver for a series of NV30-based graphics cards from 2003 known as “GeForce FX Series”/“GeForce 5”
• NVDANV40Hal.kext: Driver for a series of NV40-based graphics cards from 2004 known as “GeForce 6 Series”
• NVDANV50Hal.kext (missing): Driver for a series of G8x-based graphics cards from 2006 known as “GeForce 8 Series”, “8x00” models
• NVDAResman.kext The GraphicsDrivers project is available for use with Darwin under the Apple Driver License. The drivers in Mac OS X 10.5.5 are SourceVersion 53017 (GraphicsDrivers-5.30.17). The MacBook, MacBook Pro Software Update 1.2 contains SourceVersion 53410 (GraphicsDrivers-5.34.10). The version available for Darwin seems to be still 40024.

X server

Like most other UNIX-like operating systems, PureDarwin uses an X server to display on-screen graphics. Please see the XFree86 and X.Org pages for details.

VMware framebuffer

This is a framebuffer kext included in the VMware Tools for Mac.

IOProxyVideoFamily

http://code.google.com/p/ioproxyvideofamily/ need investigation

Mac OS X

What follows is an overview about the various terms and components that make up the graphical infrastructure of Mac OS X.

Quartz

Apple describes Quartz as the “graphics system which forms the foundation of the imaging model for Mac OS X”. The Quatz drawing engine internally uses the PDF format. It can be seen as the successor of the “Display PostScript”-based engine used in NeXTSTEP. Quartz is also responsible for rendering effects like drop shadows in the Mac OS X user interface. Quartz is contained in the closed-source, proprietary** Core Graphics** framework. According to Apple, the terms Quartz and Core Graphics are often used synonymously: “The Quartz 2D API is part of the Core Graphics framework, so you may see Quartz referred to as Core Graphics or, simply, CG”. For more information on Quartz, see the ADC documentation on Quartz. (It is roughly equivalent to what is known as a “window server” and “window manager” on other systems.)

Aqua

The term Aqua is used to describe the visual theme of the Mac OS X user interface. (It is roughly equivalent to what is known as a “skin” on other systems.)

Framebuffer

AppleIntelIntegratedFramebuffer.kext is loaded by default on Mac OS X.

Troubleshooting

AppleIntel830.kext fails to load

AppleIntel830.kext is part of the GraphicsDrivers project. ** ** Problem: 14Intel830Memory is not compatible with its superclass, 8OSObject superclass changed? ** ** Solution: Please let us know if you know the solution.

Halting the system

The command `halt’ is used to shut down the system.

kext_tools needs to be installed for `halt’ to work properly, because `halt’ calls com.apple.KernelExtensionServer and locks `kextd’. So (at the time of 9F33), we patched the kext_tools project for purity purpose, in order to avoid missing symbols expected elsewhere. Surprisedly, now `halt’ and `shutdown’ work perfectly (note: it has yet been tested with CF-lite though, and `kextcache’ depends on):

In case, `halt’ fails, this is what could happening:

WARNING: couldn't lock kext manager for reboot: %s

couldn't lock for reboot

At this time, `shutdown -s now’ is failing because of sleep:

kext_tools and its dependencies are missing in PureDarwin nano releases because they will make PureDarwin nano not “nano” anymore, explaining why halt didn’t work. halt involves IOKitUser, CF, DiskArbitration.framework and Security.framework…

HFS+ partial raw approach

draft.

How did we get there? Needed to replace some blocker as `hdid’ in pd_setup in order to be able to build PureDarwin images not only from Mac but also from PureDarwin.

Each piece is build and then “assembled” on this example:

   3:           Apple_HFS PureDarwin 305056 @ 2080   (149.0M)   

1. The raw target image file itself is created.. dd if=/dev/zero of="$TARGET" bs=512k count=$(expr $SIZE '*' 2) ..and attached to a vndevice node (does not behave as a disk device node) /usr/libexec/vndevice attach /dev/vn0 "$TARGET" Then the image/device is initialized and populated with a minimal partition map. pdisk $RDEVICE -initialize pdisk $RDEVICE -createPartition "$VOLNAME" Apple_HFS $sectors $(expr $blocks - $sectors) > /dev/null

2. The El torito image will host the volume name, the cdboot bootloader and several bootloader files.  “$MKISOFS_BIN” -quiet -V “$VOLNAME” -no-emul-boot -boot-load-size 4 -c boot.cat -b $CDBOOT -o “$T_TARGET_P2” 

   The result is then deployed via to the target image dd if=“$T_TARGET_P2” of=$RDEVICE skip=64 seek=64 bs=512

3. The HFS partition image comes also originally from /dev/zero via dd'. dd if=/dev/zero of="$T_TARGET_P3" bs=1024k count=600 vndevice’ is still involved but on another node. /usr/libexec/vndevice attach /dev/vn3 “$T_TARGET_P3” Construct a fresh HFS+ fs.. newfs_hfs -s -J -v “$VOLNAME” ${RDEVICE} ..and mount it mount -t hfs -o perm ${DEVICE} “$MOUNT”

   Finally, the HFS image is also deployed to the target image echo “ddying $T_TARGET_P2 to $RDEVICE” dd if=“$T_TARGET_P3” of=$RDEVICE seek=$sectors bs=2048

Notes: detach is not mentioned but should be used.:wq

etc.. fsck !! etc..

State

The HFS partition can be mounted in a running PureDarwin OS. If the cdrom device is attached to the node /dev/disk1: mount -o ro -t hfs /dev/disk1s0s3 /mnt

The “phys_blksz 2048 does not match journal header size 512” error message is not the first symptom of this problem, because after disabling the journalization (removing -J in `newfs_hfs’), the previous error message will not appear but the same kernel panic for same reason(s) will occur.

The `fsck’ tool will complain about bad volume header, as Disk Utility (front-end of fsck for this part).

It boots up to ‘jnl’ in case of a “bootstrap” or a “full” release, and without any problem if it is a “nano” release.

kernel panic if `fsck -fy’ has not been run on this image before as show just below:

Diffing the volume header

Diff a partition built with dd' and vndevice’ against the same one but after `fsck -fy’ on it reveals differences.

This documentation has been really usefull in this process of problem resolution: http://developer.apple.com/mac/library/technotes/tn/tn1150.html

That has also confirmed that the partition is correctly copied via `dd’ into the image, at least the problematic part we focus on.

OK The first 1024 bytes of volume (before the volume header), and the last 512 bytes of the volume (after the alternate volume header) are reserved.

OK The volume header is always located at 1024 bytes from the start of the volume.

NO A copy of the volume header, known as the alternate volume header, is stored starting at 1024 bytes before the end of the volume.

Note: All of the allocation blocks containing the volume header, alternate volume header, or the reserved areas before the volume header or after the alternate volume header, are marked as used in the allocation file. The actual number of allocation blocks marked this way depends on the allocation block size

From top to bottom, the address is growing:

0      reserved (Start of the volume) .      … 1023   reserved 1024   Start of the volume header .      … n-1024 Start of the alternate volume header (copy of the volume header) . n-512  reserved .      … n      reserver (End of the volume)

Technically, we inspect this structure in these first 1024+n bytes:

struct HFSPlusVolumeHeader {     UInt16              signature;     UInt16              version;     UInt32              attributes;     UInt32              lastMountedVersion;     UInt32              journalInfoBlock;     UInt32              createDate;     UInt32              modifyDate;     UInt32              backupDate;     UInt32              checkedDate;     UInt32              fileCount;     UInt32              folderCount;     UInt32              blockSize;     UInt32              totalBlocks;     UInt32              freeBlocks;     UInt32              nextAllocation;     UInt32              rsrcClumpSize;     UInt32              dataClumpSize;     HFSCatalogNodeID    nextCatalogID;     UInt32              writeCount;     UInt64              encodingsBitmap;     UInt32              finderInfo[8];     HFSPlusForkData     allocationFile;     HFSPlusForkData     extentsFile;     HFSPlusForkData     catalogFile;     HFSPlusForkData     attributesFile;     HFSPlusForkData     startupFile; }; typedef struct HFSPlusVolumeHeader HFSPlusVolumeHeader;

Back to the above diff of the beginning of the Volume header, take in account that not all fields, even if a difference occurs, appeard important “to patch” (e.g.: modifyDate). The main interesting diffs found are:

    UInt32              fileCount;          0000 2eec — ( -0x3 ) —> 0000 2ee9       UInt32              folderCount;        0000 052a — ( -0x2 ) —> 0000 0528 

    UInt32              freeBlocks;         0000 5090 — (+0x1F3) —> 0000 5283 

    UInt32              nextAllocation;     0001 d839 — (-0x1F1) —> 0001 d648

    HFSCatalogNodeID    nextCatalogID;      0000 356d — ( -0x7 ) —> 0000 3566     

Details

Quick info related to fields where diffs have been found before and after fsck.

attributes

UInt32              attributes;

Volume attributes (set of one bit-flags).

before fsck 8000 2100 binary: 0000 0000 0001 0010 0000 0000 0000 1000 reserv: xxxx xxx         x  xxxx xxxx xxxx xxxx enable:              x                       kHFSBootVolumeInconsistentBit is set (bit 11). Similar to kHFSVolumeUnmountedBit, but inverted in meaning. Bit should be set when a volume for writing is mounted, and be clear at the end of unmount.  If this bit is already set at mount, a consistency checking from the assumption that the volume is corrupt could be needed.

-0x100 after fsck 8000 2000

binary: 1000 0000 0000 0000 0010 0000 0000 0000

reserv: xxxx xxx         x  xxxx xxxx xxxx xxxx

http://developer.apple.com/mac/library/technotes/tn/tn1150.html#VolumeAttributes

fileCount

UInt32              fileCount;

The total number of files on the volume. The fileCount field does not include the special files. It should equal the number of file records found in the catalog file.

before fsck 0000 2ee9

-3

after fsck 0000 2eec

folderCount    

UInt32              folderCount;

Total number of folders on the volume not including the root folder. Should equal number of folder records in the catalog file minus one (the root folder in Catalog)

before fsck 0000 0528 

+2

after fsck 0000 052a

freeBlocks

UInt32              freeBlocks;

Contains the total number of unused allocation blocks.

before fsck 0000 5283 

+0x1F3 (499)

after fsck 0000 5090

nextAllocation

UInt32              nextAllocation;

Used to find where to start searching for free allocation blocks when allocation space for a file. It contains the allocation block number where the search should start. 

before fsck 0001 d648

+0x1F1

after fsck

0001 d839

Can be threated as reserved

http://developer.apple.com/mac/library/technotes/tn/tn1150.html#AllocationFile

nextCatalogID

HFSCatalogNodeID    nextCatalogID;

It appears to be an usual UInt32 which points to the next “unused” catalog ID. A catalog ID is a B-Tree.

before fsck 0000 3566

+0x7

after fsck 0000 356d

See Technical Note TN1150: HFS Plus Volume Format for more information.

HFS+

This page describes the HFS+ filesystem and how to interact with it. This is a work in progress; please contribute to this page.

What is HFS+

the HFS+ file system is an improved version of the historical Hierarchical File System (HFS). The predecessor was introduced in Mac OS. The successor is also known as Sequoia, the “new Mac OS Extended Format”. A tree data structure (B*-tree) is used in the HFS+ file system. 

How to interact with HFS+

(Please write some text)

Using Mac OS X

Mac OS X can read, write, and boot from HFS+ partitions natively. On the Mac, Disk Utility is the main tool to create and repair HFS+ partitions. (Please write some text)

Using Darwin

Darwin can read, write, and boot from HFS+ partitions natively. On Darwin, hfs_tools is the main tool to create and repair HFS+ partitions. /sbin/fsck_hfs /sbin/fstyp_hfs /sbin/mount_hfs /sbin/newfs_hfs pdisk supports HFS volume names. /usr/sbin/pdisk (Please write some text)

Using Linux

Linux can, with the appropriate driver, read and write HFS+ partitions. However, it lacks tools to create HFS+ partitions.

There is a patch to compile hfs_tools on Linux which overcomes this shortage. (Please write some text)

Using Windows

Windows cannot, per default, read or write HFS+ partitions. However, there are commercial third-party and opensource tools to do so. Opensource: http://hem.bredband.net/catacombae/hfsx.html (Please write some text)

Interprocess Communication (IPC)

Interprocess communication is a “means of information sharing and synchronization” (Singh) between processs. This page describes the various forms of IPC on a Darwin system and also shows forms of IPC not present in Darwin, but in Mac OS X.

Introduction

Processes on a typical Darwin system need to communicate with each other. The Darwin OS provides several mechanisms for such Interprocess Communication (IPC).

Forms of IPC

Since Darwin and Mac OS X are composed from various systems and infrastructures, they provide means for IPC on several different levels of the OS which will be discussed below. For a more detailed overview, read Chapter 9 of Mac OS X Internals by Amit Singh which this page is loosely structured after. 

Mach IPC

Mach IPC can approximately be compared with BSD sockets, but is more powerful and is mainly used for local machine communication. Mach IPC is a facility of the XNU kernel; it falls into two distinct categories, ports and messages. The XNU kernel implements most aspects of Mach IPC except network-transparent IPC. 

Mach ports: Kernel-provided queues of Mach messages. Tasks can send Mach messages to and receive Mach messages from Mach ports. The kernel blocks sending to full and receiving from empty Mach ports. There is also permission control for Mach ports (“port rights”) so that unauthorized processes cannot randomly access Mach ports. The kernel itself provides Mach ports to interact with resources such as tasks, threads, etc. Hence, one can see the XNU kernel as a server that serves objects through Mach ports. 

Mach messages: Can be sent and received by userspace processes through the mach_msg family of functions. Mach messages in Darwin and Mac OS X have the following structure: header, body, and trailer. There are simple and complex Mach messages, where in simple messages the body is untyped and in complex messages the body is structured. Messages can be passive (meaningful only to the sender and the receiver, but not processed by the kernel) or active (interpreted by the kernel). 

The Mach IPC implementation of Darwin and Mac OS X resides in the osfmk/ipc/ and osfmk/kern/ipc_ trees of the XNU kernel source. It is an essential part of XNU, since Mach ports play a pivotal role in the creation of Mach tasks and threads. 

launchd

Mach Exceptions

Mach Exceptions are interruptions of a program’s normal flow of operation when special conditions arise, such as errors (e.g., trying to divide by zero), when debugging (e.g., breakpoints), when using emulation/virtualization or as part of memory management.

When an exception occurs, Mach sends a Mach message to a special Mach port called an e**xception port, where an exception handler (e.g., a debugger) can pick it up and react to it. Exception ports exist at the host, task and thread levels. There is a special exception handler called the Unix exception handler which translates certain Mach exception messages to Unix signals (see below), thus bridging the Mach and Unix worlds.

Unix Signals

Unix signals are messages that are sent to running processes. Typical signals are SUGHUP, SIGKILL, SIGSEGV and others. Users most commonly use the kill command to send signals to processes. For more information on Unix signals, see Tech FAQ. In Darwin and Mac OS X, Unix signals are implemented on top of Mach Exceptions, derived from FreeBSD’s implementation.

Unnamed pipes

man ftok?

Named pipes (fifos)

man 2 mkfifo

XSI/System V IPC

The X/Open System Interface (XSI) defines a set of IPC interfaces similar to those of System V, especially message queues, semaphores, and shared memory.

POSIX IPC

POSIX IPC is defined in the POSIX Real-time Extensions of the POSIX 1003.1b-1993 standard. They are different from XSI/System V IPC despite similar names.

To be written

notifyd

notifyd is a daemon which provides basic system-wide notification support. Notifications, in the form of simple text labels, can be posted by any application using a basic Mach API. Other processes can register to receive notifications as they occur, either through signals or Mach ports. On OS X, CoreFoundation provides features, through its CFNotificationCenter functions, to post and listen for these notifications. These are missing in CFLite, although the presence of the notifyd means that patching these back in should be relatively simple.

Missing forms of IPC

Distributed Objects

Distributed Objects are a form of Remote Procedure Call (RPC) which originally appeared under NeXT. They are a feature of the Foundation.framework, which is exclusive to Mac OS X. The PureFoundation project is (slowly) bringing its features to Darwin, and hopes to eventually provide a compatible implementation of Distributed Objects.

Notifications

The form of notifications, as marshalled by notification centres, allow both intra- and interprocess communication. On OS X, compatible implementations are provided by both CoreFoundation and Foundation. CFLite lacks these functions. It is likely that a version of these functions will be patched back into CFLite.

Apple Events

Apple Events is an IPC mechanism provided by Mac OS X, but not available on Darwin. Apple Events are mainly used by the AppleScript scripting language to communicate with GUI applications. Although supported by Foundation, the PureFoundation project currently has no plans to implement Apple Events.

Credits

Chapter 9 of Mac OS X Internals by Amit Singh

References

• Wikipedia: Inter-process communication
• Apple: Mach Messaging and Mach Interprocess Communication (IPC)
• Amit Singh: Mac OS X Internals
• Mach Exception Handlers 101
• Tech FAQ: What are Unix signals?

IOKit

Kernel Extensions (KEXTs)

Darwin kernel extensions (KEXT) are modules that provide aditional functionality to the kernel, e.g., in the form of device drivers.

Minimal set of kexts needed

The kernel cannot boot at all (crashes) if there is not at least a certain set of KEXTs present. The minimal set of KEXTs required to boot Darwin 9 from USB appears to be:

• AppleACPIPlatform.kext
• AppleAPIC.kext
• AppleFileSystemDriver.kext
• AppleRTC.kext
• AppleSMBIOS.kext
• IOACPIFamily.kext
• IOATAFamily.kext
• IOHIDFamily.kext
• IOPCIFamily.kext
• IOSCSIArchitectureModelFamily.kext
• IOStorageFamily.kext
• IOUSBFamily.kext
• IOUSBMassStorageClass.kext
• System.kext

This should get the system booting from USB (At the very least, it should go beyond the Got boot device phase, so that no message Still waiting for boot device... appears).

Installing kexts

Copy the KEXT to $VOLUME/System/Library/Extensions/ and fix permissions (important):

chown -R root:wheel $VOLUME/System/Library/Extensions/ chmod -R 755 $VOLUME/System/Library/Extensions/

Determining kext dependencies

The minimal set of KEXTs above cannot, for example, boot from a CD, since the CD driver is not there. Hence, if we want to boot from CD, for example, we need to install the CD driver KEXT and its dependencies. Thus, we need to identify the dependencies.

In order to determine the dependencies of a KEXT, we can use kextlibs. Example:

kextlibs $VOLUME/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDC.kext com.apple.kpi.libkern = 9.2.2 com.apple.kpi.iokit = 9.2.2 com.apple.iokit.IOUSBFamily = 3.0.8

So in this example, AppleUSBCDC.kext has three dependencies. To see which KEXT satisfies a dependency (aka dependents), use kextfind:

kextfind -case-insensitive -bundle-id -substring ‘com.apple.iokit.IOUSBFamily’ -print /System/Library/Extensions/IOUSBFamily.kext

Of course, IOUSBFamily.kext itself has its own dependencies, so we need to make that recursive if we want to find out all dependencies.

A visual overview of dependencies

Take a look at Visualize KEXTs dependencies page.

Extensions.mkext

A cache of installed KEXTs is kept in order to speed up boot time.

Unpack Extensions.mkext

Extensions.mkext can be unpacked with the mkextunpack command:

mkextunpack -v -d /tmp/Extensions Extensions.mkext

Force cache update

To force cache update, simply change the modification date of $VOLUME/System/Library/Extensions:

touch $VOLUME/System/Library/Extensions

Types of kexts

Driver KEXTs

(To be written)

Family KEXTs

Family KEXTs are not drivers. Family KEXTs generally contain classes that you are to subclass

Filesystem KEXTs

Filesystem KEXTs are not drivers. 

Visualize KEXTs dependencies

In the spirit of Visualize dependencies in MacPorts, this page describes a way to track kernel extension dependencies and related satellite information (e.g: blockers).

Prerequisites

Graphviz is an opensource graph visualization software from AT&T Laboratories and Bell Laboratories (Lucent Technologies).

port install graphviz +the_variants_you_need

or grab and compile the source from graphviz.org. Note: On Mac OS X, Pixelglow is a nice a front-end, you can even see the graph being built in real-time.

Using pd_kextviz to generate a graph

The pd_kextviz tool is available in the svn or hg trunks.

Preliminary

A rudimentary legend is generated in the DOT language:

A KEXT is simply linked to ia bundle identifier (which can be linked to one or many KEXTs).

For clarity purpose, the bundle identifiers are hidden by default.

For purity purpose, each KEXT is examined once in order to find and count potential “current blocker”.

The number of symbols missing (returned by kextlibs) is also displayed on the respective KEXT.

An example across IOBDStorageFamily.kext

The hierarchical view:

This circular view:

The corresponding script output:

./pd_kextviz /System/Library/Extensions/IOBDStorageFamily.kext

 Legend:  1 + foo ()  2 |- bar (bundle id)                                 No more dependency  2 |+ baz impure! /Blocker_1 -> file_involved_1       Impurity detected  2 |+ baz impure! /Blocker_. -> file_involved_.       Impurity detected  2 |+ baz impure! /Blocker_n -> file_involved_n       Impurity detected  2 |+ qux ()                                          Dependency found  3 | |. bar (cached: bundle id)                       Cached bundle identifier  1 . qux                                               Cached kext (Already processed) Now generating dependencies graphs of kexts, please wait...  1 + /System/Library/Extensions/IOBDStorageFamily.kext ()  2 |- /System/Library/Extensions/System.kext/PlugIns/Mach.kext (com.apple.kpi.mach)  2 |- /System/Library/Extensions/System.kext/PlugIns/Libkern.kext (com.apple.kpi.libkern)  2 |- /System/Library/Extensions/System.kext/PlugIns/IOKit.kext (com.apple.kpi.iokit)  2 |- /System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext (com.apple.kpi.bsd)  2 |+ /System/Library/Extensions/IOStorageFamily.kext (com.apple.iokit.IOStorageFamily)  3 | |- /System/Library/Extensions/System.kext/PlugIns/Unsupported.kext (com.apple.kpi.unsupported)  2 | |. </System/Library/Extensions/System.kext/PlugIns/Mach.kext> (cached: com.apple.kpi.mach)  2 | |. </System/Library/Extensions/System.kext/PlugIns/Libkern.kext> (cached: com.apple.kpi.libkern)  2 | |. </System/Library/Extensions/System.kext/PlugIns/IOKit.kext> (cached: com.apple.kpi.iokit)  2 | |. </System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext> (cached: com.apple.kpi.bsd)  2 |+ /System/Library/Extensions/IODVDStorageFamily.kext (com.apple.iokit.IODVDStorageFamily)  2 | |. </System/Library/Extensions/System.kext/PlugIns/Mach.kext> (cached: com.apple.kpi.mach)  2 | |. </System/Library/Extensions/System.kext/PlugIns/Libkern.kext> (cached: com.apple.kpi.libkern)  2 | |. </System/Library/Extensions/System.kext/PlugIns/IOKit.kext> (cached: com.apple.kpi.iokit)  2 | |. </System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext> (cached: com.apple.kpi.bsd)  2 | |. </System/Library/Extensions/IOStorageFamily.kext> (cached: com.apple.iokit.IOStorageFamily)  3 | |+ /System/Library/Extensions/IOCDStorageFamily.kext (com.apple.iokit.IOCDStorageFamily)  3 | | |. </System/Library/Extensions/System.kext/PlugIns/Mach.kext> (cached: com.apple.kpi.mach)  3 | | |. </System/Library/Extensions/System.kext/PlugIns/Libkern.kext> (cached: com.apple.kpi.libkern)  3 | | |. </System/Library/Extensions/System.kext/PlugIns/IOKit.kext> (cached: com.apple.kpi.iokit)  3 | | |. </System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext> (cached: com.apple.kpi.bsd)  3 | | |. </System/Library/Extensions/IOStorageFamily.kext> (cached: com.apple.iokit.IOStorageFamily)  1 |. </System/Library/Extensions/IOCDStorageFamily.kext> (cached: com.apple.iokit.IOCDStorageFamily) Generation of IOBDStorageFamily.kext.dot complete. Now drawing graphs from IOBDStorageFamily.kext.dot, please wait…` Generation of IOBDStorageFamily.kext_directed.png complete.

Generation of IOBDStorageFamily.kext_circular. png complete. Generation of IOBDStorageFamily.kext_radial. png complete. Generation of IOBDStorageFamily.kext_undirected. png complete. Generation of IOBDStorageFamily.kext_undirectedBIS.png complete.

Detecting blocker inside KEXTs

The example below has been generated on Mac OS X with IOSerialFamily.kext, since we don’t have any blocker on PureDarwin.

The corresponding output:

[...]  1 + /System/Library/Extensions/IOSerialFamily.kext impure! /CoreServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/AppleVerizonSupport.kext/Contents/Resources/FixNetworkConfig   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /AppKit.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /ApplicationServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /Cocoa.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /CoreServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /Foundation.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /CoreServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext/Contents/Resources/modemd   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /CoreServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/MotorolaSM56K.kext/Contents/Resources/MDCPd   1 + /System/Library/Extensions/IOSerialFamily.kext impure! /CoreServices.framework -> /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/MotorolaSM56KUSB.kext/Contents/Resources/MDCPdUSB

 1 + /System/Library/Extensions/IOSerialFamily.kext () […]

Generation of IOSerialFamily.kext.dot complete.

Massive generation

We generate the whole dependencies tree with:

./pd_kextviz find /System/Library/Extensions/ -name ‘*.kext’``

At this time, it looks like:

The circular overview is usefull (but often too big) to isolate node with a number of links lower than 2:

Miscellaneous

The Mac OS X whole graph:

Ressources

http://www.graphviz.org The Kernel Extensions (KEXTs) page

Live CD

Live CDs are a very popular way to distribute operating systems.

How Live CDs work

In order to make a PureDarwin Live CD, we essentially need to do two things:

1. Hardware detection. Linux Live CDs configure themselves to use the correct drivers. While this is a major breaktrough for Linux distributions, Darwin has been working like this all the time. What this means for PureDarwin is that we essentially have to ensure that we ship a broad range of kexts, and the system does the rest “for free”.
2. Compressed main filesystem. Linux Live CDs contain, besides the kernel, an initrd (a small filesystem) which loads the necessary drivers (roughly comparable to Extensions.mkext), mounts a 700 MB compressed filesystem (roughly comparable to a .dmg) that contains around 2GB of compressed software, switches over (“chroot”) to that filesystem, and continues to boot from there. For PureDarwin, we can probably achieve this by using NetBoot disk images locally.
3. Union filesystem. Because the main compressed filesystem is read-only, write accesses must be redirected to an overlay/union filesystem. Most Linux Live CDs use unionfs/aufs for this purpose. Darwin can use shadow volumes for the same purpose. A PureDarwin Live CD would attach a shadow volume that is stored in a local ramdisk to the root disk image. Mac OS X does this using the nbdst tool.

If anyone knows more about how to use NetBoot images locally, please join work on the Live CD.

How Mac OS X Installation DVDs work

Mac OS X Installation DVDs are capable of running Mac OS X from a read-only medium. Maybe we can learn from that, hence we are looking at the procedure in this paragraph.

As of Snow Leopard, Mac OS X Installation DVDs contain the launchd LaunchDaemon plist file /System/Library/LaunchDaemons/com.apple.install.cd.plist with the following content:

<?xml version="1.0" encoding="UTF-8">
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>Label</key>
 <string>com.apple.install.cd</string>
 <key>OnDemand</key>
 <false/>
 <key>ProgramArguments</key>
 <array>
   <string>/bin/sh</string>
   <string>/etc/rc.install</string>
 </array>
</dict>
</plist>

Hence, when the system is booted, the script /etc/rc.install is executed. This script mainly launches the Installer. However, there is also a script /etc/rc.cdrom which does the main magic of mounting ramdisks to.

#!/bin/sh
# (...)

#
# Disable prebinding-on-the-fly while we're CD booted
#
export DYLD_NO_FIX_PREBINDING=1

#
# mount root_device to update vnode information
#
mount -u -o ro /

# (...)

#
# Create a RAM disk with same perms as mountpoint
#
RAMDisk()
{
  mntpt=$1
  rdsize=$2
  echo "Creating RAM Disk for $mntpt"
  dev=`hdik -drivekey system-image=yes -nomount ram://$rdsize`
  if [ $? -eq 0 ] ; then
    newfs_hfs $dev
    # save & restore fs permissions covered by the mount
    eval `/usr/bin/stat -s $mntpt`
    mount -t hfs -o union -o nobrowse $dev $mntpt
    chown $st_uid:$st_gid $mntpt
    chmod $st_mode $mntpt
  fi
}


**RAMDisk /Volumes 1024**
**RAMDisk /var/tmp 1024**
**RAMDisk /var/run 1024**
**
**
**RAMDisk /var/db 1024**
mkdir -m 1777 /var/db/mds


# language prefs, colorsync need to be able to write some preferences (5424449)
**RAMDisk** **** **/Library/Preferences 1024**
**RAMDisk /Library/ColorSync/Profiles/Displays 2048**


# use or create the boot cache playlist, and allow B&I to force 32-bit playlist generation
FORCETHIRTYTWO="false"
if nvram boot-args | grep "no64exec" ; then
 FORCETHIRTYTWO="true"
fi


SIXTYFOURBIT=`sysctl -n hw.cpu64bit_capable`


if [ $SIXTYFOURBIT = "0" -o $FORCETHIRTYTWO = "true" ] ; then
 echo "using 32-bit bootcache playlist"
 BootCacheControl -f /var/db/BootCache.playlist32 start
elif [ $SIXTYFOURBIT = "1" ] ; then
 echo "using 64-bit bootcache playlist"
 BootCacheControl -f /var/db/BootCache.playlist start
fi


# tell launchd to commence with loading the system.
# for the OS Install environment only, /etc/rc.install is included in this process.
launchctl load -D system


# this script sleeps forever; the installer or startup disk will always reboot the system.
sleep 9999999

How does this script get called? **How can hdik be replaced with what is in Darwin? **Please let us know. Perhaps we could use a MacFUSE based ramdisk from http://thebends.googlecode.com/svn/trunk/ramdisk/

So far, when replacing the above RAMDisk function with one based on MacFUSE’s mount_ramdisk, we get launchctl error: launch_msg(): Socket is not connected Please let us know if you know how to solve this.

How a PureDarwin Live CD might work

Alternative 1: Uncompressed from disc

Run the system uncompressed from the CD medium (like PureDarwin nano or like the Mac OS X Install DVD).

This is not a workable option for two reasons: It’s slow (since more data needs to be read from the slow optical disc) and it’s too small (700 MB is not much space).

Alternative 2: Using imageboot

The XNU kernel contains some references to “imageboot”, e.g., here: http://fxr.watson.org/fxr/source/bsd/kern/imageboot.c?v=xnu-1228

Apparently, one should be able to boot using a boot argument like -v rp=file:///some.dmg then the system would mount /some.dmg as the root device and continue booting from there.

How this works is largely undocumented. Below is a proof-of-concept for imagebooting PureDarwin nano on a Mac host.

What follows are proof-of-concept instructions that show how to boot into puredarwin.iso (from the PureDarwin nano image on the download page) that is located at / on a Mac running Mac OS X 10.5.4. Please do not try this on a production machine. Only try this if you have a spare Mac. Download PureDarwin nano, it contains puredarwin.iso which we will use as the imageboot image On the Mac running Mac OS X (tested with 10.5.4), copy puredarwin.iso to / Change IOHDIXController.kext and its plug-ins so that they are loaded at boot time (normally, this is only the case for NetBoot):

cd /System/Library/Extensions/IOHDIXController.kext/
find . -type f | xargs perl -i -p -e 'print STDERR "changed $val values on line $. of $ARGVn" if($val = s@Network-Root@Root@g)'
touch /System/Library/Extensions

Edit /Library/Preferences/SystemConfiguration/com.apple.Boot.plist so that it contains:

<key>Kernel Flags</key>
<string>-v r p=file:///puredarwin.iso</string>

Reboot the Mac. It should now boot into PureDarwin, running from puredarwin.iso

You have now performed an ImageBoot of PureDarwin nano on a Mac OS X host.

To undo, remove the extra Kernel Flags from your Boot.plist.

There are (unverified) news reports that cite “ImageBoot” as an official feature in the not-yet-released Snow Leopard: http://www.macnn.com/articles/08/10/20/more.snow.leopard.changes

However, all attempts to make this work on a Darwin host so far resulted in

According to Singh, the kernel can be forced to use the BSD vndevice instead of hdix by specifying vndevice=1 as a boot argument. In this case, the function netboot_setup() from netboot.c is supposed to mount the file system contained in the vndevice node. But we can’t get it to work yet (and it would only work for uncompressed images).

Please let us know if you know if you are aware of a working solution that does not involve IOHDIXController.kext, or where a recent version of IOHDIXController.kext can be downloaded under a suitable license. (It used to be available under the Apple Binary License, but it made its last appearance in Darwin 6…)

As a totally desperate worst-case fallback scenario: The source code for mounting filesystem images is available, and there is source code for uncompressing compressed DMGs available. Maybe it would be feasible to write a minimal IOHDIXController.kext replacement that is able to mount compressed DMGs. Volunteers?

A set of NetBoot files created by System Image Utility looks like this:

./i386
./i386/booter
./i386/mach.macosx
./i386/mach.macosx.mkext
./NBImageInfo.plist
./NetBoot.dmg
./ppc
./ppc/booter
./ppc/mach.macosx
./ppc/mach.macosx.mkext

$ file NetBoot.dmg
NetBoot.dmg: Apple Partition data block size: 2048, first type: Apple_partition_map, name: Apple, number of blocks: 63, second type: Apple_Driver43, name: Macintosh, number of blocks: 56, third type: Apple_Free, name: , number of blocks: 0, fourth type: Apple_Driver_ATAPI, name: Macintosh, number of blocks: 56

$ file i386/booter
i386/booter: Universal EFI binary with 2 architectures, i386, x86_64

(to be continued)

Alternative 3: Using a ZFS file

Maybe using a compressed ZFS file and manual trickery…

Shadow files

This is a work in progress.

#!/bin/bash -e -x

mount -uw
touch /shadowfile

/usr/libexec/vndevice attach /dev/vn0 /uncompressed.dmg
/usr/libexec/vndevice shadow /dev/vn0 /shadowfile

mount -t hfs /dev/vn0 /live/
# /usr/libexec/vndevice detach /dev/vn0

References

• System Image Utility.app (part of Server Admin Tools for Mac OS X) can create NetBoot images; probably the same can be achieved with lower-level command line tools
• /etc/rc.netboot (mailing list entry)
• BootMania, a software that supposedly can boot Darwin (8) with NetBoot
• Server Admin Tools 10.5, contains System Image Utility which is used in Mac OS X to make NetBoot images

login

Since multi-user support is available, managing logins (so that users run with only the permissions they have been granted) follows naturally.

Console login

Console login can be achieved using the ``getty’` tool. There is a launchd plist (com.apple.getty.plist) available (but uninstalled by default - we need to add this to the next revision of Spring) as part of the system_cmds project. Installing this leads to a login prompt being displayed (as long as the startx script isn’t also run).

(The prompt gets swamped by error messages, but we’re working to eliminate them.)

Also note that getty' takes care of creating user security sessions, so the *pam_sessioncreate.so* hack is no longer needed and can be removed from /etc/pam.d/login`. It even creates the SECURITYSESSIONID environment variable, which is very nice.

SSH login

SSH login is working if an sshd server is of course running. A security session is automatically created, but the SECURITYSESSIONID environment variable is not set (which is the same behaviour as on OS X).

X login

Authorised X login is not currently supported, but should be easy enough to implement. The org.puredarwin.x.plist should invoke an “Xlogin” app instead of the default window manager, as it currently does. Since X and PAM are standards on Linux/BSD, finding the source code to such an app should not be a problem. One which doesn’t rely on any particular widget set would be preferred. The source will then need to be (very slightly) modified to include the necessary security session creation code. This won’t be very hard.

So if someone can recommend a simple X login app which we can modify, let us know. (xdm is a basic one (and there is also gdm and kdm (probably more dependencies)))) (we could also provide a X CLI one tunneled in a SSH session: ssh user@::1 -X (or -Y..) + the command which launchs X (pros: ssh authentication is reliable, the session is encrypted, ::1 force to use IPv6 sockets to localhost | con: too slow in QEMU probably))

X Display manager list

To investigate:

xdm slim enter (not maintained since last update: March 26, 2007) orthos (unsecure?) Entrance (from e17) wdm (not maitained) __ __ Ready to provide (+default choice (e.g., in bold)): ..

Smartcard login

Need to investigate: http://smartcardservices.macosforge.org/

Disable login

Disabling possibility of login on the system is also part of the management. (Remove getty and login stuff, remote_cmds, sshd, etc..) (via dscl) (removing shells) Automatically create the /etc/nologin file.

Auto login

Should we “enable” this kind of dangerous feature (it is technically possible), is it really needed?

MacFUSE

MacFUSE is a filesystem in userland. It runs well on PureDarwin and can be used to mount sshfs, ramdisk and other FUSE-based filesystems. It is, according to its maintainers, “The Easiest and Fastest Way to Create File Systems for Mac OS X” (and PureDarwin, one might add).

Installing MacFUSE

MacFUSE can be installed from the official MacFUSE.pkg (from the MacFUSE site) on PureDarwin with the following commands:

cd / ; gunzip -c “MacFUSE.pkg/Contents/Resources/10.5/MacFUSE Core.pkg/Contents/Archive.pax.gz”  | pax -r chown -R root:wheel /Library/Filesystems/fusefs.fs/Support/fusefs.kext   chmod -R 755 /Library/Filesystems/fusefs.fs/Support/fusefs.kext

Now MacFUSE is ready to use on PureDarwin.

sshfs

sshfs allows you to mount volumes over SSH.

Install the sshfs filesystem with curl “http://macfuse.googlecode.com/svn/trunk/filesystems/sshfs/binary/sshfs-static-leopard” > /usr/sbin/mount_sshfs chmod a+x /usr/sbin/mount_sshfs

Now we can mount a remote filesystem with mkdir /Volumes/SSHVolume/ mount_sshfs user@some.host:/ /Volumes/SSHVolume/ -oauto_cache,reconnect,volname=SSHVolume

ramdisk

Status: functional in PureDarwin (Darwin 9)

ramdisk is, as its name implies, a ramdisk implemented in MacFUSE. Install it with

svn co http://thebends.googlecode.com/svn/trunk/ramdisk/ ramdisk cd ramdisk/ make cp ramdisk /usr/sbin/mount_ramdisk cd - rm -rf ramdisk/

Now we can use the ramdisk command to create ramdisks:

mkdir /some/path mount_ramdisk /some/path

Troubleshooting in building ramdisk and targetting Darwin 9

In case you plan to build it on Darwin 10, a couple of adjustements must be made. Edit the Makefile and replace this line in order to be able to run it on Darwin 9:

CC = g++

by this line CC = MACOSX_DEPLOYMENT_TARGET=10.5  g++

And this line

OPTS = -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 by this line OPTS = -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -arch i386

Problem: If you encounter:

file.cpp: In constructor ‘ramdisk::File::File(ramdisk::Dir*, mode_t)’: file.cpp:17: error: ‘assert’ was not declared in this scope cc1plus: warnings being treated as errors or encounter

dir.cpp: In function ‘void ramdisk::assertNoSubdirs(const std::string&)’: dir.cpp:11: error: ‘assert’ was not declared in this scope […] dir.cpp:228: error: ‘assert’ was not declared in this scope **Solution: **Simply add #include <assert.h> in file.h per example.

Problem: cc1plus: warnings being treated as errors file.cpp: In member function ‘virtual size_t ramdisk::File::Read(char*, size_t, off_t)’: file.cpp:26: warning: comparison between signed and unsigned integer expressions Solution: Replace in file.cpp this line

  if (offset < len) {

by this line

  if ((size_t) offset < len) {

Then after a make clean' and make’, everything should be fine and run on a PureDarwin release based on Darwin9:

MACOSX_DEPLOYMENT_TARGET=10.5 g++ -Wall -Werror -g -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -c node.cpp MACOSX_DEPLOYMENT_TARGET=10.5 g++ -Wall -Werror -g -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -c file.cpp MACOSX_DEPLOYMENT_TARGET=10.5 g++ -Wall -Werror -g -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -c dir.cpp MACOSX_DEPLOYMENT_TARGET=10.5 g++ -Wall -Werror -g -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -c ramdisk.cpp ar rcs libcommon.a node.o file.o dir.o ramdisk.o MACOSX_DEPLOYMENT_TARGET=10.5 g++  -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -DFUSE_USE_VERSION=26 -o ramdisk main.cpp -L. -lcommon -lfuse

To be continued

NetBSD and the experimental Darwin binary compatibility

This is a work in progress, attempting to run some mach-o binaries on NetBSD (macppc in this case).

Appeared as a significant change in NetBSD 3.0.

Kernel stuff

/netbsd

Building the kernel with darwin support

Assuming you have set a default proper environment for compiling your kernel: In the /usr/src/sys/arch/YOUR_ARCH/conf/YOUR_CONFIG

At least, you have to enable these options:

options COMPAT_DARWIN # Darwin binary compatibility (experimental) options COMPAT_MACH # Mach compatibility, needed for COMPAT_DARWIN  options EXEC_MACHO # Mach-O binary support, needed for COMPAT_MACH

Optionnaly, uncomment the following:

#options DEBUG_DARWIN # COMPAT_DARWIN debugging #options DEBUG_MACH # COMPAT_MACH debugging

After editing your configuration file, you can begin to build the kernel:

config YOUR_CONFIG cd ../compile/YOUR_CONFIG make depend make cp /netbsd /netbsd.old cp netbsd /netbsd

Then reboot..

Assembler messages: Error: bad expression Error: syntax error; found 4' but expected ,’ Error: junk at end of line: `4,0’ Error: bad expression

sysctl interface

By default:

sysctl -a | grep darwin emul.darwin.init.pid = 0 emul.darwin.ioframebuffer.unit = 0 emul.darwin.ioframebuffer.screen = 0 emul.darwin.iohidsystem.mux = 0

In the source code of darwin_sysctl.c, we can read:

/*
 * On Darwin, mach_init is the system bootstrap process. It is responsible
 * for forking the traditional UNIX init(8) and it does the Mach port naming
 * service. We need mach_init for the naming service, but unfortunately, it
 * will only act as such if its PID is 1. We use a sysctl
 * (emul.darwin.init.pid) to fool a given process into thinking its PID is 1.
 * That way we can run mach_init when we want to.
 * Typical use:
 * sysctl -w emul.darwin.init.pid=$$; exec /emul/darwin/sbin/mach_init
 *
 * The same problem exists after mach_init has forked init: the fork libc stub
 * really insist on the child to have PID 2 (if PID is not 2, then the stub
 * will issue bootstrap calls to an already running mach_init, which fails,
 * of course).
 */

darwin_lib

“These libraries are part of the Darwin compatibility option for

NetBSD/powerpc and NetBSD/i386. * * The kernel options EXEC_MACHO', COMPAT_MACH’ and `COMPAT_DARWIN’ must be in your kernel config file for this to work.“ from /usr/pkgsrc/emulators/darwin_lib/DESCR

cd /usr/pkgsrc/emulators/darwin_lib/ make install clean

If the build fails, you will probably need to edit /usr/pkgsrc/emulators/darwin_lib/Makefile and remove the problematic (XFree86) missing rpm in DISTFILES variable. Attempt to run a mach-o binary

No mach_init is present by default, and mach_init has been dropped…

sysctl -w emul.darwin.init.pid=$$ && exec /emul/darwin/sbin/mach_init

At the root of a mounted old darwin iso (ppc), populate the darwin userland shadow root:  

scp  -r bin sbin usr <NetBSD macppc host>:/emul/darwin

scp  -r System/Library <NetBSD macppc host>:/emul/darwin/System

The process in `ps aux’:

USER PID %CPU %MEM VSZ   RSS TTY   STAT STARTED    TIME COMMAND root 412  0.0  0.0   0     0 ttyE0 RW+        - 0:00.00 /emul/darwin/sbin/mach_init 

FAIL!

cd /emul/darwin ./usr/bin/uname -a

same state..

root 421  0.0  0.0   0     0 ttyp0 RW+        - 0:00.00 ./usr/bin/uname -a 

FAIL!

At this time, 

Note: It seems memory is not allocated, an the RW+ status seems curious.

Please, let us know if you have a solution.

Ressources

http://netbsd.gw.com/cgi-bin/man-cgi/man?compat_darwin+8+NetBSD-current  http://www.netbsd.org/docs/compat.html#ports  http://hcpnet.free.fr/applebsd.html 

Network

This page primarily details how to get networking working in PureDarwinXmas, but these steps should be applicable to any Darwin installation. Next releases should/could include some part present here.

Network support

A must.

Install Network Drivers

Network drivers are provided in the form of Kernel Extensions (KEXTs). While Apple has made a few available in either source or binary form, these are nowhere near as many as are provided with OS X. In particular, although the AppleIntel8254XEthernet.kext which is needed for VMWare exists, it is not available for redistribution in any form.

For the Intel d945gclf2 Atom board, Realtek’s AppleRTL8169Ethernet is reported to work. Realtek have a good selection of drivers available on their website.

VMWare settings

The first thing you will need to do is edit the virtual machines configuration file. This is the .vmx file inside the virtual machine’s bundle. Ensure that the following options are present.

ethernet0.present = “TRUE” ethernet0.virtualDev = “e1000”

ethernet0.wakeOnPcktRcv = "FALSE" ethernet0.linkStatePropagation.enable = "FALSE"

/System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/.

But since this isn’t available (blocker) for general distribution you’re pretty much stuck.

Blocker: no kext available which will match the e1000 device in VMware

QEMU settings

Through the QEMU user mode network stack, it is possible to have a weird but functional network (rtl8139 tested). For more information, refer to the QEMU page. A quick overview:

• DHCP client (KernelEventMonitor) and server (QEMU virtual DHCP server) functionality.
• Guest IP address starts from 10.0.2.15.
• DHCP server and gateway on 10.0.2.2.
• A virtual DNS server is also (10.0.2.3) present and autoset.
• A virtual SAMBA or NFS can be used on 10.0.2.4 (not tested) in order to access files on the host via file sharing.
• A workaround is involved in order to avoid the connection to stall.

Install PureFoundation

The PureFoundation.root.tar.gz available from the PureDarwin svn or the PureDarwin hg repository contains two system frameworks which are required by a number of different networking components. Also available from the same location is the ddistonoted.root.tar.gz. Install both of these. Install SystemConfiguration.framework and Components SystemConfiguration.framework, which is part of the configd project, provides the components needed to configure network interfaces. Unfortunately, it does not currently build correctly and the available binary roots (spread across configd.root and configd_executables.root) are incomplete. You’ve probably already guessed that the missing components are the ones we need. However, by loading configd into XCode it is possible to build some of the individual components needed.

The file configd.root.tar.gz below contains as many of the missing components as we could get to build and a template preferences.plist. Install it in the usual manner (using ditto) and you will have all the components needed to get networking up and running.

Install and fix these files with:

sudo ditto ~/Downloads/configd.root/ /Volumes/PureDarwinXmas/ sudo chown root:wheel /Volumes/PureDarwinXmas/System/Library/LaunchDaemons/com.apple.configd.plist

Activate DirectoryServices

You must copy the com.apple.DirectoryService* plists into /System/Library/LaunchDaemons and set their ownership to root:wheel.

This is all very well, but how do we get networking to configure itself automatically?

• The IPMonitor bundle contains no compiled code and is responsible for allowing the DirectoryService daemon to perform DNS lookups.

Getting a version of this bundle which will work in PureDarwin will now be one of our highest priorities. So we’re currently waiting for a non-linked version of bootp. Credits

Thanks to Dr. Rolf “RolfHeinrich” Jansen for providing the missing components and the knowledge to use them. Availability and investigation

Watch carefully from many points of view (e.g., legal, technical, etc..).

Available

http://src.macosforge.org/Roots/9A581/AppleIntel8255x.root.tar.gz (available in DarwinBuild consequently) (reported to work in QEMU)

Realtek’s AppleRTL8169Ethernet Intel d945gclf2 Atom board (e.g., reported to work)

AppleRTL8139Ethernet.kext is available in Darwinbuild. Realtek RTL8139 Ethernet card“ (e.g., reported to work in QEMU)

Investigate

RealtekR1000 It’s an opensource driver for network controllers RTL8168, RTL8111, RTL8169, RTL8101 and some others modification for Mac OSX. It is based on Realtek’ driver for Linux and doesn’t supported by Realtek. http://sourceforge.net/projects/realtekr1000/  82566mm svn checkout http://82566mm-osx-driver.googlecode.com/svn/trunk/ 82566mm-osx-driver-read-only http://techresearchinfo.blogspot.com/ 

intel-e1000e-kext Open source kernel extension for Intel E1000e series of network cards (supporting many models) http://code.google.com/p/intel-e1000e-kext/

iwidarwin Intel® PROSet/Wireless 2200-2915/2100/3945/4965 driver for Mac OS X http://code.google.com/p/iwidarwin 

osxbge A port of the BSD bge driver to Apple’s OS X operating system. Broadcom 57xx and 59xx network chipsets http://code.google.com/p/osxbge/

wirelessdriver

http://sourceforge.net/projects/wirelessdriver/

Blocked

AppleIntel8254XEthernet.kext is not redistributable. Intel e1000 network card (e.g., the one supported in VMware Fusion)

otool

otool is a tool that, among other things, can show which shared libraries an application needs to run (similar to “ldd” on Linux).

When to use otool

otool is useful when you want to run an application on PureDarwin, but are not sure what libraries it needs.

How to use otool

Assume we want to know which libraries are needed to run bash. Simply run:

otool -L /Volumes/PureDarwin/bin/bash

It will give us

/usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

So, we need to have these libaries installed in our PureDarwin system in order to be able to run bash.

Use chroot

In order to further test, you can use chroot. (To be described)

Package management

Historically, Darwin did not have package management. However, DarwinBuild has many elements already in place to make one. This page is for discussion what needs to be there, what is already there, and what hence needs to be done. This page is currently in brainstorming mode. Please join the discussion!

What needs to be there

1. Find out the version of a (installed/uninstalled) binary root (“package”)
2. Install a binary root, including its run-time dependencies
3. Uninstall a binary root
4. Check whether a given binary root is needed by any other binary roots that are currently installed
5. Find out which files belong to a given binary root
6. Find out which binary root a given file belongs to
7. Upgrade a binary root (taking into consideration its dependencies)
8. Prevent different binary roots from overwriting each other’s files
9. Repair permissions
10. Download binary roots from repositories (like apt-get or yum)
11. Get package descriptions into the metadata

What is already there

• The xref database, which is populated at build time, and which includes information about versions and build- and run-time dependencies (but no versions thereof? However, DarwinBuild is monolithic in the sense that every 9C31 project depends on other 9C31 projects ONLY)
• A mechanism to package binary roots into archives (tar.gz, xar)
• Darwin manifests, which contain information about which installed file belongs to which installed binary root, checksums, and permissions
• darwinup, the Darwin Update utility, which according to its description, “provides a transaction-based mechanism to install software on the base system that modifies or supersedes existing system components.  Darwin Update is not a “package manager,” and does not specify any package format.  Updates can be installed from a directory, a tar archive, or other formats.“

darwinup

darwinup looks like a useful tool, and it appears to be under currently development (check the timeline on the Darwinbuild MacOSForge page). It is provided as part of the darwinbuild source code, and is built and installed along with the other darwinbuild tools. We would recommend that you then install it in /usr/sbin on your Darwin installation. darwinup will provide the final leg of the installation/deinstallation process: installing packages from the local disk and tracking which files are affected by each operation. darwinbuild requires that the bzip2 package is installed. This is not currently provided by PureDarwinXmas, and there is no binary root available for it, but it seems to build without problems. darwinup can install from a .tar, .tar.gz, .tar.bz or even .pkg. (It can also install a directory, in the style of uncompressed binary roots).

The final line is the UUID under which the package was installed. The UUIDs of all installed packages can be shown using the list command, and can be used to un-install packages: 5DAF8472-468B-409B-A037-E8A7DD0F6E4E These UUIDs are a very good example of why a user-friendly package management system is needed.

What needs to be done

• The metadata contained in the xref database must go into the binary root packages (initial progress)
• An installer must be written which interprets this metadata and stores it in the target machine’s xref database, and that makes use of darwinup
• An uninstaller must be written which interprets the metadata from the xref db and the darwin receipts and/or darwinup. [It is possible that darwinup keeps a “reference count” for all packages, only removing them when all packages needing them are gone. This will have to be looked into. If it is correct, this simplifies this part of uninstallation: we can tell darwinup to remove a package and all of its dependencies, and darwinup can then decide what needs to actually be deleted.]
• A higher-level tool must be written which resolves run-time dependencies and downloads the appropriate binary root packages from the repositories (although current DarwinBuild is designed as “monolithic”, i.e. “the OS” = 1 unit)

“Glue” language to use: python? 

• Available on Darwin, Mac OS X, and (almost) anywhere alse
• Can talk to sqlite3 (xref) easily
• Can parse plists with python-plist
• Can use tgz, tbz2 files with tarfile and xar files with pyxar
• Needs no compilation, supports rapid prototyping and changing
• Easy to learn and understand

Questions

• darwinxref exportProject -xml nano seems not to include versions of the dependencies (this apparently comes from the fact that the DarwinBuild database was conceived as monolithic and “completely filled” once an OS release is made.) The key information here is that packages from one build version always depend on packages of the same build version (e.g., 9C31) ONLY.
• Integrate ? Integrate rpm which MacPorts apparently uses? Integrate dpkg which Fink uses?

Mac OS X

Let’s, for a minute, look at how Mac OS X does things. It comes with an utility called pkgutil which comes closest to a package manager (but at the same time lacks important functionality): sh-3.2# pkgutil –file-info $(which pkgutil) volume: / path: usr/sbin/pkgutil pkgid: com.apple.pkg.BaseSystem pkg-version: 10.5.0.1.1.1192168948 install-time: 1193314189 uid: 0 gid: 0 mode: 100555 pkgid: com.apple.pkg.update.os.10.5.1 pkg-version: 1.0.1.1191932192 install-time: 1195808274 uid: 0 gid: 0 mode: 100555 pkgid: com.apple.pkg.update.os.10.5.3.combo pkg-version: 1.0.1.1191932192 install-time: 1212138511 uid: 0 gid: 0 mode: 100555 Its man page states that “Package dependency analysis and reference counting are not yet available, hence there is no –uninstall command yet”. See the installer-dev mailing list for more information.

Security

RPM depends/relies on gnupg backend in order to check integrity. The default keyring can be spoofed with a bad keyring which can lead to validate compromised binary if somebody change the $GPGPATH variable or the macro $_gpg_path. Also md5sum can be hooked too, take care.

Parallels Desktop

draft Tested trial version: 4.0.3844

Status

.iso can be boot as cdrom but faces the read-only medium problem. qemu-img convert test.vmwarevm/test.iso (or vmdk) test.hdd results in a non bootable disk.

Screenshots

Platform Expert

The Platform Expert is a vital part of the Darwin kernel environment. It contains the hardware abstraction layer, that is hardware specific parts of the kernel space. The Platform Expert for Intel machines is contained in AppleACPIPlatform.kext, which is available under the Apple Binary Driver License.

What the Platform Expert does

You can basically think of the Platform Expert as a “driver for the logic board”. As such, it can roughly be compared to the Hardware Abstraction Layer (HAL) of other operating systems. The Platform Expert initializes the data structures that the I/O Kit needs. Specifically, it creates the root node of the device tree in the I/O Registry, which all other nodes attach to. As such, it is a fundamental part of the Darwin kernel environment. The Platform Expert also handles kernel flags (such as cpus=1), registers interrupt, scans the system for devices, and drives the text console. In the XNU source code, the Platform Expert is referred to as pexpert.  

Known issues with AppleACPIPlatformExpert

AppleACPIPlatform.kext, which is available for use with Darwin under the Apple Binary Driver License in binary-only form, has been written specifically with Intel-based Macs in mind. Apparently little to no testing has been done to ensure that it is compatible with other hardware. Over time, the AppleACPIPlatformExpert has become more and more strict about some hardware features it assumes to be present. For example, ACPI tables, such as DSDTs, are assumed to follow Apple’s standards. If the machine does not follow Apple’s standards in the ACPI tables, this can create undesired effects. For example, it results in some multi-core machines crashing whenever xnu is loaded without the cpus=1 kernel flag. It might also result in unforeseen behavior in the area of power management.

Other Platform Experts

Various PowerPC Platform Experts are available. For the i386 architecture, only two Platform Experts are of interest: AppleACPIPlatformExpert (mentioned above) and AppleI386GenericPlatform, which is Open Source but only available and working up to Darwin 8. If one wanted to use it with Darwin 9, one would have to modify it.

Specify which Platform Expert to use

The platform=ACPI kernel flag tells the kernel to load the Platform Expert which matches “ACPI”, if available. This is AppleACPIPlatform.kext, since its Info.plist looks like this:

    <key>IONameMatch</key>
    <string>ACPI</string>

See [[Generic platform kext for PureDarwin]] for alternative non-ACPI solution for Darwin 10.

Projects

This pages contains notes about individual projects that can be built with DarwinBuild like build issues, necessary patches, and solutions.

PS2 Controller

Draft.

Voodoo PS2 Controller

VoodooPS2Controller 0.98 has been released and seems to work. All KEXTs below are loaded at boot:

• VoodooPS2Controller (tested in tty)
• VoodooPS2Keyboard (tested in tty)
• VoodooPS2Mouse
• VoodooPS2Trackpad

 kextstat reports:    23    2 0xb007000  0x6000     0x5000     org.voodoo.driver.PS2Controller (1.1.0) <12>    26    0 0xb10d000  0x3000     0x2000     org.voodoo.driver.PS2Keyboard (1.1.0) <23 22 12>    51    0 0xd25f000  0x8000     0x7000     org.voodoo.driver.PS2Trackpad (1.1.0) <23 22 12>

Notes: The KEXTs above are conflicting with ACPIPS2Nub from D. Elliott (e.g., needed for ApplePS2Controller) so be sure choose one or the other solution exclusively. ACPIPS2Nub will be autoloaded, but not necessarly ApplePS2Controller KEXTs.

kextload /System/Library/Extensions/ApplePS2Controller.kext/Contents/PlugIns/ApplePS2Keyboard.kext kextload /System/Library/Extensions/ApplePS2Controller.kext/Contents/PlugIns/ApplePS2Mouse.kext kextload /System/Library/Extensions/ApplePS2Controller.kext/Contents/PlugIns/ApplePS2Trackpad.kext

PureDarwin bootstrap

draft.

TODO: ramdisk (compressed) really begins to lack.

launchd' via [/System/Library/LaunchDaemons/org.puredarwin.installer.plist](http://code.google.com/p/puredarwin/source/browse/projects/PureDarwinSettings/System/Library/LaunchDaemons/org.puredarwin.installer.plist) launches pd_installer’ (probably in /usr/local/share/puredarwin/scripts).

Generating a “bootstrap” release

PUREDARWIN_RELEASE=“bootstrap” ./pd_setup ../../vm/bootstrap.vmwarevm PureDarwin

pd_installer

Example on VMware … Host OS: MacOS X running VMware fusion Guest OS running inside VMware: PureDarwin “bootstrap”

Short count-down for the BIOS stage, where IDE devices are reported:

• A cd device (bootstrap.iso)
• An hd device (2 GB, non formated)

The screen can sometimes been entirely filled by the error below:

EBIOS read error: Error 0x31

    Block 0 Sectors 4

This is not really problematic and should lead to the next screen.

The bootloader does not come from the media (bootstrap.iso) but from VMware (as displayed version shows).

See the VMware page for more information.

If [F8] is pressed, additional boot arguments can be passed to the kernel.

A Kernel EXTens decompression might occur.

Notice the cd-rom icon blinking while reading.

etc..

disk device detection (iofindwholemedia)

PureDarwin release

[x]

Boot on cd, deploy to hd (no ramdisk).

cd to hd

PureDarwin Core

PureDarwin Core is a collection of packages which seeks to provide a Darwin system with networking and the features which make Darwin differ from other OSes (eg. the main security and configuration daemons). PureDarwin Core will be the first set of packages installed on a system, and will run the second stage of the installation process.

A possible package list would be (in no particular order):

Official Darwin packages

• files
• xnu
• configd
• configd_executables
• launchd
• bash
• bsm
• CoreOSMakefiles
• dyld
• gnuzip
• gnutar
• bzip2
• Libsystem
• Libm
• libgcc
• libiconv
• securityd
• ICU
• ncurses
• Security
• syslog
• system_config
• objc4
• autozone
• zlib
• BootCache
• efiboot
• system_cmds
• Libc
• Libcpp_kext (not sure about this)
• notify
• DiskArbitration
• bootstrap_cmds
• libutil
• adv_cmds
• diskdev_cmds
• file_cmds
• network_cmds
• hfs
• DirectoryService
• DirectoryServiceDaemon
• bootp
• libresolv
• passwordserver_sasl
• OpenSSL
• SQLite

PureDarwin additions

These can be found in the Roots directory of the PureDarwin Google Code svn/hg.

• PureDarwinSettings
• PureDarwinInstall
• voodoo_kernel 
• NotApple80211
• libstdcxx_libs (not libstdcxx, which is approx. 196Mb on its own)
• PureFoundation
• CFNetwork
• ddistnoted
• PCSC
• dm
• lua
• curl
• libedit

KEXTs and related

• IOKitUser
• kext_tools
• Apple3Com3C90x
• AppleIntel8255x
• AppleRTL8139Ethernet
• AppleAPIC
• AppleFileSystemDriver
• AppleIntelPIIXATA
• AppleSMBIOS
• AppleUSBCDCDriver
• IOACPIFamily
• IOATAFamily
• IOATAPIProtocolTransport
• IOCDStorageFamily
• IODVDStorageFamily
• IOHIDFamily
• IOPCIFamily
• IOStorageFamily
• IOUSBFamily
• IOUSBMassStorageClass
• AppleACPIPlatform
• AppleRTC
• IOATABlockStorage
• IOBDStorageFamily
• IOSCSIArchitectureModelFamily
• IONetworkingFamily
• ApplePS2Controller
• ACPIPS2Nub This little lot comes to just over 200Mb on disk, and will shrink to 67Mb as a gnu-zipped tarball.

PureDarwin Repository

Note: This document is a draft

The PureDarwin project uses a Mercurial (and used a Subversion) repository (hosted on Google Code) to maintain sources, patches, other code and binary roots that are or that are not part of one of our favorite upstream projects.

This page describes how to use the contents of the repository to build your own PureDarwin ISOs and virtual machines.

Please contact us if you need write access. Everyone who wants to make Darwin more usable is invited.

Basic structure

The current Mercurial repository is composed of the sub repositories.

• default The default full release, hosts the setup scripts and settings in order to build a fully PureDarwin release in various form. It also contains setup scripts and settings in order to make an Installer (called bootstrap) or a minimalist PureDarwin release (a.k.a. nano) where only one process will run, a shell. http://code.google.com/p/puredarwin/source/browse/
• Roots This repository is dedicated to the hosting of binaryroots (not all of them) from DarwinBuild, MacPorts and PureDarwin. It is also used by the default and the nano release. Few sources and files have been mirrored inside it too. http://code.google.com/p/puredarwin/source/browse/?repo=roots The latest revision of the repository can be browsed at http://puredarwin.googlecode.com/.

Usage

Requirements

The actual state still needs

• A Mac to create various PureDarwin images. However, deploying PureDarwin can be done from PureDarwin (“bootstrap”).

• Mercurial in order to clone, commit, archive and push fixes, modifications and enhancements to the project. We have compiled and packaged Mercurial with (hopefully) all its dependencies, you can download it here, this package installs it to /opt/local/bin/hg. Alternatively, you may build it from MacPorts.

• A local copy of the remote PureDarwin repository obtained via hg clone https://puredarwin.googlecode.com/hg/ puredarwin

  See “Source checkout” for more information on Google Code. If you get “abort: could not import module architecture!” then you could try the package linked above.

Optionally,

• The DarwinBuild project (in order to deploy your own binaryroots)
• The MacPorts project
• Xcode (which is a requirement via transitivity)

Quick steps

After cloning of the PureDarwin repository, the quickest way is to modify nothing and keep the default configuration (pd_config). Simply fetch binaryroots, thin them and build/deploy PureDarwin to the requested target after selection the `setup’ folder.

1. ./pd_fetch
2. ./pd_thin
3. ./pd_setup (a usage should display potential choices) Important: Be aware that a full (non-nano) PureDarwin system currently cannot be run from a read-only disk such as a CD-ROM, DVD, or an ISO file. It needs a r/w hard disk (real hardware) or virtual disk. This might be solved once we go the Live CD way.

!

Configuration

In case you decided to edit pd_config to reflect your needs, keep in mind only few variables need to be edited in the most cases.

All options are not fully yet described here. Please see also the comments inside pd_config.

DARWIN_RELEASE

Simply target the Operating System major release version, a.k.a Darwin 9 or Darwin 10.

DARWIN_RELEASE="9" or DARWIN_RELEASE="10"

This variable is used by

• pd_config
• pd_fetch
• pd_thin
• pd_setup

ARCH

Target the architecture.

 ARCH="i386" At this time, only “i386” is supported, but we’re convinced that minor efforts (e.g., adapting bootloader steps to different OpenFirmware, adding some needed projects specific/related to the PPC support in “pd_roots”, etc…) should be involved in order to bring PPC support in Darwin 9. Idem for “X86_64”.

Feel free to help us in this quest too.

This variable is used by

• pd_config
• pd_thin
• pd_setup

PUREDARWIN_RELEASE

This variable enables a profiling of the release. Depending the value, specific options are enabled or disabled. Note: Most of the time, the choice should be “synced” with the BINARYROOTS_LIST_FILE variable. It is possible to override the value of PUREDARWIN_RELEASE via exporting it in the environment, prior to the script execution. See this example.

PUREDARWIN_RELEASE="" or PUREDARWIN_RELEASE="bootstrap" or PUREDARWIN_RELEASE="nano" This variable is used by

• pd_setup

BINARYROOTS_LIST_FILE

This variable references a file containing the list of binaryroot project names.

By default, the BINARYROOTS_LIST_FILE variable is automatically set to the corresponding PUREDARWIN_RELEASE.

Note: Most of the time, the choice should be “synced” with the PUREDARWIN_RELEASE variable.

BINARYROOTS_LIST_FILE="pd_roots" or BINARYROOTS_LIST_FILE="pd_roots.bootstrap" or BINARYROOTS_LIST_FILE="pd_roots.nano"

A trivial set theory is visible: “pd_roots.nano∈ pd_roots.bootstrap âˆˆ pd_roots” The binaryroots in pd_roots.nano also belong to pd_roots.bootstrap and pd_roots sets. The binaryroots in pd_roots.bootstrap also belong to pd_roots.

This variable is used by:

• pd_fetch
• pd_thin
• pd_setup

DARWINBUILD_DIR

Binaryroots built locally via DarwinBuild can be used (prior to the one fetched remotely on MacOS Forge in case it has not already been fetched) if DARWINBUILD_DIR variable is correctly filled in pd_config. However that can also result in one or more conflict between all the dependents and the dependencies living in the system (e.g., missing symbols) if you tend to mix binaryroots built in different BuildRoots.

#
# Dir of darwinbuild build directories

#

# WARNING: The binaryroots built on your local computer can,
# depending on the constellation of your buildroot resulting
# in problematic relation between dependents and dependencies.
#
# First Roots/.DownloadCache/ is checked then Packages/ if nothing found
#DARWINBUILD_DIR="/[...]/darwinbuild"

This variable should points to a directory containing build directories (e.g., 9J61, 9L30, 10C540, etc…).

This variable is used by

• pd_fetch
• pd_thin Notes: DarwinBuild may access the PureDarwin repository automatically (and/or remotely) if you initialize it with a Puredarwin plist.

ADD_CLONE

..

“Genetic” constraints

Basic overview

Which kind of PureDarwin you will be able to generate from the PureDarwin you generated is conditioned by the couple of (PUREDARWIN_RELEASE/BINARYROOTS_LIST_FILE) and ADD_CLONE.

The picture above shows that nothing can be generated from PureDarwin nano.

PureDarwin and PureDarwin bootstrap are able to generate themselves and respectively the other ones.

Note: Implicitly, that’s not (yet) entirely true concerning PureDarwin boostrap.

PureDarwin will contains the same packages (c.f. pd_roots) which have been used to make it in /usr/local/share/puredarwin/…

PureDarwin bootstrap will contains the same packages (c.f. pd_roots.bootstrap)  which have been used to make it. Because “pd_roots.nano ∈ pd_roots.bootstrap ∈ `pd_roots”, PureDarwin bootstrap will be only able to generate itself or a PureDarwin nano.

Zooming chickens and eggs

This is a more detailed and realistic, where there is (by default) no alteration of the couple of (PUREDARWIN_RELEASE/BINARYROOTS_LIST_FILE) and ADD_CLONE.

Where obviously everything can be generated from a Mac (green dotted arrow), it’s “almost” the contrary a fortiori depending the flavor of PureDarwin.

The black arrow represents a successful deployment.

A blue dotted arrow shows that the deployment could be successful if the expected binaryroots are present.

A red one faces a blocker.

Resources

The full chaotic history is available on request.

PureDarwin Google Code repository

Mercurial

PureFoundation

This page is about the use of PureFoundation on Darwin. For details about its development, see the links section below. 

About PureFoundation

PureFoundation is a binary-compatible, open source clone of Apple’s Foundation framework, designed exclusively for Darwin. It uses the same components as Apple’s Foundation: the Objective-C 2.0 Runtime, CoreFoundation, and (one day) the AutoZone garbage collector. PureFoundation’s primary goal is to allow certain dependant parts of Darwin run correctly. Objective-C is a great programming language, and Foundation provides a feature-rich and mature development environment, so it’s hardly surprising that Apple chose it to write a number of key components of Darwin. However, since Foundation has not been released, this has left us in the position where these components simply will not run. While Apple’s open source team usually do an excellent job of fixing such dependencies, in these cases the only fix would be to re-write the component in question using a different set of libraries, which is an impractical amount to ask. Instructions for getting and installing PureFoundation can be found here: http://code.google.com/p/purefoundation/wiki/InstallingPureFoundation. Status

v0.003 (15/03/2009) Latest test target, dscl, seems to run correctly.

How to recognise a dependency on Foundation

At compile time, in the darwinbuild chroot, dependencies appear as missing header files (eg. “Foundation.h”) or linker errors (eg. “unable to link to Foundation.framework”). At run time, dependencies are signalled by linker errors like:

   dyld: Library not loaded: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation       Referenced from: /System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/OpenDirectory or alternatively with a message like ``. Typically, if the symbol begins “NS”, it is a problem which PureFoundation should be able to solve. See Current Blockers for a list of some of the components affected.

Report a dependent on Foundation

If (when) you encounter a tool or application which looks like it needs Foundation, please report it via the PureFoundation issue tracker at http://code.google.com/p/purefoundation/issues/list.  Links

PureFoundation is now hosted on Google Code, at http://code.google.com/p/purefoundation/. Resources

http://www.hereapi.com/pf/index.html  http://www.puredarwin.org/news/purefoundation 

http://developer.apple.com/DOCUMENTATION/Cocoa/Reference/Foundation/ObjC_classic/FoundationObjC.pdf 

http://developer.apple.com/documentation/Cocoa/Reference/Foundation/ObjC_classic/Intro/IntroFoundation.html 

Another similar project apparently was Objective-C Substrate

In the beginning… “One step at a time is a good walking” dixit a chinese proverb.

v0.0007 All classes which can be directly bridged to CFLite (strings, arrays, dictionaries, sets, calendars, timezones, etc.) are present and at least 90% complete. It can now run dscl (which complains that the server isn’t running and exits, but at least it doesn’t crash).

v0.0006 This version should now run ‘arch’ correctly. It also no longer causes the X server to break.

v0.0005 We should think to change “our case study” from now. arch i386

Exactly the expected behavior!

arch -p arch: Unknown architecture: p ``

v0.0004 Our case study:

arch i386

And arch -p EXCEPTION!!!! ``  name: NSInvalidArgumentException ``reason: Attempting mutable dictionary op on a static NSDictionary

Note: This version, we have placed Foundation.framework and replaced CoreFoundation.framework plus libobjc.A.dylib in the BuildRoot.

FoundationTool 

2009-02-06 13:12:48.468 FoundationTool[12163:10b] CFLog: Hello, World! -- back from CFLog --

Note: For your information, `FoundationTool’ is “the Cocoa command line tool you get by selecting “Foundation Tool” from the “Command Line Utility” section of XCode’s “New Project…” window. I’ve compiled it here for your convenience. All it does is create an NSAutoreleasePool, write “Hello World!” using NSLog, then drains the pool. BUT this was compiled on OS X and will run on Darwin, proving that we’ve taken our first step towards a binary-compatible Foundation.framework.“ quoting the Readme.

v0.0003 arch i386 arch -p zsh: bus error arch -p N____otes: Although the version 0.0003 “relies on a patched CFLite, which in turn relies upon PureFoundation” (dixit), it appears to work (at least for `arch’) with the default CFLite for some binary.

v0.0002

arch

+[NSObject load]  _cfisa before = 6186080 +[NSObject initialize]  +[NSObject class]  Continuing with +initialize -- means this is NSObject address of self (NSObject Class) is 193376 Created retain dictionary. +[NSString initialize]  +[NSString initialize]  +[NSCFString initialize]  +[NSObject class]  Setting _PFNSCFStringClass _PFNSCFStringClass = 193504 +[NSCFString alloc]  _PFNSCFStringClass = 193504 _cfisa after = 6186080 i386

arch -p +[NSObject load]  _cfisa before = 6186080 +[NSObject initialize]  +[NSObject class]  Continuing with +initialize -- means this is NSObject address of self (NSObject Class) is 193376 Created retain dictionary. +[NSString initialize]  +[NSString initialize]  +[NSCFString initialize]  +[NSObject class]  Setting _PFNSCFStringClass _PFNSCFStringClass = 193504 +[NSCFString alloc]  _PFNSCFStringClass = 193504 _cfisa after = 6186080 +[NSObject initialize]  +[NSObject class]  +[NSObject alloc]  NSAllocateObject  value of aClass is 193696 object var points to 10489024 -[NSAutoreleasePool init]  -[NSObject init]  +[NSAutoreleasePool __hello:]  +[NSObject initialize]  +[NSObject class]  +[NSObject initialize]  +[NSObject class]  +[NSString stringWithUTF8String:]  +[NSString stringWithCString:encoding:]  _PFBlessNSCFString  _PFBless old _cfisa = 0 zsh: bus error  arch -p ``

v0.0001

Q - [kju:]

Some QEMU attempts through Q, A CPU emulator for Macintosh.

Status

As of January 2010, Q.app still uses qemu 0.9.x, whereas PureDarwin needs 0.10 to function properly. Hence, we recommend to use QEMU instead for now.

The latest version (Q-0.9.1d118) has been updated last year, creating a big gap between the latest official QEMU and the one used in Q front-end. Consequently, Q is not usable for PureDarwin at this time.

We also tried to replace i386-softmmu with a newer version inside Q.app but no success since the usage is different between both parts (and also the features supported). UI

Q control manager

Configuration

Boot sequence

DFE bootloader

CPU:FSB multiplier detection fails

**Please, let us know if you have a solution. **

Chameleon bootloader

SMBIOS well-known problem is bypassed with Voodoo kernel (xnu-dev).

Then, the real boot begins, but quickly ends with a problem related to APIC similar to the one in VirtualBox page.

Then, with <string>-f -v -x cpus=1 busratio=16 io=0x21</string> in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist, things go far:

Ressources

http://www.kju-app.org/ (Q) http://bellard.org/qemu/ (QEMU) http://code.google.com/p/xnu-dev (Voodoo, A fork of the XNU kernel)

QEMU

This page is about running PureDarwin on the QEMU emulator and is *not *about running Mac OS X.

QEMU is a hardware emulator that can be used to run operating systems on virtualized hardware, not unlike VMware or Parallels. It is an open source project. The ability to run PureDarwin on emulated hardware can be very useful, especially for development, testing and debugging. If you get the “Error parsing plist file”, then you need to increase the amount of virtual RAM. At least 330 MB seem to be required. If the kernel just crashes and the boot prompt appears again, press F8 and enter.

Running PureDarwin Xmas on QEMU

On Linux hosts

To get PureDarwin Xmas to run in QEMU, fetch QEMU from svn, compile, run without kqemu (it might work on OSX-supported cpus). Update: if you can get a 0.10 binary of qemu for your platform (some are linked below), you don’t necessarily need to compile from svn any more. Update 2: As of Ubuntu 9.10, the QEMU that can be installed with sudo apt-get install qemu is sufficient, so you don’t need to compile or download a special version of QEMU any more. Use the following configuration:

or

-hda puredarwinxmas.vmdk -cdrom purdarwinxmas.vmdk -boot d -m 512

or

-hda puredarwinxmas.vmdk -cdrom purdarwinxmas.iso -boot d -m 512

QEMU can (at least on some platforms) emulate the Realtek RTL8139 network interface. An open source driver for this NIC is included with PureDarwinXmas. Enable the interface in QEMU with the -net nic,model=rtl8139 -no-kvm-irqchip -net user option.

Run it using the instructions above (although -hda puredarwinxmas.vmdk -cdrom puredarwinxmas.vmdk -boot d -m 512 seems the more reliable option). X will probably fail to start first time, but can then be kicked into life with startx or pd_startx.

PureDarwin Xmas running on openSUSE. Credits: oxygene 

PureDarwin Xmas on Ubuntu 8.10 (using the binary linked below) and mach_kernel.voodoo. 

Command used: qemu -hda 'puredarwinxmas.vmdk' -cdrom 'puredarwinxmas.vmdk' -boot d -m 512 press F8 when asked mach_kernel.voodoo

On Windows hosts

PureDarwin Xmas on MS Windows XP (using the binary linked above). Credits: oxygene

On Mac OS X hosts

QEMU 0.10.1 from MacPorts can run PureDarwin Xmas with

qemu -hda puredarwinxmas.vmdk -cdrom puredarwinxmas.vmdk -boot d -m 512

Note: if you want to run qemu from a different location, use the -L option as:

qemu -L ./pc-bios/ -hda puredarwinxmas.vmdk -cdrom puredarwinxmas.vmdk -boot d -m 512

If you don’t boot by default with the Voodoo kernel (xnu-dev), at boot press F8…

And enter mach_kernel.voodoo rd=disk1s3 -v

or, if you have the vmdk as -hda:

mach_kernel.voodoo rd=disk0s3 -v

Wait for a bit on failed to open/create the journal… if that happens.

At the end of the KEXTs decompression phase, the CPU FSB clock and ration should be adjusted by the voodoo kernel.

After the KEXTs decompression phase, you should see the kernel booting (notice the network adapter supported).

Then depending your settings, a login prompt or X should be waiting for you.

It is necessary to launch X11 manually by issuing /usr/X11R6/bin/startx.

QEMU 0.10.1 from MacPorts running PureDarwin on Mac OS X 10.5. QEMU devices

Here is a list of potential devices found in a QEMU guest OS.

“0x1013”,“0x00B8”,“Cirrus Logic”,“CL-GD5446”,“64-bit VisualMedia Accelerator” “0x8086”,“0x7000”,“Intel Corporation”,“82371SB”,“PIIX3 PCI-to-ISA Bridge (Triton II)” “0x8086”,“0x7113”,“Intel Corporation”,“82371AB/EB/MB”,“PIIX4/4E/4M Power Management Controller” “0x1af4”,“0x1002”,“”,“” “0x10EC”,“0x8139”,“Realtek Semiconductor”,“RTL-8139/8139C/8139C”,“Realtek RTL8139 Family PCI Fast Ethernet NIC” “0x8086”,“0x7010”,“Intel Corporation”,“82371SB”,“PIIX3 IDE Interface (Triton II)” “0x8086”,“0x1237”,“Intel Corporation”,“82440LX/EX”,“PCI & Memory”

QEMU network

The dawn of networking support in PureDarwin finally appears with QEMU.

QEMU vlan network capability is entangled with the “user mode network stack”. This network stack supports ip, tcp, udp, dhcp, tftp, etc.. but ICMP. It also acts as a proxy between the qemu process and the target process, with tcp/udp data field decapsulation and forward.

The user network stack

Credits: Partial network support already existed, thanks to “hingwah” who helped and pointed its existence to us.

As said in 3.7.3 Using the user mode network stack QEMU documentation (“The DHCP server assign addresses to the hosts starting from 10.0.2.15.”), the interface is well auto-assigned (notes: KernelEventMonitor (confid_plugins) has been added and seems to be responsible of the client DHCP capability) as the route to the virtual available gateway (a firewall / dhcp server).

Requirements

Append -net user if it is not already there to the qemu command line: […] -net nic,model={i82551|i82557b|rtl8139} -no-kvm-irqchip -net user […]

Be prepare to ping the gateway continuously, it’s a workaround. As user inp reported on #puredarwin, adding ‘-no-kvm-irqchip’ to the qemu call solves this issue with the rtl8139 driver.

Of course, it’s mandatory to have a Kernel EXTension matching its respective device.

E.g. below with the realtek kext matching its respective virtual RTL8139 device in QEMU:

DHCP (IPv4)

An example of a “correct” configuration, where everything has been provided automatically (KernelEventMonitor) via DHCP.

What expected:

10.0.2.2 should respond to ping (gateway firewall/dhcpd). 10.0.2.2 should be the default route. 10.0.2.3 should answer to DNS query. 10.0.2.4 should answer to SMB (if available). 10.0.2.15 is where starts the first guest ip address.

What is well known:

It seems that network hangs easily if the gateway is not pinged when network operations are needed. As user inp reported on #puredarwin, adding ‘-no-kvm-irqchip’ to the qemu call solves this issue with the rtl8139 driver.

Ping workaround

ping the gateway (10.0.2.2) from the guest side (PureDarwin) seems necessary at this time. If it is not the done, the connection simply hangs or fails to establish sometimes. As user inp reported on #puredarwin, adding ‘-no-kvm-irqchip’ to the qemu call solves this issue with the rtl8139 driver.

Depending the ping interval (-i) against the virtual gateway, the bandwith varies (a pseudo bandwith control state; qos?). Below is an example across the time, where the interval took the no value, then 0.9, 0.5, 0.1 and 0 (This example was done downloading nmap).

Miscellaneous

Guest fingerprint (10.0.2.15)

The famous Fyodor `nmap’ basic fingerprint result against 10.0.2.15 (guest: en0) looks like (X running without –no-listen tcp as shown).

Gateway fingerprint (10.0.2.2)

Interesting to see what looks like from nmap point of view the virtual gateway (user mode network stack):

DNS server fingerprint (10.0.2.3)

..

QEMU options

This is another non exhaustive list of (reported to work) options available. Some part also needs investigations and feedback.

Standard options

-M machine      select emulated machine (-M ? for list) Need investigations. (could be interesting to see how it is close or not the reality when it is possible to compare the cases) -cpu cpu        select CPU (-cpu ? for list) Need investigations.

-fda/-fdb file  use 'file' as floppy disk 0/1 image No thanks.

-hda/-hdb file  use 'file' as IDE hard disk 0/1 image Reported to work with a iso, dmg, vmdk (convert or not). -hdc/-hdd file  use 'file' as IDE hard disk 2/3 image Need investigations. -cdrom file     use 'file' as IDE cdrom image (cdrom is ide1 master) Reported to work with a iso, dmg, vmdk (convert or not).

``

-smp n          set the number of CPUs to 'n' [default=1] ****

-k language     use keyboard layout (for example "fr" for French) Need investigations, not working.

-vga [std|cirrus|vmware] **** -usb            enable the USB driver (will be the default soon) Need investigations.

-usbdevice name add the host or guest USB device 'name' Need investigations.

-name string    set the name of the guest PureDarwin.

-uuid %08x-%04x-%04x-%04x-%012x specify machine Need investigations, UUID C0FFEEC0-FFEE-C0FF-EEC0-FFEEC0FFEEC0 has no effect.

Network options

According to the `man’, “The NIC is an ne2k_pci by default on the PC target”, but some other valid values are:  i82551, i82557b, i82559er, ne2k_pci, ne2k_isa, pcnet, rtl8139, e1000, smc91c111, lance and mcf_fec.

-net nic[,vlan=n][,macaddr=addr][,model=type] create a new Network Interface Card and connect it to VLAN ‘n’-net nic,model=rtl8139 is enabled by PureFoundation. Need investigations.

-boot [a|c|d|n] boot on floppy (a), hard disk (c), CD-ROM (d), or network (n)** “d” with the corresponding target is functional.**

-redir to test. Need investigations -tftp prefix -smb -macaddr addr -nics

** ** The option “-net nic,model={i82551|i82557b}” seems to match with AppletIntel8255x from DarwinBuild:

Live options

Press ctrl+alt+2 to switch to QEMU monitor:

Press ctrl+alt+3 to switch to serial0 console:

Press ctrl+alt+4 to switch to parallel0 console:

Patches to run stock XNU on QEMU

Currently, it appears that one needs to used a patched version of the XNU kernel called mach_kernel.voodoo to run on QEMU. This is even true when running QEMU on an Intel Mac on Mac OS X (tested with a MacBook Pro).

Alexander Graf has sent patches to the QEMU mailing list that allow Darwin to run on QEMU natively. Specifically, these patches

• Add HPET
• Add a dummy LPC device on which the HPET is located
• Identify CPU as Core Duo by setting family 13, adding a MSR and a CPUID instruction
• Add partial ICH6 IDE controller emulation
• Add support for multiboot (such as a modified boot-132 boot loader)
• Add ACPI entries to Bochs  They also add some other functionality that is not relevant for running Darwin.

It seems that the necessary patches have made their way into QEMU 0.10, as this version doesn’t need special patching any more.

probono’s networking experiments 12/2011

The experiments are done with a “fuller” PureDarwin installation than Xmas or Nano. Above it says “everything has been provided automatically (KernelEventMonitor) via DHCP”, however it doesn’t do that for me (I must be missing something still). Hence I set up networking by hand, which is a bit cumbersome:

The following are my tests on Ubuntu 12/2011; probono

# qemu: pci_add_option_rom: failed to find romfile "pxe-rtl8139.bin"
# can be solved with
sudo apt-get install kvm-pxe
# Launch qemu as root and with -redir tcp:22::22 for SSH access
sudo qemu -hda /dev/sdc -net nic,model=rtl8139 -no-kvm-irqchip -net user -redir tcp:22::22
# Inside qemu
ifconfig en2 10.0.2.15 up
ping 10.0.2.2 # works (which is the gateway provided by qemu)
# Create /etc/rc.local with the following content to
# bring en2 up automatically at boot time
#!/bin/bash
ifconfig en2 10.0.2.15 up
sudo route add 0.0.0.0 10.0.2.2
# Headless SSH server inside qemu
sudo qemu -hda /dev/sdc -net nic,model=rtl8139 -no-kvm-irqchip -net user -redir tcp:22::22 -vnc :1 -redir tcp:80::80
# Works :-)
# The only thing that does not work yet is DNS
# scutil --dns # resolver #1 is empty, which is a problem -- very ugly workaround:
echo 'nameserver 10.0.2.3' > /etc/resolver/com
echo 'nameserver 10.0.2.3' > /etc/resolver/org
echo 'nameserver 10.0.2.3' > /etc/resolver/net
echo 'nameserver 10.0.2.3' > /etc/resolver/de
echo 'nameserver 10.0.2.3' > /etc/resolver/edu

Rafael’s networking information 01/2012

Our reader Rafael writes:

For the network problem it’s just a matter of patching kvm module and you can use full acceleration, the patch is know (qemu dev don’t want it because it’s specific to qemu userland software and they want kvm module to remain compatible with other userland software - which ones? ): Pick the latest kernel module from: http://sourceforge.net/projects/kvm/files/kvm-kmod/ Open the x86/ioapic.c file: search for this function: int kvm_ioapic_set_irq(struct kvm_ioapic *ioapic, int irq, int level) and change:         level ^= entry.fields.polarity; to         //level ^= entry.fields.polarity;          And then rtl8139 will work as well as AppleIntelE1000 from : svn co https://osx86drivers.svn.sourceforge.net/svnroot/osx86drivers/AppleIntelE1000/AppleIntelE1000 –> but this last is derived from linux so it lacks debug specific part but I think this is the more interesting given you can redistribute it. If you use recent xnu kernel you also need to patch qemu (or use kernel patched) to tell you use apic version 14 ( qemu dev don’t want ton upgrade apic version as they don’t have too to run linux or windows) or you will hit an assert/kp from kernel. Open hw/apic.c from qemu source: In this function: static uint32_t apic_mem_readl(void opaque, target_phys_addr_t addr) Change:         val = 0x11 | ((APIC_LVT_NB - 1) << 16); / version 0x11 / to         val = 0x14 | ((APIC_LVT_NB - 1) << 16); / version 0x14 */ 

Thanks Rafael for sharing this information, which is not easy to find. kvm is doing really great these days.

QSOC project on Darwin support in QEMU

http://wiki.qemu.org/Google_Summer_of_Code_2012#Finish_OS_X_Virtualization_Support

References

• Darwin on QEMU Forum
• T2 KVM packages which are able to boot PureDarwin nano (thanks rxr)
• QEMU 0.10 binary for Windows which is able to boot PureDarwin (thanks oxygene)
• QEMU 0.10 binary for Ubuntu which is able to boot PureDarwin
• QEMU 0.10.1 binary for Mac OS X  which is able to boot PureDarwin
• http://bellard.org/qemu/ (QEMU)
• http://www.kju-app.org/ (Q) this front-end is unfortunately not usable (last update was one year ago) for PureDarwin.

hfsprogs

debian and Ubuntu have a package called “hfsprogs”, which can be used to create HFS+ disk images: apt-get install hfsprogs mkfs.hfsplus disk.hfsplus Initialized disk.hfsplus as a 100 MB HFS Plus volume file disk.hfsplus disk.hfsplus: Macintosh HFS Extended version 4 data last mounted by: '10.0', created: Mon Mar 23 18:32:16 2009, last modified: Mon Mar 23 18:32:16 2009, last checked: Mon Mar 23 18:32:16 2009, block size: 4096, number of blocks: 25600, free blocks: 25197 sudo mkdir /media/hfsplus sudo mount disk.hfsplus /media/hfsplus/ -o loop Now we can copy something there (How) can we use this disk image with qemu? If we want to make this bootable with a boot loader, we need to have a partition table inside the disk image! Probably we need to do this along these lines: http://wiki.eeeuser.com/howtocustomrestoreimage:pt2mkcustomimage

RPM Package Manager

The RPM Package Manager is a package manager and package format commonly used for Linux distributions. RPM also runs on Darwin. MacPorts is capable of producing RPMs including depencency information. This page describes how to use RPM on a PureDarwin system.

About RPM

RPM is the package manager and package format used by Red Hat, Novell/SUSE, Mandriva, and other Linux distributions. It is located at http://rpm.org/ 

RPM5 is a branch of RPM located at rpm5.org. Although both have common roots, it is not the branch of RPM that is used by Red Hat, for example. It is located at http://rpm5.org/  More about the differences can be found here, for example.

RPM in MacPorts

MacPorts provides ports for RPM. However, there is a chicken-and-egg problem because RPM and its dependencies need to be installed before RPM can be used itself.

port search rpm apt-rpm                        sysutils/apt-rpm 0.5.15lorg3.93 Automatic updater and package installer/remover for RPM rpm                            sysutils/rpm   4.4.9        The RPM package management system. [...]

rpm50                          sysutils/rpm50 5.0.3        The RPM package management system. rpm51                          sysutils/rpm51 5.1.4        The RPM package management system.

RPM from rpm5.org

The rpm package from rpm5.org is a self-contained bundle that comes with all the dependencies that are not part of Darwin itself.

However, even after it has been installed it says “package rpm is not installed”. Bug?

Installing RPM5 on PureDarwin

To install RPM5 on a PureDarwin system, do the following:

1. Download the dmg from http://rpm5.org/files/rpm/rpm-5.1/BINARY/
2. Mount the dmg on the Mac, copy RPM5.pkg to the root of the PureDarwin system
3. On the target system, do: This installs RPM5 to /usr/local/bin/rpm. The RPM database is located at /var/local/lib/rpm/.

Make sure the following depenencies are met on the PureDarwin system:

• /usr/lib/libbz2.1.0.dylib
• /usr/lib/libxml2.2.dylib (DarwinBuild project libxml2)
• /usr/lib/libSystem.B.dylib
• /usr/lib/libz.1.dylib
• /usr/lib/libiconv.2.dylib
• /usr/lib/libssl.0.9.7.dylib (DarwinBuild project OpenSSL)
• /usr/lib/libcrypto.0.9.7.dylib
• /usr/lib/libgcc_s.1.dylib

Building RPMs with MacPorts

Follow the instructions on the MacPorts page and use /opt/local/bin/port rpm someproject. Should you get an error about missing parts, then do /opt/local/bin/port unarchive someproject before.

Useful RPM commands

To run commands on RPMs that are not installed yet, add the p option as shown below.

• Install a package rpm -ivh –noparentdirs somepackage.rpm
• Show which packages are installed rpm -qa
• Show information about an package rpm -qi ``somepackage or rpm -q**p**i somepackage**.rpm**
• Show which files are in an package rpm -ql somepackage or rpm -q**p**l somepackage**.rpm**
• Show which dependencies a package requires `rpm -qR somepackage or rpm -qpR somepackage.rpm
• Remove an installed package rpm -e somepackage
• Show help rpm –help

Troubleshooting

org.macports.darwin9 is needed

**Problem: **Each package fails to install with the message “org.macports.darwin9 is needed”. **Solution: **Satisfy the dependency to org.macports.darwin9 by installing the RPM below. This is a dummy package that contains no actual software but tells the RPM database about the Darwin base system (specifically, the parts installed from DarwinBuild rather than MacPorts). It is based on http://svn.macports.org/repository/macports/users/afb/macosx-base.spec and was built with ``

Installation fails due to dependencies on itself

Problem: When trying to install a package, RPM complains that directories are missing that are either part of the base system or should be part of the package that is about to be installed.

bash-3.2# ls /opt/local/ bin/     etc/     include/ lib/     share/   src/     var/  bash-3.2# rpm -ivh /libiconv-1.12-0.i386.rpm error: Failed dependencies: /opt/local/bin is needed by libiconv-1.12-0.i386 /opt/local/include is needed by libiconv-1.12-0.i386 /opt/local/lib is needed by libiconv-1.12-0.i386 /opt/local/share/doc/libiconv-1.12 is needed by libiconv-1.12-0.i386 /opt/local/share/man/man1 is needed by libiconv-1.12-0.i386 /opt/local/share/man/man3 is needed by libiconv-1.12-0.i386

**Solution: ** please let us know.

Disk fills up quickly

**Problem: **When using RPM a lot, the disk fills up quickly. Solution: By default, RPM5 saves any RPM that you uninstall in /var/local/spool/repackage/. This can be disabled by changing %repackage_all_erasures to 0 in /usr/local/lib/rpm/macros.

To be investigated

OpenDarwin 6.2.2 had RPMs for the projects in DarwinBuild. How were these made?

sh-3.2# rpm -qip /Volumes/OpenDarwin6.6.2/System/Installation/RPMS/org.opendarwin.misc_cmds-6.6.2-4.fat.rpm Name        : org.opendarwin.misc_cmds     Relocations: (not relocatable) Version     : 6.6.2                             Vendor: OpenDarwin Release     : 4                             Build Date: Sun Jul  6 10:15:26 2003 Install Date: (not installed)               Build Host: lamancha.opendarwin.org Group       : System                        Source RPM: org.opendarwin.misc_cmds-6.6.2-4.src.rpm Size        : 490564                           License: ? Signature   : (none) Summary     : misc_cmds Description : OpenDarwin project misc_cmds

According to #opendarwin, these were built before DarwinBuild was around. A Perl script was used to generate RPM spec files, and the contents od the DSTROOT was packaged up.

A quick and dirty way to unpack a directory of RPMs

UNP=$(find i386/*.rpm)  && for UN in $UNP; do ./opt/local/bin/rpm2cpio  $UN | cpio -i -d -v ; done

Thanks

afb from #macports contributed knowledge to this page.

SmartCard Services

draft. **The SmartCard Services project. ** Overview

Sources from Apple are divided in two branches respectively corresponding to Darwin 9 and Darwin 10. Each branch contains these three nested subprojects:

• SmartcardCCID
• SmartCardServices
• Tokend

Status

Darwin10

SmartCardServices build Tokend build

Darwin 9

SmartcardCCID build

Smart Card CCID

Licensed under LGPL v2.1

ccid libusb (statically linked insto Smart Card CCID)

Smart Card Services

Licensed under APSL v2

Contains: reader drivers (.bundle) for readers not supported by USB CCID Class Driver reader drivers KErnel eXTension (PPC only?) manual pages pcscd (PCSC daemon)

• responsible of reader drivers dynamic (de)allocation at run-time
• manage reader connections PKCS11 library (legacy SC abstraction layer) various scripts

TokenD

Licensed under APSL v2

Darwin 10

• BELPIC.Tokend - Belgian National ID (BELPIC) compliant Smart Cards
• CAC.Tokend - Common Access Card (CAC) compliant Smart Cards
• JPKI.Tokend - Japanese PKI (JPKI) compliant Smart Cards
• PIV.Tokend - Personal Identity Verification (PIV) compliant Smart Cards
• tokendPKCS11.so - PKCS#11 Shim over Tokend

Darwin 9

• BELPIC.Tokend - Belgian National ID (BELPIC) compliant Smart Cards
• CAC.Tokend - Common Access Card (CAC) compliant Smart Cards
• JPKI.Tokend - Japanese PKI (JPKI) compliant Smart Cards
• PIV.Tokend - Personal Identity Verification (PIV) compliant Smart Cards Building

darwinbuild

Host: Darwin 10 (Snow Leopard) Buildroot: Darwin9 (9J61)

SmartCardServices

Problem: /Developer/usr/bin/xcodebuild fails with 11 - Resource deadlock avoided Solution: …

Tokend

Problem: /Developer/usr/bin/xcodebuild fails with 11 - Resource deadlock avoided

SmartcardCCID

cd 9J61 darwinbuild -init http://smartcardservices.macosforge.org/trac/export/71/trunk/SmartcardCCID/SmartcardCCID.plist -nfs

darwinbuild SmartcardCCID

Problem: (cd /SourceCache/SmartcardCCID/SmartcardCCID-1/ccid/ccid && ./MacOSX/configure –no-configure –disable-opensc ) /bin/sh: line 0: cd: /SourceCache/SmartcardCCID/SmartcardCCID-1/ccid/ccid: No such file or directory make: *** [install] Error 1 Solution: cd BuildRoot/SourceCache/SmartcardCCID/SmartcardCCID-1/ccid tar xjvf ccid-1.3.8.tar.bz2 ln -s ccid-1.3.8 ccid

Problem: /bin/sh: /SourceCache/SmartcardCCID/SmartcardCCID-1/libusb/libusb/configure: No such file or directory make[1]: *** [/private/var/tmp/SmartcardCCID/SmartcardCCID-1.obj/libusb/configure-stamp] Error 127 make: *** [install] Error 1

Solution: chroot BuildRoot cd SourceCache/SmartcardCCID/SmartcardCCID-1/libusb tar xzvf libusb-0.1.13b.tar.gz ln -s libusb-0.1.13b libusb cd libusb ./autogen.sh make distclean

Then the build succeeds: BUILD TIME: 0h 2m 8s EXIT STATUS: 0 SmartcardCCID - 7 files registered.

Resources

http://smartcardservices.macosforge.org http://smartcardservices.macosforge.org/trac/wiki

The boot process

This page describes the boot process of a Darwin 9 system. This is a first draft, please feel free to contribute.

Single-user (-s/cmd-S)

This is a top-level overview about the Darwin 9 boot process in single-user mode.

(Source: PureDarwin)

During single-user boot, the following things happen: (please add to the list) The firmware (either BIOS or EFI) initializes the hardware

• On BIOS machines, the screen is black and shows white text during this process
• On EFI machines, the screen is gray and shows nothing during this process (this applies to Intel Macs, other EFI machines might have other implementations) The boot loader is loaded by the firmware
• On BIOS machines, boot is loaded and a boot-132 message is shown
• On EFI machines, efiboot is loaded and an Apple logo but no spinner is shown (this applies to Intel Macs, other EFI machines might have other implementations) The boot loader reads /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
• If the file is not present, the boot loader prints an error message The boot loader loads XNU and the kernel extensions (kexts)
• On BIOS machines, a spinning star or a list of kexts being loaded is shown
• On EFI machines, an Apple logo but no spinner is shown (this applies to Intel Macs, other EFI machines might have other implementations) XNU is loaded
• If the essential KEXTs (especially the Platform Expert, which is in AppleACPIPlatform.kext) were loaded successfully as well, the kernel starts and prints a copyright message mentioning University of California at Berkeley XNU loads KEXTs (for the first time; those with OSBundleRequired set to “Root”) and waits for the root device
• If the root device can be accessed using the available kexts, the kernel prints the message “Got root device”; at some point thereafter the rest of the KEXTs are loaded (those without OSBundleRequired set to “Root”)
• If the root device cannot be accessed using the available kexts, the message reads “Still waiting for root device…” instead The kernel starts /sbin/launchd on the root device launchd starts /bin/launchctl launchctl starts /bin/bash

Multi-user

Same procedure as described above for single-user boot, but instead of the last step (“launchctl starts /bin/bash”) the following happens:

• … (Please write text here)

Netbooting (-n/cmd-N)

Same procedure as described above for single-user boot, but instead of the last step (“launchctl starts /bin/bash”) the following happens:

• … (Please write text here)

bless

bless is the command used on Mac OS X to make volumes bootable. This page discusses the bless command and its applicability in a PureDarwin system.

It is a work in progress; please contribute.

What is bless

bless is a command line tool on Mac OS X and Darwin to make volumes bootable. It also includes libbless, a library which is used by other applications (such as installers) to make volumes bootable. The bless project is available as Open Source from Apple.

“Worlds” supported by bless

efiboot

The bless command is used to set up the “efiboot” boot loader on Intel-based Macintosh systems which use EFI as their firmware.

(to be written)

boot

The bless command was used to set up the “boot” boot loader on generic BIOS-based systems in older versions of Darwin.

bless-24 was known to work with BIOS-based machines. It appears that bless-37.1.4 from 2006 was the latest version that contained BIOS code. Later versions of bless are no longer capable of blessing a volume so that it works on BIOS-based machines.

 *  Revision 1.21  2006/01/02 22:27:28  ssen
 *  <rdar://problem/4395370> bless should not support BIOS systems
 *  For RC_RELEASE=Leopard, keep BIOS support, but preprocess it out
 *  for Herbie and the open source build

(Maybe the BIOS-related portions of the code should be patched back in by PureDarwin.)

(to be written)

BootX

Was used to set up the “BootX” boot loader on “New World” and “Old World” PowerPC computers which used OpenFirmware as their firmware. Not relevant for PureDarwin.

Using bless

The usage of the bless command varies depending on which “world” you are targeting. Please refer to the bless manpage that comes with the bless command.

bless alternatives

A method to make a disk bootable on BIOS and EFI machines without using the bless command is described on the boot page.

References

• http://src.gnu-darwin.org/DarwinSourceArchive/expanded/bless/bless-37.1.4/libbless/BIOS/

boot

The boot project contains the bootloader that is used to boot the system on generic hardware through BIOS. 

What is boot

boot is a series of files that collectively act as bootloader for BIOS-based hardware.

• boot (sometimes referred to as “boot2”) HFS+ startup file, lives in the HFS+ file system structure (not a regular file). (Could also be used as a regular file; using a special version of boot1h that would no longer need it to be HFS+ the startup file.)
• Master Boot Record (MBR), lives in the first 440 bytes of the disk (not identical to the MBR from other OSes)
• boot1h stage 1 booter (bootsector) for HFS+ partitions, lives in the first 512 bytes of the partition
• boot1u (not used by PureDarwin)
• boot1u0 (not used by PureDarwin)
• cdboot booter for CD-ROMs (only works with valid Extensions.mkext due to a bug)
• chain0 (tbd; probably not used by PureDarwin)

Since Intel-based Macintosh computers use EFI instead of BIOS, they need to use a different bootloader, efiboot. Another alternative to the above two bootloaders, is the new XNU loading support in grub2 (currently known as just grub), which works on both platforms (EFI and BIOS based) . For more information, check out this page (archived since XNU support has not been mentioned in newer versions of grub docs).

Requirements

To use boot, you need:

• A MBR-formatted HFS+ volume containing a Darwin system
• startupfiletool (source)
• boot-132 (patched (archive) to include the EFI tables the Darwin system expects to be present)

Installation

The disk needs to contain a HFS+ volume, and it must not be mounted.

launchctl unload /System/Library/LaunchDaemons/com.apple.diskarbitrationd.plist
startupfiletool ${RDEVICE}s1 boot
sleep 3
dd if=boot1h of=${RDEVICE}s1 bs=512 count=1
sleep 3
dd if=boot0 of=${DEVICE} bs=440 count=1
sync
launchctl load /System/Library/LaunchDaemons/com.apple.diskarbitrationd.plist

The chameleon boot loader (a fork of boot-132) has a greatly simplified installation procedure, since it does NOT need the disk to be unmounted, and it does NOT need startupfiletool:

fdisk -f boot0 -u -y /dev/rdiskX    # Install boot0 to the MBR
dd if=boot1h of=/dev/rdiskXsY       # Install boot1h to the partition's bootsector
cp boot /Volumes/XXX                # Install boot to the volume's root directory

Troubleshooting

Non-System Disk

Problem: You get the error

Boot0: MBR
Boot0: Done
Non-System Disk

Solution: You need to set the partition bootable (“boot flag”, “set partition active”), e.g., using fdisk:

sh-3.2# fdisk -e /dev/rdisk1
Enter 'help' for information
fdisk: 1> f 1
Partition 1 marked active.
fdisk:*1> w
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] y
Writing MBR at offset 0.
fdisk: 1> q
sh-3.2# 

Wrong system booted by default

Problem: On a system with multiple OSes, boot wants to boot the wrong (non-PureDarwin) one by default. This happens when a non-HFS+ partition (e.g., FAT32 or NTFS) has the bootable (“active”) flag and comes before the HFS+ partition that contains PureDarwin.

Solution: Modify boot so that it uses the first HFS+ partition instead of the first partition with the bootable (“active”) flag:

In boot-132/i386/lib/libsaio/sys.c, comment the following line:

    for ( bvr = chain; bvr; bvr = bvr->next ) 
    { 
        if ( bvr->flags & kBVFlagNativeBoot ) bvr1 = bvr; 
        // if ( bvr->flags & kBVFlagPrimary ) bvr2 = bvr; 
    }

Graphics Mode

 Resolution Color Depth

** ** ** 4** ** 8** ** 24** ** 32** 640x400 640x400x256

640x480   640x480x256 640x480x555 640x480x888 800x600 800x600x16 800x600x256 800x600x555 800x600x888 1024x768 1024x768x16 1024x768x256 1024x768x555 1024x768x888 1280x1024 1280x1024x16 1280x1024x256 1280x1024x555 1280x1024x888

To be continued…

Booting from CD-ROM

This page describes how to produce a CD-ROM (or DVD, for that matter) which can boot Darwin on both EFI- and BIOS-based systems.

What we want to do

Master a CD from which both EFI- (Intel Mac) and BIOS-based (PC) systems can boot.

An Intel-based Macintosh will actually be able to boot the volume either through EFI (right-hand side) or through its Compatibility Support Module (“Boot Camp”) BIOS emulation (left-hand side, misleadingly labeled “Windows”).

How hybrid images work

The key is to use a HFS+ filesystem for the image (thus, making a “.dmg” rather than a “.iso”) and “injecting” parts of an El Torito ISO into it, This is called a “hybrid image”. 

How to create a hybrid image using pd_makedmg

To create a hybrid image, you can use the pd_makedmg script. It is based on darwinmaster.sh, and has been extended to support EFI booting in addition to BIOS booting. Its syntax is as follows:

pd_makedmg /Volumes/PureDarwinDisk /tmp/puredarwin.dmg PureDarwin

This would take the files located at /Volumes/PureDarwinDisk (which should contain a working Darwin installation) and turn them into a disk image located at /tmp/puredarwin.dmg with the name of “PureDarwin”, which could be burned to a CD e.g., using Disk Utility.

Note that pd_makedmg currently needs a Mac to run, since it makes use of commands like hdiutil which are not part of Darwin.

How pd_makedmg works

Here is what it essentially does:

• Creates Extensions.mkext from the kexts in the source tree
• Makes a temporary ISO that contains the boot-132 files and that has cdboot as its El Torito boot image  (this allows BIOS-based machines to boot)
• Creates, initializes and mounts a HFS+ disk image (dmg)
• “Injects” parts of the temporary El Torito ISO into the dmg using dd if="$ELTORITOISO" of=$rdev skip=64 seek=64 bs=512 (Do not actually execute this command. It is ran automatically by the script.)
• Copies the contents of the source tree to the dmg
• Blesses boot.efi (this allows EFI-based machines to boot)

kexts needed for booting from CD-ROM

Following the instructions from above should produce a CD that boots at least to the point Still waiting for root device.... For the kernel to be able to access the CD, the necessary kexts need to be installed of course. These are, in addition to the minimal set of kexts:

• IOATAPIProtocolTransport.kext
• IOCDStorageFamily.kext
• IODVDStorageFamily.kext
• IOBDStorageFamily.kext (Blu-ray Disc driver; available for Darwin as binary only)

To do

• Remove any tools that are not part of Darwin
• replace hdiutil create with a simple dd if=/dev/zero and hdid -nomount with losetup … and it would appear to work on Linux then (dfe)

Booting from the network via PXE

There are now at least 2 known working ways to get forked versions of boot-132 running via PXE. This page describes the two approaches and provides scripts for you to try it out yourself.

Note that right now this page ends where boot-132 is loaded; the rest can be read on DFE’s blog.

Booting PureDarwin with a PXE-enabled boot-132

Apparently DFE has written the missing Darwin/x86 first-stage network boot program (NBP), a first-stage loader for boot-132.

Basically, booting PureDarwin over the network involves the following steps:

1. Client network card firmware asks DHCP server
2. DHCP server asks dnsmasq on the server
3. dnsmasq sends TFTP information
4. Client network card firmware downloads boot1pxe.0 file specified by dnsmasq from dnsmasq
5. boot1pxe.0 loads boot (boot-132) (known to work up to this point)
6. boot-132 loads mach_kernel and Extensions.mkext from the server (still to be implemented)
7. mach_kernel loads network kext and uses it to load the root volume from the network (still to be implemented)
8. Root volume image detects that it is booted via the network and sets up ramdisks etc. as needed (like on Mac OS X network boot) You can try this variant by:
9. Run Ubuntu 9.10 Live CD (we are using this as the server for now; later we could use PureDarwin as the server)
10. wget "http://sites.google.com/a/puredarwin.org/puredarwin/developers/booting/boot/pxe/boot-boot1pxe.bash?attredirects=0&d=1" -O ./boot-boot1pxe.bash ; sudo bash ./boot-boot1pxe.bash

Booting PureDarwin via Chameleon via mboot.c32 via pxelinux via PXE

Another route is pxelinux which can boot multiboot kernels via PXE. Since mach_kernel itself is not a multiboot-compliant kernel, we need to use a multiboot-compliant fork of boot-132 (such as Chameleon), and load it with the mboot.c32 pxelinux plug-in.

Basically, booting PureDarwin over the network involves the following steps:

1. Client network card firmware asks DHCP server
2. DHCP server asks dnsmasq on the server
3. dnsmasq sends TFTP information
4. Client network card firmware downloads pxelinux.0 file specified by dnsmasq from dnsmasq
5. pxelinux downloads its configuration
6. pxelinux loads mboot.c32 which is a multiboot loader
7. mboot.c32 loads boot which is a multiboot-compliant version of boot-132 such as Chameleon (known to work up to this point)
8. boot-132 loads mach_kernel and Extensions.mkext from a supplied ramdisk (still to be implemented)
9. mach_kernel loads network kext and uses it to load the root volume from the network (still to be implemented)
10. Root volume image detects that it is booted via the network and sets up ramdisks etc. as needed (like on Mac OS X network boot) You can try this variant by:
11. Run Ubuntu 9.10 Live CD (we are using this as the server; later we could use PureDarwin as the server)
12. wget "http://sites.google.com/a/puredarwin.org/puredarwin/developers/booting/boot/pxe/boot-chameleon-over-pxelinux.bash?attredirects=0&d=1" -O ./boot-chameleon-over-pxelinux.bash ; sudo bash ./boot-chameleon-over-pxelinux.bash

Information from dfe’s blog

The following is mirrored from dfe’s Be free little PXEs, be free! blog entry at https://tgwbd.org/blog/2009/10/17/be-free-little-pxes-be-free/

Posted Saturday, October 17, 2009 09:15:19 PM by dfe

Those of you looking over at the bootloader page have probably been rather disappointed to see no new postings for over a year. In reality I’ve made several nice changes and I need to do several posts so people are aware of them. For now we’re going to start with PXE.

For those unaware, PXE is a specification for booting PCs over the network. The proper name is Preboot eXecution Environment but it’s generally referred to by the pronunciation of its acronym: pixie.

In its most basic form, PXE operates as follows:

• Computer is turned on
• PXE boot is selected, usually by pressing F12 (standard key). On some BIOS, F12 selects PXE boot. On most newer BIOS, F12 brings up a menu and one of the choices will be something like “PXE” or “Network Boot Agent” or whatever.
• PXE BIOS code stored in ROM initializes the network hardware and brings up link
• A DHCP request is issued
• A DHCP response is received including the address from which to download a boot file and the TFTP path to that file
• PXE ROM code downloads the file in to RAM at 0:7C00h.
• PXE ROM code jumps to 0:7C00h.

A few notes: 0:7C00h is linear 0x7C00 which is the 31k mark in the first segment and the standard boot address. According to the spec, the ROM should be able to load linearly all the way up to the top of “real mode” RAM (640k mark). In practice many ROMs balk at anything that would exceed the end of the first 64k segment. That is 33k and the spec recommends limiting boot file size to 32k for other reasons. Also, because it is a jump to 0:7C00 you cannot execute a return. What you can do is invoke software INT 18h which sort of serves like an abort() call.

The Darwin implementation follows the specification pretty well. The boot1pxe binary (an NBP, Network Boot Program) is downloaded and loaded by the PXE ROM. Similar to the boot1u program for UFS filesystem booting, the boot1pxe program is a 32-bit program using portions of the same support libraries that boot2, the real booter, uses. The NBP uses the boot server discover reply packet to retrieve its own filename. From there it knocks off the last path component (i.e. the thing after the last “/”) and replaces it with “boot”. That is the name of the real boot program and is the same exact “boot” binary used as the HFS+ startup file and in other places. The boot1pxe NBP loads it to 2000:0200h, cleans itself up, and jumps to the booter.

Once the real booter has started it is able to detect that it was loaded via PXE. The boot process is virtually identical to the process on a hard drive from a UI standpoint. That is, there will be an entry in the device list representing the PXE server and a prompt where you can add all the usual options. In addition, all of the ordinary UI applies so if you want to you can at this point opt to instead directly boot an OS X volume on the hard drive or even chain to another OS partition. This is particularly useful if you’ve hosed the boot code on your hard disk and simply want to boot to it.

That said there are some special considerations for PXE boot. Because TFTP does not provide any facility for enumerating directory contents, the booter must know in advance which files to load. Those files are com.apple.lre.Boot.plist or com.apple.Boot.plist, mach.macosx, and mach.macosx.mkext. The booter uses the same trick that boot1pxe used to find it. That is, it uses the pathname from the boot server’s discover reply packet as the base for all filenames.

On the TFTP server you will want to create a directory containing all of the boot files. One very simple option is to simply use Mac OS X Server and the network boot tools from the Server Administration Tools package to set up the boot. In general it likes to set things up in a directory like {unique-name}.nbi/i386/. So for example, 10a432.nbi/i386/mach.macosx will be the kernel (normally named mach_kernel).

The list of files you need is as follows:

boot1pxe: The NBP that will be loaded by the PXE ROM boot: The normal booter program loaded by boot1pxe com.apple.lre.Boot.plist: Booter configuration file mach.macosx: The xnu kernel. mach.macosx.mkext: An Extensions.mkext archive for this kernel booter: Not needed, but if you use the “System Image Utility” you will find that this is just boot.efi On the DHCP server you simply need to set next-server to the correct TFTP server (strongly recommended this be the same as the DHCP server) and set the boot filename to /path/to/whatever.nbi/i386/boot1pxe. You may also want to set root-path option in DHCP although you can instead specify it using rp= on the command-line (including in the boot plist of course).

As an alternative to setting these DHCP options on your real DHCP server you can instead set up a separate boot server. One such boot server is Microsoft’s Windows Deployment Services (WDS) or the older Remote Installation Services (RIS). I have not figured out a way to add non-Windows choices to the WDS native menu but you can add non-Windows choices in WDS Legacy which is just Microsoft’s new name for RIS. Setting up a choice in RIS will have to be the subject of another blog entry.

When the booter boots from PXE it sets rd=en in the kernel boot args. This tells the kernel that the root device is ethernet. The kernel then looks for the root path in either the DHCP options or from the rp= option. Assuming you have the IOHDIXController.kext you can use an HTTP server so you would have e.g. rp=http://192.0.2.1/path/to/whatever.dmg on the command line in the boot plist or the http URL in the root-path DHCP option. If you don’t have IOHDIXController then it may be possible to specify an NFS path to a disk image. A glance at the kernel source seems to indicate that it has some facility for mounting flat disk images (using BSD vndevice) as the root.

There is one little gotcha about the root-path option and this is actually true of booting a Macintosh using Apple’s special Boot Service Discovery Protocol. That is that the firmware does not request the root path option. So it is incumbent upon the DHCP server to send the value even though the client did not request it. ISC DHCP has a way of telling it to send additional unrequested options. It is, however, probably easier to just set rp= in the boot plist.

The last piece of the puzzle is building mach.macosx.mkext. You cannot just use one copied from your hard drive as it is unlikely to contain the network drivers. Interestingly though, the copy on the Snow Leopard DVD does. So if you don’t need any additional extensions then you can use it outright. In practice the only machines that don’t need extra extensions are genuine Macs. So if you were using something like a gPXE CD to boot a real Mac over the network you could do this. But of course you’re then booting OS X via the BootCamp legacy BIOS layer which breaks a few things.

To build the mach.macosx.mkext you just use the ordinary kextcache tool. The general form is as follows: kextcache -m mach.macosx.kext [-n] [-l] /path/to/System/Library/Extensions … /path/to/SomeAdditional.kext …. You do not need to and should not run kextcache as root because we’re using it in a mode where it outputs an mkext file instead of updating the running system’s mkext. The options break down as follows:

• -m {output-file}: Specifies that an mkext is to be output to the specified output file
• -n: Specifies that only extensions required to mount the root filesystem over the network are to be included
• -l: Specifies that only extensions required to mount the root filesystem from a local disk are to be included.
• /path/to/Extensions: One or more directories containing .kext bundles can be specified. If provided, the -n and -l filters apply to the kexts found.
• /path/to/SomeAdditional.kext: One or more additional extensions can be included in the archive. The -n and -l options do not apply and these extensions will always be included

With neither -n or -l no filtering takes place so all extensions are included resulting in a rather hefty mkext. With -n and -l you will get almost all the kexts you need. If -n and -l are failing to include some kext you know you need then you can specify it directly on the command-line to override this. These options look at the OSBundleRequired key in the Info.plist of each kernel extension. If its value is Root then either one will include it. If it’s Local-Root then -l will include it and if it’s Network-Root then -n will include it.

Once the booter has loaded the kernel and mkext archive it jumps to the kernel as per usual. At this point it’s all about having enough driver support to bring up the network and mount the root disk image. The disk image itself is simply an ordinary OS X image. It is quite possible to use the normal DVD image as the root image. If you have a paid ADC account, the dmg files provided for download by Apple work out of the box.

Of course you aren’t limited to installer images. The System Image Utility can be used to create a directly bootable image or you can even build one by hand. You are, however, limited to a read-only root FS similar to booting from a CD or DVD. Of course you can always mount some ramdisks for temporary files and NFS or AFP or SMB shares for permanent files.

The great thing about network booting is that it is extremely fast. With a basic fileserver it’s on par with hard drive boot. If you have a fast server with fast disks, RAID, and a decent disk cache it can actually be quite a bit faster. In all cases, installing OS X off the network is certainly faster than off of a DVD. Generally you should see the GUI in about a minute as opposed to say five minutes when booting off a DVD.

There are of course a myriad of uses for network boot support. The most obvious one is to quickly install OS X. Beyond that, the network boot support has made developing the booter far easier. Prior to this testing the code involved building a vmdk or iso image, shutting down the VM, and rebooting with the new disk or CD image. With the network boot support I can set the VM to boot off the network, copy new binaries to the boot server, and simply reboot the VM. A similar situation applies for kernel or kernel extension development. With a quick little shell script I can have the code built and deployed to the boot server and I can quickly reset the target machine and start the new code running immediately.

There are other useful tricks too. Say I want to test El Torito support on some machine. The only way to have the El Torito stack correctly installed is to have booted from a CD. So I go to ROM-o-matic.net download a gPXE ISO and burn that to a CD. Now I can change the bootloader code simply by dropping a new binary on the network but because boot occurred from CD one of the BIOS devices will be the CD.

In short, if you can take a minute or two to set up a boot server you can make your life a lot easier when bringing up Darwin or OS X on a new machine.

Chameleon

The Chameleon bootloader is an APSL project based on David Elliott’s fake EFI implementation added to Apple’s boot-132 project.

The source code repository is available at http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/

Chameleon brings some nice features from low to high layers as: Preboot ramdisk image, EFI partition booting, hibernation/resume, DSDT and SMBIOS, GUI booting and custom themes supports.

draft.

Status

• Chameleon 2.0-RC4-r684 works with QEMU v0.10.6 and VMware (Fusion) 3.0.1 on a Mac.
• Chameleon 2.0-RC3-r658 works with QEMU (mac & win tested), VMware (Fusion), etc.. Prolematic points reached on windows with e.g. vmware (“Mach-o has bad magic number” error).
• Chameleon 2.0-RC1-r431 works with QEMU.
• Chameleon 2.0-RC1-r431 will not show up in VMware (observed in Fusion but not in Player), because VMware relies on darwin.iso (VMware Tools) which contains the DFE bootloader (Stage 2 boot file < 128K) is ok.
• In case of real hardware target, cdboot, boot, boot0 and boot1h have been deployed but not yet tested.
• In Image disk, virtual or not, cdboot and the “El Torito ISO trick” is used.
• Note: The error “Error parsing plist” in i386/libsaio/stringTable.c, the function “long ParseXMLFile( char * buffer, TagPtr * dict )” is responsible of returning the error.

    if (length < 0) {
        error ("Error parsing plist filen");
        return -1;
    }

Why is it failing? The plist is obviously well formated and there is no permission problem at this level. Problem: “Error parsing plist file” Solution: In fact, the error comes from the memory allocation, it seems that 256MB is not enough and make it fails in the contrary of e.g., 384M.

Some features

Please see “Introducing new features added to next version of Chameleon”, part 1 and part 2.

Default partition

A default partition to boot can be specified. Add to com.apple.Boot.plist: <key>Default Partition</key> <string>hd(x,y)</string>

Customizable UI

`` theme_folder_name

Custom UI

Default UI

RAM speed

<key>SMmemspeed</key> <string>800</string>

How to update PureDarwin running inside qemu to the latest Chameleon bootloader 11/2011

sudo apt-get install dmg2img
dmg2img /home/mint/Downloads/2120-Chameleon v2.1VS r1701.dmg
# Run qemu with 
-hdb /home/mint/Downloads/2120-Chameleon v2.1VS r1701.img

PureDarwin:~ root# mount
/dev/disk0s1 on / (hfs, local, journaled)
PureDarwin:~ root# fdisk -f "/Volumes/Chameleon 2 VS//Manual Install/boot0" -u -y /dev/rdisk0
PureDarwin:~ root# dd if="/Volumes/Chameleon 2 VS//Manual Install/boot1h" of=/dev/rdisk0s1
PureDarwin:~ root# cp "/Volumes/Chameleon 2 VS//Manual Install/boot" /

Chameleon v2.1VS r1701 seems no longer to be able to boot PD9, crashes immediately when loading the kernel

Resources

http://chameleon.osx86.hu Source code repository

efiboot

The efiboot project contains boot.efi, the bootloader that is used in Intel Macs to boot the system. 

What is boot.efi

boot.efi is a Universal EFI binary with 2 architectures, i386 and x86_64. It can be used to boot Intel-based Macintosh computers with both 32-bit (e.g., first-generation MacBook Pro) and 64-bit firmwares (e.g., Santa Rosa MacBook Pro).

Requirements

efiboot requires EFI to work. Computers that do not have EFI need to use other bootloaders, such as boot. To use efiboot, you need:

• An Intel-based Macintosh (or another computer with EFI that can read HFS+; no such computer is known)
• A HFS+ volume containing a Darwin system
• efiboot
• bless

Installation

To make a volume bootable through EFI, efiboot needs to be installed. Simply copying boot.efi, however, is not sufficient. To make it work, there are basically two options:

• Blessing the volume
• moving boot.efi to a special, UEFI-specified location (to be verified)

Blessing the volume

Assuming your Darwin volume is mounted to $MOUNT, do: "$MOUNT/usr/sbin/bless" -verbose -folder "$MOUNT/System/Library/CoreServices" -bootinfo -bootefi The above command implements an Xinfo cache for PowerPC processors which is not needed in the case of an Intel-based Macintosh.

For PureDarwin a simplified command can be used that will bless for only EFI based Macintosh computers: "$MOUNT/usr/sbin/bless" --folder "$MOUNT/System/Library/CoreServices" -bootefi --verbose

The volume should now be bootable.

Moving boot.efi to UEFI-specified location

The firmware of Intel-based Macintosh computers implement sections 3.1 and 3.2 of the UEFI 2.0 specification. UEFI 2.0 defines that the firmware looks for an EFI bootloader at the following locations:

• /EFI/BOOT/BOOTX64.EFI
• /EFI/BOOT/… of FAT16-formatted volumes. Whether this can also be used to boot a Darwin system from a HFS+ volume needs to be verified.

Using boot.efi in VirtualBox

EFI emulation in VirtualBox 4 is capable of loading and executing boot.efi as the bootloader. Hence boot-132 or its derivatives are no longer needed in VirtualBox. We were able to boot PureDarwinNano.iso this way.

GRUB 2

GRUB, the GRand Unified Bootloader, is a boot loader from the GNU project. GRUB 2 is a complete rewrite. In early 2009, Vladimir Serbinenko has added support for booting Darwin to GRUB 2, making it suitable as an alternative to boot-132 (the original Apple Darwin boot loader). However the “COPYING” file stipulates a GPLv3 license. This page discusses how to install and use GRUB 2.

For BIOS-based machines

Getting GRUB 2

Since GRUB 2 is still under heavy development, and since the XNU-related functionality is still very new at the time of this writing (June 2009), your best option for getting the most recent version of GRUB 2 is to compile it from source.

Compiling from SVN using Ubuntu

At the time of this writing, there are some issues with compiling GRUB 2 on Mac OS X and Darwin. Hence, the follwoing instructions assume that you use a Ubuntu 8.10 Live CD (more recent versions should work as well). (This page needs to be updated to explain the procedure using Mac OS X or Darwin as well.) sudo apt-get update sudo apt-get install build-essential subversion autoconf ruby bison svn co svn://svn.sv.gnu.org/grub/trunk/grub2 cd grub2/ ./autogen.sh ./configure --enable-efiemu make sudo make install This should install GRUB 2 to /usr/local/bin, from where you can call it to install the boot loader to a disk.

Installing GRUB 2

Once you have installed GRUB 2 to /usr/local/bin as described above, you need to install it to the disk you want to make bootable. sudo grub-install --root-directory=/media/XXX/ /dev/sdX This should give a message like Installation finished. No error reported. This is the contents of the device map /media/disk//boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script grub-install’. This has been tested with a FAT32-formatted USB stick. You need to replace/media/XXX/ with the mountpoint the partition is mounted to, and /dev/sdX `with the device of the USB stick (not the partition). It might be necessary that you flag the partition bootable using cfdisk. To be investigated: Can we install this to a HFS+ volume from Ubuntu?

Booting Darwin with GRUB 2

GRUB 2 lets you control the kernel and extensions to be loaded in a very fine-grained manner. Please refer to the XNUSupport page of the GRUB wiki for more detailed information. The following searches all disks for /mach_kernel, and boots it using Extensions.mkext: insmod vbe insmod gfxterm search --set ``/mach_kernel xnu_kernel /mach_kernel xnu_mkext /System/Library/Extensions.mkext terminal_output gfxterm boot For EFI-based machines

GRUB 2 can also be used on EFI-based machines, such as Intel-based Macs. The procedure is different from the one described above. Basically, you have to compile GRUB 2 as an EFI module, and place it in /EFI/BOOT/BOOTX64.EFI /EFI/BOOT/BOOTIA32.EFI on your disk. When you press the Alt key during boot, your Intel Mac should show the disk as “EFI Boot”. See this thread on the Ubuntu Forums for more information. References

• http://en.wikipedia.org/wiki/GNU_GRUB
• http://www.gnu.org/software/grub/grub-2.en.html
• http://grub.enbug.org/XNUSupport
• http://ubuntuforums.org/showpost.php?p=7275427&postcount=762

launchd

launchd is a central component of the Darwin and Mac OS X boot process.

About launchd

Starting with Darwin 8, launchd replaces different mechanisms for starting and stopping processes, thus replacing more traditional mechanisms found in other UNIX-like systems such as init, rc, the init.d and rc.d scripts, SystemStarter (Mac OS X), inetd and xinetd, atd, crond and watchdogd. As such, it plays a central role in the Darwin and Mac OS X boot process. It is also a key element of Mach IPC on Darwin and Mac OS X systems.

Making launchd verbose

Whenever you need to debug boot problems that occur after the root device has been found, you should make launchd verbose. Put the following in your /etc/launchd.conf: log level debug and append the following to your /etc/syslog.conf: *.debug /dev/console

Runtime dependencies

The 9F33 binary root of the launchd project has runtime dependencies on the following libraries and frameworks: find /Users/user/Downloads/launchd.root -exec otool -L {} 2>&1 ; | grep “compatibility version” | sort | uniq

• /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
• /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
• /System/Library/Frameworks/Security.framework/Versions/A/Security
• /usr/lib/libSystem.B.dylib
• /usr/lib/libbsm.dylib
• /usr/lib/libedit.2.dylib
• /usr/lib/libgcc_s.1.dylib Unlike in earlier builds, libauto is no longer a runtime dependency of launchd. 

launchd from SVN

The launchd project is developed in a publicly accessible subversion repository. To check out the latest development version of launchd, use 

svn co http://svn.macosforge.org/repository/launchd/trunk launchd

Note that this might be developed against a later version of the Core OS than what is publicly available. So something like

svn co http://svn.macosforge.org/repository/launchd/branches/SULeopard launchd

might be more appropriate for Darwin 9.

References

• Getting started with launchd
• launchd site
• AFP548 - launchd in Depth

The Darwin Package Manager

This is Stuart and Aladin’s proposal for “dm”, a Darwin Package Manager. It is based on the discussion on the Package management page.

Feel free to rip it apart.

Scope

“dm” will be a command line tool used to manage the darwinbuild components of a Darwin system, namely:

• Binary roots available from src.macosforge.org/Roots
• Patched binaries from code.google.com/p/puredarwin (inc. PureDarwin pd_* scripts and PureFoundation)

These locations would be checked in turn for binaries, in the same way that darwinbuild currently checks for patch files and tarballs.

Supersets

darwinup

darwinxref

(patched MacPorts?)

Subsets

“dm” would also be used to install other package managers (e.g., MacPorts), which would then be used to install other packages.

 (is a tweaked DarwinBuild where the pseudo-chroot is in fact the root (/) plausible?)

Mandatory files involved at run-time

The Darwin Package Manager should take a filename (if possible) which does not exist in any UNIX distribution and/or GNU/Linux distro.

Some propositions for the filename crossed with other involved filenames (if possible too) described later:

• dm (Darwin package Database) pdpd or pd2 (
• dtpm (Darwin’s Trivial Package Manager)
• dtbi (Darwin’s Trivial Binary Installer)

Where the “dm” tool should be installed has to be discussed, it could be in:

• /usr/local/sbin According to hier it could also be in /usr/local/sbin and by default “dm” is not included in the basic operating system (Darwin)..      /usr/         contains the majority of user utilities and applications                    local/    executables, libraries, etc. not included by the basic operating system

• /usr/sbin/ According to hier..      /usr/         contains the majority of user utilities and applications                    sbin/     system daemons & system utilities (executed by users)

• /usr/libexec/      /usr/         contains the majority of user utilities and applications                    libexec/  system daemons & system utilities (executed by other programs)

• /opt/local/bin/port Note: If we pach `port’ from the MacPorts project, then the default location is obvious.

Filename To be determined… Permissions Admin privileges, executable, read.. (-r-xr-xr-x root  admin ?) Admin users can then use it to add and remove packages as needed. Path To be determined… Miscellaneous The Darwin Package Manager

The PureDarwin Package Database (“pdpd” or “pd2”) is still abstract at this time. For the potential filename:

• “pdpd” or “pd2” for PureDarwin Package Database
• “dpd(b)” for Darwin Package Data(b)ase Note: If we choose to patch `port’ from the MacPorts project, this repository will be useless except if we want to log and/or record in parallel the events.

Filename To be determined… Permissions To be determined… Path To be determined… Miscellaneous The (Pure)Darwin Package Database

A launchd plist file (org.puredarwin.xyzt.plist?) in /System/Library/LaunchDaemons/

Filename org.puredarwin.[tobedetermined].plist Permissions (-rw-r–r–  root  wheel)

Path /System/Library/LaunchDaemons/ Miscellaneous Launchd plist (scheduling, update..)

darwinup

“dm” will use darwinup for the lowest-level installation and un-installation. darwinup works much like a version control system, keeping track of which files are altered during an install so that it can then “roll back” the file system at un-install time. It does not, however, have any idea of dependencies or the ability to fetch files from repositories. These are the features which “dm” will provide.

If we use darwinup', we could need to list *all* features/possibilities provided by darwinup’, list what we clearly need for a plausible start, and make a diff between both lists.

The PureDarwin Package Database

Central to “dm” will be the PureDarwin Package Database (“pdpd” or “pd2”). This will be based on a complete package list and dependency information extracted from the darwinxref database, augmented with information about packages provided by PureDarwin and others. The tools described below can help compile this information, but the amount of work involved should not be under estimated. Package management systems simplify matters for the user by shifting the task of tracking and resolving package inter-dependencies to those who administer the packaging system.

• For simplicity I’m not planning on keeping darwinxref’s detailed file list information (the contents of each package). Will this be a problem? Will users want to search for individual files? And if they do, could we just use a wrapper around xref.puredarwin.org to retrieve this info? Answer: Each package produced and packages by darwinbuild has a receipt (/usr/local/darwinbuild/receipts/<package>) which lists all of the files added. This will solve the problem for installed packages.

To the data from darwinxref we will add:

• Localised descriptions of each package
• “groups” and “systems” information (explained below)

One of the first things “dm” should do when it’s run is to check for an updated version of the pd2 database and download it.

Groups and Systems

Groups and Systems provide a way of grouping collections of packages together to make it easier for the user to choose and install the packages they need.

• Groups are collections of packages, assembled by theme eg. “web_services” or “perl_and_libraries”
• Systems are collections of packages, forming complete special-purpose Darwin distributions eg. “full_desktop”, “rescue_tools”, “office_server”, “web_server”

Group and Systems names should never be the same as package names.

The “core” group

There should be a special “core” group which contains all of the components every PureDarwin installation needs (eg. the kernel(s), launchd, general .KEXTs, the main frameworks). This should always be installed, and cannot be un-installed, but can be updated.

The “core” group could include all of the packages needed to create a network connection and run “dm”. We could then make the first stage of the installation process preparing the destination disk and installing the “core” group, with the second part being running “dm” from the destination disk. (This would allow us to provide multiple first stages – eg. install from LiveCD, Linux, Windows – with a single common second stage).

The “core” group would probably be written directly to the destination disk and not installed via darwinup.

Updates

“dm” will have an --update mode (possibly scheduled via launchd) which will check for updated versions of the installed packages.

Now, here we have a problem, since by default the binary roots we will be using don’t include any version information in their files names. That said, it is very rare for the MacOSForge roots to be updated, and if need be we could add version information to the roots held by PureDarwin.

Update information will have to be dated. “dm” will keep track of when it last checked for updates. It will collect a list of all packages updated since that time, check which of those it has installed, and download these updates.

“dm” should also be also be able to update itself, via several ways (itself, macports, darwinbuild, etc.. at least it should be symetric to the installation ways and perhaps more).

Security

Different “security” mechanisms could/should be provided, feel free to add and/or strike them:

• Checksuming (md5, sha-1, sha-2 family, etc..) itself and packages for from integrity to security purposes.
• If something is remotely retrieved, we should have the possibility (by default that would be nice) to establish a “secure” (many possible ways too..) connection.
• If “dm” is aware of the resident binaries deployed in the system, checksum could also be possible against them (but it could take some resource, and this kind of process could be moved into a “spotlight-like” daemon).

Language

“dm” will need to be written in a language which allows the invocation of external commands (darwinup, curl), the processing (regex) and storage of text (the output from darwinup) and database access (pd2). If “dm” is going to be included in the “core” group then so will its support libraries/interpretter. A scripting language seems like the best option.

Mini poll:

• Stuart suggests Perl: “but I’m fairly flexible on this point. (Unlike Python and indentations.)”
• Aladin suggests to not reinvent the wheel and enhance the MacPorts project in patching `port’ and creating special portfile for our needs. Stuart will look into this.
• Alternatively,  #!/bin/sh or Lua (this one is not in the “core” group).

Usage

So, could it be also possible that “dm” is a patch of `port’ command (from the MacPorts project) which extends its functionalities to our needs because a lot of things and good features are already inside. We will provide some specific ports too. We could ask exactly the same for a tweaked darwinbuild which points to root. Also in the installation process, a lot of packages are for “user-land” and comes from darwinbuild (and/or macports) at this time.

```–info { package | group | system }`

    --list { installed | available }

--get [config_setting]

--set config_setting value

--add [options] package_list

--remove [options] package_list

--update

--info displays information about the given package, group or system – whether it is currently installed, where it can be found, version, dependencies, and in the case of groups and systems, which packages they contain.

--list without an argument lists all installed packages. With “available” option, list all packages in the package database.

--get without an argument lists the current values of all all config_settings (which will have default built-in values, values stored in /etc/dm.config, and can be over-ridden by the [options] flags to --add and --remove). If config_setting is provided, the settings for just that setting are displayed.

--set sets the value of a particular config_setting (after checking that it’s valid) and stores it in /etc/dm.config.

--add adds the packages in package_list to the current Darwin install.

--remove removes the packages in package_list from the current Darwin install.

package_list 

is a list of space-separated package, group and system names. If an entry contains a “.” or a “/” it is treated as a path to a file, which is read. It is expected to contain a list of package, group or system names, which are then added to the package_list. This will allow custom configurations to be built and used time and again. eg.

perl python ruby will add the curl, perl, python and ruby packages –add recovery_tools file_servers emacs    will add the emacs package, all packages from the file_servers group, and all packages from the recovery_tools system –add Chess packages.txt will add the Chess package, and any packages, groups or systems listed in packages.txt

options

over-ride the defaults stored in /etc/dm.config for the duration of the single command. (This is not a complete list.)

• –dependencies { YES | NO } – The dependencies config_setting. By default this is YES, meaning that for every package added its dependencies are found and added at the same time. (I’m not really sure about how we handle removing dependencies. Either we store some form of reference count for packages, or we re-check dependencies at the time. Either way, we should stop the user from removing a package which other packages depend on.)
• –cache directory_path – The cache config_setting. This is checked for packages before remote repositories. This will allow installation from CD images without needing networking.
• –temp directory_path – The temp config_setting. This is where packages are downloaded to. It is also checked for packages before remote repositories.

--update fetches a list of package changes since the last update and compares it to the list of installed packages. It then downloads those packages which have changed and installs them.

At Installation Time

An interactive installer will present the user with lists of systems, groups or packages for them to choose from. Their choices will then be passed to “dm”, which will resolve dependencies, download the packages, and install them.

Package Database Admin Toold

dbtool.zip below contains a couple of simple Perl scripts, described below. These are a first attempt at producing some tools for creating and managing the package database. These are intended to be used by the packaging system admins, not by the end user. They mostly work on plain text files, so it should be possible to keep all of the associated resources (package lists, language files, core, group and system lists) under revision control and automate the process of producing the package database. Please also note that at this point I see the “dm” tool more as a binary installer than a fully-fledged package manager.

dbaudit

dbaudit does a brute-force audit of a darwinbuild environment, finding which packages have binary roots and attempting to calculate dependencies for those that do.

The output package list is a simple text file with one line per package found. Each line has the format:     PackageName Y build version { dependency1 dependency2 … dependencyN } Where “Y” could also be “N” and signals that a binary root was found. If no root was found, no version or dependency information will be provided. Dependencies are listed as package names, if resolved, or the full path of linked library paths otherwise.

dbstats

dbstats produces a simple summary of the dbaudit output file. The information in this file may go towards providing the dependency information needed by a Darwin package manager. package_list.zip contains the package list which dbaudit produced for a 9G55pd1 install of darwinbuild. It shows:     423 packages, 79 missing binary roots, 79 unresolved dependencies (The two 79s are purely coincidental and unrelated, I think.)

pdpdmake

pdpdmake takes a number of input files and either creates or updates a SQLite database file according to their contents.

As a minimum, at least one package list must be provided.

dtbi

dtbi (Darwin Trivial Binary Installer) is a Perl prototype of a basic installer for Darwin. It’s main purpose is to generate discussion. Currently it will query a pdpd database (there’s one produced from the packages_list.txt file below provided as an example) for information about packages. If darwinup is installed, dtbi will query it for a list of installed packages. It will add a new package, plus any uninstalled packages which that package depends upon, downloading the binary from MacOSForge.

To try dtbi in PureDarwinXmas:

1. Install the CPAN package (Perl modules, needed for database access).
2. Install curl (if you want to try installing packages).
3. Install darwinup (from darwinbuild) into /usr/sbin/ (we can argue about where it should go later).
4. Copy dtbi and the db database file into the same directory (/Users/Shared/ is nice).

Currently, only the --info, --list and --add options have been implemented. Again, this is just a quick Perl prototype to get people talking and to see if this solves a problem for us. The fact that this version requires 10+Mb of Perl modules suggests we’ll actually be using a different language for the production version.

Your comments below or in #puredarwin, please.

The Installer

This page is a “request for comments” related to the general installation process. Please feel free to contribute and comment. Through the general install process the installer should be able to also install itself.

The Installation Process

Installing PureDarwin should be a two stage process, as illustrated here.

First stage

The first stage installer is run from either a PureDarwin CD image, or from another operating system on the target computer. The first stage should:

• Partition the target disk, if desired.
• Format the target partition.
• Install the PureDarwin Core package. This will provide all of the utilities and services necessary to allow the second stage installer to complete successfully.
• Install the appropriate bootloaders (/usr/standalone/i386 -> install bootloader into MBR (beginning of disk), boot sector (beginning of partition), grub and HFS startup file (alternatively /boot)), according to user choice and whether it will be a multi-boot system. The user will have the choice of MBR (Chameleon) or EFI. The question should be “Is this a Mac or VMware Fusion?” If they answer “yes”, install the EFI bootloader; if they answer “no”, install MBR.
• Reboot the system when done.

**

Pre-configuration and questions

The user will be asked a quick list of questions. The question must always have a default answer available and “compatible” with all others answers of previous and next questions.

• Interactive mode (advanced) Questions, questions and questions…

• Semi interactive mode

• Non interactive mode (full) MODE=1

• Non interactive mode (automatic) MODE=0 When the second stage installer runs, it should check for the presence of a configuration file in a specific location. If it finds it, it should read all settings from here and complete the installation without asking the user any more question. If this file isn’t found then it should continue with the standard interactive installation. If not all settings has been provided in the present file, it should continue filling with the default value or (alternatively jump into interactive mode. Caution about this fact, because if “the user” explicitly has chosen “non interactive mode”, it is not to fall into interactive mode because 1 settings is missing in the file).

“Non-interactive mode” will require the user (eg. system admin) to do some extra work. The installer should always automatically attempt to copy non-interactive configuration files from a set location on the boot CD (eg. in /Library/Install/ ) to the target disk. In order to make use of this facility, a boot CD with files in this location should be specially prepared. We can make a root of the install CD, along with the pd_makedmg script, available for download for exactly this purpose.

** Grouping in categories and sub-categories the sequences of questions seems common. 

This leads us to another possibilities, we could also target a type of PureDarwin release installed (e.g., nano, dev, rescue, test/bench, etc..).

** Notes: We can’t depend on what admin tools are loaded onto the target (having the core system ship without eg. the DSTools package), so user records should be created by generating the data files (a la pd_injectuser) rather than via tools (pd_adduser).

Preparation of destination media

Partitioning the destination disk, formatting, installing bootloader. This stage could also see the installation of the kernel(s) and a core system so that the rest of the install process could run from the destination, as outlined above.

Notes: We need to know from where we can put and provide the installation materials and to where the PureDarwin project will be installed. e.g., disk, but we have also: iso and VMware, qemu and other democratised emulation/simulation/virtualisation solution.

First Stage Installer Script

An installer script will be needed to guide the user through the first stage installation. A rough idea of how this would work (using the Chameleon bootloader components replacing the standard Darwin ones in /usr/standalone/i386/) is:

Show the user a list of attached drives and ask them to choose one. Show the user a list of partitions on the chosen drive, and ask them to choose one or enter the fdisk interactive partitioner. If the user chose to partition the disk, restart the system so that the changes take effect. Once the user has chosen a disk (number = $disk) and partition (number = $part) to install on, we can ask them for a volume name ($name) to give it, and then without further interaction:

• newfs_hfs -s -J -v [$name] /dev/rdisk[$disk]s[$part]
• dd if=/usr/standalone/i386/boot1h of=/dev/rdisk[$disk]s[$part]
• mount -t hfs /dev/disk[$disk]s[$part] /tmp
• cp /usr/standalone/i386/boot /tmp/ (for MBR)
• tar xfz /usr/standalone/PureDarwinCore.root.tar.gz -C /tmp/
• umount /tmp
• echo 'Remove CD-ROM...'
• shutdown -r now And we’re on to the second stage install.

__ __

Correctly setting up bootloaders is a tricky business, especially in a multi-boot environment. One of the advantages of this two stage approach is that the user will find out if the system can successfully boot into Darwin before spending time installing (potentially involving lengthy downloads) all the packages needed by a complete system. 

**Comment: **See the boot page for setting up the bootloader

Second stage

The second stage installer will be designed to run in a Darwin environment, meaning that it will be exactly the same no matter what the first stage installer was.

In this way we will be moving the environment-specific parts of setup into the first stage (of which there will be a few different platform-specific versions), consequently we only need to maintain a single version of the main installation code. It will possibly need access to a network connection, although providing a local cache of packages will make this unnecessary.

“PureDarwin Core” is basically (in minimal PureDarwin installation which automatically runs a setup and install script at boot) allowing the user to add extra packages to. It should be possible for the user to chose not to install anything an be left with a working, bare-bones system.

(“PureDarwin Boot” above is a fictional version of Nano equipped with the extra packages needed to run pd_setup)

Copying across and installing packages

This is covered on the Package management page.

Post-configuration

This will include adding users (a default one is provided if no user account has been created) to the system and some settings.

The choices (configuring details such as the system timezone, preferred language, keyboard layouts, etc…) made by the user at the “pre-configuration” phase let the installation to be finish without the user waiting around..

A final question could be (or not) to fall into a shell or to reboot (on timeout too).

The world of bootstrapping

This page gives an overview over some basic concepts about booting operating systems. It is based on a conversation with dfe in #puredarwin.

Linux

Linux needs two files to boot.  A kernel, and an initrd any time you upgrade your kernel you’ve got to build a new initrd to go with it which pulls needed drivers off the filesystem as is and puts them into the initrd now in Linux’s case you’re typically not going to be adding a driver needed at boot time to the filesystem after the fact but in the case of Windows or OS X you’ll have a lot of third-party drivers which the user might want to install at any time therefore the bootloader must be able to read all of those drivers which means the bootloader must be able to read the root filesystem which the bootloader will do using BIOS calls to read sectors and its own code to read the filesystem

Windows NTLDR

NTLDR does basically the same thing the boot sector knows barely enough to get NTLDR loaded, just like boot1 knows barely enough to get boot (a.k.a. boot2) loaded once there, the second-stage bootloader (be it NTLDR or boot) has enough code to read the filesystem and locate the kernel and drivers in NTLDR’s case it even has enough code to read a registry hive which tells it which drivers to load rather than simply loading any drivers that might be needed for boot which is also why windows won’t boot if you move the hard drive to a different system.  The system registry hive only says to load say the 440bx HD controller driver, not the ICH-7 driver or the VIA driver or whatever that’s part of the reason why EFI is such a big deal. 

EFI

With EFI you’ve got a decent 32-bit callable interface to read sectors from the hard drive plus you’re guaranteed to be able to read FAT32 plus you can supply drivers for other filesystems so it enables you to write bootloaders that can read quite a bit, certainly enough to get all the individual drivers loaded Now take something like GRUB for instance.  GRUB is actually advanced enough that it code theoretically load a vmlinuz and a  number of .ko files to get the system loaded.  But which .ko files would it load? if you look on a macbook you’ll note that everything you need to boot is in ROM there’s hardly anything in the EFI partition well there never was anything on the service partition because Apple has enough in the firmware that it doesn’t need the service partition but that’s because Apple wants to explicitly support booting of OS X which is an addition to the EFI spec and to boot from CD apple may have used the EFI El Torito spec to load enough to get the HFS+ driver and boot.efi loaded then boot.efi could take over as per usual yeah, take the linux case for instance assume you had everything to do from scratch and there was no legacy of initrds what you would probably do is write an ext2/3 driver for EFI and you might then have a bootloader which looked for a config file to tell it which kernel and set of drivers to load yeah, if OS X was made to run on generic PCs then the CD might have a custom loader that was just good enough to load an HFS+ driver and the real second-stage booter (boot.efi) notice how nothing really changes from x86 boot here.  You still have the situation of a first stage loader good enough to load the second stage loader which is good enough to load the OS welcome to the world of bootstrapping

Multiboot

multiboot is an open specification designed to allow you to boot a kernel straight into protected mode for it to have any chance of working you’ve either got to have enough in the kernel itself to be able to root or you’ve got to supply modules to the kernel the multiboot spec can supply modules to the kernel though but again you wind up in a similar situation.  Now part of your bootstrapping code is sort of in the kernel at least it has to have enough code to know how to link in the additional modules because let’s face it, at some point you need to root a filesystem there’s no getting around that typically multiboot is used primarily for toy operating systems yes, multiboot doesn’t really give you a whole lot basically all it does is say that your kernel and some number of additional files will have been loaded by the bootloader basically all it does is say that your kernel and some number of additional files will have been loaded by the bootloader and then the bootloader will jump into your code which will start in protected mode

Modified boot-132 to run as multiboot kernel

kernel being boot-132 in our special case well the reason for multiboot in boot-132 is to avoid having to replace the startup file to develop it and boot-132 uses multiboot in a rather queer way basically there’s an alternative entrypoint coming from the multiboot bootloader that entrypoint sets up enough to get a stack and whatnot and from there runs the bootloader as per usual i.e. it still thunks into real-mode to make BIOS calls Q: So in a nutshell, it’s BIOS/EFI -> (GRUB) and/or boot1 (our “kernel” for argument’s sake) -> boot2 -> xnu (our “real” kernel)? when using multiboot there is no boot1 GRUB boots boot(2) directly that is the point of it the reason being that 512 bytes for boot1h is barely enough to find the HFS+ startupfile and load it now it’s really the case that you’re guaranteed to have 1024 bytes available which as we’ve seen is actually enough to read some of the HFS+ directory structure and find a file in the root but even then the 1024-byte is really not enough to do it right

Network booting

Q: from a server’s perspective the i386 network boot mechanisms are all the same?

yeah, just provide an IP via DHCP and files via TFTP

PXE

PXE is an x86 thing it does use TFTP like basically everything else out there to grab the kernel and modules (extensions) though actually bootstrapping over the network is interesting regardless of platform this is basically how it is supposed to go down DHCP or BootP so the firmware can get itself an IP address TFTP to actually grab the bootloader which depending on system might be a first-stage loader (PXE tends to require this) or might be THE loader PXE tends to require it primarily because PXE spec says to only force the firmware to load 32k so 32k is usually only enough to get your own code in place that can load the larger real booter either way you’ll eventually get the real (second-stage) booter loaded

BootX (PPC)

for PPC that’d be BootX so BootX itself would be loaded by OpenFirmware from there BootX will make open firmware calls to load more files from tftp, including the kernel and hopefully the Extensions.mkext package

Netboot (PPC)

although PPC Macs have the whole netboot spec too which is some more stuff on top of TFTP/DHCP

there is a command to do a netboot in openfirmware typically just hold down N

Windows

ditto for Windows NT, it has a special server program there’s actually a server program that tells the client which drivers it needs the Windows PXE client enumerates PCI devices and sends that info to this special server the special server responds back and tells it which drivers it needs to download via TFTP

General

the thing is that this kinda goes back to what I was talking about earlier on having to know which drivers to load there’s different ways to accomplish it Windows actually has a client/server thing to do this and the client side tells the server about the hardware and the server then does the hard work of sifting through the INF files to determine which SYS files to load a typical Linux setup uses an initrd for something like Fedora the initrd intended for PXE boot will basically contain any driver (.ko) that might possibly be needed to root locally or over the network for OS X it’s similar except that instead of an initrd you have an Extensions.mkext

Universal binaries

Mac OS X and Darwin can use so-called Mach-O (Mach Object) “fat” files, or universal binaries that contain code for more than one architecture, e.g., ppc and i386. PureDarwin, however, currently uses i386 only (also referred to as “x86”) but hopes to use x86_64 a day and future architectures.

Finding and removing files that have no i386 code

The command-line tool lipo can be used to inspect and modify the architecture-related aspects of executable files and libraries.

To find ppc-only files, you can use

find /some/path -exec lipo -i {} 2>&1 ; | grep ppc | grep -v i386

Since the PureDarwin project currently supports only the i386 platform, you should be able to safely delete files found by the command above.

Example

The old UNIX file command is also useful to determine fat file types.

file /usr/lib/libedit.2.dylib  /usr/lib/libedit.2.dylib: Mach-O universal binary with 4 architectures /usr/lib/libedit.2.dylib (for architecture ppc7400): Mach-O dynamically linked shared library ppc /usr/lib/libedit.2.dylib (for architecture ppc64): Mach-O 64-bit dynamically linked shared library ppc64 /usr/lib/libedit.2.dylib (for architecture i386): Mach-O dynamically linked shared library i386 /usr/lib/libedit.2.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64

Then we use lipo. Compare the size before thin (565K) and after (128K).

Mach

From /usr/share/file/magic:

# mach file description # # Since Java bytecode and Mach-O universal binaries have the same magic number the test # must be preformed in the same "magic" sequence to get both right.  The long # at offset 4 in a universal binary tells the number of architectures.  The short at # offset 4 in a Java bytecode file is the compiler minor version and the # short at offset 6 is the compiler major version.  Since there are only  # only 18 labeled Mach-O architectures at current, and the first released  # Java class format was version 43.0, we can safely choose any number # between 18 and 39 to test the number of architectures against # (and use as a hack). [...]

0 belong&0xfffffffe 0xfeedface Mach-O [...]

What is Mach-o?

• A file format
• An ABI (Application Binary Interface)

Where does it come from?

OSF (Open Software Foundation) for mach kernel.

What does it specify?

• Processus address space
• Dynamic loader to use
• Shared library to load

Structure

+–––––––––––––––––––––––––––––––––––––+ | ** Header | | ** | +–––––––––––––––––––––––––––––––––––––+ | ** Load commands |

References

http://developer.apple.com/documentation/DeveloperTools/Conceptual/MachOTopics/introduction.html  http://developer.apple.com/documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html 

http://en.wikipedia.org/wiki/Mach-O 

http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/Introduction.html 

http://en.wikipedia.org/wiki/Universal_Binaries

man otool man dyld man Mach-o

Using DarwinBuild

The DarwinBuild project provides an integrated build environment for Darwin projects. There are many reasons why you should use DarwinBuild and although some parts of Darwin can be built without DarwinBuild, it is easier with it. This page describes some ways to use DarwinBuild in order to build Darwin projects. It is a work in progress. Please post your comments below or edit this wiki page.

Prerequisites

Have a look at (to be determined)

• A Mac with the latest Xcode installed (whether it needs to be an Intel Mac and whether it needs to be (Snow) Leopard is still to be determined). (Some projects require Xcode and hence a Mac OS X system to build: those do not use a makefile, but instead a .pbproj or .xcode project file. It is unclear at this time whether the requirement for a Mac with Xcode could also be satisfied using just Darwin and the Xcode sources.
• Subversion available (Leopard comes with it, otherwise use the binaries from fink or compile sources from the MacPorts project)
• Some coffee

If you are using svn from fink, you need to put it in your path by

PATH=/sw/bin:$PATH # If you are using svn from fink

In case you use MacPorts, your path should already and probably be set to

export PATH=/opt/local/bin:/opt/local/sbin:$PATH

Terminology

Since the terminology used by DarwinBuild and PureDarwin is slightly different from what you might know from Linux, it makes sense to look at some commonly used terms now.

Project

Upstream project’s source code; .orig.tar.gz

Example

bash (as a project not command)

Comments

Most of Apple’s own projects are under the APSL, other upstream open source projects have been converted to DarwinBuild projects and are under the respective project’s sources

xref database

Database of the package manager

Example

dpkg, rpm

Comments

The xref database has (so far) only been used during the build process, but not as a package manager for a running Darwin system. Like package manager databases, the xref database knows about build-time and run-time dependencies

Roots

binary roots

Example

Binary packages (.deb, .rpm)

Comments

Binary roots that contain code for all architectures (“universal/fat binaries”) are packed as .tar.gz files, whereas binary roots that contain code for just one architecture (“stripped”, e.g., i386) are usually packed as .tar.bz2 files

BinaryDrivers

Closed-source binary packages

Example

AppleRTC

Comments

As of May 2008, 6 projects are released by Apple in binary-only form.

Development on macosforge’s darwinbuild seem stopped on github, and subversion repository seems to be offline. Use the git repo bellow for now.

Installation

From Git

git clone https://github.com/PureDarwin/darwinbuild.git

Generic Instructions (after getting darwinbuild source)

Change directory to ensure you are in darwinbuild (if not already)

cd darwinbuild
xcodebuild install DSTROOT=/

A fresh darwinbuild folder is now present: “/usr/local/share/darwinbuild”.

From MacPorts

Simply run: % port install darwinbuild

Output:

    ---> Computing dependencies for darwinbuild
    ---> Fetching darwinbuild
    ---> Verifying checksum(s) for darwinbuild
    ---> Extracting darwinbuild
    ---> Configuring darwinbuild
    ---> Building darwinbuild
    ---> Staging darwinbuild into destroot
    ---> Installing darwinbuild @0.8.0_508
    ---> Activating darwinbuild @0.8.0_508
    ---> Cleaning darwinbuild

In order to upgrade to the latest revision of trunk:

    % port selfupdate
    % port -f upgrade darwinbuild

Initialize Darwinbuild

Some part of the environment

The BuildRoot directory

This place could also be called the BuildChroot directory, everything fetch or built by darwinbuild will reside inside this directory.

Notes: The build version “9J61” (2009/05) used below is just an example.

(At the time of this writing, 9F33pd1.plist and 9G55pd1.plist are recommended, as it includes PureDarwin-specific patches. You can get them from the PureDarwin repository.)

Create and select a BuildRoot location hierarchy in the current working directory:

cd //darwinbuild
mkdir 9J61
cd 9J61

The DarwinBuild ticket#1 workaround (DarwinBuild inherits a bug from Xcode that makes it impossible to use it on a HFS+ volume, the workaround(s) involve(s) setting up NFS locally or using an UFS disk image) is no longer needed since on the Darwinbuild website, we can read (news from 2009/04/17): “The latest revision of trunk has support for sparsebundles and NFS Loopback in order to avoid the problems with xcodebuild inside of chroots. If you do not change the way you use darwinbuild, you will start seeing the sparsebundle storage. Nothing else is needed and Xcode-based projects will build on whatever filesystem you have.”

darwinbuild -init 9J61 -nfs

If you want to avoid the use of NFS, the old fashioned method is still available with: darwinbuild -init 9J61 -nodmg The command above should download the .plist files (it will run nfsd if it is not yet the case and will mount the build root over NFS loopback when a project will be built) from the darwinbuild website and give:

Adding build root to NFS exports file ...
nfsd: nfsd not running?
Checking exports file ...
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9J61.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9G55.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9F33.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9E17.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9D34.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9C31.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9B18.plist ...
Download complete
Downloading http://svn.macosforge.org/repository/darwinbuild/trunk/plists//9A581.plist ...
Download complete
Initialization Complete

If you get “.build/9F33.plist: No such file or directory”, it can be necessary to repeat this step. As a result, you should now have inside the current working directory:

./.build
./.build/9A581.plist
./.build/9B18.plist
./.build/9C31.plist
./.build/9D34.plist
./.build/9E17.plist
./.build/9F33.plist
./.build/9G55.plist
./.build/9J61.plist
./.build/build
./.build/buildroot.nfs
./.build/xref.db
./Headers
./Logs
./Roots
./Sources
./Symbols

Whenever there are new Darwin projects or versions, you should do darwinbuild -init again in order to refresh the .plist files (think of it as “apt-get update” for Darwin source projects). Notes: Keep in mind that/etc/exports must be cleaned sometimes, since there is no concept of “uninitializing” (implicitly removing the added line from /etc/exports). An example of what is added:

# Added by darwinbuild on 20090523154428
/Users/aladin/PureDarwin/darwinbuild/9J61/.build/buildroot.nfs -maproot=0:10

Take a look at http://darwinbuild.macosforge.org/trac/ticket/86 if your /etc/exports grows to fast.

Logs folder

Later on, if a project fails to build (and depending your tty), you will want to look into the entire history of build logs. So simply look into the Logs/<project>/<project>-<version>~<build attempts> folder for a detailled compilation loh. In this case the “CommonCrypto” project has been successfully built at the first attempt and its log can be found in […]/9J61/Logs/CommonCrypto/CommonCrypto-32207.log~1. The entire content cannot be pasted here, but most the time, the end crowns with:

[...]

** BUILD SUCCEEDED **
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 BUILD TIME: Xh Ym Zs
EXIT STATUS: 0

With a project which has failed to build, the end can looks like:

[...]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 BUILD TIME: 0h 0m 0s
EXIT STATUS: 2

Building projects

Before building a project, it is mandatory to initialize again (refresh) the darwinbuild environment. Same apply if the initialized darwinbuild shell session has been closed. After running darwinbuild -init ..., the output should look like for:

$ darwinbuild -init 9J61


> > Creating build root disk image ...
> > Found 9J61.plist in .build
> > Found 9G55.plist in .build
> > Found 9F33.plist in .build
> > Found 9E17.plist in .build
> > Found 9D34.plist in .build
> > Found 9C31.plist in .build
> > Found 9B18.plist in .build
> > Found 9A581.plist in .build
> > Initialization Complete


$ darwinbuild -init 9J61 -nfs


> > Adding build root to NFS exports file ...
> > Checking exports file ...
> > Found 9J61.plist in .build
> > Found 9G55.plist in .build
> > Found 9F33.plist in .build
> > Found 9E17.plist in .build
> > Found 9D34.plist in .build
> > Found 9C31.plist in .build
> > Found 9B18.plist in .build
> > Found 9A581.plist in .build
> > Initialization Complete

Ideally, one could transfer the contents of the BuildRoot to a volume, bless it, and boot a fully working Darwin system from it. In fact, it’s not so simple. Whenever you build something using DarwinBuild and don’t specifiy otherwise (using -nochroot), you will be building inside a chrooted environment using the DarwinBuild directory. Consequently, your build results, hence, will be “built on Darwin” as opposed to “built on Mac OS X”. If during the process of downloading you get errors like “ERROR: could not find root: AppleUSBIrDA”, this simply means that a binary root of the respective project has not been uploaded to the DarwinBuild server yet. (Perhaps it does not build correctly with DarwinBuild yet.) The file xref.db contains the Darwin xref database. It keeps track of the Darwin projects installed in your BuildRoot and their files and version numbers (think of xref roughly as a package manager like “apt” for Darwin binary roots). The xref database has been filled by the darwinbuild -load command, and will be updated whenever you build something with DarwinBuild.

CoreFoundation as a first test case

To build a specific package, e.g., CF, type:

$ darwinbuild CF

Troubles with CF building

CF is a test case to build. On the first build in the new BuildRoot, DarwinBuild will do some initializations, e.g., copy some header files from the host OS. If it fails, then some prerequisites might be missing or you might need to use -nochroot (in case not all prerequisites are uploaded to DarwinBuild yet; this would then use the files from the currently running OS rather than from DarwinBuild). If the build succeeds, you should see a Roots/CF/CF-476.10.root~1 directory containing the files you just built.

xnu

A classic test case is xnu, the kernel. The command below will fetch and build the xnu project. Before that step, some binaryroots (dependencies of the xnu project. as e.g., libgcc, dylib, developer_cmds, etc..) will be downloaded and loaded into the BuildRoot.

$ darwinbuild xnu

If the build succeeds, you can see a xnu/xnu-1228.12.14.root~1 directory containing the built project. The ~1 stands for the number of time the project has been built. Then, in order to populate the BuildRoot dir with the freshly built project:

$ darwinbuild -load xnu
Copying xnu from /Volumes/Builds/9J61/Roots/xnu/xnu-1228.12.14.root~1 ...
xnu - 2640 files registered.

/XCD/loper

You might come across a warning that /XCD/loper is missing. Inside BuildRoot, there should be a directory called XCD/ which contains Xcode and its dependencies (e.g., Xcode requires a proper CoreFoundation, not CF-Lite). Anything under XCD should only link or refer to any other thing in XCD in order to “keep away” Xcode dependencies. If not, there’s something wrong. The contents of XCD/ are copied there from the host system by DarwinBuild’s installXcode. This can be invoked manually as well:

/usr/local/share/darwinbuild/installXcode /Developer/darwinbuild/9C31/BuildRoot/ Analyzing Xcode dependencies … Copying Xcode and dependencies …

More cool stuff DarwinBuild can do

These need to be documented here

• buildorder.pl
• ditto.sh
• log-index.pl
• packageRoots.sh
• thinFile.sh
• buildlist.sh
• createChroot
• darwinmaster.sh
• installXcodebuild
• manifest
• processtrace.sh
• thinPackages.sh

darwinxref

Listing all the projects for a given branch

darwinxref -b 9G55 version '*'

Searching the project of a given file

darwinxref findFile launchctl
launchd:
 /bin/launchctl

Building all the projects (brutus way)

for X in $(darwinxref version '*' | cut -f 1 -d '-'); do darwinbuild $X; done

Note: Of course, this doesn’t mean all the projects will be compiled.

Package the built binaries

Time to package them up!

{DarwinBuild_Checkout_Dir}/packageRoots.sh
Archive tool: tar (GNU tar) 1.14
*** Packaging Headers
*** Packaging Roots

{DarwinBuild_Checkout_Dir} is your working copy from SVN of DarwinBuild. If you followed the article as suggested at the beginning, it must be located in /Developer/darwinbuild/trunk/darwinbuild/. We now have a nice Darwin binary root archive in the Packages/ directory:

ls Packages/
CF.root.tar.gz

Why doesn’t it have a version number?

Resources

Deprecated

Workaround DarwinBuild ticket #1 (no longer needed)

The DarwinBuild ticket#1 workaround is no longer needed since on the Darwinbuild website, we can read (news from 2009/04/17): “The latest revision of trunk has support for sparsebundles and NFS Loopback in order to avoid the problems with xcodebuild inside of chroots. If you do not change the way you use darwinbuild, you will start seeing the sparsebundle storage. Nothing else is needed and Xcode-based projects will build on whatever filesystem you have.” Since DarwinBuild currently inherits a bug from Xcode that makes it impossible to use it on a HFS+ volume, we are going to use a workaround that involves setting up NFS locally.

sudo su
cat >> /etc/exports <<EOF
/Developer -maproot=root localhost
EOF
nfsd restart
sleep 20
mkdir /DeveloNFS
mount -t nfs localhost:/Developer /DeveloNFS

You should use /DeveloNFS for your DarwinBuild-related work, then you should not encounter DarwinBuild ticket #1. Notes: Using an UFS disk image (a bit deprecated though) is another possible alternative not described here.

Populate BuildRoot (no longer needed)

Populating the BuildRoot directory via the way below is no longer needed because the dependencies of a project are automatically retrieved and loaded in the BuildRoot. Theoretically you could begin building projects with DarwinBuild now. However, this would mean that you would have to build binaries using your host Mac OS X as the build environment (using -nochroot). This would clearly not be ideal, since the resulting binaries would not be guaranteed to run on Darwin. Hence, we want to build Darwin projects using Darwin itself as the build environment (“self-hosted”). To do this, we use a chroot environment which resides in the BuildRoot directory. We can fill this BuildRoot with all available Darwin binaries using the following command:

for X in `darwinxref version '*'` ; do darwinbuild -load ${X/-*/} ; done

This downloads any Darwin components that are available in pre-compiled form (called “binary roots”) to Roots/.DownloadCache and installs them into our BuildRoot directory. Since it downloads all available binary roots, it is obviously going to take some time, even on a fast Internet connection. The result is an almost-complete Darwin system inside the BuildRoot directory.

• May 27, 2008, a 9C31 Roots/.DownloadCache populated in this way was 714M in size, and the BuildRoot consisted of about 69,000 files taking up 2.21 GB of space.
• September 29, 2008, a 9F33 Roots/.DownloadCache populated was 811M. The BuildRoot took around 2.6GB of disk space.
• February 12, 2009, a 9G55 Roots/.DownloadCache is still at 811M. And the BuildRoot is taking 4.5G of space.
• May 25, 2009, a 9J61/ seems to need more than 11G (related to svk infinite loop) and fools nicely (4Ti !!!) `df’ available space: /dev/disk1s2 11Gi 11Gi 4.0Ti 1% /Volumes/Builds
• As of June 13, 2009, situation fixed and more than the half of the projects are built and packaged.

Help and further reading

The DarwinBuild Project Archives (darwinbuild-dev mailing list at lists.macosforge.org)

Credits

Credits go to kvv and _wms for their work on DarwinBuild and for their excellent online support. This page was started by probono in the spirit of the DarwinBuild newbie guide by Craig Harman, but specifically covers Darwin versions starting with 9.

DarwinBuild troubleshooting

The subpages available below represents collections of troubleshooting regarding some Darwin projects that are built with DarwinBuild. Most of fixes and workaround tends to be deprecated with time and BuildVersion number grow. And yes, you can sometimes use these pages as an entropy generator, the chaos leads here.

Darwin 10

… 10C540 status

No dependency problem and half of the projects can be build without any patches. Some projects in the list below also have been volontary not built but build, including: 

BerkeleyDB MySQL bind9 cups_libs gcc_select libtelnet passwordserver_saslkerberos passwordserver_saslextra

PROJECT BIN SRC PAK PASSES Apple16X50Seri       [1](javascript al :void(0); “** BUILD FAILED * ”) AppleAPIC       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) AppleDisplays       [1](javascript :void(0); “EXI T STATUS: 2”) AppleFileSyste       [1](javascript mDriver :void(0); “ BUILD FAILED * ”) AppleHWSensor       [1](javascript :void(0); “* BUILD FAILED * ”) AppleIntelPIIX       [1](javascri ATA pt:void(0); “ * BUILD SUCCEE DED ”) AppleKeyswitch       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) AppleRAID       [1](javascript :void(0); “ BUILD FAILED * ”) AppleRTL8139Et       [1](javascri hernet pt:void(0); “ * BUILD SUCCEE DED ”) AppleSMBIOS       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) AppleTalk       [1](javascript :void(0); “EXI T STATUS: 2”) AppleUSBAudio       [1](javascript :void(0); “ BUILD FAILED * ”) AppleUSBCDCDri       [1](javascript ver :void(0); “ BUILD FAILED * ”) AppleUSBIrDA       [1](javascript :void(0); “ BUILD FAILED * ”) BerkeleyDB       BootCache       [1](javascript :void(0); “* BUILD FAILED * ”) CF       [1](javascript :void(0); “EXI T STATUS: 2”) CFOpenDirector       [1](javascript y :void(0); “* BUILD FAILED * ”) CPAN       [1](javascript :void(0); “EXI T STATUS: 2”) CPANInternal       [1](javascript :void(0); “EXI T STATUS: 2”) CarbonHeaders       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ChatServer       [1](javascript :void(0); “ BUILD FAILED * ”) Chess       [1](javascript :void(0); “* BUILD FAILED * ”) CommonCrypto       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) CoreOSMakefile       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) CrackLib       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Csu       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) CyrusIMAP       [1](javascript :void(0); “EXI T STATUS: 2”) DSPasswordServ       [1](javascript erFramework :void(0); “ BUILD FAILED * ”) DSPasswordServ       [1](javascript erPlugin :void(0); “ BUILD FAILED * ”) DSTools       [1](javascript :void(0); “ BUILD FAILED * ”) DirectoryServi       [1](javascript ce :void(0); “ BUILD FAILED * ”) DirectoryServi       [1](javascript ceDaemon :void(0); “* BUILD FAILED * ”) DirectoryServi       [1](javascript ceMIG :void(0); “* BUILD FAILED * ”) DiskArbitratio       [1](javascript n :void(0); “* BUILD FAILED * ”) FastCGI       [1](javascript :void(0); “EXI T STATUS: 2”) ICU       [1](javascript :void(0); “EXI T STATUS: 2”) ICU_debug       [1](javascript :void(0); “EXI T STATUS: 2”) ICU_profile       [1](javascript :void(0); “EXI T STATUS: 2”) IOACPIFamily       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) IOATAFamily       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) IOATAPIProtoco       [1](javascript lTransport :void(0); “ BUILD FAILED * ”) IOAudioFamily       [1](javascript :void(0); “ BUILD FAILED * ”) IOBDStorageFam       [1](javascript ily :void(0); “* BUILD FAILED * ”) IOCDStorageFam       [1](javascript ily :void(0); “* BUILD FAILED * ”) IODVDStorageFa       [1](javascript mily :void(0); “* BUILD FAILED * ”) IOFWDVComponen       [1](javascript ts :void(0); “* BUILD FAILED * ”) IOFireWireAVC       [1](javascript :void(0); “* BUILD FAILED * ”) IOFireWireFami       [1](javascript ly :void(0); “* BUILD FAILED * ”) IOFireWireIP       [1](javascript :void(0); “* BUILD FAILED * ”) IOFireWireSBP2       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) IOFireWireSeri       [1](javascript alBusProtocolT :void(0); “ ransport BUILD FAILED * ”) IOGraphics       [1](javascript :void(0); “* BUILD FAILED * ”) IOHIDFamily       [1](javascript :void(0); “* BUILD FAILED * ”) IOKitTools       [1](javascript :void(0); “* BUILD FAILED * ”) IOKitUser       [1](javascript :void(0); “* BUILD FAILED * ”) IONetworkingFa       [1](javascript mily :void(0); “* BUILD FAILED * ”) IOPCIFamily       [1](javascript :void(0); “* BUILD FAILED * ”) IOSCSIParallel       [1](javascript Family :void(0); “* BUILD FAILED * ”) IOSerialFamily       [1](javascript :void(0); “* BUILD FAILED * ”) IOStorageFamil       [1](javascript y :void(0); “* BUILD FAILED * ”) IOUSBFamily       [1](javascript :void(0); “* BUILD FAILED * ”) IOUSBMassStora       [1](javascript geClass :void(0); “* BUILD FAILED * ”) JavaScriptCore       [1](javascript :void(0); “* BUILD FAILED * ”) JavaScriptGlue       [1](javascript :void(0); “* BUILD FAILED * ”) KerberosHelper       [1](javascript :void(0); “* BUILD FAILED * *”) KerberosLibrar       [1](javascript ies :void(0); “EXI T STATUS: 2”) LDAPFramework       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libc       [1](javascript :void(0); “EXI T STATUS: 2”) Libc_debug       [1](javascript :void(0); “EXI T STATUS: 2”) Libc_headers       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libc_man       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libc_profile       [1](javascript :void(0); “EXI T STATUS: 2”) Libcpp_kext       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libinfo       [1](javascript :void(0); “EXI T STATUS: 2”) Libm       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libmx       [1](javascript :void(0); “ BUILD FAILED * ”) Libnotify       [1](javascript :void(0); “EXI T STATUS: 2”) Librpcsvc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libsyscall       [1](javascript :void(0); “EXI T STATUS: 2”) Libsystem       [1](javascript :void(0); “EXI T STATUS: 2”) Liby       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) MySQL       NFS       [1](javascript :void(0); “EXI T STATUS: 2”) OpenAL       [1](javascript :void(0); “EXI T STATUS: 2”) OpenBSM       [1](javascript :void(0); “ BUILD FAILED * ”) OpenDirectory       [1](javascript :void(0); “ BUILD FAILED * ”) OpenLDAP       [1](javascript :void(0); “EXI T STATUS: 2”) OpenSSH       [1](javascript :void(0); “EXI T STATUS: 2”) OpenSSL096       [1](javascript :void(0); “EXI T STATUS: 2”) OpenSSL097       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) OpenSSL098       [1](javascript :void(0); “ BUILD FAILED * ”) PowerManagemen       [1](javascript t :void(0); “ BUILD FAILED * *”) PyRSS2Gen       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) RubyCocoa       [1](javascript :void(0); “EXI T STATUS: 2”) RubyGems       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) RubyOnRails       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) SQLite       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) SQLite_tcl       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Security       [1](javascript :void(0); “ BUILD FAILED * ”) SecurityTokend       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) SecurityTool       [1](javascript :void(0); “ BUILD FAILED * *”) SmartCardServi       *[1](javascri ces pt:void(0); “ * BUILD SUCCEE DED ”) SpamAssassin       [1](javascript :void(0); “EXI T STATUS: 2”) SquirrelMail       [1](javascript :void(0); “EXI T STATUS: 2”) SystemStubs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) TargetConfig       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) TargetConfig_       *[1](javascri headers pt:void(0); “ * BUILD SUCCEE DED ”) TimeZoneData       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Tokend       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Twisted       [1](javascript :void(0); “EXI T STATUS: 2”) UserNotificati       [1](javascri on pt:void(0); “ * BUILD SUCCEE DED ”) WebCore       [1](javascript :void(0); “ BUILD FAILED * *”) X11apps       [1](javascript :void(0); “EXI T STATUS: 2”) X11fonts       [1](javascript :void(0); “EXI T STATUS: 2”) X11libs       [1](javascript :void(0); “EXI T STATUS: 2”) X11misc       [1](javascript :void(0); “EXI T STATUS: 2”) X11proto       [1](javascript :void(0); “EXI T STATUS: 2”) X11server       [1](javascript :void(0); “EXI T STATUS: 2”) adv_cmds       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) amavisd       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) apache       [1](javascript :void(0); “EXI T STATUS: 2”) apache_mod_b       [1](javascript onjour :void(0); “EXI T STATUS: 2”) apache_mod_f       [1](javascri astcgi pt:void(0); “ * BUILD SUCCEE DED ”) apache_mod_h       [1](javascript fs_apple :void(0); “EXI T STATUS: 2”) apache_mod_p       [1](javascript erl :void(0); “EXI T STATUS: 2”) apache_mod_p       [1](javascript hp :void(0); “EXI T STATUS: 2”) apr       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) architecture       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) autoconf       [1](javascript :void(0); “EXI T STATUS: 2”) autofs       [1](javascript :void(0); “ BUILD FAILED * ”) automake       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) autozone       [1](javascript :void(0); “ BUILD FAILED * ”) awk       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bash       [1](javascript :void(0); “EXI T STATUS: 2”) basic_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bc       [1](javascript :void(0); “EXI T STATUS: 2”) bind9       bison       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bison1       [1](javascript :void(0); “EXI T STATUS: 2”) bless       [1](javascript :void(0); “ BUILD FAILED * ”) bootp       [1](javascript :void(0); “ BUILD FAILED * ”) bootstrap_cmd       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) bsdmake       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bzip2       [1](javascript :void(0); “EXI T STATUS: 2”) cctools       [1](javascript :void(0); “EXI T STATUS: 2”) cctools_ofile       [1](javascript s :void(0); “EXI T STATUS: 2”) cddafs       [1](javascript :void(0); “ BUILD FAILED * ”) clamav       [1](javascript :void(0); “EXI T STATUS: 2”) configd       [1](javascript :void(0); “ BUILD FAILED * ”) configd_execu       [1](javascript tables :void(0); “ BUILD FAILED * ”) configd_libSy       [1](javascript stem :void(0); “ BUILD FAILED * ”) configd_plugi       [1](javascript ns :void(0); “ BUILD FAILED * *”) copyfile       [1](javascript :void(0); “EXI T STATUS: 2”) cron       [1](javascript :void(0); “EXI T STATUS: 2”) crontabs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) cscope       [1](javascript :void(0); “EXI T STATUS: 2”) cups       [1](javascript :void(0); “EXI T STATUS: 2”) cups_libs       [1](javascript :void(0); “EXI T STATUS: 2”) curl       [1](javascript :void(0); “EXI T STATUS: 2”) cvs       [1](javascript :void(0); “EXI T STATUS: 2”) cxxfilt       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) developer_cmd       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) diffstat       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) diskdev_cmds       [1](javascript :void(0); “EXI T STATUS: 2”) disklabel       [1](javascript :void(0); “ BUILD FAILED * ”) distcc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) doc_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) dtrace       [1](javascript :void(0); “ BUILD FAILED * ”) dyld       [1](javascript :void(0); “ BUILD FAILED * ”) eap8021x       [1](javascript :void(0); “ BUILD FAILED * *”) efax       [1](javascript :void(0); “EXI T STATUS: 2”) emacs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) enscript       [1](javascript :void(0); “EXI T STATUS: 2”) expat       [1](javascript :void(0); “EXI T STATUS: 2”) fetchmail       [1](javascript :void(0); “EXI T STATUS: 2”) file       [1](javascript :void(0); “EXI T STATUS: 2”) file_cmds       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) files       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) flex       [1](javascript :void(0); “EXI T STATUS: 2”) freeradius       [1](javascript :void(0); “EXI T STATUS: 2”) gcc       gcc_select       gdb       [1](javascript :void(0); “EXI T STATUS: 2”) glibtool       [1](javascript :void(0); “EXI T STATUS: 2”) gm4       [1](javascript :void(0); “EXI T STATUS: 2”) gnudiff       [1](javascript :void(0); “EXI T STATUS: 2”) gnumake       [1](javascript :void(0); “EXI T STATUS: 2”) gnuserv       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) gnutar       [1](javascript :void(0); “EXI T STATUS: 2”) gnuzip       [1](javascript :void(0); “EXI T STATUS: 2”) gperf       [1](javascript :void(0); “EXI T STATUS: 2”) gpt       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) graphviz       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) grep       [1](javascript :void(0); “EXI T STATUS: 2”) groff       [1](javascript :void(0); “EXI T STATUS: 2”) gssd       [1](javascript :void(0); “EXI T STATUS: 2”) headerdoc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) hfs       [1](javascript :void(0); “EXI T STATUS: 2”) iodbc       [1](javascript :void(0); “EXI T STATUS: 2”) ipsec       [1](javascript :void(0); “ BUILD FAILED * ”) ipv6configurat       [1](javascri ion pt:void(0); “ * BUILD SUCCEE DED ”) kext_tools       [1](javascript :void(0); “ BUILD FAILED * ”) keymgr       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ksh       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) launchd       [1](javascript :void(0); “ BUILD FAILED * ”) launchd_libs       [1](javascript :void(0); “ BUILD FAILED * ”) ld64       [1](javascript :void(0); “ BUILD FAILED * ”) less       [1](javascript :void(0); “EXI T STATUS: 2”) libdispatch       [1](javascript :void(0); “ BUILD FAILED * *”) libdyld       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libedit       [1](javascript :void(0); “EXI T STATUS: 2”) libffi       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libfs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libgcc       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libiconv       [1](javascript :void(0); “EXI T STATUS: 2”) libkxld       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libmd       [1](javascript :void(0); “EXI T STATUS: 2”) libpcap       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libresolv       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       *[1](javascri gent pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       *[1](javascri pple_csp pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       *[1](javascri pple_cspdl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_file_dl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_x509_cl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_x509_tp pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascript sn1 :void(0); “ BUILD FAILED * ”) libsecurity_a       [1](javascript uthorization :void(0); “ BUILD FAILED * *”) libsecurity_c       *[1](javascri dsa_client pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_plugin pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_utilities pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_utils pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri heckpw pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascript ms :void(0); “ BUILD FAILED * ”) libsecurity_c       [1](javascript odesigning :void(0); “ BUILD FAILED * ”) libsecurity_c       [1](javascri ssm pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_d       [1](javascript otmacdl :void(0); “ BUILD FAILED * ”) libsecurity_f       [1](javascri iledb pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_f       [1](javascript ilevault :void(0); “ BUILD FAILED * ”) libsecurity_k       [1](javascript eychain :void(0); “ BUILD FAILED * *”) libsecurity_l       *[1](javascri dap_dl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_m       *[1](javascri anifest pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_m       *[1](javascri ds pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_o       [1](javascri cspd pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_p       [1](javascri kcs12 pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_s       [1](javascri d_cspdl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_s       [1](javascript mime :void(0); “ BUILD FAILED * ”) libsecurity_s       [1](javascript sl :void(0); “ BUILD FAILED * *”) libsecurity_u       *[1](javascri tilities pt:void(0); “ * BUILD SUCCEE DED ”) libsecurityd       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libstdcxx       [1](javascript :void(0); “EXI T STATUS: 2”) libstdcxx_40       [1](javascript :void(0); “EXI T STATUS: 2”) libtelnet       [1](javascript :void(0); “EXI T STATUS: 2”) libutil       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libxml2       [1](javascript :void(0); “EXI T STATUS: 2”) libxslt       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) lsof       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) lukemftp       [1](javascript :void(0); “EXI T STATUS: 2”) lukemftpd       [1](javascript :void(0); “EXI T STATUS: 2”) mDNSResponder       [1](javascript :void(0); “EXI T STATUS: 2”) mDNSResponderS       [1](javascript ystemLibraries :void(0); “EXI T STATUS: 2”) mail_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) mailman       [1](javascript :void(0); “EXI T STATUS: 2”) man       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) misc_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) modemccl       [1](javascript :void(0); “ BUILD FAILED * ”) msdosfs       [1](javascript :void(0); “ BUILD FAILED * ”) nano       [1](javascript :void(0); “EXI T STATUS: 2”) nasm       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ncurses       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) neon       [1](javascript :void(0); “EXI T STATUS: 2”) net_snmp       [1](javascript :void(0); “EXI T STATUS: 2”) netcat       [1](javascript :void(0); “EXI T STATUS: 2”) netinfo       [1](javascript :void(0); “EXI T STATUS: 2”) network_cmds       [1](javascript :void(0); “ BUILD FAILED * ”) notify       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ntfs       [1](javascript :void(0); “ BUILD FAILED * ”) ntp       [1](javascript :void(0); “EXI T STATUS: 2”) objc4       [1](javascript :void(0); “ BUILD FAILED * ”) openmpi       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) pam_modules       [1](javascript :void(0); “EXI T STATUS: 2”) passwordserver       [1](javascri _sasl pt:void(0); “ * BUILD SUCCEE DED ”) passwordserver       [1](javascript _saslextra :void(0); “ BUILD FAILED * ”) passwordserver       [1](javascript _saslkerberos :void(0); “ BUILD FAILED * *”) patch_cmds       [1](javascript :void(0); “EXI T STATUS: 2”) pb_makefiles       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) pdisk       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) perl       [1](javascript :void(0); “EXI T STATUS: 2”) portmap       [1](javascript :void(0); “EXI T STATUS: 2”) postfix       [1](javascript :void(0); “EXI T STATUS: 2”) ppp       [1](javascript :void(0); “ BUILD FAILED * *”) procmail       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) pyOpenSSL       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) pyobjc       [1](javascript :void(0); “EXI T STATUS: 2”) python       [1](javascript :void(0); “EXI T STATUS: 2”) python23       [1](javascript :void(0); “EXI T STATUS: 2”) python_dateut       *[1](javascri il pt:void(0); “ * BUILD SUCCEE DED ”) python_module       [1](javascript s :void(0); “EXI T STATUS: 2”) rcs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) remote_cmds       [1](javascript :void(0); “EXI T STATUS: 2”) removefile       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) rsync       [1](javascript :void(0); “EXI T STATUS: 2”) ruby       [1](javascript :void(0); “EXI T STATUS: 2”) ruby_dnssd       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ruby_libxml       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) samba       [1](javascript :void(0); “EXI T STATUS: 2”) screen       [1](javascript :void(0); “EXI T STATUS: 2”) security_auth       [1](javascri trampoline pt:void(0); “ * BUILD SUCCEE DED ”) security_cert       [1](javascri ificates pt:void(0); “ * BUILD SUCCEE DED ”) security_cert       [1](javascri tool pt:void(0); “ * BUILD SUCCEE DED ”) security_crlr       [1](javascri efresh pt:void(0); “ * BUILD SUCCEE DED ”) security_dotm       [1](javascript ac_tp :void(0); “ BUILD FAILED * ”) security_ocsp       [1](javascript d :void(0); “ BUILD FAILED * ”) security_syst       [1](javascript emkeychain :void(0); “ BUILD FAILED * ”) securityd       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) shell_cmds       [1](javascript :void(0); “EXI T STATUS: 2”) smb       [1](javascript :void(0); “ BUILD FAILED * ”) srm       [1](javascript :void(0); “EXI T STATUS: 2”) subversion       [1](javascript :void(0); “EXI T STATUS: 2”) sudo       [1](javascript :void(0); “ BUILD FAILED * *”) svk       swig       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) syslog       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) system_cmds       [1](javascript :void(0); “EXI T STATUS: 2”) system_config       [1](javascript :void(0); “EXI T STATUS: 2”) tcl       [1](javascript :void(0); “EXI T STATUS: 2”) tcp_wrappers       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) tcpdump       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) tcsh       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) texi2html       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) texinfo       [1](javascript :void(0); “EXI T STATUS: 2”) text_cmds       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) tidy       [1](javascript :void(0); “EXI T STATUS: 2”) top       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) update_dyld_       [1](javascri shared_cache pt:void(0); “ * BUILD SUCCEE DED ”) usertemplate       [1](javascript :void(0); “EXI T STATUS: 2”) uucp       [1](javascript :void(0); “EXI T STATUS: 2”) vim       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) webdavfs       [1](javascript :void(0); “ BUILD FAILED * *”) wxWidgets       [1](javascript :void(0); “EXI T STATUS: 2”) xar       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) xelf       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) xnu       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) xnu_debug       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) zip       [1](javascript :void(0); “EXI T STATUS: 2”) zlib       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) zsh       [1](javascript :void(0); “EXI T STATUS: 2”)

129 / 347 successfully built. 345 / 347 sources available (and usable). 344 / 347 binaryroots available. 10B504 status

Without providing any fixes for the projects which do not build on the first pass, the second pass reveals no dependency issue.

PROJECT BIN SRC PAK PASSES Apple16X50Seri       [1](javascript al :void(0); “** BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleAPIC       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleDisplays       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) AppleFileSyste       [1](javascript mDriver :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleHWSensor       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleIntelPIIX       [1](javascript ATA :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleKeyswitch       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleRAID       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleRTL8139Et       [1](javascript hernet :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleSMBIOS       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleTalk       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) AppleUSBAudio       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleUSBCDCDri       [1](javascript ver :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) AppleUSBIrDA       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) BerkeleyDB       BootCache       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) CF       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) CFOpenDirector       [1](javascript y :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) CPAN       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) CPANInternal       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) CarbonHeaders       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ChatServer       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) Chess       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) CommonCrypto       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) CoreOSMakefile       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) CrackLib       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Csu       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) CyrusIMAP       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) DSPasswordServ       [1](javascript erFramework :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) DSPasswordServ       [1](javascript erPlugin :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) DSTools       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) DirectoryServi       [1](javascript ce :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) DirectoryServi       [1](javascript ceDaemon :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) DirectoryServi       [1](javascript ceMIG :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) DiskArbitratio       [1](javascript n :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) FastCGI       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ICU       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ICU_debug       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ICU_profile       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) IOACPIFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOATAFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOATAPIProtoco       [1](javascript lTransport :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOAudioFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOBDStorageFam       [1](javascript ily :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOCDStorageFam       [1](javascript ily :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IODVDStorageFa       [1](javascript mily :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFWDVComponen       [1](javascript ts :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFireWireAVC       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFireWireFami       [1](javascript ly :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFireWireIP       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFireWireSBP2       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOFireWireSeri       [1](javascript alBusProtocolT :void(0); “ ransport BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOGraphics       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOHIDFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOKitTools       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOKitUser       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IONetworkingFa       [1](javascript mily :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOPCIFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOSCSIParallel       [1](javascript Family :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOSerialFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOStorageFamil       [1](javascript y :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOUSBFamily       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) IOUSBMassStora       [1](javascript geClass :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) JavaScriptCore       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) JavaScriptGlue       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED ”) KerberosHelper       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “* BUILD FAI LED **”) LDAPFramework       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libc       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libc_debug       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libc_headers       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libc_man       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libc_profile       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libcpp_kext       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libinfo       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libm       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libmx       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) Libnotify       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Librpcsvc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Libsyscall       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Libsystem       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) Liby       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) MySQL       NFS       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) OpenAL       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) OpenBSM       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) OpenDirectory       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) OpenLDAP       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) OpenSSH       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) OpenSSL096       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) OpenSSL097       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) OpenSSL098       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) PowerManagemen       [1](javascript t :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) PyRSS2Gen       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) RubyCocoa       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) RubyGems       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) RubyOnRails       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) SQLite       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) SQLite_tcl       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Security       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) SecurityTokend       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) SecurityTool       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) SmartCardServi       *[1](javascri ces pt:void(0); “ * BUILD SUCCEE DED ”) SpamAssassin       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) SquirrelMail       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) SystemStubs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) TargetConfig       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) TargetConfig_       *[1](javascri headers pt:void(0); “ * BUILD SUCCEE DED ”) TimeZoneData       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Tokend       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) Twisted       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) UserNotificati       [1](javascri on pt:void(0); “ * BUILD SUCCEE DED ”) WebCore       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED *”) X11apps       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) X11fonts       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) X11libs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) X11misc       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) X11proto       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) X11server       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) adv_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) amavisd       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) apache       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apache_mod_b       [1](javascript onjour :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apache_mod_f       [1](javascript astcgi :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apache_mod_h       [1](javascript fs_apple :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apache_mod_p       [1](javascript erl :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apache_mod_p       [1](javascript hp :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) apr       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) architecture       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) autoconf       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) autofs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) automake       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) autozone       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) awk       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bash       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) basic_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bc       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) bind9       bison       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bison1       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) bless       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) bootp       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) bootstrap_cmd       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) bsdmake       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) bzip2       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cctools       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cctools_ofile       [1](javascript s :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cddafs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) clamav       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) configd       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) configd_execu       [1](javascript tables :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) configd_libSy       [1](javascript stem :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) configd_plugi       [1](javascript ns :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) copyfile       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cron       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) crontabs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cscope       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cups       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cups_libs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) curl       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cvs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) cxxfilt       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) developer_cmd       [1](javascri s pt:void(0); “ * BUILD SUCCEE DED ”) diffstat       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) diskdev_cmds       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) disklabel       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) distcc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) doc_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) dtrace       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) dyld       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) eap8021x       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) efax       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) emacs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) enscript       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) expat       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) fetchmail       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) file       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) file_cmds       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) files       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) flex       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) freeradius       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gcc       gcc_select       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) gdb       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) glibtool       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gm4       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gnudiff       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gnumake       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gnuserv       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) gnutar       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gnuzip       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gperf       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gpt       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) graphviz       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) grep       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) groff       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) gssd       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) headerdoc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) hfs       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) iodbc       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ipsec       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) ipv6configurat       [1](javascri ion pt:void(0); “ * BUILD SUCCEE DED ”) kext_tools       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) keymgr       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) ksh       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) launchd       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) launchd_libs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) ld64       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) less       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libdispatch       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) libdyld       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libedit       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libffi       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libfs       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libgcc       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libiconv       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libkxld       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libmd       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libpcap       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libresolv       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascript gent :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) libsecurity_a       *[1](javascri pple_csp pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_cspdl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_file_dl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_x509_cl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascri pple_x509_tp pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_a       [1](javascript sn1 :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_a       [1](javascript uthorization :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) libsecurity_c       [1](javascri dsa_client pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_plugin pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_utilities pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri dsa_utils pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascri heckpw pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_c       [1](javascript ms :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_c       [1](javascript odesigning :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_c       [1](javascri ssm pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_d       [1](javascript otmacdl :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_f       [1](javascri iledb pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_f       [1](javascript ilevault :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_k       [1](javascript eychain :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED *”) libsecurity_l       [1](javascri dap_dl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_m       [1](javascri anifest pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_m       [1](javascri ds pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_o       [1](javascript cspd :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_p       [1](javascri kcs12 pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_s       [1](javascri d_cspdl pt:void(0); “ * BUILD SUCCEE DED ”) libsecurity_s       [1](javascript mime :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_s       [1](javascript sl :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libsecurity_u       [1](javascri tilities pt:void(0); “ * BUILD SUCCEE DED ”) libsecurityd       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) libstdcxx       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libstdcxx_40       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libtelnet       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libutil       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) libxml2       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) libxslt       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) lsof       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) lukemftp       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) lukemftpd       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) mDNSResponder       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) mDNSResponderS       [1](javascript ystemLibraries :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) mail_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) mailman       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) man       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) misc_cmds       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) modemccl       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) msdosfs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) nano       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) nasm       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ncurses       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) neon       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) net_snmp       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) netcat       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) netinfo       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) network_cmds       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) notify       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ntfs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) ntp       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) objc4       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) openmpi       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) pam_modules       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) passwordserver       [1](javascri _sasl pt:void(0); “ * BUILD SUCCEE DED ”) passwordserver       [1](javascript _saslextra :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) passwordserver       [1](javascript _saslkerberos :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED *”) patch_cmds       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) pb_makefiles       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) pdisk       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) perl       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) portmap       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) postfix       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ppp       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) procmail       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) pyOpenSSL       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) pyobjc       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) python       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) python23       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) python_dateut       [1](javascript il :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) python_module       [1](javascript s :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) rcs       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) remote_cmds       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) removefile       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) rsync       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ruby       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ruby_dnssd       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) ruby_libxml       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) samba       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) screen       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) security_auth       [1](javascri trampoline pt:void(0); “ * BUILD SUCCEE DED ”) security_cert       [1](javascri ificates pt:void(0); “ * BUILD SUCCEE DED ”) security_cert       [1](javascri tool pt:void(0); “ * BUILD SUCCEE DED ”) security_crlr       [1](javascri efresh pt:void(0); “ * BUILD SUCCEE DED ”) security_dotm       [1](javascript ac_tp :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) security_ocsp       [1](javascript d :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) security_syst       [1](javascript emkeychain :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) securityd       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) shell_cmds       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) smb       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED ”) srm       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) subversion       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) sudo       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) svk       swig       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) syslog       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) system_cmds       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) system_config       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) tcl       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) tcp_wrappers       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) tcpdump       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) tcsh       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) texi2html       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) texinfo       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) text_cmds       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) tidy       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) top       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) update_dyld_       [1](javascri shared_cache pt:void(0); “ * BUILD SUCCEE DED ”) usertemplate       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) uucp       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) vim       [1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) webdavfs       [1](javascript :void(0); “ BUILD FAILED * ”) [2](javas cript:void(0); “ BUILD FAI LED **”) wxWidgets       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) xar       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) xelf       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) xnu       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) xnu_debug       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) zip       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”) zlib       *[1](javascri pt:void(0); “ * BUILD SUCCEE DED ”) zsh       [1](javascript :void(0); “EXI T STATUS: 2”)  [2](javascrip t:void(0); “EX IT STATUS: 2”)

Darwin 9

… 9L30 status

not tested. 9J61 status

Principle