- 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.
Locally it rendered for me with the title of the target document, however when
deployed it rendered with the filename of the target document. So include the
document titles explicitly instead.
* 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
What this change accomplishes:
1. Move PostgreSql to Database Section
2. Remove Tips and Trips in PostgreSQL and move to the following
3. Add manage-sql-server.adoc and add GUI for Mysql/MariaDB/PostgreSQL
4. Add install information phpPgadmin because in fedora 33 is out of repo.
This is now the second time when rpmconf reverted me
google-chrome-stable.repo file back to version where I have `enabled=0`.
It looks like this package generates the repo file in the post scriplet
and does not mention it in the list of installed files, this probably
tricks rpmconf to do an incorrect action. I would love to investigate
further and maybe file a bug for chrome/chromium, but now that I
finished my upgrade I can't look back why rpmconf thought this file
needs updating - scriplet looks like this:
YUM_REPO_FILE="/etc/yum.repos.d/google-chrome.repo"
install_yum() {
install_rpm_key
if [ ! "$REPOCONFIG" ]; then
return 0
fi
if [ -d "/etc/yum.repos.d" ]; then
cat > "$YUM_REPO_FILE" << REPOCONTENT
[google-chrome]
name=google-chrome
baseurl=$REPOCONFIG/$DEFAULT_ARCH
enabled=1
gpgcheck=1
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
REPOCONTENT
fi
}
It was likely some older version of the package. Anyway, I thought I'd
drop a warning note for others, because I accidentally disabled this
repo which left my Chrome on an old version for about a year until it
websites started warning me about an unsupported version. This is
dangerous, my main browser is Firefox but this could be a security
problem for others.
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>
Use "reboot" consistently, emphasize the immediate no-prompt reboot, mention it's a console terminal, then a second reboot, and clean up step 6 language. This fixes issue #294 and I think is an improvement.
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>
This commit renames the "Adding new fonts in Fedora" file name. This
is done for two reasons:
1. Ensures the following changes are easier to review commit-by-commit
2. Better optimization in URL for search engines (i.e. this page is
about fonts, so using a single word in the URL optimizes for that
specific keyword)
Signed-off-by: Justin W. Flory (he/him) <git@jwf.io>
Many grammatical fixes and edits to clarify meaning. Missing portions of commands or outputs have been populated. Reformatted code snippets for aesthetic consistency.
Edited the Quick Docs landing page to be more user oriented. I moved the
existing instructions about how to contribute to its own page.
Fixes: #265
Signed-off-by: Richard Gregory <richardgrecoson@gmail.com>
Fixed some grammatical issues. About half of the content didn't copy over from the wiki, so I filled the rest in. Note: "this video" link under the subheader "What is bad about patented formats?" leads to an website which seems to have security issues. There is no SSL certificate for that link and my browser prompts me with a warning. I also removed other broken links. The suggestion to use Ogg Vorbis might be outdated, as I tried to visit the site and didn't get a response. I kept the link and content, however, because I'm not expert in this subject and have no alternative to offer.
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>
The instructions included adding symlinks in the system files which we
should not suggest to end users. The Flatpak works fine, so it's much
better that users use that instead of snap.
In the future, if someone can add the snap bits without requiring any
extra system-modification commands, it can be re-added.
Removed reference to Gnome Software - extensions are now primarily installed and managed through extensions.gnome.org or the extensions-tool but not through Gnome Software anymore.
This is a personal preference, but the `fixfiles` command is a
convenient binary in Fedora that ships with SELinux to handle relabels.
It does the same thing, but note the use of the `-B` flag.
From the man pages:
> -B:
> If specified with onboot, this fixfiles will record the current date
> in the /.autorelabel file, so that it can be used later to speed up
> labeling. If used with restore, the restore will only affect files
> that were modified today.
I thought I would share this improvement upstream since I use this page
often, but I prefer this way of running more lean SELinux checks.
Signed-off-by: Justin W. Flory <git@jwf.io>
%{_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}/".)
