Fix antora build warnings
This commit is contained in:
Brian (bex) Exelbierd
parent
cf5acc8f3a
commit
f854c719a9
51 changed files with 259 additions and 192 deletions
|
|
@ -3,7 +3,7 @@
|
|||
|
||||
Use this guide for information about the specific macros in a `.spec` file.
|
||||
|
||||
NOTE: You can use the macros `%{name}`, `%{version}` and `%{release}` to refer to the Name, Version and Release tags respectively. When you change the tag, the macros automatically update to use the new value.
|
||||
NOTE: You can use the macros `%\{name}`, `%\{version}` and `%\{release}` to refer to the Name, Version and Release tags respectively. When you change the tag, the macros automatically update to use the new value.
|
||||
|
||||
`Name`::
|
||||
Add the base name of the package, which must match the `.spec` file name. Follow the http://fedoraproject.org/wiki/Packaging:Naming[Package Naming Guidelines] and write the file name in lower-case letters.
|
||||
|
|
@ -12,7 +12,7 @@ Add the base name of the package, which must match the `.spec` file name. Follow
|
|||
Add the upstream version number. See http://fedoraproject.org/wiki/Packaging:Versioning[Package Versioning]. If the version contains tags that are non-numeric, you might need to include the non-numeric characters in the `Release` tag. If upstream uses full dates to distinguish versions, consider using version numbers of the form. For example, `yy.mm[dd]` where `2008-05-01` becomes `8.05`.
|
||||
|
||||
`Release`::
|
||||
Set the initial value to `1%{?dist}`. Increment the number every time you release a new package for the same version of software. When a new upstream version is released, change the `Version` tag to match and reset the `Release` number to `1`. For more information, see the http://fedoraproject.org/wiki/Packaging:Versioning[Versioning Guide] of the packaging guidelines.
|
||||
Set the initial value to `1%\{?dist}`. Increment the number every time you release a new package for the same version of software. When a new upstream version is released, change the `Version` tag to match and reset the `Release` number to `1`. For more information, see the http://fedoraproject.org/wiki/Packaging:Versioning[Versioning Guide] of the packaging guidelines.
|
||||
|
||||
`Summary`::
|
||||
Enter a brief, one-line summary of the package. Use American English. Do not end with a period.
|
||||
|
|
@ -34,7 +34,7 @@ NOTE: Do not add a link to the original source code. Add the link to the source
|
|||
`Source0`::
|
||||
Enter the full URL for the compressed archive that contains the original, pristine source code, as upstream released it. "`Source`" is synonymous with "`Source0`".
|
||||
+
|
||||
The full URL basename is used when looking in the `SOURCES` directory. If possible, embed `%{name}` and `%{version}`, so that changes to the go to the right place. Preserve the timestamps when downloading source files. For more information, see http://fedoraproject.org/wiki/Packaging:Guidelines#Timestamps[Preserve timestamps].
|
||||
The full URL basename is used when looking in the `SOURCES` directory. If possible, embed `%\{name}` and `%\{version}`, so that changes to the go to the right place. Preserve the timestamps when downloading source files. For more information, see http://fedoraproject.org/wiki/Packaging:Guidelines#Timestamps[Preserve timestamps].
|
||||
+
|
||||
If there is more than one source, name them `Source1`, `Source2`.
|
||||
+
|
||||
|
|
@ -47,7 +47,7 @@ Enter the name of the first patch to apply to the source code. If you must patch
|
|||
If you package files that are architecture-independent, for example shell scripts, data files, then add `BuildArch: noarch`. The architecture for the binary RPM is then `noarch`.
|
||||
|
||||
`BuildRoot`::
|
||||
This is now redundant in Fedora and is only needed for EPEL5. By default, the build root is placed in `%{_topdir}/BUILDROOT/`.
|
||||
This is now redundant in Fedora and is only needed for EPEL5. By default, the build root is placed in `%\{_topdir}/BUILDROOT/`.
|
||||
+
|
||||
In EPEL5, this is where files are installed during the %install process (after the %build process).
|
||||
|
||||
|
|
@ -75,13 +75,13 @@ Add script commands to "prepare" the program. For example, to extract the progra
|
|||
Add script commands to compile the program and get it ready for installing. The program must come with instructions on how to do this.
|
||||
|
||||
`%install`::
|
||||
Add script commands to "install" the program. The commands must copy the files from the `BUILD` directory `%{_builddir}` into the buildroot directory, `%{buildroot}`.
|
||||
Add script commands to "install" the program. The commands must copy the files from the `BUILD` directory `%\{_builddir}` into the buildroot directory, `%\{buildroot}`.
|
||||
|
||||
`%check`::
|
||||
Add script commands to "test" the program. This is run after the `%install` procedure, so place it there if you have this section. Often it contains `make test` or `make check`. This is separated from `%build` so that people can skip the self-test if they desire.
|
||||
|
||||
`%clean`::
|
||||
Note that this section is now redundant in Fedora and is only necessary for EPEL. Typically this contains only the following command: `rm -rf %{buildroot}`.
|
||||
Note that this section is now redundant in Fedora and is only necessary for EPEL. Typically this contains only the following command: `rm -rf %\{buildroot}`.
|
||||
|
||||
`%files`::
|
||||
Add the list of files to be installed.
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ The libvirt default storage pool is located at /var/lib/libvirt/images - which i
|
|||
|
||||
You have several disk storage options for your VM. While it's outside the scope of this article to discuss these in detail, the following are a few common options. These examples use 20G as the upper limit for disk size, but you can adjust this size to fit your needs.
|
||||
|
||||
[Note]
|
||||
[NOTE]
|
||||
====
|
||||
Again, you do not need to manually allocate storage using the example options shown below if you specify the size parameter in the virt-install example shown below.
|
||||
====
|
||||
|
|
@ -88,7 +88,7 @@ Finally, run the virt-install command using the following format (adjusting para
|
|||
--noautoconsole
|
||||
----
|
||||
|
||||
[Note]
|
||||
[NOTE]
|
||||
====
|
||||
Note: For the graphics parameter, we're setting the vnc listener to localhost because it's more secure to tunnel your VNC connection through SSH so that you don't expose VNC to everyone with access to the network.
|
||||
====
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ mkdir -p %{buildroot}/%{_bindir}
|
|||
install -p -m 755 %{SOURCE0} %{buildroot}/%{_bindir}
|
||||
----
|
||||
+
|
||||
NOTE: In this example, we use the following three macros: `%{buildroot}`, `%{_bindir}`, and `%{SOURCE0}`. This method ignores the origin of the files and directories and focuses on the destination of the files. Without `%{buildroot}` the files might install directly onto your development machine. This is not recommended, especially if you run as root. For more information on macros and `.spec` file entries, see xref:con_rpm_spec_file_overview[].
|
||||
NOTE: In this example, we use the following three macros: `%\{buildroot}`, `%\{_bindir}`, and `%\{SOURCE0}`. This method ignores the origin of the files and directories and focuses on the destination of the files. Without `%\{buildroot}` the files might install directly onto your development machine. This is not recommended, especially if you run as root. For more information on macros and `.spec` file entries, see xref:con_rpm_spec_file_overview[].
|
||||
+
|
||||
. To tell RPM about the file, enter the following information to the `%files` section:
|
||||
+
|
||||
|
|
@ -69,7 +69,7 @@ NOTE: In this example, we use the following three macros: `%{buildroot}`, `%{_bi
|
|||
%{_bindir}/howdy
|
||||
----
|
||||
+
|
||||
NOTE: In general, the `%files` section is about files you have installed into the buildroot. You do not use the `%{buildroot}` macro when listing files there.
|
||||
NOTE: In general, the `%files` section is about files you have installed into the buildroot. You do not use the `%\{buildroot}` macro when listing files there.
|
||||
+
|
||||
. Save your edits and to run a local build, enter the following command:
|
||||
+
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
:experimental:
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: adding-new-fonts-fedora
|
||||
|
||||
|
||||
[[adding-new-fonts-fedora]]
|
||||
|
|
@ -9,3 +11,5 @@ The default installation of the Fedora Linux (Fedora) includes several basic fon
|
|||
include::{partialsdir}/proc_adding-new-fonts-as-superuser.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_adding-new-fonts-as-user.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
:experimental:
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: adding-or-removing-software-respositories-in-fedora
|
||||
|
||||
[id='adding-or-removing-software-repositories-in-fedora']
|
||||
= Adding or removing software repositories in Fedora
|
||||
|
|
@ -10,3 +12,5 @@ include::{partialsdir}/proc_adding-repositories.adoc[leveloffset=+1]
|
|||
include::{partialsdir}/proc_enabling-repositories.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_disabling-repositories.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -11,7 +11,13 @@ include::{partialsdir}/attributes.adoc[]
|
|||
|
||||
// The following line is necessary to allow assemblies be included in other
|
||||
// assemblies. It restores the `context` variable to its previous state.
|
||||
:parent-context: {context}
|
||||
|
||||
// The `context` attribute enables module reuse. Every module's ID
|
||||
// includes {context}, which ensures that the module has a unique ID even if
|
||||
// it is reused multiple times in a guide.
|
||||
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: assembly_installing-plugins-for-playing-movies-and-music
|
||||
|
||||
// The file name and the ID are based on the assembly title.
|
||||
// For example:
|
||||
|
|
@ -31,11 +37,6 @@ include::{partialsdir}/attributes.adoc[]
|
|||
[id='assembly_installing-plugins-for-playing-movies-and-music_{context}']
|
||||
= Installing plugins for playing movies and music
|
||||
|
||||
// The `context` attribute enables module reuse. Every module's ID
|
||||
// includes {context}, which ensures that the module has a unique ID even if
|
||||
// it is reused multiple times in a guide.
|
||||
:context: assembly_installing-plugins-for-playing-movies-and-music
|
||||
|
||||
As a Fedora user and system administrator, you can use these steps to install additional multimedia plugins that enable you to play various video and audio types.
|
||||
|
||||
WARNING: If you live in a country where software patents apply, such as in the United States or in Japan, you need to obtain multimedia codecs from a source that legally distributes patented software in your country. For example, see the Fluendo Codec Pack: link:https://fluendo.com/en/products/enterprise/fluendo-codec-pack/[].
|
||||
|
|
@ -82,4 +83,5 @@ include::{partialsdir}/con_the-purpose-of-rpm-fusion.adoc[leveloffset=+1]
|
|||
|
||||
// The following line is necessary to allow assemblies be included in other
|
||||
// assemblies. It restores the `context` variable to its previous state.
|
||||
:context: {parent-context}
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: bootloading-with-grub2
|
||||
[id='bootloading-with-grub2']
|
||||
= Bootloading with GRUB2
|
||||
|
||||
|
|
@ -34,3 +36,5 @@ include::{partialsdir}/proc_enabling-serial-console-grub.adoc[leveloffset=+1]
|
|||
== Additional resources
|
||||
|
||||
* http://www.gnu.org/software/grub/manual/grub.html
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
include::{partialsdir}/attributes.adoc[]
|
||||
include::{partialsdir}/3rdparty-message.adoc[]
|
||||
|
||||
[[description]]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
:experimental:
|
||||
:parent-context: {context}
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: changing-selinux-states-and-modes
|
||||
|
||||
// NOTE (TODO): several links (URLs) in the included modules could be replaced with URLs when the appropriate docs become available on fp.org
|
||||
|
||||
|
|
@ -16,4 +17,5 @@ include::{partialsdir}/proc_changing-to-enforcing-mode.adoc[leveloffset=+2]
|
|||
include::{partialsdir}/proc_disabling-selinux.adoc[leveloffset=+1]
|
||||
include::{partialsdir}/ref_changing-selinux-modes-at-boot-time.adoc[leveloffset=+1]
|
||||
|
||||
:context: {parent-context}
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: configuring-ip-networking-with-nmcli
|
||||
[id='Configuring-networking-with-nmcli']
|
||||
= Configuring IP networking with nmcli
|
||||
|
||||
|
|
@ -10,3 +12,5 @@ include::{partialsdir}/proc_Brief-selection-of-nmcli-examples.adoc[leveloffset=+
|
|||
include::{partialsdir}/con_Understanding-the-nmcli-options.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_Configuring-networking-with-nmcli.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,6 +1,10 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: configuring-x-window-system-using-the-xorg-conf-file
|
||||
[id='configuring-x-window-system-using-the-xorg-conf-file']
|
||||
= Configuring X Window System using the xorg.conf file
|
||||
|
||||
include::{partialsdir}/con_xorg-conf.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_creating_xorg_conf.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
[id='configuring-xorg-as-default-gnome-session']
|
||||
= Configuring Xorg as the default GNOME session
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: xorg
|
||||
|
||||
Wayland is the default GNOME display server. If GNOME freezes, or some applications do not function correctly in Wayland, you can choose to run GNOME in X11.
|
||||
|
|
@ -13,3 +14,5 @@ include::{partialsdir}/proc_configuring-xorg-as-default-gnome-session.adoc[level
|
|||
. link:https://docs.fedoraproject.org/f27/system-administrators-guide/Wayland.html[Wayland Display Server in the System Administrator's Guide]
|
||||
|
||||
. link:https://wayland.freedesktop.org/[Wayland @ freedesktop.org]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: creating-gpg-keys
|
||||
= Creating GPG Keys
|
||||
:experimental:
|
||||
|
||||
|
|
@ -65,3 +67,5 @@ include::{partialsdir}/proc_revoking-gpg-keys.adoc[leveloffset=+1]
|
|||
* http://en.wikipedia.org/wiki/Public-key_cryptography[Wikipedia - Public Key Cryptography]
|
||||
|
||||
See a typo, something missing or out of date, or anything else which can be improved? Edit this document at https://pagure.io/fedora-docs/quick-docs[quick-docs's git repository].
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ $ rpmbuild -ba hello.spec
|
|||
|
||||
It will complain and list the unpackaged files, i.e. the files that would be installed in the system that weren't declared as belonging to the package.
|
||||
We need to declare them in the `%files` section.
|
||||
Do not hardcode names like `/usr/bin/`, but use macros, like `%{_bindir}/hello` instead.
|
||||
Do not hardcode names like `/usr/bin/`, but use macros, like `%\{_bindir}/hello` instead.
|
||||
The manual pages should be declared in the `%doc` subsection:
|
||||
|
||||
....
|
||||
|
|
@ -137,9 +137,9 @@ This is an iterative process; after editing the `.spec` file, rerun `rpmbuild`.
|
|||
Since our program uses translations and internationalization, we are seeing a lot of undeclared i18 files.
|
||||
The link:https://fedoraproject.org/wiki/Packaging:Guidelines#Handling_Locale_Files[recommended method] to declare them is:
|
||||
|
||||
* find the filenames in the `%install` step: `%find_lang %{name}`
|
||||
* find the filenames in the `%install` step: `%find_lang %\{name}`
|
||||
* add the required build dependencies: `BuildRequires: gettext`
|
||||
* use the found filenames `%files -f %{name}.lang`
|
||||
* use the found filenames `%files -f %\{name}.lang`
|
||||
|
||||
If the program uses GNU `info` files, you need to make sure the installation and uninstallation of the package does not interfere with other software on the system, by using this boilerplate:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,12 @@
|
|||
:experimental:
|
||||
|
||||
:parent-context: {context}
|
||||
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: using-parted
|
||||
[id='disk-partition-in-linux-{context}']
|
||||
= Creating a disk partition in Linux
|
||||
:context: using-parted
|
||||
|
||||
include::{partialsdir}/con_disk-partition-linux.adoc[leveloffset=+1]
|
||||
include::{partialsdir}/proc_creating-a-disk-partition-in-linux.adoc[leveloffset=+1]
|
||||
include::{partialsdir}/ref_help-mkpart.adoc[leveloffset=+1]
|
||||
|
||||
:context: {parent-context}
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: creating-an-using-a-live-installation-image
|
||||
= Creating and using a live installation image
|
||||
|
||||
include::{partialsdir}/proc_downloading-fedora.adoc[leveloffset=+1]
|
||||
|
|
@ -9,3 +11,5 @@ include::{partialsdir}/proc_booting-from-usb-sticks.adoc[leveloffset=+1]
|
|||
include::{partialsdir}/proc_troubleshooting-live-usb.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_creating-and-using-live-cd.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: creating-rpm-packages
|
||||
[id='creating-rpm-packages']
|
||||
= Creating RPM packages
|
||||
|
||||
|
|
@ -10,3 +12,5 @@ include::{partialsdir}/proc_rpm_preparing_your_system.adoc[leveloffset=+1]
|
|||
include::{partialsdir}/proc_rpm_creating_an_rpm.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/con_rpm_spec_file_overview.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: creating-windows-virtual-machines-using-virtio-drivers
|
||||
[id='creating-windows-virtual-machines-using-virtio-drivers']
|
||||
= Creating Windows virtual machines using virtIO drivers
|
||||
|
||||
|
|
@ -31,3 +33,5 @@ include::{partialsdir}/proc_filing-virtio-win-bugs.adoc[leveloffset=+1]
|
|||
* Spice guest tools installer code: http://cgit.freedesktop.org/~teuf/spice-nsis/
|
||||
* spice-guest-tools downloads: http://www.spice-space.org/download/binaries/spice-guest-tools/
|
||||
* Fedora virtio-win build scripts: https://github.com/crobinso/virtio-win-pkg-scripts
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: disabling-automatic-screenlock
|
||||
include::{partialsdir}/proc_disabling-gnome-screenlock.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: displaying-user-prmopt-on-gnome-login-screen
|
||||
:md: en-US/modules
|
||||
|
||||
include::{partialsdir}/proc_displaying_user_prompt_on_gnome_login_screen.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -45,12 +45,10 @@ initial creation of Rules chains.
|
|||
__TOC__
|
||||
|
||||
[[cli-command-line-interface]]
|
||||
CLI (command line interface)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== CLI (command line interface)
|
||||
|
||||
[[hot-changes-to-iptables-rules]]
|
||||
Hot changes to iptables Rules
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== Hot changes to iptables Rules
|
||||
|
||||
The following procedures allow changes in the behaviour of the firewall
|
||||
while it is running.
|
||||
|
|
@ -59,8 +57,7 @@ Read the man pages for iptables (man iptables) for further explanations
|
|||
and more sophisticated Rules examples.
|
||||
|
||||
[[listing-rules]]
|
||||
Listing Rules
|
||||
+++++++++++++
|
||||
==== Listing Rules
|
||||
|
||||
Current running iptables Rules can be viewed with the command
|
||||
|
||||
|
|
@ -96,8 +93,7 @@ specified allowing ssh, the Rule to reject is applied and the later Rule
|
|||
to accept the ssh connection is not.
|
||||
|
||||
[[appending-rules]]
|
||||
Appending Rules
|
||||
+++++++++++++++
|
||||
==== Appending Rules
|
||||
|
||||
The following adds a Rule at the end of the specified chain of iptables:
|
||||
|
||||
|
|
@ -123,8 +119,7 @@ Notice the last line in chain INPUT. There are now five Rules in that
|
|||
chain.
|
||||
|
||||
[[deleting-rules]]
|
||||
Deleting Rules
|
||||
++++++++++++++
|
||||
==== Deleting Rules
|
||||
|
||||
To delete a Rule, you must know its position in the chain. The following
|
||||
example deletes an existing Rule created earlier that is currently in
|
||||
|
|
@ -148,8 +143,7 @@ target prot opt source destination
|
|||
....
|
||||
|
||||
[[inserting-rules]]
|
||||
Inserting Rules
|
||||
+++++++++++++++
|
||||
==== Inserting Rules
|
||||
|
||||
Create a Rule at the top (first) position:
|
||||
|
||||
|
|
@ -177,8 +171,7 @@ the third rule you specify the number 3. Afterward, the existing Rule
|
|||
will then be in the fourth position in the chain.
|
||||
|
||||
[[replacing-rules]]
|
||||
Replacing Rules
|
||||
+++++++++++++++
|
||||
==== Replacing Rules
|
||||
|
||||
Rules may be specified to replace existing Rules in the chain.
|
||||
|
||||
|
|
@ -206,8 +199,7 @@ target prot opt source destination
|
|||
....
|
||||
|
||||
[[flushing-rules]]
|
||||
Flushing Rules
|
||||
++++++++++++++
|
||||
==== Flushing Rules
|
||||
|
||||
To flush or clear iptables Rules, use the *--flush*, *-F* option :
|
||||
|
||||
|
|
@ -225,8 +217,7 @@ Example to flush Rules in the *OUTPUT* chain :
|
|||
....
|
||||
|
||||
[[making-changes-persistent]]
|
||||
Making changes persistent
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== Making changes persistent
|
||||
|
||||
The iptables Rules changes using CLI commands will be lost upon system
|
||||
reboot. However, iptables comes with two useful utilities:
|
||||
|
|
@ -316,8 +307,7 @@ useful, if you want to know how many packets were captured for a
|
|||
specific rule.
|
||||
|
||||
[[tui-text-based-user-interface]]
|
||||
TUI (text-based user interface)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== TUI (text-based user interface)
|
||||
|
||||
There is two ways to managing iptables rules with a text-based user
|
||||
interface, either using *setup* or *system-config-firewall-tui*. Using
|
||||
|
|
@ -422,12 +412,10 @@ Select *Yes* if the configuration you made fits to you and exit
|
|||
interface, or *No* to go back to the firewall configuration screen.
|
||||
|
||||
[[gui]]
|
||||
GUI
|
||||
~~~
|
||||
== GUI
|
||||
|
||||
[[red-hat-gui-configuration-tool]]
|
||||
Red Hat GUI configuration tool
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== Red Hat GUI configuration tool
|
||||
|
||||
GUI interface allow you exactly the same thing that TUI interface, but
|
||||
it is more friendly usable.
|
||||
|
|
@ -500,8 +488,7 @@ and _Custom Rules_' have exactly the same effect than in TUI interface.
|
|||
When configuration fits to you, just click on the *Apply* button.
|
||||
|
||||
[[others-gui]]
|
||||
Others GUI
|
||||
^^^^^^^^^^
|
||||
=== Others GUI
|
||||
|
||||
There are others GUI available to configure iptables rules.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,8 +33,7 @@ with the following macro:
|
|||
|
||||
|
||||
[[scope]]
|
||||
Scope
|
||||
~~~~~
|
||||
== Scope
|
||||
|
||||
Fedora tries to make various desktop environments available to its
|
||||
users. Since Fedora tries to
|
||||
|
|
@ -49,8 +48,7 @@ discussions on this setting, please talk to the relevant DE upstream.
|
|||
Fedora does not intend to make any changes to upstream defaults.*
|
||||
|
||||
[[desktop-configurations]]
|
||||
Desktop configurations
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Desktop configurations
|
||||
|
||||
This wiki page has more information about
|
||||
link:Input_device_configuration[Input Device configuration]. An example
|
||||
|
|
@ -58,8 +56,7 @@ xorg.conf.d snippet to enable tapping is given
|
|||
Input_device_configuration#Example:_Tap-to-click[here].
|
||||
|
||||
[[gnome]]
|
||||
GNOME
|
||||
^^^^^
|
||||
=== GNOME
|
||||
|
||||
The "*mouse and touchpad*" utility can be used to enable tapping and set
|
||||
scrolling options in GNOME.
|
||||
|
|
@ -68,8 +65,7 @@ http://library.gnome.org/users/gnome-help/stable/mouse-touchpad-click.html.en[Of
|
|||
GNOME documentation]
|
||||
|
||||
[[kde-plasma-workspaces]]
|
||||
KDE Plasma Workspaces
|
||||
^^^^^^^^^^^^^^^^^^^^^
|
||||
=== KDE Plasma Workspaces
|
||||
|
||||
1. enter KDE System Settings
|
||||
2. choose Hardware / Input Devices / Touchpad (If it's not there,
|
||||
|
|
@ -84,8 +80,7 @@ Alternatively, the systemwide method described under
|
|||
link:#Other_window_managers[Other window managers] can also be used.
|
||||
|
||||
[[xfce]]
|
||||
XFCE
|
||||
^^^^
|
||||
=== XFCE
|
||||
|
||||
1. Enter XFCE Settings
|
||||
2. Select the Mouse and Touchpad settings
|
||||
|
|
@ -93,8 +88,7 @@ XFCE
|
|||
4. In the General section, enable "Tap touchpad to click"
|
||||
|
||||
[[other-window-managers]]
|
||||
Other window managers
|
||||
^^^^^^^^^^^^^^^^^^^^^
|
||||
=== Other window managers
|
||||
|
||||
Create a new file named
|
||||
/etc/X11/xorg.conf.d/99-synaptics-overrides.conf.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,10 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: fedora-and-red-hat-enterprise-linux
|
||||
[id='fedora-and-red-hat-enterprise-linux']
|
||||
= Fedora and Red Hat Enterprise Linux
|
||||
|
||||
What is the difference between Fedora and Red Hat Enterprise Linux?
|
||||
|
||||
include::{partialsdir}/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: finding-and-installing-linux-applications
|
||||
:imagesdir: images
|
||||
|
||||
[[finding-and-installing-linux-applications]]
|
||||
|
|
@ -16,3 +18,5 @@ include::{partialsdir}/proc_package-browsing-installing-software.adoc[leveloffse
|
|||
include::{partialsdir}/proc_package-install-command-line.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_package-enabling-third-party.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: using-firewalld
|
||||
:experimental:
|
||||
:imagesdir: ./images
|
||||
|
||||
|
|
@ -27,3 +29,5 @@ include::{partialsdir}/proc_opening_ports_firewalld.adoc[]
|
|||
include::{partialsdir}/proc_closing_ports_firewalld.adoc[]
|
||||
|
||||
:leveloffset: 0
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: ch-flash
|
||||
:experimental:
|
||||
[[ch-flash]]
|
||||
= Flash
|
||||
|
|
@ -21,12 +23,9 @@ Before downloading Flash, you will need to know whether you are using Fedora 32-
|
|||
Open the terminal and enter:
|
||||
|
||||
[source,bash]
|
||||
|
||||
====
|
||||
|
||||
----
|
||||
uname -p
|
||||
|
||||
====
|
||||
----
|
||||
|
||||
A result of `x86` means it is 32-bit, and `x86_64` is 64-bit.
|
||||
|
||||
|
|
@ -43,11 +42,10 @@ To install Adobe Flash on Fedora:
|
|||
. Open a terminal, go to the directory where the file was downloaded and enter:
|
||||
|
||||
[source,bash]
|
||||
|
||||
====
|
||||
|
||||
----
|
||||
sudo dnf install flash-player-*.rpm
|
||||
|
||||
====
|
||||
----
|
||||
|
||||
You have successfully installed the Adobe Flash plugin and websites using Flash will now work on your browser.
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: getting-started-with-apache-http-server
|
||||
[id='getting-started-with-apache-http-server']
|
||||
= Getting started with Apache HTTP Server
|
||||
|
||||
|
|
@ -20,3 +22,5 @@ include::{partialsdir}/proc_configuring-apache-httpd.adoc[leveloffset=+1]
|
|||
* https://httpd.apache.org/docs/current/ssl/[Apache TLS/SSL documentation]
|
||||
* https://httpd.apache.org/docs/current/misc/security_tips.html[Apache security tips]
|
||||
* https://fedoraproject.org/wiki/OwnCloud[OwnCloud]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
:parent-context: {context}
|
||||
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: getting-started-with-selinux
|
||||
[id='getting-started-with-selinux-{context}']
|
||||
= Getting started with SELinux
|
||||
:context: getting-started-with-selinux
|
||||
|
|
@ -15,4 +15,5 @@ include::{partialsdir}/con_selinux-architecture.adoc[]
|
|||
include::{partialsdir}/con_selinux-states-and-modes.adoc[]
|
||||
:leveloffset: -1
|
||||
|
||||
:context: {parent-context}
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: getting-started-with-virtualization
|
||||
[id='getting-started-with-virtualization']
|
||||
= Getting started with virtualization
|
||||
|
||||
|
|
@ -12,3 +14,5 @@ include::{partialsdir}/proc_creating-virtual-machines.adoc[leveloffset=+1]
|
|||
include::{partialsdir}/ref_managing-virtual-machines.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/ref_other-virtualization-options.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
:experimental:
|
||||
:imagesdir: ./images
|
||||
:md: en-US/modules
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: installing-and-running-vlc
|
||||
|
||||
[[installing-and-running-vlc]]
|
||||
= Installing and Running VLC
|
||||
|
|
@ -15,3 +17,5 @@ include::{partialsdir}/concept_third-party-repositories.adoc[]
|
|||
include::{partialsdir}/con_the-purpose-of-rpm-fusion.adoc[]
|
||||
|
||||
:leveloffset: 0
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
[i='installing-chromium-or-google-chrome-browsers']
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: installing-chromium-or-google-chrome-browsers
|
||||
[id='installing-chromium-or-google-chrome-browsers']
|
||||
= Installing Chromium or Google Chrome browsers
|
||||
|
||||
include::{partialsdir}/3rdparty-message.adoc[]
|
||||
|
|
@ -9,3 +11,5 @@ include::{partialsdir}/proc_installing-chromium-web-browser.adoc[leveloffset=+1]
|
|||
|
||||
include::{partialsdir}/proc_enabling-chromium-plugins.adoc[leveloffset=+1]
|
||||
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: bootloading-with-grub2
|
||||
:md: en-US/modules
|
||||
|
||||
|
||||
|
|
@ -24,4 +26,6 @@ include::{partialsdir}/proc_creating-menu-entries-with-uefi-bootloader.adoc[leve
|
|||
|
||||
include::{partialsdir}/proc_adding-other-operating-systems-grub2.adoc[leveloffset=+1]
|
||||
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: assembly_installing-java
|
||||
[id="assembly_installing-java"]
|
||||
= Installing Java
|
||||
|
||||
|
|
@ -32,3 +34,5 @@ To develop Java applications, consider the following open-source IDEs:
|
|||
* link:https://netbeans.org/[NetBeans]
|
||||
* link:https://eclipse.org/[Eclipse]
|
||||
* link:https://www.jetbrains.com/idea/[IntelliJ IDEA]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: installing-software-from-source
|
||||
[[installing-software-from-source]]
|
||||
= Installing software from source code
|
||||
|
||||
|
|
@ -11,3 +13,5 @@ include::{partialsdir}/proc_setting-up-your-local-dev-and-compilation-environmen
|
|||
include::{partialsdir}/proc_downloading-source-code.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_compiling_your_application_from_source.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: installing-spotify
|
||||
= Installing Spotify
|
||||
|
||||
include::{partialsdir}/3rdparty-message.adoc[]
|
||||
|
|
@ -5,3 +7,5 @@ include::{partialsdir}/3rdparty-message.adoc[]
|
|||
Installing the Spotify music service client on Fedora.
|
||||
|
||||
include::{partialsdir}/proc_installing-spotify-on-fedora.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,8 +1,7 @@
|
|||
:parent-context: {context}
|
||||
|
||||
ifdef::context[:parent-context: {context}]
|
||||
:context: gnome-boxes
|
||||
[id='installing-virtual-operating-systems-with-gnome-boxes-{context}']
|
||||
= Installing virtual operating systems with GNOME Boxes
|
||||
:context: gnome-boxes
|
||||
|
||||
:md: en-US/modules
|
||||
:imagesdir: ./images
|
||||
|
|
@ -12,3 +11,5 @@ GNOME Boxes is an application in GNOME Desktop Environment, which enables you to
|
|||
:leveloffset: +1
|
||||
include::{partialsdir}/proc_install-predefined-systems.adoc[]
|
||||
:leveloffset: -1
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -70,10 +70,10 @@ to check out that branch with:
|
|||
1. Check out the branch for which you would like to build a kernel (`master`
|
||||
corresponds to Rawhide):
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
git checkout origin/f28
|
||||
----
|
||||
[source,bash]
|
||||
----
|
||||
git checkout origin/f28
|
||||
----
|
||||
|
||||
2. To avoid conflicts with existing kernels, you can set a custom buildid by
|
||||
changing `# define buildid .local` to `%define buildid .<your_custom_id_here>`
|
||||
|
|
@ -83,17 +83,17 @@ in `kernel.spec`.
|
|||
|
||||
4. Build the RPMs:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
fedpkg local
|
||||
----
|
||||
[source,bash]
|
||||
----
|
||||
fedpkg local
|
||||
----
|
||||
|
||||
5. Install the new kernel:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install --nogpgcheck ./x86_64/kernel-$version.rpm
|
||||
----
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install --nogpgcheck ./x86_64/kernel-$version.rpm
|
||||
----
|
||||
|
||||
|
||||
=== Building a non-debugging kernel
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: managing-keyboard-shortcuts-for-running-app-in-gnome
|
||||
:experimental:
|
||||
|
||||
[id='managing-keyboard-shortcuts-for-running-app-in-gnome']
|
||||
|
|
@ -25,3 +27,5 @@ https://askubuntu.com/questions/26056/where-are-gnome-keyboard-shortcuts-stored
|
|||
|
||||
tested on F28 live CD in VM
|
||||
////
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -33,8 +33,7 @@ with the following macro:
|
|||
|
||||
|
||||
[[missing-package]]
|
||||
Missing Package
|
||||
~~~~~~~~~~~~~~~
|
||||
== Missing Package
|
||||
|
||||
Unfortunately, the package you were searching for is not available in
|
||||
Fedora. There are a few common reasons why a package might not be in
|
||||
|
|
@ -49,8 +48,7 @@ adding it to the link:PackageMaintainers/WishList[Package WishList], or
|
|||
even link:PackageMaintainers/Join[packaging it yourself]!
|
||||
|
||||
[[missing-codec]]
|
||||
Missing Codec
|
||||
~~~~~~~~~~~~~
|
||||
== Missing Codec
|
||||
|
||||
Unfortunately, the codec you were searching for is not available in
|
||||
Fedora. A codec is a program that enables encoding and/or decoding of a
|
||||
|
|
@ -78,8 +76,7 @@ so. Scroll down more for details on what we are doing and how you can
|
|||
help.
|
||||
|
||||
[[missing-driver]]
|
||||
Missing Driver
|
||||
~~~~~~~~~~~~~~
|
||||
== Missing Driver
|
||||
|
||||
Unfortunately, the driver you were searching for is not available in
|
||||
Fedora. There are a few common reasons why a driver might not be in
|
||||
|
|
@ -103,8 +100,7 @@ software that has been not been included in the official Fedora software
|
|||
repository.
|
||||
|
||||
[[missing-font]]
|
||||
Missing Font
|
||||
~~~~~~~~~~~~
|
||||
== Missing Font
|
||||
|
||||
Unfortunately, the font you were searching for is not available in
|
||||
Fedora. There are a few common reasons why a font might not be in
|
||||
|
|
@ -117,8 +113,7 @@ consider adding it to the :Category:Font_wishlist[Font WishList], or
|
|||
even link:PackageMaintainers/Join[packaging it yourself]!
|
||||
|
||||
[[missing-mime-support]]
|
||||
Missing MIME Support
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
== Missing MIME Support
|
||||
|
||||
Unfortunately, there is nothing in Fedora that claims to support the
|
||||
MIME type you were searching for. There are a few common reasons why
|
||||
|
|
@ -135,8 +130,7 @@ it to the link:PackageMaintainers/WishList[Package WishList], or even
|
|||
link:PackageMaintainers/Join[packaging it yourself]!
|
||||
|
||||
[[fedora-position-on-software-patents]]
|
||||
Fedora Position on Software Patents
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Fedora Position on Software Patents
|
||||
'''
|
||||
|
||||
See a typo, something missing or out of date, or anything else which can be
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: performing-administration-tasks-using-sudo
|
||||
[id='performing-administration-tasks-using-sudo']
|
||||
= Performing administration tasks using sudo
|
||||
|
||||
|
|
@ -30,3 +32,5 @@ include::{partialsdir}/con_using-sudo-access-docker.adoc[leveloffset=+2]
|
|||
include::{partialsdir}/proc_run-docker-using-sudo.adoc[leveloffset=+2]
|
||||
|
||||
include::{partialsdir}/con_using-sudo-without-password.adoc[leveloffset=+2]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -33,8 +33,7 @@ with the following macro:
|
|||
|
||||
|
||||
[[installation]]
|
||||
Installation
|
||||
~~~~~~~~~~~~
|
||||
== Installation
|
||||
|
||||
The installation and initialization of the postgresql server is a little
|
||||
bit different in comparison to other packages and other linux distros.
|
||||
|
|
@ -97,8 +96,7 @@ Or on Fedora 22 and later:
|
|||
`$ sudo postgresql-setup --initdb --unit postgresql`
|
||||
|
||||
[[upgrade]]
|
||||
Upgrade
|
||||
~~~~~~~
|
||||
== Upgrade
|
||||
|
||||
As you can see from error message in my example, it is not a fresh
|
||||
installation, but ugprade.
|
||||
|
|
@ -137,8 +135,7 @@ You can also upgrade by dumping your database and loading it again. For
|
|||
more information, see link:#link-upgrade[official documentation].
|
||||
|
||||
[[tips-and-tricks]]
|
||||
Tips and tricks
|
||||
~~~~~~~~~~~~~~~
|
||||
== Tips and tricks
|
||||
|
||||
For database management is comfortable to use graphical tools such as
|
||||
phpPgAdmin or pgadmin3
|
||||
|
|
@ -152,8 +149,7 @@ Or with dnf in Fedora 22 and later versions:
|
|||
`$ sudo dnf install pgadmin3`
|
||||
|
||||
[[firewall]]
|
||||
Firewall
|
||||
~~~~~~~~
|
||||
== Firewall
|
||||
|
||||
PostgreSQL operates on port 5432 (or whatever else you set in your
|
||||
`postgresql.conf`). In firewalld you can open it like this:
|
||||
|
|
@ -171,8 +167,7 @@ Bear in mind that you probably don't want to open your database server
|
|||
to the whole world.
|
||||
|
||||
[[selinux]]
|
||||
SELinux
|
||||
~~~~~~~
|
||||
== SELinux
|
||||
|
||||
If you have SELinux enforced, you may run into trouble when trying to do
|
||||
some non-standard configuration. For example if you would like to change
|
||||
|
|
@ -193,8 +188,7 @@ host:
|
|||
`# setsebool -P httpd_can_network_connect_db on`
|
||||
|
||||
[[user-creation-and-database-creation]]
|
||||
User Creation and Database Creation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== User Creation and Database Creation
|
||||
|
||||
Soon you run into need of creating a user (and database for the user).
|
||||
First, you have to switch user to interact with postgres:
|
||||
|
|
@ -226,8 +220,7 @@ this could be done from system shell too:
|
|||
`$ createdb --owner=lenny carl`
|
||||
|
||||
[[configuration]]
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
== Configuration
|
||||
|
||||
The postgresql server is using two main configuration files
|
||||
|
||||
|
|
@ -235,8 +228,7 @@ The postgresql server is using two main configuration files
|
|||
* /var/lib/pgsql/data/pg_hba.conf
|
||||
|
||||
[[systemd]]
|
||||
systemd
|
||||
^^^^^^^
|
||||
=== systemd
|
||||
|
||||
Some configuration parameters are passed to daemon via command line
|
||||
options. This behaviour may override settings in postgresql.conf. For
|
||||
|
|
@ -255,8 +247,7 @@ http://fedoraproject.org/wiki/systemd#How_do_I_customize_a_unit_file.2F_add_a_cu
|
|||
for more details.
|
||||
|
||||
[[postgresql.conf]]
|
||||
postgresql.conf
|
||||
^^^^^^^^^^^^^^^
|
||||
=== postgresql.conf
|
||||
|
||||
If you want postgres to accept network connections, you should change
|
||||
|
||||
|
|
@ -267,8 +258,7 @@ to
|
|||
`listen_addresses = '*'`
|
||||
|
||||
[[pg_hba.conf]]
|
||||
pg_hba.conf
|
||||
^^^^^^^^^^^
|
||||
=== pg_hba.conf
|
||||
|
||||
Once your database is set up, you need to configure access to your
|
||||
database server. This may be done by editing file
|
||||
|
|
@ -320,8 +310,7 @@ For more information see official documentation for
|
|||
link:#link-pghba[pg_hba.conf file].
|
||||
|
||||
[[optimisation]]
|
||||
Optimisation
|
||||
~~~~~~~~~~~~
|
||||
== Optimisation
|
||||
|
||||
Default configuration of postgres is severely undertuned. It can handle
|
||||
simple application with not so often database access but if you require
|
||||
|
|
@ -330,8 +319,7 @@ magic is happening in `/var/lib/pgsql/data/postgresql.conf\``. Also
|
|||
logging mechanism is configured not very intuitively.
|
||||
|
||||
[[performance]]
|
||||
Performance
|
||||
^^^^^^^^^^^
|
||||
=== Performance
|
||||
|
||||
Number of clients which may be connected to PostgreSQL at the same time:
|
||||
|
||||
|
|
@ -363,8 +351,7 @@ For more information about this topic I advise you to read official
|
|||
link:#link-tuning[documentation about] tuning PostgreSQL.
|
||||
|
||||
[[logging]]
|
||||
Logging
|
||||
^^^^^^^
|
||||
=== Logging
|
||||
|
||||
By default, logs are rotated every week and you don't find much
|
||||
information in there (one could miss log level, date, time, ...). Also
|
||||
|
|
@ -433,8 +420,7 @@ would make more sense to simplify the prefix to
|
|||
`log_line_prefix = '%t [%p] '`
|
||||
|
||||
[[final-recipe]]
|
||||
Final recipe
|
||||
++++++++++++
|
||||
==== Final recipe
|
||||
|
||||
`log_destination = 'stderr'` +
|
||||
`logging_collector = on` +
|
||||
|
|
@ -447,8 +433,7 @@ Final recipe
|
|||
`log_line_prefix = '%t %u@%r:%d [%p] '`
|
||||
|
||||
[[reference]]
|
||||
Reference
|
||||
~~~~~~~~~
|
||||
== Reference
|
||||
|
||||
link:PostgreSQL/README.rpm-dist[Full RPM packaging documentation]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: setting-key-shortcut
|
||||
[id='setting-key-shortcut_{context}']
|
||||
= Setting a key shortcut to run an application in GNOME
|
||||
|
||||
|
|
@ -21,3 +23,5 @@ Your shortcut appears under *Custom Shortcuts* and is ready to use.
|
|||
image:custom_shortcut.png[]
|
||||
|
||||
To edit or remove your shortcut, click the shortcut to open its details.
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: securing-the-system-by-keeping-it-up-to-date
|
||||
:experimental:
|
||||
|
||||
[id='securing-the-system-by-keeping-it-up-to-date']
|
||||
|
|
@ -22,3 +24,5 @@ include::{partialsdir}/proc_setting-automatic-updates.adoc[leveloffset=+1]
|
|||
== Additional Resources
|
||||
|
||||
* The https://docs-old.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/ch-DNF.html[DNF] chapter in the Fedora System Administrator's Guide
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: switching-desktop-environments
|
||||
:imagesdir: ./images
|
||||
|
||||
[[switching-desktop-environments]]
|
||||
|
|
@ -10,3 +12,5 @@ include::{partialsdir}/proc_installing-additional-desktop-enviroments.adoc[level
|
|||
include::{partialsdir}/proc_switching-desktop-enviroments-using-gui.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_switching-desktop-enviroments-using-cli.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: prod_troubleshooting_selinux
|
||||
[id='prod_troubleshooting_selinux']
|
||||
= Troubleshooting SELinux
|
||||
|
||||
|
|
@ -63,3 +65,5 @@ include::modules/proc_troubleshooting_selinux_allowing_access_audit.adoc[levelof
|
|||
* link:https://docs-old.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/chap-Security-Enhanced_Linux-Troubleshooting.html[Troubleshooting] in the SELinux User's and Administrator's Guide
|
||||
|
||||
* link:https://fedorapeople.org/~dwalsh/SELinux/Presentations/selinux_four_things.pdf[Four Key Causes of SELinux Errors]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: understanding-and-administering-systemd
|
||||
:source-highlighter: prettify
|
||||
|
||||
[id='understanding-and-administering-systemd']
|
||||
|
|
@ -31,3 +33,5 @@ include::{partialsdir}/ref_mapping-service-commands.adoc[leveloffset=+1]
|
|||
* http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks
|
||||
* link:Features/systemd[ Features Fedora 15:systemd]
|
||||
* http://fosdem.org/2011/interview/lennart-poettering.html[Interview with the developer]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -36,12 +36,10 @@ This page contains information explaining how to upgrade Fedora online
|
|||
using (without the DNF system upgrade plugin).
|
||||
|
||||
[[upgrading-fedora-using-dnf-directly]]
|
||||
Upgrading Fedora using dnf directly
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Upgrading Fedora using dnf directly
|
||||
|
||||
[[participate]]
|
||||
Participate
|
||||
~~~~~~~~~~~
|
||||
== Participate
|
||||
|
||||
If you are upgrading using Dnf and it shows any general dependency
|
||||
issues, please file them in http://bugzilla.redhat.com[Bugzilla]. But
|
||||
|
|
@ -53,8 +51,7 @@ If you want to help make live upgrades work smoothly, join the
|
|||
link:SIGs/LiveUpgrade[ Live Upgrade Special Interest Group].
|
||||
|
||||
[[upgrading-across-multiple-releases]]
|
||||
Upgrading across multiple releases
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Upgrading across multiple releases
|
||||
|
||||
If you need to upgrade across several releases, it is generally
|
||||
recommended to go one release at a time: for example, rather than going
|
||||
|
|
@ -64,20 +61,17 @@ are upgrading from an link:End_of_life[End of life] release, please also
|
|||
see link:#eol[the end-of-life section].
|
||||
|
||||
[[instructions-to-upgrade-using-dnf]]
|
||||
Instructions to upgrade using dnf
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Instructions to upgrade using dnf
|
||||
|
||||
[[backup-your-system]]
|
||||
1. Backup your system
|
||||
^^^^^^^^^^^^^^^^^^^^^
|
||||
=== 1. Backup your system
|
||||
|
||||
Backup any personal data to an external hard drive or to another
|
||||
machine. If there is some unrecoverable error that requires a fresh
|
||||
install, you don't want to lose any data.
|
||||
|
||||
[[read-about-common-problems]]
|
||||
2. Read about common problems
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== 2. Read about common problems
|
||||
|
||||
Further down in this page there is a list of common problems specific to
|
||||
dnf upgrades for specific versions. Some of them require attention
|
||||
|
|
@ -92,8 +86,7 @@ regarding upgrading issues. Finally, check the list of
|
|||
link:Common_bugs[Common bugs].
|
||||
|
||||
[[clean-stuff]]
|
||||
3. Clean Stuff
|
||||
^^^^^^^^^^^^^^
|
||||
=== 3. Clean Stuff
|
||||
|
||||
Review and remove all .rpmsave and .rpmnew files before and after
|
||||
upgrading. (And if you have selinux enabled then remember to check
|
||||
|
|
@ -103,8 +96,7 @@ Now is a good time to remove packages you don't use - especially
|
|||
non-standard packages.
|
||||
|
||||
[[do-the-upgrade]]
|
||||
4. Do the upgrade
|
||||
^^^^^^^^^^^^^^^^^
|
||||
=== 4. Do the upgrade
|
||||
|
||||
If you have 3rd party repositories configured, you may need to adjust
|
||||
them for the new Fedora version. If you switch from one Fedora release
|
||||
|
|
@ -121,8 +113,7 @@ It is a good idea to do the upgrade outside the graphical environment.
|
|||
Log out of your graphical desktop and then
|
||||
|
||||
[[fedora-upgrade]]
|
||||
fedora-upgrade
|
||||
++++++++++++++
|
||||
==== fedora-upgrade
|
||||
|
||||
A small script named fedora-upgrade is available which aims to automate
|
||||
the process outlined below. To run it, do the following
|
||||
|
|
@ -139,8 +130,7 @@ your connection drops.
|
|||
Alternatively, follow the manual steps:
|
||||
|
||||
[[go-to-a-text-console]]
|
||||
Go to a text console
|
||||
++++++++++++++++++++
|
||||
==== Go to a text console
|
||||
|
||||
....
|
||||
ctrl + alt + F2
|
||||
|
|
@ -155,16 +145,14 @@ systemctl isolate multi-user.target
|
|||
....
|
||||
|
||||
[[fully-update-your-current-fedora-install]]
|
||||
Fully update your current Fedora install
|
||||
++++++++++++++++++++++++++++++++++++++++
|
||||
==== Fully update your current Fedora install
|
||||
|
||||
....
|
||||
# dnf upgrade
|
||||
....
|
||||
|
||||
[[install-the-package-signing-key-for-the-release-you-are-upgrading-to]]
|
||||
Install the package signing key for the release you are upgrading to
|
||||
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
||||
==== Install the package signing key for the release you are upgrading to
|
||||
|
||||
If you are upgrading across two releases or fewer from Fedora 20 or
|
||||
later, this step should be unnecessary. If you are upgrading from an
|
||||
|
|
@ -195,8 +183,7 @@ to install the key. On old releases, may have trouble doing this; if
|
|||
that happens, download the file with or and import the downloaded file.
|
||||
|
||||
[[clean-the-cache]]
|
||||
Clean the cache
|
||||
+++++++++++++++
|
||||
==== Clean the cache
|
||||
|
||||
Then remove all traces of the version you are leaving from the dnf cache
|
||||
in `/var/cache/dnf`.
|
||||
|
|
@ -206,8 +193,7 @@ in `/var/cache/dnf`.
|
|||
....
|
||||
|
||||
[[upgrade-all-packages]]
|
||||
Upgrade all packages
|
||||
++++++++++++++++++++
|
||||
==== Upgrade all packages
|
||||
|
||||
Run the upgrade command:
|
||||
|
||||
|
|
@ -216,8 +202,7 @@ Run the upgrade command:
|
|||
....
|
||||
|
||||
[[make-sure-fedora-is-upgraded]]
|
||||
5. Make sure Fedora is upgraded
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== 5. Make sure Fedora is upgraded
|
||||
|
||||
Distro-sync will usually take care of upgrades for the third party
|
||||
repositories you have enabled as well. Confirm with after the upgrade
|
||||
|
|
@ -251,8 +236,7 @@ For example
|
|||
....
|
||||
|
||||
[[preparing-for-reboot]]
|
||||
6. Preparing for reboot
|
||||
^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== 6. Preparing for reboot
|
||||
|
||||
Before booting you should usually install the bootloader from your new
|
||||
grub by running
|
||||
|
|
@ -274,8 +258,7 @@ cp --backup=numbered -a /boot/grub2/grub.cfg{,.bak} # create backup copy
|
|||
....
|
||||
|
||||
[[cleanup-your-system]]
|
||||
7. Cleanup your system
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== 7. Cleanup your system
|
||||
|
||||
Again, cleanup your system as described in section 2. Also you might
|
||||
want to remove some cache files that are no longer used, for example
|
||||
|
|
@ -286,8 +269,7 @@ files from older Fedora releases in the following directories:
|
|||
* /var/lib/mock
|
||||
|
||||
[[release-specific-notes]]
|
||||
Release specific notes
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
== Release specific notes
|
||||
|
||||
Note: the release-specific notes for link:End_of_life[End of life]
|
||||
releases are on the
|
||||
|
|
@ -295,16 +277,14 @@ link:Upgrading_from_EOL_Fedora_using_package_manager[EOL packager
|
|||
manager upgrade page].
|
||||
|
||||
[[from-pre-release]]
|
||||
From pre-release
|
||||
^^^^^^^^^^^^^^^^
|
||||
=== From pre-release
|
||||
|
||||
If you are upgrading to a final release from an Alpha, Beta, or release
|
||||
candidate, please see link:Upgrading_from_pre-release_to_final[Upgrading
|
||||
from pre-release to final].
|
||||
|
||||
[[to-rawhide]]
|
||||
To Rawhide
|
||||
^^^^^^^^^^
|
||||
=== To Rawhide
|
||||
|
||||
See the link:Releases/Rawhide[Rawhide] release page for more information
|
||||
on Rawhide.
|
||||
|
|
@ -322,20 +302,17 @@ on Rawhide.
|
|||
....
|
||||
|
||||
[[fedora-25]]
|
||||
Fedora 25
|
||||
^^^^^^^^^
|
||||
=== Fedora 25
|
||||
|
||||
No special instructions. Follow the above instructions.
|
||||
|
||||
[[fedora-24]]
|
||||
Fedora 24
|
||||
^^^^^^^^^
|
||||
=== Fedora 24
|
||||
|
||||
No special instructions. Follow the above instructions.
|
||||
|
||||
[[upgrading-from-legacy-end-of-life-eol-fedora-releases]]
|
||||
Upgrading from legacy end of life (EOL) Fedora releases
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
=== Upgrading from legacy end of life (EOL) Fedora releases
|
||||
|
||||
Note that Fedora strongly recommends against ever running an end-of-life
|
||||
release on any production system, or any system connected to the public
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: using-nested-virtiualization-in-kvm
|
||||
= How to enable nested virtualization in KVM
|
||||
|
||||
Learn how to run a virtual machine within a virtual machine.
|
||||
|
|
@ -14,3 +16,5 @@ include::{partialsdir}/proc_testing-nested-virtualization.adoc[leveloffset=+1]
|
|||
* https://bugzilla.redhat.com/show_bug.cgi?id=1055002
|
||||
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/
|
||||
* https://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: using-shared-system-certificates
|
||||
[[using-shared-system-certificates]]
|
||||
= Using Shared System Certificates
|
||||
|
||||
|
|
@ -17,3 +19,5 @@ For more information, see the following man pages:
|
|||
|
||||
* `update-ca-trust(8)`
|
||||
* `trust(1)`
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
ifdef::context[:parent-context: {context}]
|
||||
:context: viewing-logs
|
||||
|
||||
:md: en-US/modules
|
||||
|
||||
|
|
@ -6,3 +8,5 @@ include::{partialsdir}/con_viewing-logs.adoc[leveloffset=+1]
|
|||
include::{partialsdir}/proc_log-files-command-line.adoc[leveloffset=+1]
|
||||
|
||||
include::{partialsdir}/proc_log-files-GUI.adoc[leveloffset=+1]
|
||||
ifdef::parent-context[:context: {parent-context}]
|
||||
ifndef::parent-context[:!context:]
|
||||
|
|
|
|||
|
|
@ -11,8 +11,7 @@ and providing alternative implementations of Windows system libraries,
|
|||
system services through https://wiki.winehq.org/Wineserver[wineserver]
|
||||
and various other components such as Internet Explorer, the Windows Registry Editor, and msiexec.
|
||||
|
||||
Packages
|
||||
~~~~~~~~
|
||||
== Packages
|
||||
|
||||
Fedora's Wine packages are split up to allow for smaller installations.
|
||||
The `wine` meta package will bring with it the most important components
|
||||
|
|
@ -87,8 +86,7 @@ integration
|
|||
Additional documentation is provided via the ''wine-docs '' package.
|
||||
|
||||
[[available-versions]]
|
||||
Available versions
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
== Available versions
|
||||
|
||||
Fedora applies fixes and features from the *wine-staging* project. EPEL
|
||||
packages do not use wine-staging patches.
|
||||
|
|
@ -107,8 +105,7 @@ Newer versions may be available in the corresponding `updates-testing`
|
|||
repositories.
|
||||
|
||||
[[testing-versions]]
|
||||
Testing Versions
|
||||
~~~~~~~~~~~~~~~~
|
||||
== Testing Versions
|
||||
|
||||
[cols=",",]
|
||||
|=================
|
||||
|
|
@ -118,8 +115,7 @@ Testing Versions
|
|||
|=================
|
||||
|
||||
[[bugs-and-problems]]
|
||||
Bugs and problems
|
||||
~~~~~~~~~~~~~~~~~
|
||||
== Bugs and problems
|
||||
|
||||
Before reporting bugs against Wine please make sure your system is fully
|
||||
up to date.
|
||||
|
|
@ -172,8 +168,7 @@ the Wine component in https://bugzilla.redhat.com[Fedora's bug tracking
|
|||
system].
|
||||
|
||||
[[updates-testing]]
|
||||
Updates-Testing
|
||||
~~~~~~~~~~~~~~~
|
||||
== Updates-Testing
|
||||
|
||||
If you use the version of wine in the updates-testing repository then
|
||||
please log into https://bodhi.fedoraproject.org/updates/?packages=wine[bodhi] and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue