From a8da2c0803ee71ce521e5901dc204b33006782fc Mon Sep 17 00:00:00 2001 From: Michael Gebetsroither Date: Sun, 2 Apr 2006 20:39:59 +0200 Subject: [PATCH] fixed a few other typos --- grml-crypt | 2 +- grml-crypt.8.txt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/grml-crypt b/grml-crypt index 0b49f25..03d7d1f 100755 --- a/grml-crypt +++ b/grml-crypt @@ -252,7 +252,7 @@ function actionFormat notice "Operating on a file" IS_IMAGE_='true' if [ -e "$TARGET_" ]; then - $FORCE_ || die "file $TARGET_ does allready exist" + $FORCE_ || die "$TARGET_ does already exist" warn "overwriting file $TARGET_" init_='donothing' else diff --git a/grml-crypt.8.txt b/grml-crypt.8.txt index 27ccf29..6cf20fd 100644 --- a/grml-crypt.8.txt +++ b/grml-crypt.8.txt @@ -26,11 +26,11 @@ ACTIONS *format [mountpoint]*:: This command "formats" a device/file. If the second parameter is not a blockdevice grml-crypt assumes that it should operate in file modus. If the - file does not allready exist it will be created with the given size. The + file does not already exist it will be created with the given size. The first 2MB of a device (luks header) are initialised with /dev/urandom, the other space is initialised with the given initialisation. If grml-crypt is in file modus the first 2MB of the loop file are also initialised with - /dev/urandom except where the file allready exist (with -f vor + /dev/urandom except where the file already exist (with -f vor overwriting). Commands: [losetup], dd, cryptsetup luksFormat, cryptsetup luksOpen, [dd], mkfs, [mount] @@ -110,7 +110,7 @@ INITIALISATION MODES *Default/Secure mode (no -o or -z given)*:: This mode is the default. It should be quite secure. The device/file gets - initialised with /dev/urandom. Except with an allready existing file and + initialised with /dev/urandom. Except with an already existing file and -f, where NO initialisation will be done (all other modes behave as usual). *Optimized secure mode (-o)*:: -- 2.1.4