Issue in man page sfdisk.8

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: sfdisk → B<sfdisk>

"Specify sector size. This header is informative only and it is not used when "
"sfdisk creates a new partition table, in this case the real device specific "
"value is always used and sector size from the dump is ignored."

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: btmp → I<btmp>

"For security reasons, B<su> always logs failed log-in attempts to the btmp "
"file, but it does not write to the I<lastlog> file at all. This solution can "
"be used to control B<su> behavior by PAM configuration. If you want to use "
"the B<pam_lastlog>(8) module to print warning message about failed log-in "
"attempts then B<pam_lastlog>(8) has to be configured to update the "
"I<lastlog> file as well. For example by:"

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: pam_getenvlistB<(3))> → B<pam_getenvlist>(3)

"Note that B<su> in all cases uses PAM (B<pam_getenvlist>(3)) to do the final "
"environment modification. Command-line options such as B<--login> and B<--"
"preserve-environment> affect the environment before it is modified by PAM."

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: Last sentence: If the ... then the

"The default value of I<start> is the first non-assigned sector aligned "
"according to device I/O limits. The default start offset for the first "
"partition is 1 MiB. The offset may be followed by the multiplicative "
"suffixes (KiB, MiB, GiB, TiB, PiB, EiB, ZiB and YiB) then the number is "
"interpreted as offset in bytes."

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: Last sentence: The offset ... then → If the offset ... then

"The first non-assigned sector aligned according to device I/O limits. The "
"default start offset for the first partition is 1 MiB. The offset may be "
"followed by the multiplicative suffixes (KiB, MiB, GiB, TiB, PiB, EiB, ZiB "
"and YiB) then the number is interpreted as offset in bytes."
msgstr ""
"Der erste nicht zugewiesene Sektor, der entsprechend der E/A-Begrenzungen "
"ausgerichtet ist. Der Vorgabestartversatz für die erste Partition ist 1 MiB. "

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue 1: udevd → B<systemd-udevd>(8)
Issue 2: B<"yes"> → B<yes>

"Use exclusive BSD lock for device or file it operates. The optional argument "
"I<mode> can be B<yes>, B<no> (or 1 and 0) or B<nonblock>. If the I<mode> "
"argument is omitted, it defaults to B<\"yes\">. This option overwrites "
"environment variable B<$LOCK_BLOCK_DEVICE>. The default is not to use any "
"lock at all, but it\\(cqs recommended to avoid collisions with udevd or "
"other tools."

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: partitions → partition

"Wipe filesystem, RAID and partition-table signatures from a newly created "
"partitions, in order to avoid possible collisions. The argument I<when> can "
"be B<auto>, B<never> or B<always>. When this option is not given, the "
"default is B<auto>, in which case signatures are wiped only when in "
"interactive mode and after confirmation by user. In all cases detected "
"signatures are reported by warning messages after a new partition is "
"created. See also B<wipefs>(8) command."

Issue in man page sfdisk.8

[Helge Kreutzmann]

Without further ado, the following was found:

Issue: udevd → B<systemd-udevd>(8)

"B<sfdisk> uses B<BLKRRPART> (reread partition table) ioctl to make sure that "
"the device is not used by system or other tools (see also B<--no-reread>). It"
"\\(cqs possible that this feature or another B<sfdisk> activity races with "
"B<udevd>. The recommended way how to avoid possible collisions is to use B<--"
"lock> option. The exclusive lock will cause udevd to skip the event handling "
"on the device."