machinery.1.html in machinery-tool-1.15.0

- old
+ new

@@ -239,27 +239,41 @@
 scope to <code>packages</code>. This will output only the requested information.</p>
 
 <p>Machinery supports the following scopes:</p>
 
 <ul>
-<li><p>os</p>
+<li>os</li>
+</ul>
 
+
 <p>Contains information about the operating system, name, version, and
-architecture of the inspected system.</p></li>
-<li><p>packages</p>
+architecture of the inspected system.</p>
 
+<ul>
+<li>packages</li>
+</ul>
+
+
 <p>Contains information on all installed RPM packages installed on the
-inspected system.</p></li>
-<li><p>patterns</p>
+inspected system.</p>
 
+<ul>
+<li>patterns</li>
+</ul>
+
+
 <p>Contains all patterns installed on the inspected system. A pattern is a
 collection of software packages.
 The meaning of software patterns depends on the package manager of the
 distribution. Therefore, the pattern scope on SUSE based systems uses the
-<code>zypper</code> command to obtain the information about installed pattern names.</p></li>
-<li><p>repositories</p>
+<code>zypper</code> command to obtain the information about installed pattern names.</p>
 
+<ul>
+<li>repositories</li>
+</ul>
+
+
 <p>Contains all information about software repositories configured on the
 inspected system. The information about repositories depends on the package
 manager of the distribution. Thus on SUSE-based systems the <code>zypper</code> command
 is used. Machinery collects the following information from each configured repository:</p>
 
@@ -275,45 +289,65 @@
 <li><p>A boolean flag that indicates if packages which would be installed from
 this repository should be checked by their gpg key or not.</p></li>
 <li><p>A numeric value for a priority. The priority of a repository is compared
 to the priorities of all other activated repositories. Values can
 range from 1 (highest) to 99 (lowest, default).</p></li>
+<li><p>users</p></li>
 </ul>
-</li>
-<li><p>users</p>
 
+
 <p>Contains information about the system users including user and group ids,
 login information, such as password hashes and - if available - additional
-password properties.</p></li>
-<li><p>groups</p>
+password properties.</p>
 
+<ul>
+<li>groups</li>
+</ul>
+
+
 <p>Contains information about the system groups such as group attributes and the
-list of group members.</p></li>
-<li><p>services</p>
+list of group members.</p>
 
+<ul>
+<li>services</li>
+</ul>
+
+
 <p>Services are applications running in the background doing continuous work
 or waiting for requests to do work.
 The scope determines which services are configured to be started in which
 runlevel. It uses the <code>chkconfig</code> command to obtain that information.
 The xinetd services that are also displayed by <code>chkconfig</code> are switched
-on/off by editing config files and are ignored in this context.</p></li>
-<li><p>config_files</p>
+on/off by editing config files and are ignored in this context.</p>
 
+<ul>
+<li>config_files</li>
+</ul>
+
+
 <p>Contains all configuration files which have been changed since they were
 installed.
 Configuration files are all those files which are marked as such in the
 package which has installed them. A configuration file change is reported
 if its content or its attributes like Linux permission bits or ownership
-have changed.</p></li>
-<li><p>changed_managed_files</p>
+have changed.</p>
 
+<ul>
+<li>changed_managed_files</li>
+</ul>
+
+
 <p>Contains the names and contents of all non-configuration files which have
 been changed compared to the files in the package. A file change is reported
 if its content or its attributes like Linux permission bits or ownership
-have changed.</p></li>
-<li><p>unmanaged_files</p>
+have changed.</p>
 
+<ul>
+<li>unmanaged_files</li>
+</ul>
+
+
 <p>Contains the names and contents of all files which are not part of any RPM
 package. The list of unmanaged files contains only plain files and
 directories. Special files like device nodes, named pipes and Unix domain
 sockets are ignored. The directories <code>/tmp</code>,  <code>/var/tmp</code>, <code>/.snapshots/</code>,
 <code>/var/run</code> and special mounts like procfs and sysfs are ignored, too.
@@ -323,12 +357,10 @@
 <p>Meta data information of unmanaged files is only available if the files were
 extracted during inspection.</p>
 
 <p>Using the <code>--extract-unmanaged-files</code> option, the files are transferred from
 the system and stored in the system description. Depending on the content of
-the inspected system, the amount of data stored may be huge.</p></li>
-</ul>
-
+the inspected system, the amount of data stored may be huge.</p>
 
 <h3 id="System-Description">System Description</h3>
 
 <p>The System Description format and file structure is documented in the machinery
 wiki: <a href="https://github.com/SUSE/machinery/wiki/System-Description-Format" data-bare-link="true">https://github.com/SUSE/machinery/wiki/System-Description-Format</a></p>