This section describes problems that have occured while porting the package to various operating systems.
|• OS-Generic:||Problems and mistakes common to all operating systems|
|• SCO-322:||SCO Unix 3.2.2 (ODT 1.0 / 1.1)|
|• SCO-324:||SCO Unix 3.2v4 (ODT 2.0 / 3.0)|
|• SVR4:||SVR4 Unix|
|• SVR42:||SVR4.2 Unix - Onsite, UnixWare, ...|
|• BSD:||BSD-like flavours of Unix|
|• AIX:||IBM’s AIX Operating System|
|• SunOS:||SunOS 4.1.1 and up|
|• Solaris2:||SunSoft Solaris 2.3 and up|
|• 3b1:||AT&T 3b1|
|• HP-UX:||The HP-UX operating system|
|• NEXTSTEP:||The NEXTSTEP operating system|
|• Darwin:||Apple’s MacOS X / Darwin operating system|
If your system is not in the list, that doesn’t mean it won’t work. It just means that I didn’t get a report (or a port) for that system yet.
mgetty+sendfax should work on most unixoid operating systems, as long as
SysV termio or
POSIX termios call for tty
BSD sgtty support isn’t finished yet.
For best results, your system should have
poll(S), but if both functions are not available or don’t work on
poll(S) is known to do this on SVR3.1 and earlier), you can
use a kludge,
Besides that, you’ll need some fiddling with the header files to get all defines and prototypes right.
Further, you’ll have to check tio.c, function
tio_set_flow_control(), whether the way hardware flow control is
activated works on your system. Most likely, it won’t — that’s one of the
major portability problems. If you change something and get it to work,
please send me patches. (You’re welcome to do so anyway).