- 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
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.
* Simplify list of required packages (and add `grubby`).
* Move Disabled -> Enforcing steps from `changing-to-enforcing-mode` to
`enabling-selinux`.
* In `changing-to-enforcing-mode`, use the correct procedure based on
whether SELinux is currently Permissive or Disabled.
* Add step for ensuring that filesystem is relabeled when re-enabling
SELinux.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
The kernel functionality that allowed to disable SELinux by changing
/etc/selinux/config is now deprecated and will be removed in F34 [1].
While setting SELINUX=Disabled will still lead to a similar state even
after the removal, it is better to guide users to disable SELinux via
kernel boot parameters, which will actually disable SELinux completely
(as in no SElinux code is executed by the kernel).
[1] https://fedoraproject.org/wiki/Changes/Remove_Support_For_SELinux_Runtime_Disable
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
This commit refactors the content for the fonts page. I focused on
organization and layout. I restructured the previous layout from a more
command line vs. GUI approach, and instead emphasized "packaged vs.
unpackaged" fonts.
I was inspired to rework this page because I went looking for it
recently, and the search engine led me here. :-)
Signed-off-by: Justin W. Flory (he/him) <git@jwf.io>
So that users can configure their VMs appropriately and are not caught
by surprise if they encounter driver signature errors on boot.
Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
%{_bindir} etc. already starts with a slash.
There is no need to put a slash after %{buildroot}.
(Except when pointing to the literal root of the buildroot and using just "%{buildroot}/".)
https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/ had
"Untitled" in the title of the webpage. I removed it from the partial
and added it to the main page, this should fix it.
Signed-off-by: JJ Asghar <awesome@ibm.com>
Signed-off-by: JJ Asghar <jjasghar@gmail.com>
What this change accomplishes:
* Ask Fedora about Java -> point out to https://ask.fedoraproject.org/en/questions/scope:all/sort:activity-desc/tags:java/page:1/ instead of https://ask.fedoraproject.org/tags/java
* Add it switch between Version
* Add Version, LTS, and Latest
* Where this premise come from? Do NOT use Oracle rpms as these are NOT compatible with fedora/openjdk packages, actually is very well compatible and works with fedora rpm format package, and I install it without any problem or message...
[Ticket: #160 ]
NOTE: I did not remove the unreviewed warning from the parent page ‘Creating and using a live installation image’ as the Live CD section has the notice ‘needs modularization’ and I was confused by what it was asking.
- Remove Caution
- Review and Check View Log Information via Systemctl
- Add Using journalctl to View Log Information for a Specific Service
- Add to know more about systemd -> understanding-and-administering-systemd
- Sections can be moved up one level replaceing rsyslog
- Improve con_viewing-logs.adoc with adding some usefull information
- Change in using nano and vim to you can use favourite text editor
- Remove rsyslog completly
- Add -b and --list-boots if the user needs flter log messages for the current boot or view old log's
- instead of using bold for commands and file/folder names, maybe make them monospace too. That does'nt work in _NOTE_
- "Using the command line to open log files in a text editor" -> "Use a text editor" as a separate section.
- Observe a Warning when editing view_log.adoc and there is a PR in ASCCIDOCTOR
https://github.com/asciidoctor/asciidoctor/issues/2855.
[Ticket: 107] - https://pagure.io/fedora-docs/quick-docs/issue/107
Unfortunately it's not moral (if even legal) to advertise a license
violation. Spotify does not allow the client application to be distributed
elsewhere than by spotify.com, this is a well-known issue over the web.
Here are the exact license terms:
http://www.spotify.com/se/legal/end-user-agreement/
This commit also fixes the RPM Fusion documentation using lpf framework
to workaround with particular issue.
(lpf is a fedora package that show the license, download and re-package
a given software).
Please also spell the project as appropriate:
- RPM Fusion (by default)
or
- rpmfusion (when space within name is not possible)
