Rich Ramos <smartmon-sup@...> writes:
> Just a few things on the Darwin port:
> 1) The panther APIs that you are relying on, do you know if they will
> work with third party PCI to ATA cards or only ATA drivers written by
I'd expect that they'll work with most third-party drivers, since they
would have to go to special effort to make them not work (the driver
that talks to the hardware is different to the driver that implements
the calls); but third-party driver writers often do strange things.
> The reason I ask...
> I have an older power mac G4 and the built-in ATA adapter doesn't have
> the 48bit support and I have a 250G hard drive. So I went out and
> bought a card from SIIG called an "UltraATA 133/100 Pro" to be able to
> address the entire drive. However, this card does something really
> screwy. It does some kind of protocol conversion and the device shows
> up on the host system as a SCSI device! I sent an email to SIIG about
> this behavior and their response was:
> "Our card uses the SCSI technology.
> That is why it is shown up as SCSI.
> This is ferfectly fine."
> I'm now wondering if that was really a type-o :-)
> Anyway, before I go out and hunt down another PCI to ATA card, I'm
> wondering if there is any known limitations I should know about for
> third party cards.
I don't know of any limitations, but I don't know of any successes,
either. Let us know how it goes...
> 2) This must be me not knowing how to use cvs properly, but I want to
> know what I did wrong for next time...
> A few weeks ago I downloaded for the first time the code out of cvs so
> I could build on darwin/Mac OS X. This was prior to the startup
> script changes. The other day I saw the info about the new startup
> scripts so I tried the "cvs update" command. Everything in the /sm5
> directory got updated, however I didn't get the sm5/os_darwin
> directory (or anything inside obviously). I couldn't figure out how
> to get cvs to update that. I had to do a completely new checkout of
> the source before I get that directory and it's contents. What did I
> do wrong?
You want 'cvs update -P'.
> 3) Finally, with the current startup script setup, the files only seem
> to get copied to the directory:
> However nothing go put into:
> If the scripts aren't there, they won't startup at boot up time will
> they? They didn't on my system.
No, it won't work if the scripts don't go to the right place. You need
to use the '--with-initscriptdir=/Library/StartupItems' option to configure.