From Fedora Project Wiki
(Created page with "<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = Install Using GPT on all architectures by Default = {{Change_Proposal_Banner}} == Summary == This is a follow-up for the Fedora 37 change which made GPT the default partition table for x86_64. This change proposes switching to GPT for the other supported architectu...")
 
(Announcing the Change proposal)
 
(13 intermediate revisions by one other user not shown)
Line 7: Line 7:
== Summary ==
== Summary ==


This is a follow-up for the [[Changes/GPTforBIOSbyDefault|Fedora 37]] change which made GPT the default partition table for x86_64. This change proposes switching to GPT for the other supported architectures.
This is a follow-up for the [[Changes/GPTforBIOSbyDefault|Fedora 37]] change which made GPT the default partition table for x86_64. This change proposes switching to GPT for the other supported architectures as well.


== Owner ==
== Owner ==
<!--
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:vtrefny| Vojtech Trefny]]
* Name: [[User:vtrefny| Vojtech Trefny]]
<!-- Include you email address 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. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: vtrefny AT redhat.com
* Email: vtrefny AT redhat.com
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
-->


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAnnounced]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 40: Line 34:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* [Announced]
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/T3BGPFIMRMKWSXS4ZJMJCXXJIOLM3Y4V/ Announced]
* [<will be assigned by the Wrangler> Discussion thread]
* [https://discussion.fedoraproject.org/t/f42-change-proposal-install-using-gpt-on-all-architectures-by-default-system-wide/139538 Discussion thread]
* FESCo issue: <will be assigned by the Wrangler>
* FESCo issue: <will be assigned by the Wrangler>
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: <will be assigned by the Wrangler>
Line 47: Line 41:


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
In Fedora 37 we switched to GPT as the default partition table (disklabel) for x86_64, for Fedora 42 we propose to make the switch for other architectures as well. Because GPT was already the default for ARM64 this means switching to GPT for ppc64le and s390x architectures when installing on an empty disk or when the disk is being completely reset during the installation.
 
Note: for s390x this applies only to disks where MSDOS disklabel is currently being used as the default disklabel, for DASD we'll continue to use the DASD disklabel.


== Feedback ==
== Feedback ==
Line 53: Line 50:


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
    When a Change has multiple benefits, it's better to list them all.


    Consider these Change pages from previous editions as inspiration:
Similarly to the previous change: simplifying the code path and making the same default across all architectures with as few exceptions as possible. Fedora CoreOS now also uses GPT as default on all architectures so this change will also unify our defaults.
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
== Scope ==
* Proposal owners: Change [[Blivet]] to prefer GPT as default partition table on all architectures.
* Proposal owners: Change [[Blivet]] to prefer GPT as the default partition table on all architectures. Proposed upstream pull request: https://github.com/storaged-project/blivet/pull/1322


* Other developers: No work from other developers will be needed.
* Other developers: No work from other developers will be needed.


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/12491 #12491] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
Line 98: Line 70:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
This change will affect only new installations, no change to the partition table will be done during the upgrade.


== Early Testing (Optional) ==
== Early Testing (Optional) ==
<!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. -->


Do you require 'QA Blueprint' support? N
Do you require 'QA Blueprint' support? N
Early testing can be done by using the boot option `inst.disklabel=gpt`. This option tells the installer to use GPT disklabel so it can be used to make sure the system is compatible and will install and boot correctly with GPT.


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  This can be based off of the above section if early testing has been completed. If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
Any of the installer test cases (for example [[QA:Testcase_Anaconda_autopart_(use_all_space)_install]]) can be used to test this. Note that the installer will create a new partition table only when an empty disk is used or when all preexisting devices are selected to be removed, the partition table cannot  be changed when existing partitions are being reused.


A good "how to test" should answer these four questions:
The expected result is that GPT will be used as the partition table type on s390x and ppc64le. `sudo fdisk -l /dev/sdx` can be used to verify that GPT was used by the installer.
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.


Describe what Users will see or notice, for example:
Users shouldn't notice any significant change other than the switch from MSDOS to GPT disklabel. Other than that the user experience during installation, booting or using the system shouldn't change at all.
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


There are no dependencies for this change, all work will be done in [[Blivet]], the library that Anaconda uses for storage configuration.
There are no dependencies for this change, all work will be done in [[Blivet]], the library that Anaconda uses for storage configuration.


== Contingency Plan ==
== Contingency Plan ==
Line 149: Line 98:
* Contingency deadline: Final Freeze
* Contingency deadline: Final Freeze
* Blocks release? Yes
* Blocks release? Yes


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
The change will be documented in [https://github.com/rhinstaller/anaconda/blob/master/docs/release-notes.rst Anaconda release notes] for Fedora 42 similarly to the [https://github.com/rhinstaller/anaconda/blob/master/docs/release-notes.rst#gpt-is-the-default-disk-label-type documentation for the original Fedora 37 change].
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==

Latest revision as of 15:12, 12 December 2024


Install Using GPT on all architectures by Default

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

This is a follow-up for the Fedora 37 change which made GPT the default partition table for x86_64. This change proposes switching to GPT for the other supported architectures as well.

Owner

Current status

  • Targeted release: Fedora Linux 42
  • Last updated: 2024-12-12
  • Announced
  • Discussion thread
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

In Fedora 37 we switched to GPT as the default partition table (disklabel) for x86_64, for Fedora 42 we propose to make the switch for other architectures as well. Because GPT was already the default for ARM64 this means switching to GPT for ppc64le and s390x architectures when installing on an empty disk or when the disk is being completely reset during the installation.

Note: for s390x this applies only to disks where MSDOS disklabel is currently being used as the default disklabel, for DASD we'll continue to use the DASD disklabel.

Feedback

Benefit to Fedora

Similarly to the previous change: simplifying the code path and making the same default across all architectures with as few exceptions as possible. Fedora CoreOS now also uses GPT as default on all architectures so this change will also unify our defaults.

Scope

  • Other developers: No work from other developers will be needed.
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:

Upgrade/compatibility impact

This change will affect only new installations, no change to the partition table will be done during the upgrade.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

Early testing can be done by using the boot option inst.disklabel=gpt. This option tells the installer to use GPT disklabel so it can be used to make sure the system is compatible and will install and boot correctly with GPT.

How To Test

Any of the installer test cases (for example QA:Testcase_Anaconda_autopart_(use_all_space)_install) can be used to test this. Note that the installer will create a new partition table only when an empty disk is used or when all preexisting devices are selected to be removed, the partition table cannot be changed when existing partitions are being reused.

The expected result is that GPT will be used as the partition table type on s390x and ppc64le. sudo fdisk -l /dev/sdx can be used to verify that GPT was used by the installer.

User Experience

Users shouldn't notice any significant change other than the switch from MSDOS to GPT disklabel. Other than that the user experience during installation, booting or using the system shouldn't change at all.

Dependencies

There are no dependencies for this change, all work will be done in Blivet, the library that Anaconda uses for storage configuration.

Contingency Plan

  • Contingency mechanism: Revert the change in upstream
  • Contingency deadline: Final Freeze
  • Blocks release? Yes

Documentation

The change will be documented in Anaconda release notes for Fedora 42 similarly to the documentation for the original Fedora 37 change.

Release Notes