summaryrefslogtreecommitdiff
path: root/doc/official_installation_guide_en
diff options
context:
space:
mode:
authorDieter Plaetinck <dieter@plaetinck.be>2009-08-05 21:53:24 +0200
committerDieter Plaetinck <dieter@plaetinck.be>2009-08-05 21:53:24 +0200
commit797c3ac668cbff65336197a0641bf45c235d281a (patch)
treecd5895b7daf3a419650fe0b21e3ca6f8a55f3828 /doc/official_installation_guide_en
parentd6b08f0cb077a886bcf4969dec3b75a0c965b703 (diff)
notes about what we do and dont support, blockdevice/filesystem-wise. + nice example for user on how to use the interactive filesystem thing
Diffstat (limited to 'doc/official_installation_guide_en')
-rw-r--r--doc/official_installation_guide_en39
1 files changed, 39 insertions, 0 deletions
diff --git a/doc/official_installation_guide_en b/doc/official_installation_guide_en
index 827e793..25c637c 100644
--- a/doc/official_installation_guide_en
+++ b/doc/official_installation_guide_en
@@ -332,6 +332,15 @@ you want to retry.
want to undo or redo a certain scheme. You will be prompted for this if
you forget.
+Notes:
+
+* AIF can help you set up new dm_crypt and lvm volumes, but not (yet) softraid.
+* AIF currently doesn't help you creating volumegroups that span multiple
+ physical volumes. (if you need this -unlikely- : use vgcreate)
+* AIF supports reusing filesystems, but only if it can find the blockdevice.
+ If you want to reuse a filesystem that is on top of lvm/dm_crypt/softraid,
+ you'll need to bring up the volumes yourself.
+
##### Auto-Prepare
Auto-Prepare will automatically partition a hard drive of your choice
@@ -380,6 +389,36 @@ swap).
If anything is found, you can go back to fix these issues, or continue at
which point everything will be setup the way you asked.
+For example, if you want a setup that uses LVM on top of dm_crypt, you would:
+
+* make sure that you have a 2 partitions: a small one for the unencrypted
+ boot (about 100M) and one for the rest of the (encrypted) system.
+ (do this in "Manually partition hard drives")
+* on your /dev/sdX1, make an ext2 filesystem with mountpoint /boot
+* on your /dev/sdX2, make a dm_crypt volume, with label sdX2crypt
+ (or whatever you want)
+* /dev/mapper/sdX2crypt will appear. Put a LVM physical volume on this
+* /dev/mapper/sdX2crypt+ appears. This is the representation of the
+ physical volume. Put a volumegroup on this, with label cryptpool
+ (or whatever you want)
+* /dev/mapper/cryptpool appears. On this volumegroup you are able to put
+ multiple logical volumes. Make 2:
+ * one with size 5G: label this cryptroot
+ * one with size 10G: label this crypthome
+* 2 new volumes appear:
+ * /dev/mapper/cryptpool-cryptroot: on this blockdevice, you can put your
+ root filesystem, with mountpoint /.
+ * /dev/mapper/cryptpool-crypthome is the blockdevice on which you can put
+ the filesystem with mountpoint /home.
+* If you want swapspace, make a logical volume for swap and put
+ a swap volume on it.
+* That's it! If you select 'done' it should process the model and create
+ your disk setup the way you specified.
+ The cool part is that you can pick relatively small
+ values for your volumes to start with, and if you need more space later
+ you can grow the logical volume and the filesystem on top of it.
+
+
##### Rollbacks
The rollback function will do everything necessary to "undo" changes you