@@ -147,7 +147,7 @@ config UML_NET
147
147
make use of UML networking.
148
148
149
149
config UML_NET_ETHERTAP
150
- bool "Ethertap transport"
150
+ bool "Ethertap transport (obsolete) "
151
151
depends on UML_NET
152
152
help
153
153
The Ethertap User-Mode Linux network transport allows a single
@@ -167,14 +167,13 @@ config UML_NET_ETHERTAP
167
167
has examples of the UML command line to use to enable Ethertap
168
168
networking.
169
169
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
172
- Slip Transport. You'll need at least one of them, but may choose
173
- more than one without conflict. If you don't need UML networking,
174
- say N.
170
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
171
+ migrate to UML_NET_VECTOR.
172
+
173
+ If unsure, say N.
175
174
176
175
config UML_NET_TUNTAP
177
- bool "TUN/TAP transport"
176
+ bool "TUN/TAP transport (obsolete) "
178
177
depends on UML_NET
179
178
help
180
179
The UML TUN/TAP network transport allows a UML instance to exchange
@@ -185,8 +184,13 @@ config UML_NET_TUNTAP
185
184
To use this transport, your host kernel must have support for TUN/TAP
186
185
devices, either built-in or as a module.
187
186
187
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
188
+ migrate to UML_NET_VECTOR.
189
+
190
+ If unsure, say N.
191
+
188
192
config UML_NET_SLIP
189
- bool "SLIP transport"
193
+ bool "SLIP transport (obsolete) "
190
194
depends on UML_NET
191
195
help
192
196
The slip User-Mode Linux network transport allows a running UML to
@@ -201,16 +205,13 @@ config UML_NET_SLIP
201
205
has examples of the UML command line to use to enable slip
202
206
networking, and details of a few quirks with it.
203
207
204
- The Ethertap Transport is preferred over slip because of its
205
- limitations. If you prefer slip, however, say Y here. Otherwise
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
209
- UMLs on a single host). You may choose more than one without
210
- conflict. If you don't need UML networking, say N.
208
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
209
+ migrate to UML_NET_VECTOR.
210
+
211
+ If unsure, say N.
211
212
212
213
config UML_NET_DAEMON
213
- bool "Daemon transport"
214
+ bool "Daemon transport (obsolete) "
214
215
depends on UML_NET
215
216
help
216
217
This User-Mode Linux network transport allows one or more running
@@ -225,13 +226,10 @@ config UML_NET_DAEMON
225
226
has examples of the UML command line to use to enable Daemon
226
227
networking.
227
228
228
- If you'd like to set up a network with other UMLs on a single host,
229
- say Y. If you need a network between UMLs on multiple physical
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
232
- transports. You'll need at least one of them, but may choose
233
- more than one without conflict. If you don't need UML networking,
234
- say N.
229
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
230
+ migrate to UML_NET_VECTOR.
231
+
232
+ If unsure, say N.
235
233
236
234
config UML_NET_VECTOR
237
235
bool "Vector I/O high performance network devices"
@@ -245,7 +243,7 @@ config UML_NET_VECTOR
245
243
drivers.
246
244
247
245
config UML_NET_VDE
248
- bool "VDE transport"
246
+ bool "VDE transport (obsolete) "
249
247
depends on UML_NET
250
248
help
251
249
This User-Mode Linux network transport allows one or more running
@@ -263,11 +261,13 @@ config UML_NET_VDE
263
261
That site has a good overview of what VDE is and also examples
264
262
of the UML command line to use to enable VDE networking.
265
263
266
- If you need UML networking with VDE,
267
- say Y.
264
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
265
+ migrate to UML_NET_VECTOR.
266
+
267
+ If unsure, say N.
268
268
269
269
config UML_NET_MCAST
270
- bool "Multicast transport"
270
+ bool "Multicast transport (obsolete) "
271
271
depends on UML_NET
272
272
help
273
273
This Multicast User-Mode Linux network transport allows multiple
@@ -284,15 +284,13 @@ config UML_NET_MCAST
284
284
has examples of the UML command line to use to enable Multicast
285
285
networking, and notes about the security of this approach.
286
286
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
289
- with other IP machines, make sure you select one of the other
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
292
- the transports.
287
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
288
+ migrate to UML_NET_VECTOR.
289
+
290
+ If unsure, say N.
293
291
294
292
config UML_NET_PCAP
295
- bool "pcap transport"
293
+ bool "pcap transport (obsolete) "
296
294
depends on UML_NET
297
295
help
298
296
The pcap transport makes a pcap packet stream on the host look
@@ -304,11 +302,13 @@ config UML_NET_PCAP
304
302
<http://user-mode-linux.sourceforge.net/old/networking.html> That site
305
303
has examples of the UML command line to use to enable this option.
306
304
307
- If you intend to use UML as a network monitor for the host, say
308
- Y here. Otherwise, say N.
305
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
306
+ migrate to UML_NET_VECTOR.
307
+
308
+ If unsure, say N.
309
309
310
310
config UML_NET_SLIRP
311
- bool "SLiRP transport"
311
+ bool "SLiRP transport (obsolete) "
312
312
depends on UML_NET
313
313
help
314
314
The SLiRP User-Mode Linux network transport allows a running UML
@@ -328,9 +328,10 @@ config UML_NET_SLIRP
328
328
that of a host behind a firewall that masquerades all network
329
329
connections passing through it (but is less secure).
330
330
331
- To use this you should first have slirp compiled somewhere
332
- accessible on the host, and have read its documentation. If you
333
- don't need UML networking, say N.
331
+ NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
332
+ migrate to UML_NET_VECTOR.
333
+
334
+ If unsure, say N.
334
335
335
336
Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp"
336
337
0 commit comments