hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-28 14:56:35 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

format & typos detected by languagetool

Browse source
This commit is contained in:
Jean-Baptiste Holcroft 2021-08-22 17:13:47 +02:00
parent c90c5f8236
commit e5434c995e
4 changed files with 26 additions and 47 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
modules/ROOT/pages/_partials/proc_enabling-nested-virtualization-in-kvm.adoc
View file

@ -45,12 +45,12 @@ sudo modprobe -r kvm_amd
----
. Activate the nesting feature:
+
----
----
sudo modprobe kvm_amd nested=1
----
. Nested virtualization is enabled until the host is rebooted. To enable it permanently, add the following line to the `/etc/modprobe.d/kvm.conf` file:
+
----
----
options kvm_amd nested=1
----

49
modules/ROOT/pages/autoupdates.adoc
View file

@ -8,7 +8,7 @@ single answer to this question: it is up to the system administrator or
owner of each machine to decide whether automatic updates are desirable
or not for that machine. One of the things which makes one a good system
administrator is the ability to evaluate the facts and other people's
suggestions, and then decide for onesself what one should do.
suggestions, and then decide for oneself what one should do.
A general rule that applies in most cases is as follows:
@ -21,7 +21,7 @@ Some issues might be resolved through a special setup on your part. For
example, you could create your own DNF repository on a local server,
and only put in tested or trusted updates. Then use the automatic
updates from only your own repository. Such setups, while perhaps more
difficult to setup and maintain, can remove a large amount of risk
difficult to set up and maintain, can remove a large amount of risk
otherwise inherent in automatic updates.
[[how-are-automatic-updates-done]]
@ -37,8 +37,7 @@ started automatically.
[[install-and-settings-of-dnf-automatic]]
=== Install and settings of dnf-automatic
On a fresh install of Fedora 22 with default options the dnf-automatic
RPM is not installed, the first command below installs this RPM.
On a fresh Fedora 22 installation with default options the dnf-automatic RPM is not installed, the first command below installs this RPM.
[source,bash]
----
@ -111,7 +110,7 @@ problems during or after installation.
The main advantage of automating the updates is that machines are likely
to get updated more quickly, more often, and more uniformly than if they
updates are done manually. We see too many compromised machines on the
update are done manually. We see too many compromised machines on the
internet which would have been safe if the latest updates where
installed in a timely way.
@ -137,8 +136,8 @@ updates are:
* You do not have any irreplaceable data on the machine, or have proper
backups of such data.
If all of the above apply to your machine(s), then automatic updates may
be your best option to help secure your machine. If not all of the above
If all the above apply to your machine(s), then automatic updates may
be your best option to help secure your machine. If not all the above
apply, then you will need to weigh the risks and decide for yourself if
automatic updates are the best way to proceed.
@ -156,17 +155,9 @@ automatic updates are:
unscheduled downtime.
* You installed custom software, compiled software from source, or use
third party software that has strict package version requirements.
* You installed a custom kernel, custom kernel modules, third party
kernel modules, or have a third party application that depends on kernel
versions (this may not be a problem if you exclude kernel updates, which
is the default in Fedora `dnf.conf` files). (But see also
https://bugzilla.redhat.com/show_bug.cgi?id=870790[bug #870790] - you
may need to modify in Fedora 22 or later versions in base section to add
`exclude=kernel*`.)
* You installed a custom kernel, custom kernel modules, third party kernel modules, or have a third party application that depends on kernel versions (this may not be a problem if you exclude kernel updates, which is the default in Fedora `dnf.conf` files). (But see also https://bugzilla.redhat.com/show_bug.cgi?id=870790[bug #870790] - you may need to modify in Fedora 22 or later versions in base section to add `exclude=kernel*`.)
* Your environment requires meticulous change-control procedures.
* You update from other third party DNF repositories besides Fedora
(core, extras, legacy ) repositories which may conflict in versioning
schemes for the same packages.
* You update from other third party DNF repositories besides Fedora (core, extras, legacy ) repositories which may conflict in versioning schemes for the same packages.
There are also some other reasons why installing automatic updates
without testing may be a bad idea. A few such reasons are:
@ -176,22 +167,16 @@ without testing may be a bad idea. A few such reasons are:
file which is not flagged as a configuration file, then you might lose
your configuration changes. Or an update may have a different format of
configuration file, requiring a manual reconfiguration. It is often best
to backup your configuration files before doing updates on critical
to back up your configuration files before doing updates on critical
packages such as mail, web, or database server packages.
* Unwanted side effects. Some packages can create annoying side effects,
particularly ones which have cron jobs. Updates to base packages like
openssl, openldap, sql servers, etc. can have an effect on many other
seemingly unrelated packages.
* Bugs. Many packages contain buggy software or installation scripts.
The update may create problems during or after installation. Even
cosmetic bugs, like those found in previous Mozilla updates causing the
user's icons to be removed or break, can be annoying or problematic.
* Automatic updates may not complete the entire process needed to make
the system secure. For example, DNF can install a kernel update,
but until the machine is rebooted (which DNF will not do
automatically) the new changes won't take effect. The same may apply to
restarting daemons. This can leave the user feeling that he is secure
when he is not.
The update may create problems during or after installation. Even cosmetic bugs, like those found in previous Mozilla updates causing the user's icons to be removed or break, can be annoying or problematic.
* Automatic updates may not complete the entire process needed to make the system secure. For example, DNF can install a kernel update, but until the machine is rebooted (which DNF will not do automatically) the new changes won't take effect.
The same may apply to restarting daemons. This can leave the user feeling that he is secure when he is not.
[[best-practices-when-using-automatic-updates]]
@ -223,8 +208,8 @@ email_to = root
email_host = localhost
----
You would replace root with a actual email address to which you want to
report sent, and localhost with a actual address of SMTP server. This
You would replace root with an actual email address to which you want to
report sent, and localhost with an actual address of SMTP server. This
change will mean that after dnf-automatic runs, it will email you
information you about available updates, or log about downloaded
packages, or installed updates according to settings in `automatic.conf`.
@ -282,7 +267,7 @@ could then install manually. It can be set by editing of `/etc/dnf/automatic.con
Another common problem is having automatic updates run when it isn't
desired (holidays, weekends, vacations, etc). If there are times that no
one will be around to fix any problem arising the from the updates, it
one will be around to fix any problem arising from the updates, it
may be best to avoid doing updates on those days.
This problem can be fixed by modification of the timer of dnf-automatic
@ -298,6 +283,6 @@ provide your machine with some other forms of protection to help defend
any attacks that might occur before updates are in place. This might
include an external firewall, a host-based firewall (like iptables,
ipchains, and/or tcp wrappers), not performing dangerous tasks on the
computer (like browsing the web, reading e-mail, etc), and monitoring
the system for instrusions (with system log checkers, IDS systems,
computer (like browsing the web, reading e-mail, etc.), and monitoring
the system for intrusions (with system log checkers, IDS systems,
authentication or login monitoring, etc).

2
modules/ROOT/pages/publish-rpm-on-copr.adoc
View file

@ -23,7 +23,7 @@ TIP: You can set up similar automation when packaging someone else's program, i.
The following is needed:
. Our program's source in a publicly available git repository somewhere. This tutorial uses a simple example program - hellocopr - to demonstrate the process.
The program and all files referenced in this guide can be found in the link:https://pagure.io/copr-tito-quickdoc[project's git repository]. It's a very simple (& pointless) python program with a setuptools installer:
The program and all files referenced in this guide can be found in the link:https://pagure.io/copr-tito-quickdoc[project's git repository]. It's a very simple (& pointless) python program with a setuptools installer:
+
```
user@host ~/copr-tito-quickdoc % ls

18
modules/ROOT/pages/samba.adoc
View file

@ -111,12 +111,9 @@ file. Add this section to the bottom of the file:
Explanation of the above:
* `valid users`: only users of the group `family` have access rights. The @
denotes a group name.
* `force group = +myfamily`: files and directories are created with this
group, instead of the user group.
* `create mask = 0660`: files in the share are created with permissions to
allow all group users to read and write files created by other users.
* `valid users`: only users of the group `family` have access rights. The @ denotes a group name.
* `force group = +myfamily`: files and directories are created with this group, instead of the user group.
* `create mask = 0660`: files in the share are created with permissions to allow all group users to read and write files created by other users.
* `directory mask = 0770`: as before, but for directories.
Restart Samba for the changes to take effect:
@ -200,8 +197,7 @@ No locked files
Some things to check if you cannot access the share.
. Be sure that the user exists as a system user as well as a
Samba user
. Be sure that the user exists as a system user as well as a Samba user
+
Find `maria` in the Samba database:
+
@ -237,8 +233,7 @@ drwxrwx---. 2 root myfamily 4096 May 29 14:03 /home/share
+
In this case, the user should be in the `myfamily` group.
. Check in the configuration file `/etc/samba/smb.conf` that the
user and group have access permission.
. Check in the configuration file `/etc/samba/smb.conf` that the user and group have access permission.
+
....
[family]
@ -258,8 +253,7 @@ In this case, the user should be in the `myfamily` group.
[[trouble_with_writing_in_the_share]]
=== Trouble with writing in the share
. Check in the samba configuration file if the user/group has
write permissions.
. Check in the samba configuration file if the user/group has write permissions.
+
....
[family]