Re: How to build a new ISO 9660 FS and test it
Re: How to build a new ISO 9660 FS and test it
- Subject: Re: How to build a new ISO 9660 FS and test it
- From: Markus Hitter <email@hidden>
- Date: Tue, 14 Nov 2006 19:55:56 +0100
Am 14.11.2006 um 15:13 schrieb Thomas Tempelmann:
I'd now like to bring OS X's old ISO 9660 driver up to date,
with the hope that Apple will incorporate the improvements into OS X.
Even if Apple doesn't, you'd be able to replace their driver on the
fly by providing a version with a higher number. Ryan Rempel did this
for XPostFacto and IIRC, a speech of him describing his work is
floating around on the 'net.
1. All I need is to build the XNU sources, right?
Most/all of the drivers moved out into dedicated kexts, see /System/
Library/Extensions/..., so there's likely no need to change the
kernel at all. With some luck you can change the driver by unmounting
the volume and unloading the .kext, then doing the reverse for the
new driver.
Being successful here obviously needs some patience, googling and
Technical Note reading, as Apple's Darwin lists are full of
straightforward and confused questions, vague and valueable hints ;-)
2. I have some trouble building the kernel.
If you still want to build a kernel, download the sources, unpack
them, type "make". You'll need a few additional tools as you found
out already.
There's a way with even less typing, using darwinbuild, described at
Mac OS Forge, OpenDarwin's successor.
If you still experience trouble, please note wether you attempt to
build for ppc or i386, as both used different sources after the
launch of Intel Macs and until recently and differ in some
technologies, e.g. all this TPM stuff, as well.
Or is the [ISO driver] in the kernel not even the one OS X uses -
is there
another one that's loaded later?
There are several locations for drivers:
- The bootloader, alias BootX. This part is dumped as soon as the
kernel loads, AFAIK.
- OpenFirmware: only used on ppc and by BootX, so dumped early.
- EFI: initially similar to OpenFirmware on i386, but I've read
rumours about high performance driver sighted there, effectively
replacing OS drivers. Only unconfirmed rumours, though.
- The kernel it's self.
- Kernel Extensions (kexts). Find all the .kext files on your system,
examine their name for broad hints; their Info.plists for more
detailed hints.
Many drivers were moved out of the kernel and some of them into kexts
between public beta and Mac OS X 10.0.
Undefined symbols:
_kld_load_basefile_from_memory
_kld_set_link_options
Maybe this ist the reason why Mac OS Forge announced Darwin 8.8.1
rarther than 8.8?
I tried to sign up with that site, even received a
login, but my login is not accepted. Is that normal?
My subscription went flawlessly; pinging one of the administrators
there might help.
4. Lastly, if I should succeed, what's the chances that Apple
incorporates the improvements?
As the current driver works sufficiently in Apple's opinion, I
wouldn't expect them to invest efforts here.
How would I go about that?
Make the thing public, similar to DarwinPorts, Unsanities Haxies,
etc. IMHO the best one can do.
I know of others who files related bug reports years ago and
nothing ever changed with the iso 9660 file system.
They even dropped multisession support after 10.1.5.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden