Update links to https part 2
This commit is contained in:
Frank Sträter
parent
49a673dfdb
commit
ee7add2057
22 changed files with 44 additions and 44 deletions
|
|
@ -29,7 +29,7 @@ In fact, for most Linux distributions, including Fedora, all of the system insta
|
|||
|
||||
== RPM
|
||||
|
||||
Fedora's package management system uses the http://rpm.org[RPM] package format. The application that manages packages in Fedora (since version 22) is https://fedoraproject.org/wiki/DNF[DNF]. Graphical package management is provided by the Gnome Software utility. For automatic updates, Fedora uses the PackageKit utility. Command-line and graphical tools provide the same results.
|
||||
Fedora's package management system uses the https://rpm.org[RPM] package format. The application that manages packages in Fedora (since version 22) is https://fedoraproject.org/wiki/DNF[DNF]. Graphical package management is provided by the Gnome Software utility. For automatic updates, Fedora uses the PackageKit utility. Command-line and graphical tools provide the same results.
|
||||
|
||||
|
||||
== Repositories
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ For more information about packaging guidelines, see the following guides:
|
|||
* https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/[Recipes for RPM scriptlets]
|
||||
|
||||
|
||||
If you plan to submit a package to the official Fedora repository, follow the procedure in http://fedoraproject.org/wiki/Join_the_package_collection_maintainers[Join the package collection maintainers].
|
||||
If you plan to submit a package to the official Fedora repository, follow the procedure in https://fedoraproject.org/wiki/Join_the_package_collection_maintainers[Join the package collection maintainers].
|
||||
|
||||
Before you begin, select a text editor that you want to use, and ensure that you understand the following terminology.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,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.
|
||||
|
||||
`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.
|
||||
Add the base name of the package, which must match the `.spec` file name. Follow the https://fedoraproject.org/wiki/Packaging:Naming[Package Naming Guidelines] and write the file name in lower-case letters.
|
||||
|
||||
`Version`::
|
||||
Add the upstream version number. See https://docs.fedoraproject.org/en-US/packaging-guidelines/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`.
|
||||
|
|
@ -22,7 +22,7 @@ This tag is deprecated since Fedora 17. See https://docs-old.fedoraproject.org/e
|
|||
File Reference Preamble]
|
||||
|
||||
`License`::
|
||||
Enter an open source software license. Do not use the old Copyright tag. Use a standard abbreviation, for example, `GPLv2+` and be specific. For example, use `GPLv2+` for GPL version 2 or greater rather than `GPL` or `GPLv2` where it's true. For more information, see the http://fedoraproject.org/wiki/Packaging:LicensingGuidelines[Licensing Guidelines].
|
||||
Enter an open source software license. Do not use the old Copyright tag. Use a standard abbreviation, for example, `GPLv2+` and be specific. For example, use `GPLv2+` for GPL version 2 or greater rather than `GPL` or `GPLv2` where it's true. For more information, see the https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/[Licensing Guidelines].
|
||||
+
|
||||
You can list multiple licenses by combining them with `and` and `or` (e.g. `GPLv2 and BSD`).
|
||||
|
||||
|
|
@ -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 https://docs.fedoraproject.org/en-US/packaging-guidelines/#_timestamps[Preserve timestamps].
|
||||
+
|
||||
If there is more than one source, name them `Source1`, `Source2`.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -16,4 +16,4 @@ The following examples demonstrate how SELinux increases security:
|
|||
|
||||
* SELinux helps mitigate the damage made by configuration mistakes. Domain Name System (DNS) servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the Berkeley Internet Name Domain (BIND) as a DNS server in Fedora, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files footnote:[Text files that include information, such as host name to IP address mappings, that are used by DNS servers.] from being updated using zone transfers, by the BIND `named` daemon itself, and by other processes.
|
||||
|
||||
* See the link:++http://www.networkworld.com++[NetworkWorld.com] article, link:++http://www.networkworld.com/article/2283723/lan-wan/a-seatbelt-for-server-software--selinux-blocks-real-world-exploits.html++[A seatbelt for server software: SELinux blocks real-world exploits]footnote:[Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 27 August 2009: link:++http://www.networkworld.com/article/2283723/lan-wan/a-seatbelt-for-server-software--selinux-blocks-real-world-exploits.html++[].], for background information about SELinux, and information about various exploits that SELinux has prevented.
|
||||
* See the link:++https://www.networkworld.com++[NetworkWorld.com] article, link:++https://www.networkworld.com/article/2283723/lan-wan/a-seatbelt-for-server-software--selinux-blocks-real-world-exploits.html++[A seatbelt for server software: SELinux blocks real-world exploits]footnote:[Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 27 August 2009: link:++https://www.networkworld.com/article/2283723/lan-wan/a-seatbelt-for-server-software--selinux-blocks-real-world-exploits.html++[].], for background information about SELinux, and information about various exploits that SELinux has prevented.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ Only the Chromium browser is available from official Fedora repositories.
|
|||
|
||||
Chromium is the upstream project for Google Chrome.
|
||||
|
||||
NOTE: As of August 2016, Chromium is included in the Fedora Repositories. If you were using the old Chromium http://copr.fedoraproject.org/coprs/spot/chromium/[Copr] repository, upgrade your Chromium.
|
||||
NOTE: As of August 2016, Chromium is included in the Fedora Repositories. If you were using the old Chromium https://copr.fedorainfracloud.org/coprs/spot/chromium/[Copr] repository, upgrade your Chromium.
|
||||
|
||||
Fedora's Chromium package does not support h264, mp3, or aac because of legal concerns. It is built to support the *widevine* plugin (but does not include it).
|
||||
|
||||
|
|
|
|||
|
|
@ -174,6 +174,6 @@ To ensure a persistent mapping between the device and the mount point, add the e
|
|||
|
||||
* https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions[LUKS Project Wiki: Frequently Asked Questions]
|
||||
|
||||
* http://man7.org/linux/man-pages/man8/cryptsetup.8.html[cryptsetup(8) man page]
|
||||
* https://man7.org/linux/man-pages/man8/cryptsetup.8.html[cryptsetup(8) man page]
|
||||
|
||||
* http://man7.org/linux/man-pages/man8/dmsetup.8.html[dmsetup(8) man page]
|
||||
* https://man7.org/linux/man-pages/man8/dmsetup.8.html[dmsetup(8) man page]
|
||||
|
|
|
|||
|
|
@ -27,5 +27,5 @@ Adding other records into the *GRUB2* menu only means to run `grub2-mkconfig` co
|
|||
.More information
|
||||
|
||||
* The `grub2-mkconfig` command will add entries for all operating systems it can find.
|
||||
* When problems appear, see the link:http://www.gnu.org/software/grub/manual/grub.html#Multi_002dboot-manual-config[GRUB manual] to solve issues with booting secondary operating systems.
|
||||
* When problems appear, see the link:https://www.gnu.org/software/grub/manual/grub/grub.html#Multi_002dboot-manual-config[GRUB manual] to solve issues with booting secondary operating systems.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ IMPORTANT: Your computer could become unbootable or lose functionality if you ch
|
|||
|
||||
If your system has a UEFI firmware, it will usually allow you to boot the stick in UEFI native mode or BIOS compatibility mode. If you boot in UEFI native mode and perform a Fedora installation, you will get a UEFI native Fedora installation. If you boot in BIOS compatibility mode and perform a Fedora installation, you will get a BIOS compatibility mode Fedora installation.
|
||||
|
||||
For more information on all this, see the http://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface[UEFI page]. USB sticks written from x86_64 images with xref:creating-and-using-a-live-installation-image.adoc#using-fedora-media-writer[Fedora Media Writer], xref:creating-and-using-a-live-installation-image.adoc#gnome-disk-utility[GNOME Disk Utility], `dd`, other dd-style utilities should be UEFI native bootable. Sticks written with other utilities may not be UEFI native bootable, and sticks written from i686 images will never be UEFI bootable.
|
||||
For more information on all this, see the https://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface[UEFI page]. USB sticks written from x86_64 images with xref:creating-and-using-a-live-installation-image.adoc#using-fedora-media-writer[Fedora Media Writer], xref:creating-and-using-a-live-installation-image.adoc#gnome-disk-utility[GNOME Disk Utility], `dd`, other dd-style utilities should be UEFI native bootable. Sticks written with other utilities may not be UEFI native bootable, and sticks written from i686 images will never be UEFI bootable.
|
||||
|
||||
|
||||
[id='identifying_stick']
|
||||
|
|
|
|||
|
|
@ -154,11 +154,11 @@ UNetbootin may work in some cases but not others - for instance, it will likely
|
|||
While your results may vary, it is usually the case that the Fedora Media Writer, `livecd-iso-to-disk`, GNOME, and `dd` methods give better results than UNetbootin. If you encounter problems with UNetbootin, please contact the UNetbootin developers, not the Fedora developers.
|
||||
====
|
||||
|
||||
http://unetbootin.github.io/[UNetbootin] is a graphical, bootable USB image creator. Using it will allow you to preserve any data you have in the USB drive. If you have trouble booting, however, you may wish to try with a blank, cleanly FAT32-formatted drive.
|
||||
https://unetbootin.github.io/[UNetbootin] is a graphical, bootable USB image creator. Using it will allow you to preserve any data you have in the USB drive. If you have trouble booting, however, you may wish to try with a blank, cleanly FAT32-formatted drive.
|
||||
|
||||
NOTE: If you are running a 64-bit Linux distribution, UNetbootin may fail to run until you install the 32-bit versions of quite a lot of system libraries.
|
||||
|
||||
. Download the latest UNetbootin version from the http://unetbootin.github.io/[official site] and install it. On Linux, the download is an executable file: save it somewhere, change it to be executable using `chmod ugo+x` filename or a file manager, and then run it.
|
||||
. Download the latest UNetbootin version from the https://unetbootin.github.io/[official site] and install it. On Linux, the download is an executable file: save it somewhere, change it to be executable using `chmod ugo+x` filename or a file manager, and then run it.
|
||||
. Launch UNetbootin. On Linux, you might have to type the root password.
|
||||
. Click on `Diskimage` and search for the ISO file you downloaded.
|
||||
. Select Type: USB drive and choose the correct device for your stick.
|
||||
|
|
|
|||
|
|
@ -25,13 +25,13 @@ This procedure shows Microsoft Windows users how to add Fedora ARM to a microSD
|
|||
* A computer running Microsoft Windows.
|
||||
* SD card reader.
|
||||
* A Fedora ARM image from: link:https://arm.fedoraproject.org/[].
|
||||
* File-decompression software (such as link:http://www.7-zip.org/[7zip]).
|
||||
* File-decompression software (such as link:https://www.7-zip.org/[7zip]).
|
||||
|
||||
._Procedure_
|
||||
|
||||
. Download a Fedora ARM image from the link:https://arm.fedoraproject.org/[Fedora ARM website].
|
||||
+
|
||||
. Extract the `.raw` file from the Fedora ARM image using file-decompression software (such as link:http://www.7-zip.org/[7zip]).
|
||||
. Extract the `.raw` file from the Fedora ARM image using file-decompression software (such as link:https://www.7-zip.org/[7zip]).
|
||||
+
|
||||
For example:
|
||||
+
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ dnf search openjdk
|
|||
* Copy the version of OpenJDK you want to install.
|
||||
|
||||
[NOTE]
|
||||
Various flavors of OpenJDK are available. For information about these options, search the link:http://openjdk.java.net/[OpenJDK web site].
|
||||
Various flavors of OpenJDK are available. For information about these options, search the link:https://openjdk.java.net/[OpenJDK web site].
|
||||
|
||||
* Run the following command to install OpenJDK:
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ include::{partialsdir}/3rdparty-message.adoc[]
|
|||
|
||||
To install Oracle Java SE:
|
||||
|
||||
. Navigate to link:http://www.oracle.com/technetwork/java/javase/downloads[Oracle Java SE downloads page], and
|
||||
. Navigate to link:https://www.oracle.com/java/technologies/javase-downloads.html[Oracle Java SE downloads page], and
|
||||
choose the version of Java you wish to use.
|
||||
|
||||
. Accept the license agreement and download the appropriate tar.gz file for your systems architecture. Do NOT use Oracle rpms as these are NOT compatible with fedora/openjdk packages. Download the tar.gz archive instead, unpack it somewhere and set to path if necessary.
|
||||
|
|
|
|||
|
|
@ -73,4 +73,4 @@ If this command lists `kvm_intel` or `kvm_amd`, KVM is properly configured.
|
|||
|
||||
By default, libvirt will create a private network for your guests on the host machine. This private network will use a 192.168.x.x subnet and not be reachable directly from the network the host machine is on. However, virtual guests can use the host machine as a gateway and can connect out via it. If you need to provide services on your guests that are reachable via other machines on your host network you can use iptables DNAT rules to forward in specific ports, or you can set up a bridged environment.
|
||||
|
||||
See the http://wiki.libvirt.org/page/Networking[libvirt networking setup page] for more information on how to setup a bridged network.
|
||||
See the https://wiki.libvirt.org/page/Networking[libvirt networking setup page] for more information on how to setup a bridged network.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Most applications available on Linux are open-source software. You can use open-
|
|||
Access the following websites to review Linux alternatives to popular software packages:
|
||||
|
||||
* https://linuxappfinder.com/alternatives
|
||||
* http://www.linuxalt.com/
|
||||
* https://www.linuxalt.com/
|
||||
* https://opensource.com/alternatives
|
||||
* https://www.osalt.com/
|
||||
* https://alternativeto.net/
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Use the following commands as the `root` user or under the `sudo` utility.
|
|||
# dnf install dnf-automatic
|
||||
----
|
||||
|
||||
. Edit the [filename]`/etc/dnf/automatic.conf` configuration file as needed. See the http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation for details.
|
||||
. Edit the [filename]`/etc/dnf/automatic.conf` configuration file as needed. See the https://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation for details.
|
||||
|
||||
. Enable and start the `systemd` timer:
|
||||
+
|
||||
|
|
@ -65,4 +65,4 @@ Dec 14 11:33:14 mazlik systemd[1]: Started dnf-automatic-download timer.
|
|||
[discrete]
|
||||
== Additional Resources
|
||||
|
||||
* The http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation
|
||||
* The https://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
[[using-old-graphics-modes]]
|
||||
= Using old graphics modes in bootloader
|
||||
|
||||
The terminal device is chosen with GRUB_TERMINAL. For more information, see the link:http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration[Grub manual].
|
||||
The terminal device is chosen with GRUB_TERMINAL. For more information, see the link:https://www.gnu.org/software/grub/manual/grub/grub.html#Simple-configuration[Grub manual].
|
||||
|
||||
Valid terminal output names depend on the platform, but may include `console` (PC BIOS and EFI consoles), `serial` (serial terminal), `gfxterm` (graphics-mode output), `ofconsole` (Open Firmware console), or `vga_text` (VGA text output, mainly useful with Coreboot).
|
||||
|
||||
|
|
|
|||
|
|
@ -189,7 +189,7 @@ nmcli> quit
|
|||
|
||||
To manually edit an `ifcfg` connection configuration, open or create with a text editor the configuration file of the connection located in `/etc/sysconfig/network-scripts/ifcfg-`.
|
||||
|
||||
A description of most common configuration options is available in the link:http://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html[RHEL6 Deployment Guide].
|
||||
A description of most common configuration options is available in the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s1-networkscripts-interfaces[RHEL6 Deployment Guide].
|
||||
|
||||
To modify a connection password, open with a text editor and edit the file `keys-` located in `/etc/sysconfig/network-scripts/`. The password is stored in plain text. For example:
|
||||
----
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ SDK:: Software Development Kit; see JDK
|
|||
JavaWS:: link:https://en.wikipedia.org/wiki/Java_Web_Start[Java Web Start] is a framework to start application from the Internet
|
||||
JavaFX:: link:https://en.wikipedia.org/wiki/JavaFX[JavaFX] is a plateform to create and deliver desktop and Rich Internet Apps
|
||||
OpenJFX:: is the JavaFX Open Source implementation
|
||||
OpenJDK:: Open Source project behind the Java Platform link:http://openjdk.java.net/[openjdk.java.net].
|
||||
OpenJDK:: Open Source project behind the Java Platform link:https://openjdk.java.net/[openjdk.java.net].
|
||||
IcedTea:: is a support project for OpenJDK (concern only developers) link:http://icedtea.classpath.org/[icedtea.classpath.org]
|
||||
IcedTea-Web:: is the Java Web Start package (contains only JavaWS, no applets anymore); install to run *JNPL* files
|
||||
applets:: are obsolete technology; Not implemented in any recent package
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ After the installation is complete, you can reboot into your installed system an
|
|||
|
||||
Anaconda is a fairly sophisticated installer.
|
||||
It supports installation from local and remote sources such as CDs and DVDs, images stored on a hard drive, NFS, HTTP, and FTP.
|
||||
Installation can be scripted with http://pykickstart.readthedocs.io/en/latest/[kickstart] to provide a fully unattended installation that can be duplicated on scores of machines.
|
||||
Installation can be scripted with https://pykickstart.readthedocs.io/en/latest/[kickstart] to provide a fully unattended installation that can be duplicated on scores of machines.
|
||||
It can also be run over VNC on headless machines.
|
||||
A variety of advanced storage devices including LVM, RAID, iSCSI, and multipath are supported from the partitioning program.
|
||||
Anaconda provides advanced debugging features such as remote logging, access to the python interactive debugger, and remote saving of exception dumps.
|
||||
|
|
|
|||
|
|
@ -115,11 +115,11 @@ Run `analog` without the `-o` option to see how exactly does a fitting configura
|
|||
Also notice that it uses the same message format for remote logging as anaconda does, but you can of course modify this to specify any format you want.
|
||||
|
||||
=== See also
|
||||
* link:http://www.rsyslog.com/doc[Rsyslog documentation]
|
||||
* link:https://www.rsyslog.com/doc/master/index.html[Rsyslog documentation]
|
||||
* `man tailf`
|
||||
|
||||
== Remote logging via virtio
|
||||
QEMU/KVM in Fedora 13 and onwards allows one to create virtual machines with link:http://fedoraproject.org/wiki/Features/VirtioSerial[multiple virtio char devices] exposed to the guest machine.
|
||||
QEMU/KVM in Fedora 13 and onwards allows one to create virtual machines with link:https://fedoraproject.org/wiki/Features/VirtioSerial[multiple virtio char devices] exposed to the guest machine.
|
||||
One such device can be used to forward anaconda logs to the host machine.
|
||||
In that way we can get logs forwarded in real time, as soon the anaconda logging subsystem is initialized (early) and not need to wait for the network to come up.
|
||||
Also, it's the only way to forward the logs in a no-network setup.
|
||||
|
|
@ -178,8 +178,8 @@ If you are using virt-install you can configure it with the --channel option:
|
|||
|
||||
=== See also
|
||||
* link:https://fedoraproject.org/wiki/Features/VirtioSerial[VirtioSerial]
|
||||
* link:http://wiki.libvirt.org/page/Virtio[Virtio at the libvirt wiki]
|
||||
* link:http://libvirt.org/formatdomain.html#elementsConsole[libvirt domain XML format]
|
||||
* link:https://wiki.libvirt.org/page/Virtio[Virtio at the libvirt wiki]
|
||||
* link:https://libvirt.org/formatdomain.html#elementsConsole[libvirt domain XML format]
|
||||
|
||||
== Anaconda logs on the running system
|
||||
After every successful installation, anaconda logs are copied into `/var/log` on the system you just installed.
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The Fedora Project FAQ and the more informal, unofficial
|
|||
http://fedorafaq.org[1] provide useful answers on commonly asked
|
||||
questions. However, the unofficial site is not associated with or
|
||||
supported by the Fedora Project. You can find many interesting things
|
||||
using a search engine like http://google.com[Google].
|
||||
using a search engine like https://google.com[Google].
|
||||
link:Third_party_repositories[Third party repositories] might contain
|
||||
software that has been not been included in the official Fedora software
|
||||
repository.
|
||||
|
|
@ -88,7 +88,7 @@ MIME type you were searching for. There are a few common reasons why
|
|||
Fedora may not have support for a MIME type:
|
||||
|
||||
* Many MIME types are Windows-only. You may be able to use
|
||||
http://en.wikipedia.org/wiki/Wine_(software)[Wine] to run a Windows
|
||||
https://en.wikipedia.org/wiki/Wine_(software)[Wine] to run a Windows
|
||||
program under Linux that supports your MIME type.
|
||||
* Some MIME types are only supported by proprietary or
|
||||
link:Package_Not_Found#Patents[patent encumbered] software.
|
||||
|
|
@ -103,7 +103,7 @@ WARNING: This information is provided only for answering common questions from F
|
|||
|
||||
[[what-is-a-software-patent]]
|
||||
=== What is a software patent?
|
||||
A patent is a set of exclusionary rights granted by a government to a patent holder for a limited period of time, usually 20 years from the earliest effective filing date of the patent application. These monopoly rights are granted to patent applicants in exchange for their disclosure of the invention claimed by the patent. Once a patent is granted in a given country, the patent holder may exclude someone from making, using, selling or importing embodiments of the claimed invention in that country. Software patents are different from copyright or trademarks despite being lumped together with them under the collective term link:http://www.gnu.org/philosophy/not-ipr.html[Intellecutal Property].
|
||||
A patent is a set of exclusionary rights granted by a government to a patent holder for a limited period of time, usually 20 years from the earliest effective filing date of the patent application. These monopoly rights are granted to patent applicants in exchange for their disclosure of the invention claimed by the patent. Once a patent is granted in a given country, the patent holder may exclude someone from making, using, selling or importing embodiments of the claimed invention in that country. Software patents are different from copyright or trademarks despite being lumped together with them under the collective term link:https://www.gnu.org/philosophy/not-ipr.html[Intellecutal Property].
|
||||
|
||||
[[who-is-responsible-for-taking-care-of-any-legal-issues-in-fedora]]
|
||||
=== Who is responsible for taking care of any legal issues in Fedora?
|
||||
|
|
@ -117,7 +117,7 @@ Contrary to common belief, software patents are granted in some form or other in
|
|||
=== Can't you pay the patent license fees for patent encumbered codecs?
|
||||
A codec is a set of methods to encode and decode video or audio information into a data stream. In the case of codecs like MP3 or WMV, the company or companies associated with developing the format are also involved in asserting (or restrictively licensing) patents that purportedly cover the format; we refer to such codecs as "patent encumbered". Other codecs, such as WebM, Ogg Theora or Ogg Vorbis, Dirac, and FLAC, are made available by their developers without asserting patents on their implementations; we refer to such codecs as "patent unencumbered". Fedora includes comprehensive support for open, patent-unencumbered codecs but is unable to include support for the patent encumbered ones.
|
||||
|
||||
Patent licenses usually require the licensee to pay royalties based on the number of users. Since Fedora is free and open source software, the effective number of users is essentially unrestricted. Patent holders are generally unwilling to give a blanket patent license for unlimited use; moreover, the royalty payments would be too high for it to be practical for the Fedora Project, or its sponsors, to pay them. Proprietary operating systems like Microsoft Windows link:http://www.softwarefreedom.org/resources/2007/patent-tax.html[include the costs of third-party patent licenses paid by Microsoft in the pricing of the product] as sold to end users. Fedora is not sold commercially, so there is no way to recoup these substantial expenses.
|
||||
Patent licenses usually require the licensee to pay royalties based on the number of users. Since Fedora is free and open source software, the effective number of users is essentially unrestricted. Patent holders are generally unwilling to give a blanket patent license for unlimited use; moreover, the royalty payments would be too high for it to be practical for the Fedora Project, or its sponsors, to pay them. Proprietary operating systems like Microsoft Windows link:https://www.softwarefreedom.org/resources/2007/patent-tax.html[include the costs of third-party patent licenses paid by Microsoft in the pricing of the product] as sold to end users. Fedora is not sold commercially, so there is no way to recoup these substantial expenses.
|
||||
|
||||
Even if funds were available to do so, such royalty-bearing patent licenses would have to be compatible with the free/open source software licenses governing the software covered by the patent license. In practice this is usually challenging. For example, the most widely-used FOSS licenses (GPL and LGPL) place constraints on the ability of distributors to distribute software under benefit of third-party patent licenses. Even if the software in question is placed under some other license, distributing such software under benefit of a patent license may make the software effectively non-free and thus incompatible with Fedora legal policies.
|
||||
|
||||
|
|
@ -175,11 +175,11 @@ That is the reality for any sound, image, or document format that is encumbered
|
|||
|
||||
And, since that patent license applies to every copy in use, it's one of the reasons why you are not allowed to freely copy and redistribute software such as Microsoft Windows (although, to be sure, even if software patents did not exist, Microsoft would be unlikely to make Windows free software).
|
||||
|
||||
Fedora, however, has a link:https://docs.fedoraproject.org/en-US/project/objectives/[public promise] to always be freely redistributable by anyone. That is why Fedora cannot include support for patented media formats - it would break this redistribution promise. This means that, out of the box, you can't directly play media files such as Windows Media, MPEG-4 video, or MP3 audio. Fedora supports open media formats such as WebM or Ogg link:http://www.vorbis.com/[Vorbis] and link:https://www.theora.org/[Theora], which are **freely implementable and usable by anyone without a patent license**.
|
||||
Fedora, however, has a link:https://docs.fedoraproject.org/en-US/project/objectives/[public promise] to always be freely redistributable by anyone. That is why Fedora cannot include support for patented media formats - it would break this redistribution promise. This means that, out of the box, you can't directly play media files such as Windows Media, MPEG-4 video, or MP3 audio. Fedora supports open media formats such as WebM or Ogg link:https://xiph.org/vorbis/[Vorbis] and link:https://www.theora.org/[Theora], which are **freely implementable and usable by anyone without a patent license**.
|
||||
|
||||
Red Hat has consistently taken the position that software patents generally impede innovation in software development and that software patents are inconsistent with open source/free software. Red Hat holds a number of software patents for defensive purposes and has a patent policy under which it agrees to refrain from enforcing its patents against any party for exercising rights under certain free and open source software licenses, including GPLv2, GPLv3, LGPLv2.1, and LGPLv3.
|
||||
|
||||
* http://www.redhat.com/legal/patent_policy.html
|
||||
* https://www.redhat.com/en/about/patent-promise
|
||||
|
||||
Red Hat explained why software patents are problematic to the European Patent Office.
|
||||
|
||||
|
|
@ -207,10 +207,10 @@ December 2010, Red Hat filed brief with U.S. Supreme Court opposing expansion of
|
|||
|
||||
[[references]]
|
||||
== References
|
||||
* http://fedoraproject.org/wiki/Forbidden_items
|
||||
* http://fedoraproject.org/wiki/Foundations
|
||||
* http://playogg.org
|
||||
* http://www.gnu.org/philosophy/why-audio-format-matters.html
|
||||
* http://www.dwheeler.com/essays/software-patents.html
|
||||
* https://fedoraproject.org/wiki/Forbidden_items
|
||||
* https://docs.fedoraproject.org/en-US/project/
|
||||
* https://www.fsf.org/campaigns/playogg/en/
|
||||
* https://www.gnu.org/philosophy/why-audio-format-matters.html
|
||||
* https://dwheeler.com/essays/software-patents.html
|
||||
|
||||
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.
|
||||
|
|
@ -469,16 +469,16 @@ log_line_prefix = '%t %u@%r:%d [%p] '
|
|||
|
||||
link:PostgreSQL/README.rpm-dist[Full RPM packaging documentation]
|
||||
|
||||
http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server[Tuning
|
||||
https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server[Tuning
|
||||
performance]
|
||||
|
||||
http://www.postgresql.org/docs/9.1/static/runtime-config-logging.html[Logging
|
||||
https://www.postgresql.org/docs/9.1/runtime-config-logging.html[Logging
|
||||
configuration]
|
||||
|
||||
http://www.postgresql.org/docs/9.1/static/upgrading.html[Upgrading
|
||||
https://www.postgresql.org/docs/9.1/static/upgrading.html[Upgrading
|
||||
PostgreSQL]
|
||||
|
||||
http://www.postgresql.org/docs/8.3/static/auth-pg-hba-conf.html[pg_hba.conf
|
||||
https://www.postgresql.org/docs/8.3/static/auth-pg-hba-conf.html[pg_hba.conf
|
||||
file]
|
||||
|
||||
See a typo, something missing or out of date, or anything else which can be
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue