1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
|
menu "Block devices support"
config ADK_KERNEL_MD
boolean
config ADK_KERNEL_SWAP
boolean
config ADK_KERNEL_LBD
boolean
config ADK_KERNEL_BLK_DEV_IO_TRACE
boolean
config ADK_KERNEL_LSF
boolean
config ADK_KERNEL_IOSCHED_AS
boolean
config ADK_KERNEL_IOSCHED_DEADLINE
boolean
config ADK_KERNEL_IOSCHED_CFQ
boolean
config ADK_KERNEL_SCSI
boolean
config ADK_KERNEL_BLK_DEV_SD
boolean
config ADK_KERNEL_DM_CRYPT
boolean
config ADK_KERNEL_BLK_DEV_DM
boolean
select ADK_KERNEL_MD
depends on !ADK_LINUX_CRIS_FOXBOARD
config ADK_KERNEL_ATA
boolean
config ADK_KERNEL_ATA_SFF
boolean
config ADK_KERNEL_ATA_PIIX
boolean
select ADK_KERNEL_BLOCK
select ADK_KERNEL_ATA
select ADK_KERNEL_ATA_SFF
select ADK_KERNEL_BLK_DEV_SD
default y if ADK_HARDWARE_IBMX40
default y if ADK_HARDWARE_QEMU_X86
default y if ADK_HARDWARE_QEMU_X86_64
default n
config ADK_KERNEL_SATA_AHCI
tristate
select ADK_KERNEL_BLOCK
select ADK_KERNEL_ATA
select ADK_KERNEL_BLK_DEV_SD
default y if ADK_HARDWARE_SHUTTLE
default n
config ADK_KPACKAGE_KMOD_SATA_AHCI
prompt "kmod-sata-ahci.................... AHCI SATA driver"
tristate
select ADK_KERNEL_BLOCK
select ADK_KERNEL_ATA
select ADK_KERNEL_BLK_DEV_SD
depends on !ADK_KERNEL_SATA_AHCI
default n
help
Enables support for AHCI Serial ATA.
config ADK_KPACKAGE_KMOD_BLK_DEV_LOOP
prompt "kmod-loop......................... Loop mount support"
tristate
default n
help
Saying 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
<ftp://ftp.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.
There are several ways of encrypting disks. Some of these require
kernel patches. The vanilla kernel offers the cryptoloop option
and a Device Mapper target (which is superior, as it supports all
file systems). If you want to use the cryptoloop, say Y to both
LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
or later) version of util-linux. Additionally, be aware that
the cryptoloop is not safe for storing journaled filesystems.
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
config ADK_KPACKAGE_KMOD_BLK_DEV_NBD
prompt "kmod-nbd.......................... Network Block Device"
tristate
default n
help
Saying Y here will allow your computer to be a client for network
block devices, i.e. it will be able to use block devices exported by
servers (mount file systems on them etc.). Communication between
client and server works over TCP/IP networking, but to the client
program this is hidden: it looks like a regular local file access to
a block device special file such as /dev/nd0.
Network block devices also allows you to run a block-device in
userland (making server and client physically the same computer,
communicating using the loopback network device).
Read <file:Documentation/nbd.txt> for more information, especially
about where to find the server code, which runs in user space and
does not need special kernel support.
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
config ADK_KPACKAGE_KMOD_SCSI
prompt "kmod-scsi......................... SCSI support"
select ADK_KERNEL_LBD
select ADK_KERNEL_LSF
select ADK_KERNEL_IOSCHED_AS
depends on !ADK_KERNEL_SCSI
depends on !ADK_KERNEL_SATA_AHCI
depends on !ADK_KERNEL_ATA_PIIX
tristate
help
If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
any other SCSI device under Linux, say Y and make sure that you know
the name of your SCSI host adapter (the card inside your computer
that "speaks" the SCSI protocol, also called SCSI controller),
because you will be asked for it.
You also need to say Y here if you have a device which speaks
the SCSI protocol. Examples of this include the parallel port
version of the IOMEGA ZIP drive, USB storage devices, Fibre
Channel, FireWire storage and the IDE-SCSI emulation driver.
config ADK_KPACKAGE_KMOD_BLK_DEV_SD
prompt "kmod-scsi-disk.................... SCSI disk support"
select ADK_KPACKAGE_KMOD_SCSI
depends on !ADK_KERNEL_BLK_DEV_SD
tristate
help
If you want to use SCSI hard disks, Fibre Channel disks,
USB storage or the SCSI or parallel port version of
the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
the Disk-HOWTO and the Multi-Disk-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
CD-ROMs.
config ADK_KPACKAGE_KMOD_BLK_DEV_SR
prompt "kmod-scsi-cdrom................... SCSI CDROM support"
depends on !ADK_KERNEL_SCSI
depends on ADK_KPACKAGE_KMOD_SCSI
tristate
help
If you want to use a SCSI or FireWire CD-ROM under Linux,
say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
<http://www.tldp.org/docs.html#howto>. Also make sure to say
Y or M to "ISO 9660 CD-ROM file system support" later.
config ADK_KERNEL_BLK_DEV_MD
tristate
select ADK_KERNEL_MD
depends on !ADK_LINUX_CRIS_FOXBOARD
default n
config ADK_KPACKAGE_KMOD_BLK_DEV_MD
prompt "kmod-md........................... RAID support"
tristate
depends on !ADK_KERNEL_BLK_DEV_MD
depends on !ADK_LINUX_CRIS_FOXBOARD
select ADK_KERNEL_MD
help
config ADK_KERNEL_MD_RAID0
tristate
depends on ADK_KERNEL_BLK_DEV_MD
help
config ADK_KPACKAGE_KMOD_MD_RAID0
prompt "kmod-md-raid0..................... RAID0 support"
tristate
depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
help
config ADK_KERNEL_MD_RAID1
tristate
depends on ADK_KERNEL_BLK_DEV_MD
help
config ADK_KPACKAGE_KMOD_MD_RAID1
prompt "kmod-md-raid1..................... RAID1 support"
tristate
depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
help
config ADK_KPACKAGE_KMOD_MD_RAID456
prompt "kmod-md-raid456................... RAID456 support"
tristate
depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
help
config ADK_KPACKAGE_KMOD_BLK_DEV_DM
prompt "kmod-dm........................... Device Mapper support"
select ADK_KERNEL_MD
depends on !(ADK_KERNEL_BLK_DEV_DM || ADK_LINUX_CRIS_FOXBOARD)
tristate
help
Device-mapper is a low level volume manager. It works by allowing
people to specify mappings for ranges of logical sectors. Various
mapping types are available, in addition people may write their own
modules containing custom mappings if they wish.
Higher level volume managers such as LVM2 use this driver.
config ADK_KPACKAGE_KMOD_DM_CRYPT
prompt "kmod-dm-crypt................... Crypt target support"
depends on !(ADK_KERNEL_DM_CRYPT || ADK_LINUX_CRIS_FOXBOARD)
select ADK_KPACKAGE_KMOD_BLK_DEV_DM
select ADK_KERNEL_MD
select ADK_KERNEL_CRYPTO
select ADK_KPACKAGE_KMOD_CRYPTO_CBC
select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
tristate
help
This device-mapper target allows you to create a device that
transparently encrypts the data on it. You'll need to activate
the ciphers you're going to use in the cryptoapi configuration.
Information on how to use dm-crypt can be found on
<http://www.saout.de/misc/dm-crypt/>
config ADK_KPACKAGE_KMOD_DM_SNAPSHOT
prompt "kmod-dm-snapshot................ Snapshot target"
select ADK_KPACKAGE_KMOD_BLK_DEV_DM
depends on !ADK_LINUX_CRIS_FOXBOARD
tristate
help
Allow volume managers to take writable snapshots of a device.
config ADK_KPACKAGE_KMOD_DM_MIRROR
prompt "kmod-dm-mirror.................. Mirror target"
select ADK_KPACKAGE_KMOD_BLK_DEV_DM
depends on !ADK_LINUX_CRIS_FOXBOARD
tristate
help
Allow volume managers to mirror logical volumes, also
needed for live data migration tools such as 'pvmove'.
endmenu
|
