From edc8e7b81f061dec9871f8255741f1f8964d82b6 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 29 Nov 2018 11:17:36 +0100 Subject: [PATCH] docs: fix typo --- docs/BLOCK_DEVICE_LOCKING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/BLOCK_DEVICE_LOCKING.md b/docs/BLOCK_DEVICE_LOCKING.md index bf84484255..ceb060c0c9 100644 --- a/docs/BLOCK_DEVICE_LOCKING.md +++ b/docs/BLOCK_DEVICE_LOCKING.md @@ -55,7 +55,7 @@ take a `LOCK_EX` *exclusive* lock instead. For further details, see the And please keep in mind: BSD file locks (`flock()`) and POSIX file locks (`lockf()`, `F_SETLK`, …) are different concepts, and in their effect orthogonal. The scheme discussed above uses the former and not the latter, -because the these types of locks more closely match the required semantics. +because these types of locks more closely match the required semantics. Summarizing: it is recommended to take `LOCK_EX` BSD file locks when manipulating block devices in all tools that change file system block devices