Thanks for the feedback, John.

> You need to be in the same directory as isc4.gdb
> (/Library/Frameworks/Firebird.framework/Versions/A/Resources/
> English.lproj/var) for gsec to find it.

Yes that worked. Thanks!

But... Has this always been the case? I used 1.0.0 up till about June, then the project was killed. Just trying to get back into FB for a new one. I have no recollection or notes about having to dig for the isc4.gdb. I thought that it "just worked". Maybe my brain is fried tonight.

> > Poking around, I find that my inetd.conf is now ZERO length.
> > Timestamp matches the installer run. This is bad.
>
> You are right, that is bad. Did you have one to begin with? Either
> way I can send you mine (all the entries are commented out, BTW).

Yes I did. See my other message for the precise bug that caused this. I ended up replacing it with a copy from my other machine. The plain darwin install script doesn't have the same problem.

> > I also note that I have no /Library/StartupItems folder. Dunno if one
> > was there before or not.
>
> That is how the OS ships, AFIAK.

When I looked at the script, it appears that the Semaphores startup is no longer needed with Jaguar. I didn't see this noted in the readmes, so I was troubled to find it not there (since I knew it was installed for 1.0.0). But apparently all is well.

Oh, I seem to be ok after running the Darwin install script manually. I'll note that the 1.0 Release notes file doesn't say that you need to use SUDO when running it. (Just having admin permissions isn't enough, you have to run it as root.) I also get a couple funky errors:

[firebird_install]$ sudo ./install
ln: /Library/Frameworks/Firebird.framework/Firebird: File exists
cat: /var/run/inetd.conf: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec]
[firebird_install]$ which kill
/bin/kill

Thanks
.T.