compat_ultrix(8) [netbsd man page]
COMPAT_ULTRIX(8) BSD System Manager's Manual COMPAT_ULTRIX(8) NAME
compat_ultrix -- setup procedure for ULTRIX compatibility on MIPS and VAX architectures DESCRIPTION
NetBSD/mips and NetBSD/vax architectures can run Risc ULTRIX and VAX ULTRIX executables, respectively. However, you have to worry about the legal issues of ensuring that you have a right to use any ULTRIX binaries on your machine. Most executables will work. The exceptions include programs that use proprietary, ULTRIX-specific features (LAT, CI support, DECnet support) and various system calls, ioctl()'s, or ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or buggy (e.g. ULTRIX NIS). All ULTRIX executables are static, so no shared libraries are required for ULTRIX compatibility. However, ULTRIX is based on a 4.3BSD alpha release. ULTRIX commands and libraries are often much older than their NetBSD or even SunOS 4.x equivalents, and may require incompatible configuration files. SYSTEM CONFIGURATION FILES
Set up resolv.conf and svc.conf as below: # mkdir -p /emul/ultrix/etc # cd /emul/ultrix/etc # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf # cp -p /usr/share/examples/emul/ultrix/etc/* ./ /etc/resolv.conf The ULTRIX resolver library only understands domain and nameserver lines in resolv.conf(5). You should create a copy of /etc/resolv.conf containing only those commands and put it in /emul/ultrix/etc/resolv.conf. Note that the domain search order used by ULTRIX executables may not be the same as native binaries; there is no good way around this. /etc/svc.conf ULTRIX uses /etc/svc.conf to select an ordered search of NIS, Hesiod, or local flat-file mappings. You should create an /emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) lookups for all ULTRIX name services. SEE ALSO
resolv.conf(5) BUGS
RISC ULTRIX NIS (YP) is known to not work. The ULTRIX NIS libraries have a consistent endian-ness bug. ULTRIX NIS client will not inter- operate with the NetBSD ypbind(8) process. The only workaround is to use /etc/svc.conf to disable NIS (YP). The ndbm hashed-password file used by ULTRIX are incompatible with the db hashed-password file used by NetBSD. There is no good solution for this. NIS would be a good one, if ULTRIX NIS worked. The API used by Xservers to talk to the kernel is currently compatible with ULTRIX 4.1. An implementation of the ULTRIX 4.2 Xws interface (used by X11R6) is in progress. A complete list of things which fail to work in ULTRIX compatibility mode should be added here. BSD
January 16, 1999 BSD
Check Out this Related Man Page
mh-alias(5mh) mh-alias(5mh) Name mh-alias - alias file for MH message system Description Aliasing allows you to send mail to a person or group of persons without typing their complete mail address. Both your MH personal alias file and the system alias file for mail delivery, process aliases in the same way. You can specify the name of your personal alias file in your A line of the alias file can have the following formats: alias : address-group alias ; address-group < alias-file The first line of the example is the standard format. The alias appears at the start of the line, followed by a colon, followed by the address or addresses that it represents. If the alias is terminated with a semicolon (;) instead of a colon (:), the mail system outputs both the alias and the address-list in the correct format. If the line starts with a <, the file named after the < is read for more alias definitions. The reading is done recursively, so a < can occur in the beginning of an alias file with the expected results. Addresses can be expressed in the following formats: alias: address1, address2, address3, ... alias: <file alias: =ULTRIX-group alias: +ULTRIX-group alias: * Addresses are normally given in a list, separated by a comma and one or more spaces. If the list goes over one line, you can create a con- tinuation line by placing a back-slash () immediately before the new-line character. If the address-group begins with a <, the file named after the < is read and its contents added to the address list for the alias. If the address-group starts with an =, then the file is consulted for the ULTRIX-group named after the =. Each login name occurring as a member of the group is added to the address list for the alias. If the address-group starts with a +, then the file is consulted to determine the group-id of the ULTRIX-group named after the +. Each login name occurring in the file whose group-id is indicated by this group is added to the address list for the alias. If the address-group is simply *, then the file is consulted and all login names with a user-id greater than a given number (usually 200) are added to the address list for the alias. Aliases are resolved at posting time in the following way. A list of all the addresses from the message is built and duplicate addresses are eliminated. If the message originated on the local host, then alias resolution is performed for those addresses in the message that have no host specified. For each line in the alias file, aliases are compared against all of the existing addresses. If there is a match, the matched alias is removed from the address list, and each new address in the address-group is added to the address list, if it is not already on the list. The alias itself is not usually output; the address-group that the alias maps to is output instead. However, if the alias is terminated with a semicolon (;) instead of a colon (:), both the alias and the address are output in the correct format. This makes replies possible, because in MH aliases and personal aliases are unknown to the mail transport system. MH alias files are expanded into the headers of messages posted. This aliasing occurs first, at posting time, without the knowledge of the message transport system. In contrast, once the message transport system is given a message to deliver to a list of addresses, for each address that appears to be local, a system-wide alias file is consulted. These aliases are not expanded into the headers of messages delivered. An alias file must not reference itself directly, or indirectly through another alias file, using the <file construct. Using Aliasing To use aliasing in MH, you need to set up a personal alias file. It can have any name, but it is usually called and is usually located in your Mail directory. To set up the file, you need to perform the following steps. First, add the following line to your Aliasfile: aliases If you have chosen a different name for your file, you should use this instead of If your file is in a directory other than your Mail directory, you must supply the full pathname. Next, create the file in your Mail directory. You can now start to add aliases to your file. Examples This section gives an example of an alias file, followed by an explanation of the entries: sgroup: fred, fear, freida fred: frated@UCI ULTRIX-committee: <ultrix.aliases staff: =staff wheels: +wheel everyone: * On the first line of the example, sgroup is defined as an alias for the three names frated@UCI, fear, and freida. On the second line of the example, fred is defined as an alias for frated@UCI. Next, the definition of ULTRIX-committee is given by reading the file ultrix.aliases in your Mail directory. The alias staff is defined as all users who are listed as members of the group staff in the file. The alias wheels is defined as all users whose group-id in is equal to the group wheel. Finally, the alias everyone is defined as all users with a user-id in greater than 200. Files System alias file. Your user profile. See Also ali(1mh), send(1mh), whom(1mh), group(5), passwd(5), mh_profile(5mh), mtstailor(5mh), conflict(8mh), post(8mh) mh-alias(5mh)