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.
82 This is the string describing the channel to which the main console
85 main console to stdin and stdout.
86 It is safe to leave this unchanged.
92 This is the string describing the channel to which all consoles
96 It is safe to leave this unchanged, although you may wish to change
97 this if you expect the UML that you build to be run in environments
104 This is the string describing the channel to which the serial lines
106 command line. The default value is "pty", which attaches them to
108 It is safe to leave this unchanged, although you may wish to change
109 this if you expect the UML that you build to be run in environments
118 It is safe to say 'Y' here.
141 While the User-Mode port cannot directly talk to any physical
144 kernels can talk to each other, the host, and with the host's help,
151 If you'd like to be able to enable networking in the User-Mode
153 enable at least one of the following transport options to actually
161 running UML to exchange packets with its host over one of the
165 Ethernet network, it's in fact communicating over a point-to-point
168 To use this, your host kernel must have support for Ethertap
174 has examples of the UML command line to use to enable Ethertap
178 migrate to UML_NET_VECTOR.
186 The UML TUN/TAP network transport allows a UML instance to exchange
188 work with a 2.4 host, unless you've applied the TUN/TAP patch to
191 To use this transport, your host kernel must have support for TUN/TAP
195 migrate to UML_NET_VECTOR.
203 The slip User-Mode Linux network transport allows a running UML to
204 network with its host over a point-to-point link. Unlike Ethertap,
208 To use this, your host must support slip devices.
212 has examples of the UML command line to use to enable slip
216 migrate to UML_NET_VECTOR.
225 UMLs on a single host to communicate with each other, but not to
228 To use this form of networking, you'll need to run the UML
233 has examples of the UML command line to use to enable Daemon
237 migrate to UML_NET_VECTOR.
247 transport, normally it defaults to /tmp/uml.ctl.
258 with up to 4 times higher network throughput than the UML network
267 UMLs on a single host to communicate with each other and also
271 You must have libvdeplug installed in order to build the vde
274 To use this form of networking, you will need to run vde_switch
279 of the UML command line to use to enable VDE networking.
282 migrate to UML_NET_VECTOR.
291 UMLs (even ones running on different host machines!) to talk to
293 at least one UML with one of the other transports to act as a
294 bridge if any of them need to be able to talk to their hosts or any
297 To use this, your host kernel(s) must support IP Multicasting.
301 has examples of the UML command line to use to enable Multicast
305 migrate to UML_NET_VECTOR.
317 installed in order to build the pcap transport into UML.
321 has examples of the UML command line to use to enable this option.
324 migrate to UML_NET_VECTOR.
333 to network by invoking a program that can handle SLIP encapsulated
334 packets. This is commonly (but not limited to) the application
339 to the outside world that the host user is permitted, and unlike
350 migrate to UML_NET_VECTOR.
371 When PM_SLEEP is configured, it may be desirable to wake up using
393 wish to use for experimentation here. The default of -1 is
394 not valid and will cause the driver to fail at probe.