diff options
author | Tim Riker <tim@rikers.org> | 2006-01-25 03:08:53 +0300 |
---|---|---|
committer | Tim Riker <tim@rikers.org> | 2006-01-25 03:08:53 +0300 |
commit | c1ef7bdd8d002ae0889efcf883d0e1b7faa938d4 (patch) | |
tree | 5f329b7d0c7f20ecced0dc7581a9ba6dc720d965 /util-linux/Config.in | |
parent | f64ff682a3d58dbb627e760e6fe1ec21d9ccdf61 (diff) |
just whitespace
Diffstat (limited to 'util-linux/Config.in')
-rw-r--r-- | util-linux/Config.in | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/util-linux/Config.in b/util-linux/Config.in index bf3e13b2a..27410bf10 100644 --- a/util-linux/Config.in +++ b/util-linux/Config.in @@ -214,7 +214,7 @@ config CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS depends on CONFIG_HWCLOCK help Starting with FHS 2.3, the adjtime state file is supposed to exist - at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish + at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish to use the FHS behavior, answer Y here, otherwise answer N for the classic /etc/adjtime path. @@ -406,7 +406,7 @@ config CONFIG_FEATURE_MOUNT_LOOP command will detect you are trying to mount a file instead of a block device, and transparently associate the file with a loopback device. The umount command will also free that loopback device. - + You can still use the 'losetup' utility (to manually associate files with loop devices) if you need to do something advanced, such as specify an offset or cryptographic options to the loopback device. |