Lines Matching refs:host

15 	  lines on the UML that are usually made to show up on the host as
34 	  lines to host portals.  They may be accessed with 'telnet <host>
44 	  lines to host pseudo-terminals.  Access to both traditional
46 	  with this option.  The assignment of UML devices to host devices
54 	  lines to host terminals.  Access to both virtual consoles
112 	  between the host's dsp and mixer devices and the UML sound system.
127 	  kernels can talk to each other, the host, and with the host's help,
144 	  running UML to exchange packets with its host over one of the
145 	  host's Ethertap devices, such as /dev/tap0.  Additional running
149 	  link with the host.
151 	  To use this, your host kernel must have support for Ethertap
152 	  devices.  Also, if your host kernel is 2.4.x, it must have
170 	  packets with the host over a TUN/TAP device.  This option will only
171 	  work with a 2.4 host, unless you've applied the TUN/TAP patch to
172 	  your 2.2 host kernel.
174 	  To use this transport, your host kernel must have support for TUN/TAP
187 	  network with its host over a point-to-point link.  Unlike Ethertap,
191 	  To use this, your host must support slip devices.
208 	  UMLs on a single host to communicate with each other, but not to
209 	  the host.
212 	  networking daemon on the host.
230 	and receive functions. The host running the UML guest must have
242 	UMLs on a single host to communicate with each other and also
250 	on the host.
266 	  UMLs (even ones running on different host machines!) to talk to
272 	  To use this, your host kernel(s) must support IP Multicasting.
289 	The pcap transport makes a pcap packet stream on the host look
291 	UML act as a network monitor for the host.  You must have libcap
311 	  he host on which it is run.  Only IP packets are supported,
314 	  to the outside world that the host user is permitted, and unlike
316 	  privleges, setuid binaries, or SLIP devices on the host.  This
321 	  that of a host behind a firewall that masquerades all network