From Fedora Project Wiki

  • = Packaging kernel modules for Fedora Extras = ...s Steering Commitee (FESCo) worked out below standard for packaging kernel-modules in Fedora. This standard hopefully solves many pitfalls earlier standards i
    18 KB (2,809 words) - 16:47, 3 June 2008
  • ...n Fedora 26 Boltron, splitting the minimal system further into independent modules allowing for greater flexibility when composing and maintaining the base sy ...nge focuses on modular content structure; [[Changes/ModularRelease]] deals with details regarding modular delivery.
    11 KB (1,685 words) - 19:22, 3 November 2017
  • = NSS load p11-kit modules by default = When NSS database is created, PKCS#11 modules configured in the system's p11-kit will be automatically registered and vis
    12 KB (1,823 words) - 06:56, 29 August 2019
  • ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    10 KB (1,610 words) - 14:05, 23 March 2017
  • {{#fedoradocs: https://docs.fedoraproject.org/en-US/server-working-group/}} ...|Server SIG and Server WG are [https://docs.fedoraproject.org/en-US/server-working-group/ reorganized into one team].}}
    7 KB (1,021 words) - 14:34, 5 December 2021
  • ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.
    15 KB (2,428 words) - 14:34, 14 July 2015
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.
    13 KB (2,120 words) - 10:23, 20 March 2014
  • ...o pip3</code> in Fedora is not safe. Pip shares its installation directory with dnf, can remove dnf-managed files and generally break the Python 3 interpre ...system. '''Never ever ever ever use <code>pip</code> or <code>pip3</code> with <code>sudo</code>.''' Use <code>pip --user</code> or [https://developer.fed
    15 KB (2,406 words) - 13:00, 11 April 2018
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...on of the application server previously known as JBoss Application Server. With the version 8 it makes it possible to run your Java EE 7 applications and m
    13 KB (2,121 words) - 15:29, 16 September 2013
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ges to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release.
    14 KB (2,225 words) - 19:23, 3 November 2017
  • ...28, Fedora will provide a new set of repositories for software and updates with alternative versions from those shipped in the default release. ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.
    11 KB (1,780 words) - 14:35, 2 March 2018
  • ...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved GFS2 is part of the upstream kernel, but is still listed as experimental. The plan is that this will become sta
    11 KB (1,885 words) - 21:25, 27 April 2011
  • ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    11 KB (1,745 words) - 12:08, 15 October 2014
  • ...requires on packages that provide cmake(foo) or place files into the CMake Modules directory. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    8 KB (1,269 words) - 09:30, 25 August 2017
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.
    13 KB (2,044 words) - 11:18, 14 March 2014
  • | A kernel regression and perf testing DO session | Automate Building Custom Atomic Host with Ansible
    7 KB (812 words) - 15:52, 23 March 2019
  • ...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved (this fixes some segfaults seen on i686 (fixed in 0.4), along with numerous other improvements).
    10 KB (1,546 words) - 22:31, 4 October 2011
  • ...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved ...unding ecosystem, most notably with the addition of the npm (Node-packaged modules) package manager and developing packaging guidelines around it.
    10 KB (1,681 words) - 21:36, 2 August 2014
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG = Modules for Everyone <!-- The name of your change proposal --> =
    17 KB (2,659 words) - 17:32, 9 July 2018
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.
    16 KB (2,729 words) - 09:48, 27 August 2013
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)