| 1 |
README for partconf |
| 2 |
=================== |
| 3 |
|
| 4 |
partconf currently consists of three binary packages. |
| 5 |
1. partconf The main program. |
| 6 |
2. partconf-find-partitions Support program for shell scripts that |
| 7 |
want information about partitions and |
| 8 |
logical volumes. |
| 9 |
3. partconf-mkfstab Creates the /target/etc/fstab file. |
| 10 |
|
| 11 |
|
| 12 |
Mapping devfs names into something easier to read |
| 13 |
------------------------------------------------- |
| 14 |
/dev/ide/host0/bus0/target0/lun0/part1 kinda sucks to read, and uses a lot |
| 15 |
of space too :) same for scsi. I think it's OK to have /dev/volgrp/vol1 |
| 16 |
for LVM volumes. If you're using LVM you probably know what you are doing |
| 17 |
and it's harder to map this. RAID can probably be mapped to. |
| 18 |
|
| 19 |
Mappings for IDE: |
| 20 |
* hostX/busY is translated to IDE(2*X+Y+1), so host0/bus0 becomes IDE1, |
| 21 |
host0/bus1 becomes IDE2, host1/bus0 becomes IDE3 et.c. |
| 22 |
* target0 is translated to "master", target1 to "slave". Will there ever |
| 23 |
be target2+? Unlikely. |
| 24 |
* We ignore lunN, it is unlikely that an IDE device will have more than one |
| 25 |
LUN. |
| 26 |
Examples: |
| 27 |
/dev/ide/host0/bus0/target0/lun0/part2 -> "IDE1 master, part. 2" |
| 28 |
/dev/ide/host0/bus1/target1/lun0/part1 -> "IDE2 slave, part. 1" |
| 29 |
|
| 30 |
Mappings for SCSI: |
| 31 |
* hostX is translated to SCSI(X+1), so host0 is SCSI1, host1 is SCSI2 |
| 32 |
* busX/targetY/lunZ is mapped to a (X,Y,Z) triplet. People using SCSI are |
| 33 |
probably familiar with these triplets. |
| 34 |
Examples: |
| 35 |
/dev/scsi/host0/bus0/target0/lun5/part1 -> "SCSI1 (0,0,5), part. 1" |
| 36 |
|
| 37 |
Mappings for RAID: |
| 38 |
* /dev/md/X is translated to "RAID logical volume X" |
| 39 |
Examples: |
| 40 |
/dev/md/0 -> "RAID logical volume 0" |