Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

talk(1) 						      General Commands Manual							   talk(1)

Name
       talk, otalk - talk to another user

Syntax
       talk person [ttyname]

       otalk person [ttyname]

Description
       The command is a visual communication program which copies lines from your terminal to that of another user.

       If  you	wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
       host, then person is of the form :
       host!user
	or
       host.user
	or
       host:user
	or
       user@host
       The form user@host is perhaps preferred.

       If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.

       When first called, it sends the message
       Message from TalkDaemon@his_machine...
       talk: connection requested by your_name@your_machine.
       talk: respond with: talk your_name@your_machine

       to the user you wish to talk to. At this point, the recipient of the message should reply by typing
       talk  your_name@your_machine

       It doesn't matter from which machine the recipient replies, as long as his login-name is the same.  Once communication is established,  the
       two parties may type simultaneously, with their output appearing in separate windows.  Typing Ctrl-L will cause the screen to be reprinted,
       while your erase, kill, and word kill characters will work in talk as normal.  To exit, just type your interrupt character; then moves  the
       cursor to the bottom of the screen and restores the terminal.

       Permission to talk may be denied or granted by use of the mesg command.	At the outset talking is allowed.  Certain commands, in particular
       and disallow messages in order to prevent messy output.

       In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session  with
       the  command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
       gram with the command. See the Restrictions section.

Examples
       The following example demonstrates how to use the command.  In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates  a
       session with user2, whose system (system2) is running ULTRIX V3.0.  User1 types the following:
       system1> talk user2@system2
       The following message appears on the screen of user2:
       Message from Talk_Daemon@system2 at 12:37 ...
       talk: connection requested by user1@system1.
       talk: respond with:  otalk user1@system1
       To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
       system2> otalk user1@system1

Restrictions
       The  version  of  released  with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
       ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3  BSD  or  versions	of
       UNIX based on 4.3 BSD.

       The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
       followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
       which has DECMCS characters in its alphabet.

Files
       to find the recipient's machine

       to find the recipient's tty

See Also
       mail(1), mesg(1), who(1), write(1), talkd(8c)

																	   talk(1)
Man Page