CONFIG_SLIP_COMPRESSED: CSLIP compressed headers

General informations

The Linux kernel configuration item CONFIG_SLIP_COMPRESSED has multiple definitions:

CSLIP compressed headers found in drivers/net/slip/Kconfig

The configuration item CONFIG_SLIP_COMPRESSED:

• prompt: CSLIP compressed headers
• type: bool
• depends on: CONFIG_SLIP
• defined in drivers/net/slip/Kconfig
• found in Linux kernels: 3.2–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.13, 6.14-rc+HEAD

Help text

This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from http://www.tldp.org/docs.html#howto, explains how to configure CSLIP. This won't enlarge your kernel.

CSLIP compressed headers found in drivers/net/Kconfig

The configuration item CONFIG_SLIP_COMPRESSED:

• prompt: CSLIP compressed headers
• type: bool
• depends on: CONFIG_SLIP
• defined in drivers/net/Kconfig
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.1

Help text

This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from http://www.tldp.org/docs.html#howto, explains how to configure CSLIP. This won't enlarge your kernel.

CSLIP compressed headers found in arch/um/Kconfig_net

The configuration item CONFIG_SLIP_COMPRESSED:

• prompt: CSLIP compressed headers
• type: bool
• depends on: CONFIG_SLIP = CONFIG_y
• defined in arch/um/Kconfig_net
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.8

Help text

(none)

CSLIP compressed headers found in arch/sparc/Kconfig

The configuration item CONFIG_SLIP_COMPRESSED:

• prompt: CSLIP compressed headers
• type: bool
• depends on: CONFIG_SLIP
• defined in arch/sparc/Kconfig
• found in Linux kernels: 2.5.45–2.5.54

Help text

This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from http://www.linuxdoc.org/docs.html#howto, explains how to configure CSLIP. This won't enlarge your kernel.

CSLIP compressed headers found in arch/m68k/Kconfig

The configuration item CONFIG_SLIP_COMPRESSED:

• prompt: CSLIP compressed headers
• type: bool
• depends on: CONFIG_SLIP
• defined in arch/m68k/Kconfig
• found in Linux kernels: 2.5.45–2.5.54

Help text

This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from http://www.linuxdoc.org/docs.html#howto, explains how to configure CSLIP. This won't enlarge your kernel.

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: