Package: systemd
Version: 20-1
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man5/locale.conf.5.gz',
'/usr/share/man/man5/systemd.device.5.gz',
'/usr/share/man/man7/daemon.7.gz',
'/usr/share/man/man7/systemd.special.7.gz',
and '/usr/share/man/man8/systemd-tmpfiles.8.gz',
see attached '.diff' files.
Hope this helps...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii libaudit0 1.7.13-1+b2 Dynamic library for security audit
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libcap2 1:2.19-3 support for getting/setting POSIX.
ii libcryptsetup1 2:1.2.0-2 libcryptsetup shared library
ii libdbus-1-3 1.2.24-4 simple interprocess messaging syst
ii libpam0g 1.1.2-2 Pluggable Authentication Modules l
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libudev0 164-4 libudev shared library
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
ii util-linux 2.17.2-9.1 Miscellaneous system utilities
Versions of packages systemd recommends:
ii libpam-systemd 20-1 system and service manager - PAM m
Versions of packages systemd suggests:
ii systemd-gui 20-1 system and service manager - GUI
-- no debconf information
--- locale.conf.5 2011-03-21 01:08:26.000000000 -0400
+++ /tmp/locale.conf.5 2011-04-19 01:46:25.528603215 -0400
@@ -60,7 +60,7 @@
.PP
The locale settings configured in
/etc/locale\&.conf
-are system\-wide and are inherited by every service or user, unless overriden
or unset by individual programs or individual users\&.
+are system\-wide and are inherited by every service or user, unless overridden
or unset by individual programs or individual users\&.
.PP
Depending on the operating system other configuration files might be checked
for locale configuration as well, however only as fallback\&.
.SH "OPTIONS"
@@ -85,7 +85,7 @@
\fBlocale\fR(7)\&.
.SH "EXAMPLE"
.PP
-\fBExample\ \&1.\ \&German locale with english messages\fR
+\fBExample\ \&1.\ \&German locale with English messages\fR
.PP
/etc/locale\&.conf:
.sp
--- systemd.device.5 2011-03-21 01:08:26.000000000 -0400
+++ /tmp/systemd.device.5 2011-04-19 01:48:03.264603222 -0400
@@ -78,7 +78,7 @@
.PP
\fISYSTEMD_READY=\fR
.RS 4
-If set to 0 systemd will consider this device unplugged even if it shows up in the udev tree\&. If this property is unset or set to 1 the device will be considered plugged the moment it shows up in the udev tree\&. This property has no influence on the behaviour when a device disappears from the udev tree\&. This option is useful to support devices that initially show up in an unitialized state in the tree, and for which a changed event is generated the moment they are fully set up\&.
+If set to 0 systemd will consider this device unplugged even if it shows up in the udev tree\&. If this property is unset or set to 1 the device will be considered plugged the moment it shows up in the udev tree\&. This property has no influence on the behaviour when a device disappears from the udev tree\&. This option is useful to support devices that initially show up in an uninitialized state in the tree, and for which a changed event is generated the moment they are fully set up\&.
.RE
.PP
\fIID_MODEL_FROM_DATABASE=\fR, \fIID_MODEL=\fR
--- daemon.7 2011-03-21 01:08:26.000000000 -0400
+++ /tmp/daemon.7 2011-04-19 01:54:44.416612469 -0400
@@ -384,7 +384,7 @@
.SS "Activation on Boot"
.PP
Old\-style daemons are usually activated exclusively on boot (and manually by the administrator) via SysV init scripts, as detailed in the
-\m[blue]\fBLSB Linux Standard Base Core Specification\fR\m[]\&\s-2\u[1]\d\s+2\&. This method of activation is supported ubiquitiously on Linux init systems, both old\-style and new\-style systems\&. Among other issues SysV init scripts have the disadvantage of involving shell scripts in the boot process\&. New\-style init systems generally employ updated versions of activation, both during boot\-up and during runtime and using more minimal service description files\&.
+\m[blue]\fBLSB Linux Standard Base Core Specification\fR\m[]\&\s-2\u[1]\d\s+2\&. This method of activation is supported ubiquitously on Linux init systems, both old\-style and new\-style systems\&. Among other issues SysV init scripts have the disadvantage of involving shell scripts in the boot process\&. New\-style init systems generally employ updated versions of activation, both during boot\-up and during runtime and using more minimal service description files\&.
.PP
In systemd, if the developer or administrator wants to make sure a service or other unit is activated automatically on boot it is recommended to place a symlink to the unit file in the
\&.wants/
@@ -626,7 +626,7 @@
.RE
.\}
.PP
-This snippet allows automatic installation of the unit files on systemd machines, and optionally allows their installation even on machines lacking systemd\&. (Modification of this snippet for the user unit directory is left as excercise to the reader\&.)
+This snippet allows automatic installation of the unit files on systemd machines, and optionally allows their installation even on machines lacking systemd\&. (Modification of this snippet for the user unit directory is left as an exercise to the reader\&.)
.PP
Additionally, to ensure that
\fBmake distcheck\fR
--- systemd.special.7 2011-03-21 01:08:26.000000000 -0400
+++ /tmp/systemd.special.7 2011-04-19 01:58:25.524603016 -0400
@@ -112,7 +112,7 @@
or
graphical\&.target\&.
.sp
-The default unit systemd starts at bootup can be overriden with the
+The default unit systemd starts at bootup can be overridden with the
\fIsystemd\&.default=\fR
kernel command line option\&.
.RE
@@ -177,7 +177,7 @@
The mail transfer agent (MTA) service\&. Usually this should pull\-in all units necessary for sending/receiving mails on the local host\&.
.sp
systemd automatically adds dependencies of type After for this target unit to all SysV init script service units with an LSB header referring to the
-$mail\-transfer\-argent
+$mail\-transfer\-agent
or
$mail\-transport\-agent
facilities, for compatibility with Debian\&.
@@ -259,13 +259,13 @@
.PP
runlevel2\&.target
.RS 4
-This is a target that is called whever the SysV compatibility code asks for runlevel 2\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
+This is a target that is called whenever the SysV compatibility code asks for runlevel 2\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
multi\-user\&.target\&.
.RE
.PP
runlevel3\&.target
.RS 4
-This is a target that is called whever the SysV compatibility code asks for runlevel 3\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
+This is a target that is called whenever the SysV compatibility code asks for runlevel 3\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
multi\-user\&.target
or
graphical\&.target\&.
@@ -273,7 +273,7 @@
.PP
runlevel4\&.target
.RS 4
-This is a target that is called whever the SysV compatibility code asks for runlevel 4\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
+This is a target that is called whenever the SysV compatibility code asks for runlevel 4\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
multi\-user\&.target
or
graphical\&.target\&.
@@ -281,7 +281,7 @@
.PP
runlevel5\&.target
.RS 4
-This is a target that is called whever the SysV compatibility code asks for runlevel 5\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
+This is a target that is called whenever the SysV compatibility code asks for runlevel 5\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
multi\-user\&.target
or
graphical\&.target\&.
--- systemd-tmpfiles.8 2011-03-21 01:08:26.000000000 -0400
+++ /tmp/systemd-tmpfiles.8 2011-04-19 01:59:34.944603174 -0400
@@ -75,7 +75,7 @@
\fB\-\-create\fR,
\fB\-\-clean\fR, and
\fB\-\-remove\fR
-in one invocation\&. For example, during boot the following command line is executed to ensure that all temporary and volatile directores are removed and created according to the configuration file:
+in one invocation\&. For example, during boot the following command line is executed to ensure that all temporary and volatile directories are removed and created according to the configuration file:
.sp
.if n \{\
.RS 4
