Lines Matching full:to
9 console driver which dumps all printk messages to stderr.
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
19 information and command line examples of how to use this facility.
27 lines to a device similar to /dev/null. Data written to it disappears
28 and there is never any data to be read.
34 lines to host portals. They may be accessed with 'telnet <host>
36 attached to a single portal, although what UML device you get when
37 you telnet to that portal will be unpredictable.
38 It is safe to say 'Y' here.
44 lines to host pseudo-terminals. Access to both traditional
46 with this option. The assignment of UML devices to host devices
48 It is safe to say 'Y' here.
54 lines to host terminals. Access to both virtual consoles
57 It is safe to say 'Y' here.
63 lines to xterms. Each UML device so assigned will be brought up in
65 It is safe to say 'Y' here.
75 This is the string describing the channel to which the main console
78 main console to stdin and stdout.
79 It is safe to leave this unchanged.
85 This is the string describing the channel to which all consoles
89 It is safe to leave this unchanged, although you may wish to change
90 this if you expect the UML that you build to be run in environments
97 This is the string describing the channel to which the serial lines
99 command line. The default value is "pty", which attaches them to
101 It is safe to leave this unchanged, although you may wish to change
102 this if you expect the UML that you build to be run in environments
111 It is safe to say 'Y' here.
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,
144 If you'd like to be able to enable networking in the User-Mode
146 enable at least one of the following transport options to actually
154 running UML to exchange packets with its host over one of the
158 Ethernet network, it's in fact communicating over a point-to-point
161 To use this, your host kernel must have support for Ethertap
167 has examples of the UML command line to use to enable Ethertap
170 If you'd like to set up an IP network with the host and/or the
171 outside world, say Y to this, the Daemon Transport and/or the
180 The UML TUN/TAP network transport allows a UML instance to exchange
182 work with a 2.4 host, unless you've applied the TUN/TAP patch to
185 To use this transport, your host kernel must have support for TUN/TAP
192 The slip User-Mode Linux network transport allows a running UML to
193 network with its host over a point-to-point link. Unlike Ethertap,
197 To use this, your host must support slip devices.
201 has examples of the UML command line to use to enable slip
206 choose the Multicast transport (to network multiple UMLs on
207 multiple hosts), Ethertap (to network with the host and the
208 outside world), and/or the Daemon transport (to network multiple
217 UMLs on a single host to communicate with each other, but not to
220 To use this form of networking, you'll need to run the UML
225 has examples of the UML command line to use to enable Daemon
228 If you'd like to set up a network with other UMLs on a single host,
230 hosts, choose the Multicast Transport. To set up a network with
231 the host and/or other IP machines, say Y to the Ethertap or Slip
244 with up to 4 times higher network throughput than the UML network
252 UMLs on a single host to communicate with each other and also
256 You must have libvdeplug installed in order to build the vde
259 To use this form of networking, you will need to run vde_switch
264 of the UML command line to use to enable VDE networking.
274 UMLs (even ones running on different host machines!) to talk to
276 at least one UML with one of the other transports to act as a
277 bridge if any of them need to be able to talk to their hosts or any
280 To use this, your host kernel(s) must support IP Multicasting.
284 has examples of the UML command line to use to enable Multicast
287 If you need UMLs on multiple physical hosts to communicate as if
288 they shared an Ethernet network, say Y. If you need to communicate
290 transports (possibly in addition to Multicast; they're not
291 exclusive). If you don't need to network UMLs say N to each of
301 installed in order to build the pcap transport into UML.
305 has examples of the UML command line to use to enable this option.
307 If you intend to use UML as a network monitor for the host, say
315 to network by invoking a program that can handle SLIP encapsulated
316 packets. This is commonly (but not limited to) the application
321 to the outside world that the host user is permitted, and unlike
331 To use this you should first have slirp compiled somewhere