The USB port conflict is more generic than just for HPLIP - it affects
even other classic drivers, so let's move it into ipp-usb section.
Additionally, mention the common issue that device sometimes does not
advertise all of its options via driverless protocols.
If --ippserver is specified, output of get-printer-attributes request
from ipptool is created in format compatible with ippeveprinter printer
application, which helps during debugging.
The content in page "Creating RPM Packages"
has been subsumed under "Package Tutorial: GNU Hello"
in the Package Maintainer Docs.
Thus, the page is removed
and all references to it are pointed to the Packaging Tutorial.
"Creating RPM Packages" has one subpage,
which is moved to a top-level page.
In a separate commit for the Package Maintainer Docs,
the url of "Creating RPM Packages" will be listed as an alias
of the "Package Tutorial" so that external links will keep working.
Following the upstream documentation for systemd network target:
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
It is not supposed to be used as an active unit and it cannot be started
directly. Quote from the website:
Note that network.target is a passive unit: you cannot start it directly
and it is not pulled in by any services that want to make use of the
network. Instead, it is pulled in by the network management service
itself. Services using the network should hence simply place an
After=network.target dependency in their unit files, and avoid any
Wants=network.target or even Requires=network.target.
This patch changes the documentation to follow the upstream
recommendation.
- Place a large caution box at the top of the file, warning
users of the outdated information on the page and directing
them to the more current "Using firewalld" quick doc.
- Drop the second and third iptables section partials entirely,
as it's been years since either 'system-config-firewall' or
'system-config-firewall-tui' has been available in the repos.
* Improve messaging regarding N->N+2 upgrades.
* Move some details regarding Rawhide issues to the specific Rawhide wiki page.
This generic guide doesn't need to go into detail about Rawhide issues,
because that makes it harder to read for general users (not interested in
Rawhide). Power users can follow a link.
* Update gnome-software screenshot (more recent, with graphics).
* Clearly state that upgrading using pure `dnf` or `fedora-upgrade` is
unsupported.
* Other small adjustments and clarifications, link fixes. Make section headlines
look consistent across articles (don't capitalize every word).
The current version of the page includes hardcoded, obsolete references
to e.g. Fedora 28, 30, and 31, which can be confusing.
Replace references with attributes, and add a new one, `{NEXTNEXTVER}`
for the branched example.
Signed-off-by: Michel Alexandre Salim <salimma@fedoraproject.org>
The virtio-win docs are out of date, and soon to be even more so with
coming upstream changes to the yum repo. Upstream devs would like to
move the docs closer to the upstream project infrastructure.
Delete most of the content and point at the upstream packaging README.md
https://pagure.io/fedora-docs/quick-docs/issue/327
Signed-off-by: Cole Robinson <crobinso@redhat.com>
Added sudo to lines where needed
Changed "apachectl reload" to "sudo systemctl reload httpd.service"
Added / to the end of /etc/httpd/conf.d
Technical review completed and is now accurate.
Why this change is needed:
With the new default system in BTRF as Defautl for new instalation
this procedure needs updated.
What this change accomplishes:
. Reflect the diferences between rescue a system in a LVM/BTRF file System.
. Remove Sequence Number Warninig in a debug-dracut-problems.adoc
fix ticket: #316
Note: Please don't push .adoc with Warning Messages is quite anoying
