* systemd (since v209) uses only one library (when compiled
without --enable-compat-libs)
* all systemd build-sys stuff is merged into HAVE_SYSTEMD
(automake) and HAVE_LIBSYSTEMD (C macro) now
* all is controlled by --with-systemd, default is to automatically
check for systemd libs
* no more --enable-socket-activation and --enable-journald
Signed-off-by: Karel Zak <kzak@redhat.com>
-- changed to \(en (an en-dash) if it is a dash (pause, separation)
- changed to \- if it indicates an option
A full stop (.), that begins or ends a string, protected with \&
Space between sentences corrected to two word spaces
-- changed to \-\- if it indicates an option
Signed-off-by: Karel Zak <kzak@redhat.com>
The unit "MB" is ambigous. Use "MiB" if "M" does not mean 10^6.
Otherwise add "(M = 10^6)" after it.
Changes:
Unpaddable space (\ ) added between a number and an unit. A nuber
and a unit are not one word. Is "16MB" written "sixteenmegabytes"?
Signed-off-by: Karel Zak <kzak@redhat.com>
- changed to \- if it means an option
A full stop (.), that begins or ends a string, protected with \&
No line adjustment used for section "SEE ALSO" (.na/.ad)
Signed-off-by: Karel Zak <kzak@redhat.com>
A full stop (.), that begins or ends a string, protected with \&
A space between a number and an unit changed to an unpaddable space
"\ "
Signed-off-by: Karel Zak <kzak@redhat.com>
- between numbers changed to \(en if it means a range
A full stop (.), that begins or ends a string, protected with \&
Signed-off-by: Karel Zak <kzak@redhat.com>
The word "kilobytes" is ambiguous. Change it to "kibibytes" if kilo
does not mean 1000. Otherwise add "(1000 B)" after it.
A string, that begins or ends with a full stop (.), protected with \&
- changed to \- if it shows an option
-- change to \(en if it means a dash (pause, separation)
Space between sentences is two word spaces in *roff. Thus it is
better to begin each sentence on a new line when the file contains
formatting commands
--- changed to \(en if it means a dash (pause, separation)
Punctuation separated from a word with a space, if it is an argument
to a macro like "BR" (two font styles used alternately)
Adjusting inhibited for the section "SEE ALSO" with ".na/.ad"
Signed-off-by: Karel Zak <kzak@redhat.com>
\- changed to - (code "hyphen-minus", rendered with the glyph hyphen
in troff) if it is a part of a compound name. A minus is not used in
words. People using UTF-8 and copy-and-pase can(?) (may?) use "info",
"man --ascii" or the command "man" should have an option to display the
- in names of options with the code (character name) "hyphen-minus"
(u002D) instead of "u2010" (code (character) name "hyphen")
Signed-off-by: Karel Zak <kzak@redhat.com>
Macro, that alternately changes the input between two font styles,
changed to the macro for one font style change, if there is only one
argument
Text string, that begins or ends with a full stop (.) protected with \&
-- changed to \-\- if it is an option
- changed to \(en if it is a dash (pause, seperation)
Signed-off-by: Karel Zak <kzak@redhat.com>
I forgot to add the patch to the attachment.
Additional changes to "Changes:"
" \(em " changed to " \(en ", as the em-dash with a word space on each
side is to long (troff)
".na/.ad" is not used but .nf/.fi for a long command line and it is
split into two lines
Word "illegal" is changed to "invalid"
Word "hyphen-separated" is changed to '"hyphen-minus"-separated' as
the meaning is the code and not the glyph (on the command line) (beware
of UTF-8)
--
Bjarni I. Gislason
fstab:
UUID=nonexist /mnt/nonexist1 ext4 nofail 0 1
# mount -av
mount: can't find UUID=nonexist
.. this is bug of course.
Reported-by: Patrick McLean <chutzpah@gentoo.org>
Signed-off-by: Karel Zak <kzak@redhat.com>
Now the "nofail" affects warnings warning messages only. That's wrong
and regression (against original non-libmount version). The nofail has
to control return code too.
Reported-by: Patrick McLean <chutzpah@gentoo.org>
Signed-off-by: Karel Zak <kzak@redhat.com>
Return 64 (aka SOME_OK) when more than process specified and the
operation success only for subset of the processes.
# kill -s 0 firefox mutt xxx; echo $?
kill: cannot find process "xxx"
64
We already use this concept for chcpu(8) or mount(8).
Signed-off-by: Karel Zak <kzak@redhat.com>
* 'kill' of git://github.com/kerolasa/lelux-utiliteetit:
kill: move sigqueue inputs to control struct
kill: add parse_arguments() function
kill: tell what is wrong rather than output usage()
kill: use control structure to pass user input to functions
kill: deprecat invocation as 'pid' command name
kill: make usage() not to return
kill: move magic numbers in beginning of the file
kill: flip all comparions to be in smaller - greater order
kill: fix coding style
The function is no critical for fdisk functionality. The SUN label
verification will check for less issues. All the verification code is
optional ('v' fdisk command).
Signed-off-by: Karel Zak <kzak@redhat.com>
As of linux 3.14, the initramfs device will have both major and
minor 0, causing our paranoia check to fail. Make this version agnostic
by checking the filesystem type, rather than a device number.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
* rename flags functions to scols_table_enable_*
* rename *_no_foo() functions to _nofoo()
* output formats are mutually exclusive, so don't use flags there
* don't assume symbols in scols_new_table(), use scols_table_set_symbols()
Signed-off-by: Karel Zak <kzak@redhat.com>
Karel Zak
Anton Blanchard
Jonathan Liu
Thomas Bächler
Ondrej Oprala
Bjarni Ingi Gislason
Dave Reisner