In the case of AIX, you'll likely need to use a recent version.

With OpenServer 1.x you may need to use the configure option:
--with-LIBTIFF="-ltiff -ljpeg -lz -lm"

On Silicon Graphics Indigo and Indy machines you can not use a Macintosh modem cable to connect your modem to the DIN-8 connector on the back of your host. A Macintosh cable uses a special wiring pattern to pass the RTS and CTS signals between the host and modem. This wiring is not compatible with the wiring used on SGI machines. While it may appear that the the modem and cable work, hardware flow control will not function properly and data will eventually be lost. Consult the serial(7) manual page for an explanation of how to wire up modem cables.

The tty device that is used must reflect whether hardware or software flow control is to be used. Under IRIX, modem devices (i.e. those that monitor DCD) come in two flavors: ttyf* devices support RTS/CTS flow control while ttym* devices support XON/XOFF flow control. If you want to use hardware flow control to communicate with your modem you should use a ttyf* device, otherwise use a ttym* device. If you fail to use the correct device you may still get the correct flow control (because later versions of IRIX actually permit flow control to be switched irrespective of the device used), but you are likely to collide with other modem users such as cu, uucp, ppp, and slip that still use the old-style device names (so UUCP lock files may be created for a different name than the one HylaFAX is using).

Note!

USR modems work under IRIX 5.x only when patch 475 or a successor is installed and ClocalAsRoot is set to Yes in the modem configuration file.

Versions of IRIX prior to 6.2 have a bug in the device driver for the on-board serial ports on several systems that causes RTS/CTS flow control to be turned off as a side effect of setting the CLOCAL flag on the associated tty device. Patch 475 (``RTS/CTS flow control busted when CLOCAL is set'') and its successors correct this problem and must be installed to use HylaFAX with RTS/CTS flow control (install the appropriate successor to patch 475). Also, when this patch is installed the ClocalAsRoot modem configuration parameter must be set to Yes for proper operation (see config(4F) for a detailed explanation of what this parameter does). If you do not have the appropriate patch installed on your system then you will either see flow control-related problems when transmitting facsimile or possibly some other problems related to modems dropping DCD when carrier is lost.

Note!

The DPS-based PostScript imager program distributed with HylaFAX is available only in COFF format. Because IRIX 6.2 does not support COFF executables this program cannot be used with HylaFAX. A Ghostscript-based RIP should be used under IRIX 6.2.

The font metric files required by client applications are contained in the dps_eoe.sw.dpsfonts image that is part of the standard IRIX distribution.

Mac OS X Installation Notes

1) Use HylaFAX 4.1.2 or newer.
2) Create a user and group "uucp" with a home directory of /var/spool/uucp/.
3) Create a user "bin".
4) Create a user "fax" which belongs to the "uucp" group.
5) Use chpass to create the /etc/passwd listing for "uucp". I.e.:

	chpass -a "uucp:*:10:66::0:0:uucp:/var/spool/uucp:"

where "10" and "66" are the appropriate user and group numeric values.
6) execute ranlib /usr/local/lib/libtiff.a
7) Build and install the source as normally instructed for other systems. If using a HylaFAX version prior to 4.2.0, make sure to untar the source onto a UFS (not HFS) disk.
8) After running faxaddmodem you may want to check file ownerships in /var/spool/hylafax/ and /var/spool/hylafax/etc/ if you guessed at the uucp user and group numeric values.
9) Create the required DSP directory for DEVFS mounting:

	mkdir ~fax/dev

10) Do this:

	mkdir /Library/StartupItems/HylaFAX
	chown root.admin /Library/StartupItems/HylaFAX
	chmod 775 /Library/StartupItems/HylaFAX

11) Make the file /Library/StartupItems/HylaFAX/HylaFAX with root:admin ownership and access mode 775 containing this text:

	#!/bin/sh
	. /etc/rc.common
	ConsoleMessage "Starting HylaFAX server processes"
	/sbin/mount -t devfs ~fax/dev /var/spool/hylafax/dev
	/usr/local/sbin/hylafax start
	ConsoleMessage "HylaFAX server processes started"

12) Make the file /Library/StartupItems/HylaFAX/StartupParameters.plist with root:admin ownership and access mode 775 containing this text:

	{
	  Description     = "HylaFAX daemon";
	  Provides        = ("HylaFAX Server");
	  OrderPreference = "Last";
	  Messages =
	  {
	    start = "Starting HylaFAX Server";
	    stop  = "Stopping HylaFAX Server";
	  };
	}

