Lines Matching +full:host +full:- +full:command
1 # SPDX-License-Identifier: GPL-2.0
14 The User-Mode Linux environment allows you to create virtual serial
15 lines on the UML that are usually made to show up on the host as
18 See <http://user-mode-linux.sourceforge.net/old/input.html> for more
19 information and command line examples of how to use this facility.
34 lines to host portals. They may be accessed with 'telnet <host>
44 lines to host pseudo-terminals. Access to both traditional
45 pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
46 with this option. The assignment of UML devices to host devices
54 lines to host terminals. Access to both virtual consoles
55 (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
77 command line. The default value is "fd:0,fd:1", which attaches the
87 be overridden from the command line. The default value is "xterm",
99 command line. The default value is "pty", which attaches them to
100 traditional pseudo-terminals.
110 between the host's dsp and mixer devices and the UML sound system.
134 While the User-Mode port cannot directly talk to any physical
137 kernels can talk to each other, the host, and with the host's help,
142 <http://user-mode-linux.sourceforge.net/old/networking.html>.
144 If you'd like to be able to enable networking in the User-Mode
153 The Ethertap User-Mode Linux network transport allows a single
154 running UML to exchange packets with its host over one of the
155 host's Ethertap devices, such as /dev/tap0. Additional running
157 While the UML believes it's on a (multi-device, broadcast) virtual
158 Ethernet network, it's in fact communicating over a point-to-point
159 link with the host.
161 To use this, your host kernel must have support for Ethertap
162 devices. Also, if your host kernel is 2.4.x, it must have
166 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
167 has examples of the UML command line to use to enable Ethertap
180 packets with the host over a TUN/TAP device. This option will only
181 work with a 2.4 host, unless you've applied the TUN/TAP patch to
182 your 2.2 host kernel.
184 To use this transport, your host kernel must have support for TUN/TAP
185 devices, either built-in or as a module.
196 The slip User-Mode Linux network transport allows a running UML to
197 network with its host over a point-to-point link. Unlike Ethertap,
198 which can carry any Ethernet frame (and hence even non-IP packets),
201 To use this, your host must support slip devices.
204 <http://user-mode-linux.sourceforge.net/old/networking.html>.
205 has examples of the UML command line to use to enable slip
217 This User-Mode Linux network transport allows one or more running
218 UMLs on a single host to communicate with each other, but not to
219 the host.
222 networking daemon on the host.
225 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
226 has examples of the UML command line to use to enable Daemon
239 This User-Mode Linux network driver uses multi-message send
240 and receive functions. The host running the UML guest must have
251 This User-Mode Linux network transport allows one or more running
252 UMLs on a single host to communicate with each other and also
260 on the host.
264 of the UML command line to use to enable VDE networking.
275 This Multicast User-Mode Linux network transport allows multiple
276 UMLs (even ones running on different host machines!) to talk to
282 To use this, your host kernel(s) must support IP Multicasting.
285 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
286 has examples of the UML command line to use to enable Multicast
299 The pcap transport makes a pcap packet stream on the host look
301 UML act as a network monitor for the host. You must have libcap
305 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
306 has examples of the UML command line to use to enable this option.
317 The SLiRP User-Mode Linux network transport allows a running UML
320 known as SLiRP, a program that can re-socket IP packets back onto
321 he host on which it is run. Only IP packets are supported,
324 to the outside world that the host user is permitted, and unlike
326 privleges, setuid binaries, or SLIP devices on the host. This
331 that of a host behind a firewall that masquerades all network
348 drivers over vhost-user sockets.