Linked by Thom Holwerda on Sun 26th Feb 2006 14:15 UTC, submitted by subterrific
Apple had their pick of kernels when transitioning from OS 9 to OS X, and they chose to create their own kernel based on Mach 3.0. Was that really the best decision or did Apple make a huge mistake? At the time Linux was gaining support and developing rapidly, while development on Mach had pretty much ended two years earlier. This article makes a case for Apple using the Linux kernel in a future version of the Mac OS.
Thread beginning with comment 99532
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: What is this facination with source code?
by rayiner on Mon 27th Feb 2006 04:40
in reply to "What is this facination with source code?"
Member since:2005-07-06
Did you just grep the source for "unfixable"? Because the line in question isn't a problem to be fixed, per se. Resource.c handles allocations of chunks of I/O port space to clients (mostly drivers), and the function in question just enforces the following semantics:
1) If the client requests a new resource range that is fully a subset of an existing one, the new resource range becomes the child of the existing one.
2) If some existing resource ranges are fully subsets of the new one, then they become children of the new one.
3) It is an error to define a new resource range that only partially overlaps an existing one.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-11
Come on now, How many of you can tell me what does line 340 of file /usr/src/linux/kernel/resource.c do?
The comment says:
/* Partial overlap? Bad, and unfixable */
Can any of you fix this problem? I can't even though I'm a PhD in computer science.
Edited 2006-02-27 03:37