13) Edit /etc/ttys and add a line like:

	tty.usbmodem091 "/usr/local/sbin/faxgetty"      unknown on secure

where "tty.usbmodem091" is the device name of your modem.
14) Reboot the computer or run the above HylaFAX shell script and restart init.

Many thanks to Guy Loucks and the Apple Developer Connection for their exhaustive work on this.

Note that some unresolved communication (timeout) problems have been experienced when using the AppleSCCModem (tty.modem) driver with xonxoff flow control. More success has been had using rtscts flow control or USB modems.

OpenBSD Installation Notes

Use a recent HylaFAX version.

Due to a problem in the 4.1beta3 source code, SCO 5 users will be unable to compile it without modification.

The standard SCO serial I/O driver (SIO) does nothing with modem control lines if CLOCAL is set on the tty device. The usual workaround is to use the FAS driver instead.

Slackware Linux does not use a SysV init style, but rather follows the "traditional" BSD type. However, HylaFAX itself uses SysV init format. If you would like to configure HylaFAX to run in some runlevels but not in others, you will need to indicate this appropriately with the lines added to /etc/inittab, and you should not edit /etc/rc.d/rc.local as explained above, but instead, directories should be made in /etc/rc.d/ for every runlevel in the format of 'rc?.d' where ? is the runlevel number, and a symlink to /usr/local/sbin/hylafax should be made in each of them.

Before configure, you may need to execute:
export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
ln -s /usr/local/lib/gcc-lib/ /usr/local/lib/gcc-lib/i386-pc-solaris2.7/2.95...

Thanks goes to Nate Sanders darkskull@damnation.net and Christoph Scheeder christoph.scheeder@scheeder.de for their work on this.

• Versions of Solaris prior to 2.5 require a patch to correct the handling of RTS/CTS flow control with serial ports built around the Zilog ZS8530 chip.
• Some versions of Solaris (2.3 is known to do this) silently truncate or discard syslog messages longer than about 120 characters.
• Use the /dev/cua/* devices and not the /dev/term/* devices.
• When using ttymon to service inbound data calls set the GettyArgs parameter to something like the following:
  GettyArgs: "-g -h -d /dev/cua/a -l 38400 -m ldterm,ttcompat"
• Note: Be certain you are not running a ttymon with sac when using HylaFAX. Disable all ports that are to be used by HylaFAX with admintool or pmadm(1m).

  Also search the mailing archives and review:
  http://www.hylafax.org/archive/2000-08/msg00498.html
  http://www.hylafax.org/archive/2000-08/msg00479.html
  http://www.hylafax.org/archive/2000-08/msg00617.html
  and their threads.

Versions of SunOS prior to 4.1.4 require a patch to correct the handling of RTS/CTS flow control with serial ports built around the Zilog ZS8530 chip. These patches are available at:
• ftp://sunsolve1.sun.com/pub/patches/100513-05.tar.Z for SunOS 4.1.[123], and
• ftp://sunsolve1.sun.com/pub/patches/101621-04.tar.Z for SunOS 4.1.3_U1.
  (choose the one appropriate to the system you are running).

SVR4 Installation Notes

The following GettyArgs: configuration parameter is suitable for many SVR4-based systems:
GettyArgs: "-g -h -t 60 -l ff_%s"
Be sure entries for different baud rates are defined in the /etc/ttydefs file.

Compaq Tru64 Installation Notes

• See: http://www.hylafax.org/archive/2001-04/msg00457.html

Ultrix Installation Notes

[Ed: Thanks to Albert DeKnuydt for the following advice.]

• As Ultrix has a brain-damaged shell, the command /bin/sh ./configure does not work properly. You should use instead /bin/sh5 < configure .
• The archaic syslog facility should be upgraded from ftp://gatekeeper.dec.com/pub/DEC/jtkohl-syslog-complete.tar.Z.
• Ultrix lacks some functions in the c library, and needs to linked to libiberty.a as well. After configuration, change the line in the defs file from

  MACHDEPLIBS = -lm -lmalloc

  to

  MACHDEPLIBS = -lm -lmalloc -liberty

  Libiberty is available with the gcc compiler.
• Ultrix header files violate ANSI rules so you have to tell gcc 2.95 (and later) to allow this with the added line in the defs file :

  LC++OPTS = -fpermissive

• Interrupt handling is out of date, and cannot claim to be compatible with SV_INTERRUPT. Add the following line to port.h after configuration :

  #undef SV_INTERRUPT

• Most (all?) DEC mips machines do not completely support serial port speeds above 19200.