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}/".)
Verification and minor change of " repository for 29." to " repository for release 29." places where it was " 30 version" changed to "version 30"
Otherwise, the page has no errors in the text;
in response to issue #178 - verification of repositories page;
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>
Add information on cleaning old symlinks in /usr in dnf-system-upgrade.adoc.
Fedora includes the symlinks utility, so it is easy to clean the old cruft.
Add information on cleaning old symlinks in /usr in dnf-system-upgrade.adoc.
Fedora includes the symlinks utility, so it is easy to clean the old cruft.
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 ]
Single typographical error correction
* "Prerequisits -> Prerequisites"
* elsewhere in the documentation, "Prerequsites" is spelled correctly
so this is for consistency
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.
I’ve removed the ‘update’ command from the page as ‘update’ is a depreciated alias to ‘upgrade’. I also removed the link to the DNF blog as the link is broken and I wasn’t able to find a suitable replacement
Lastly, I removed the unreviewed message from the page.
* Remove the unreviewed wiki content admonintion
* Remove unnecessary DNF arguments
* Remove references to 'Atomic Host' and replace with Fedora CoreOS and Fedora Silverblue
This is now in sync with
https://fedoraproject.org/wiki/Upgrading so a redirect can now be placed
there.
Again, I'm not sure what is to be done with the translations.
- was pretty good to go, one or two minor cosmetic issues
- left the "upgrade using anaconda" section in, even though it applies
to releases < 17 only. Should this be removed?
This gives info about installing packages using the `rpm` command and is
extremely bad advice. End users should be using the standard package
managers (DNF) to install packages and not resort to `rpm` unless as a
last resort. So, this documentation does not fit into user-end
quickdocs.
Fixes#102
- 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
When using the Nvidia proprietary driver from `rpmfusion-nonfree-nvidia-driver`, the `nvidia-fallback` service is disabled by default but it is started as a dependency. The correct way to prevent it from starting is to mask it.
Since the 3rd party policy adoption, the RPM Fusion community repository was preferred
over other single maintained repository.
See https://pagure.io/fedora-workstation/issue/43
This change switch the preferred method to install the nvidia driver.
Signed-off-by: Nicolas Chauvet <kwizart@gmail.com>
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)
