Unixism
operating system, jargon
A piece of code or a coding technique that depends on the protected multitasking environment with relatively low process-spawn overhead that exists on virtual-memory Unix systems.
Common Unixisms include: gratuitous use of “fork”; the assumption that certain undocumented but well-known features of Unix libraries such as “stdio” are supported elsewhere; reliance on obscure side-effects of system calls (use of “sleep” with a 0 argument to tell the scheduler that you’re willing to give up your time-slice, for example); the assumption that freshly allocated memory is zeroed; and the assumption that fragmentation problems won’t arise from never freeing memory.
Compare vaxocentrism. See also New Jersey.
[Jargon File]
(1995-02-27)
Read Also:
- Unix man page
Unix manual page
- Unix manual page
operating system (Or “man page”) A part of Unix’s extensive on-line documentation. To read a manual page from the Unix command line, type: man [-s ] e.g. “man ftp” (the section number can usually be omitted). Pages are traditionally referred to using the notation “page(section)”, e.g. ftp(1). Under SunOS (which is fairly typical), Section 1 […]
- Unix system v
System V
- Unix to unix copy
networking, messaging (uucp) A Unix utility program and protocol that allows one Unix system to send files to another via a serial line which may be a cable going directly from one machine’s serial port to another’s or may involve a modem at each end of a telephone line. Software is also available to allow […]
- Unixware
operating system Novell’s implementation of Unix System 5 heavily based on Release 4.2 but with enhancements and new bundled products. In 1993 Novell acquired Unix Systems Laboratories from AT&T along with the Unix trademark. UnixWare was the result of Novell’s efforts to make Unix interoperable with Novell NetWare. In 1995 Novell sold UnixWare and the […]