Linux Kits - Firebird

Scroll down the SourceForge showfiles display until you find the files shown in Figure.

Linux kits on SourceForge

Linux kits on SourceForge

Where practicable, executable installers are provided. Both RPM installers and tarballs are available. If your Linux distribution supports RPM installers, make that your choice. It will create the directories and install everything required, set a password for the SYSDBA user, and start your chosen server. Release names of the installers are as follows:

  • Firebird 1.5: FirebirdCS- (Classic) and FirebirdSS- (Superserver)
  • Firebird 1.03: FirebirdCS- (Classic) and FirebirdSS- (Superserver)

Consult the appropriate platform documentation for instructions about using Red Hat Package Manager. In most distributions you will have the choice of running the RPM installer from a command shell or through a GUI interface.

Compressed Files (Tarballs)

For Linux distributions that cannot process rpm packages, and for the various UNIX flavors, use the tarball kit as it will give the experienced Linux hand more control over the installation process. The appropriate decompression utility will be needed on your server for decompressing and “untarring” the kit into the filesystem. You will find detailed instructions in the release notes, README files, and distribution notes. Skilled users can also study and adjust the installation scripts to make it work on the less common Linuxen.


In all cases, read any distributed text files, along with any specific topics in the official release notes that pertain to the version of Firebird that you are going to install. There may be significant variations between POSIX -compliant OS distributions and releases, especially the open source ones. Where possible, the build engineers for each Firebird version attempt to document in release notes any known issues with various kernel versions and distributions.

NPTL Implementation on Higher Linuxen

The new Native POSIX Thread Library (NPTL) in Red Hat 9 (and possibly more recent Linux distributions) will cause problems for Superserver and locally compiled programs, including the utilities. gbak is reported to throw a “broken pipe” error. To fix this, follow these steps:

  • Take care of the server instance. In /etc/init.d/firebird,
  • You need to have the environment variable set up within the local environment as well, so add the following to /etc/profile, to ensure every user picks it up for the command line utilities. After



    On the following line, export it:


All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

Firebird Topics