Taking the NeXT step (mach kernel upgrades)

[neozeed]

You can create a 'manifest file' from the extracted tarballs from something like this where you extracted them (if using a bourne shell):

Code Select Expand

for i in $(ls -1) ; do echo "dir $i all" >> buildmanifest.txt
and using:

Code Select Expand

darwin-buildall buildmanifest.txt /path/to/debrepo /path/to/debdestination
Will build all the packages it can, and automatically deleting the temp files under /tmp/roots/ on a successful build.
The third field of the manifest is the same as the --target flag for darwin-buildpackage, so it can be any of all|headers|objs|local

There's a Manifest file on the Darwin 0.3 disc (Darwin OS Install CD/Binary Packages/Manifest ... it has mac line endings, so you'll have to change those to unix line endings first before using it with buildall, and change ^cvs to dir) that I believe shows how they built the deb packages for the release

This is what I needed to know.

Sigh, pitty the forum has been down for so long.

I need to do a full build.

[NCommander]

Yeash, this isn't dead. I actually have all my test VMs from when we did this and I think I have most of my notes as well. I'm not super active here and honestly RL took a serious dump on me about the time I dropped off but I'm around to offer big brain support. a PM works best but I'll set an alert on this thread for the future.

[evolver56k]

I have had a github repo set up for this for a while now, but recently made it public. I've gotten the entire Darwin 0.3 sources to build fat binaries on both intel and ppc installs, and have a binary tarball from an early build run as a release, which can be used for the binary repo during building.

I've also added the NE2K and VMXNet drivers to the package manifest, so they'll get built (i386 only) during the darwin-buildall run.

https://github.com/evolver56k/Darwin-0.3

The way I use the github repo, is to have it checked out on my modern machine, and have an NFS export of the local repo mounted on the darwin machine, either i386 via VMware, or a B&W G3 running ppc native.

With the repo on an NFS share, I can use modern editors to muck with the packages, and it's instantly reflected on the darwin build box to attempt another build.

My goal is to get other modern packages into the repo like openssh, openssl, etc., all being built with the darwinbuild system natively.

[neozeed]

I have had a github repo set up for this for a while now, but recently made it public. I've gotten the entire Darwin 0.3 sources to build fat binaries on both intel and ppc installs, and have a binary tarball from an early build run as a release, which can be used for the binary repo during building.

awesome job!

[texta]

Hi guys,

Sorry to bump an old post, I've been very eager to see if I can work on the USB stack for MOSX Server 1.2v3, and I was very excited to see a git repo for something that's at least somewhat close to the mach_kernel!

Long thread, I'm having a bit of trouble working out where it ended up. Were you guys able to compile a kernel from the Darwin 0.3 source that ran in multi-user and "just worked" (ran the loginwindow, with drivers, networking etc.?)

Cheers, keen to keep this train going in 2022.

[evolver56k]

It's been a good while since I've toyed with this but yeah, everything should "work". There's a couple of caveats though that I have found in my testing:

- The kernel source is roughly equivalent to the kernel in MOSX 1.0, so don't expect it to work any magic on MOSX 1.2 or 1.2v3.
- If you're running RDR2 on i386 or ppc, or MOSX 1.0 on ppc, you can't use System.framework built from these sources, as they're missing some libraries like java that'll break everything.

If you're running Darwin 0.3 though, these should compile fine on either arch.

[gtnicol]

Has anyone played around with OpenDarwin? I still have the source tree and an ISO from it... though I never hacked on it much.