DataMuseum.dk

Presents historical artifacts from the history of:

Regnecentalen RC-900

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Regnecentalen RC-900

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download

⟦17057d836⟧ TextFile

    Length: 996 (0x3e4)
    Types: TextFile
    Notes: UNIX file
    Names: »Devconfig«

Derivation

└─⟦50c223e0a⟧ Bits:30004042/network1.imd SW95705I 386/ix Multi-user Release 1.2
└─⟦50c223e0a⟧ UNIX Filesystem
    └─⟦this⟧ »bn/new/usr/lib/uucp/Devconfig« 

TextFile

#ident	"@(#)uucp:Devconfig	1.1"
#
#	Devconfig provides a means of configuring STREAMS devices
#	by service.
#
#	FORMAT:
#
#	service=<service name>	device=<device type> \
#				push=<STREAMS module list>
#
#	where service name is "uucico" or "cu", device type is the device or
#	caller type (3rd field in Systems file, 1st field in Devices file),
#	and STREAMS module list is a colon-separated list of STREAMS modules
#	to be pushed on this stream.
#
#	The examples below are for the STARLAN NETWORK and assume that both
#	cu & uucico are going through login and so need full tty capabilities.
#	If uucico connects to a uucico server on the remote machine without
#	going through login, you would need to push only tirdwr.
#
#	EXAMPLE:
#		service=cu	device=STARLAN	push=ntty:tirdwr:ld0
#		service=uucico	device=STARLAN	push=ntty:tirdwr:ld0
#
#	Note: The tirdwr module is part of the STREAMS package.  Other 
#	modules needed to provide tty capabilites must be supplied by the
#	network provider.
#