CONFIG_UML_NET_SLIP: SLIP transport (obsolete)

General informations

The Linux kernel configuration item CONFIG_UML_NET_SLIP has multiple definitions:

SLIP transport (obsolete) found in arch/um/drivers/Kconfig

The configuration item CONFIG_UML_NET_SLIP:

• prompt: SLIP transport (obsolete)
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/drivers/Kconfig
• found in Linux kernels: 5.6–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

The slip User-Mode Linux network transport allows a running UML to network with its host over a point-to-point link. Unlike Ethertap, which can carry any Ethernet frame (and hence even non-IP packets), the slip transport can only carry IP packets.

To use this, your host must support slip devices.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html. has examples of the UML command line to use to enable slip networking, and details of a few quirks with it.

NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please migrate to UML_NET_VECTOR.

If unsure, say N.

SLIP transport found in arch/um/drivers/Kconfig

The configuration item CONFIG_UML_NET_SLIP:

• prompt: SLIP transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/drivers/Kconfig
• found in Linux kernels: 4.19–4.20, 5.0–5.5

Help text

The slip User-Mode Linux network transport allows a running UML to network with its host over a point-to-point link. Unlike Ethertap, which can carry any Ethernet frame (and hence even non-IP packets), the slip transport can only carry IP packets.

To use this, your host must support slip devices.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html. has examples of the UML command line to use to enable slip networking, and details of a few quirks with it.

The Ethertap Transport is preferred over slip because of its limitations. If you prefer slip, however, say Y here. Otherwise choose the Multicast transport (to network multiple UMLs on multiple hosts), Ethertap (to network with the host and the outside world), and/or the Daemon transport (to network multiple UMLs on a single host). You may choose more than one without conflict. If you don't need UML networking, say N.

SLIP transport found in arch/um/Kconfig.net

The configuration item CONFIG_UML_NET_SLIP:

• prompt: SLIP transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/Kconfig.net
• found in Linux kernels: 2.6.14–2.6.39, 3.0–3.19, 4.0–4.18

Help text

The slip User-Mode Linux network transport allows a running UML to network with its host over a point-to-point link. Unlike Ethertap, which can carry any Ethernet frame (and hence even non-IP packets), the slip transport can only carry IP packets.

To use this, your host must support slip devices.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html. has examples of the UML command line to use to enable slip networking, and details of a few quirks with it.

The Ethertap Transport is preferred over slip because of its limitations. If you prefer slip, however, say Y here. Otherwise choose the Multicast transport (to network multiple UMLs on multiple hosts), Ethertap (to network with the host and the outside world), and/or the Daemon transport (to network multiple UMLs on a single host). You may choose more than one without conflict. If you don't need UML networking, say N.

SLIP transport found in arch/um/Kconfig_net

The configuration item CONFIG_UML_NET_SLIP:

• prompt: SLIP transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/Kconfig_net
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.13

Help text

The slip User-Mode Linux network transport allows a running UML to network with its host over a point-to-point link. Unlike Ethertap, which can carry any Ethernet frame (and hence even non-IP packets), the slip transport can only carry IP packets.

To use this, your host must support slip devices.

For more information, see http://user-mode-linux.sourceforge.net/networking.html. That site has examples of the UML command line to use to enable slip networking, and details of a few quirks with it.

The Ethertap Transport is preferred over slip because of its limitations. If you prefer slip, however, say Y here. Otherwise choose the Multicast transport (to network multiple UMLs on multiple hosts), Ethertap (to network with the host and the outside world), and/or the Daemon transport (to network multiple UMLs on a single host). You may choose more than one without conflict. If you don't need UML networking, say N.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: