Custom Search
Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - B index
The Linux kernel configuration item CONFIG_BLK_DEV_LOOP has multiple definitions:
drivers/block/KconfigThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loopSaying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc.
This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver.
To use the loop device, you need the losetup utility, found in the util-linux package, see https://www.kernel.org/pub/linux/utils/util-linux/.
The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server.
Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself.
To compile this driver as a module, choose M here: the module will be called loop.
Most users will answer N here.
arch/um/Kconfig_blockThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loop(none)
arch/ia64/KconfigThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loop(none)
arch/sparc64/KconfigThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loopSaying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc.
This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver.
The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server. If you want to do this, you will first have to acquire and install a kernel patch from <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to say Y to this option.
Note that alternative ways to use encrypted file systems are provided by the cfs package, which can be gotten from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs package, available at http://tcfs.dia.unisa.it/. You do not need to say Y here if you want to use one of these. However, using cfs requires saying Y to "NFS file system support" below while using tcfs requires applying a kernel patch. An alternative steganography solution is provided by StegFS, also available from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
To use the loop device, you need the losetup utility and a recent version of the mount program, both contained in the util-linux package. The location and current version number of util-linux is contained in the file Documentation/Changes.
Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself.
To compile this driver as a module, choose M here: the module will be called loop.
Most users will answer N here.
arch/sparc/KconfigThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loopSaying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc.
This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver.
The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server. If you want to do this, you will first have to acquire and install a kernel patch from <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to say Y to this option.
Note that alternative ways to use encrypted file systems are provided by the cfs package, which can be gotten from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs package, available at http://tcfs.dia.unisa.it/. You do not need to say Y here if you want to use one of these. However, using cfs requires saying Y to "NFS file system support" below while using tcfs requires applying a kernel patch. An alternative steganography solution is provided by StegFS, also available from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
To use the loop device, you need the losetup utility and a recent version of the mount program, both contained in the util-linux package. The location and current version number of util-linux is contained in the file Documentation/Changes.
Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself.
To compile this driver as a module, choose M here: the module will be called loop.
Most users will answer N here.
drivers/s390/KconfigThe configuration item CONFIG_BLK_DEV_LOOP:
(none)loop, loop, loop, loop, loop, loopSaying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc.
This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver.
The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server. If you want to do this, you will first have to acquire and install a kernel patch from <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to say Y to this option.
Note that alternative ways to use encrypted file systems are provided by the cfs package, which can be gotten from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs package, available at http://tcfs.dia.unisa.it/. You do not need to say Y here if you want to use one of these. However, using cfs requires saying Y to "NFS file system support" below while using tcfs requires applying a kernel patch. An alternative steganography solution is provided by StegFS, also available from <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
To use the loop device, you need the losetup utility and a recent version of the mount program, both contained in the util-linux package. The location and current version number of util-linux is contained in the file Documentation/Changes.
Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called loop.
Most users will answer N here.
Raw data from LKDDb:
lkddb module loop CONFIG_BLK_DEV_LOOP : arch/ia64/Kconfig : "Loopback device support" # in 2.5.45–2.5.75, 2.6.0–2.6.4lkddb module loop CONFIG_BLK_DEV_LOOP : arch/sparc/Kconfig : "Loopback device support" # in 2.5.45–2.5.75, 2.6.0lkddb module loop CONFIG_BLK_DEV_LOOP : arch/sparc64/Kconfig : "Loopback device support" # in 2.5.45–2.5.75, 2.6.0lkddb module loop CONFIG_BLK_DEV_LOOP : arch/um/Kconfig_block : "Loopback device support" # in 2.5.45–2.5.75, 2.6.0–2.6.10lkddb module loop CONFIG_BLK_DEV_LOOP : drivers/block/Kconfig : "Loopback device support" # in 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12lkddb module loop CONFIG_BLK_DEV_LOOP : drivers/s390/Kconfig : "Loopback device support" # in 2.5.45–2.5.75This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - B index
Automatically generated (in year 2024). See also LKDDb sources on GitLab