dev-manual: Updated a few occurrences of "dnf" to "DNF"

These depend on context.  In general, "DNF" is the preferred
terminology unless directly referring to an application or such.

(From yocto-docs rev: 29012a8f8e21b964e1ea6d32841dffa8dae7df9f)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2017-05-01 17:34:48 -07:00 committed by Richard Purdie
parent bcf22c0bb6
commit cbea3d8b6b
1 changed files with 3 additions and 3 deletions

View File

@ -9802,12 +9802,12 @@
<listitem><para><emphasis>Be sure your host's firewall
accepts incoming connections from
192.168.7.0/24:</emphasis>
Some of the tests (in particular dnf tests) start
Some of the tests (in particular DNF tests) start
an HTTP server on a random high number port,
which is used to serve files to the target.
The DNF module serves
<filename>${WORKDIR}/oe-rootfs-repo</filename>
so it can run dnf channel commands.
so it can run DNF channel commands.
That means your host's firewall
must accept incoming connections from 192.168.7.0/24,
which is the default IP range used for tap devices
@ -10506,7 +10506,7 @@
</para></listitem>
<listitem><para><emphasis><filename>server_ip</filename>:</emphasis>
The host's IP address, which is
usually used by the "dnf" test
usually used by the DNF test
suite.
</para></listitem>
<listitem><para><emphasis><filename>run(cmd, timeout=None)</filename>:</emphasis>