Updating docs for Btrfs by default

[Chris Murphy]

Hi,

This doc is in need of updating for the Btrfs by default feature
approved for Fedora 33:
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...
https://fedoraproject.org/wiki/Changes/BtrfsByDefault

I can fork https://pagure.io/fedora-docs/install-guide and submit
PR's. But I don't think that method is interactive, i.e. it's pretty
much accept the PR or reject it, correct? Any other ideas?

I've identified these specific areas:

- Automatic partitioning -  should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Some partition types - notably the /boot and /usr directories and
the BIOS Boot and EFI partitions - can not be placed on Btrfs
subvolumes. Use standard physical volumes for them (or an LVM logical
volume for /usr). See
Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended
for more information.

- Ext4 is the default and recommended file system used by Fedora
Workstation and Cloud.

- Advice on Partitions

- Recommended Partitioning Scheme (recommendations, sizes all need updates)
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Manual partitioning should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Silverblue
https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/
https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-informat...

- swap - based on your system parameters
    - unrelated to btrfs, but needs updating for swaponzram feature
https://fedoraproject.org/wiki/Changes/SwapOnZRAM


Original list and discussion appears here:
https://pagure.io/fedora-workstation/issue/158#comment-672898


Thanks,

-- 
Chris Murphy

[Leslie S Satenstein]

Hi Docs group.Hi Chris 

I have started to read the text below and I may I present some feedback.
I have a slight rephrase of a sentenceBEFORE
Some screens will be automatically configured depending on your hardware and the type of
media you used to start the installation. You can still change the detected settings in
any screen. Screens which have not been automatically configured, and therefore require
your attention before you begin the installation, are marked by an exclamation mark. You
can not start the actual installation process before you finish configuring these
settings.
AFTERSome screens will be automatically configured depending on your hardware and the type
of media you used to start the installation. You can still change the detected settings in
any screen. Screens which have not been automatically configured,  are marked by an
exclamation mark and therefore require your attention before you begin the installation.
You can not start the actual installation process before you finish configuring these
settings.
CHANGE GO BACK to return
If you incorporate the above change,  there is a "go back"  that could be
replaced with "return" in the following
The terminal multiplexer is running in virtual console 1. To switch from the actual
installation environment to tmux, press Ctrl+Alt+F1. To go back to the main installation
interface which runs in virtual console 6, press Ctrl+Alt+F6.

Software Selection
 My experience with anaconda is:If you select too many groups (eg all) to install,
anaconda will definitely crash before completing the installation. Users should be
cautioned to not install more than the necessary groups, and complete the installation of
the remaining groups post installation  (sudo dnf group list).  

From what I read below, it is very very well written and accolades to those who were the
authors/editors

Regards 
 Leslie
 Leslie Satenstein
Montréal Québec, Canada

 

    On Sunday, August 23, 2020, 9:56:53 p.m. EDT, Chris Murphy
<lists(a)colorremedies.com&gt; wrote:  
 
 Hi,

This doc is in need of updating for the Btrfs by default feature
approved for Fedora 33:
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...
https://fedoraproject.org/wiki/Changes/BtrfsByDefault

I can fork https://pagure.io/fedora-docs/install-guide and submit
PR's. But I don't think that method is interactive, i.e. it's pretty
much accept the PR or reject it, correct? Any other ideas?

I've identified these specific areas:

- Automatic partitioning -  should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Some partition types - notably the /boot and /usr directories and
the BIOS Boot and EFI partitions - can not be placed on Btrfs
subvolumes. Use standard physical volumes for them (or an LVM logical
volume for /usr). See
Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended
for more information.

- Ext4 is the default and recommended file system used by Fedora
Workstation and Cloud.

- Advice on Partitions

- Recommended Partitioning Scheme (recommendations, sizes all need updates)
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Manual partitioning should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Silverblue
https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/
https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-informat...

- swap - based on your system parameters
    - unrelated to btrfs, but needs updating for swaponzram feature
https://fedoraproject.org/wiki/Changes/SwapOnZRAM


Original list and discussion appears here:
https://pagure.io/fedora-workstation/issue/158#comment-672898


Thanks,

-- 
Chris Murphy
_______________________________________________
docs mailing list -- docs(a)lists.fedoraproject.org
To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

[Leslie S Satenstein]

May I make another recommendation
Date & Time

The Date & Time screen allows you to configure time and date-related settings for your
system. This screen is automatically configured based on the settings you selected in
Installing_Using_Anaconda.adoc#sect-installation-gui-welcome, but you can change your
date, time and location settings before you begin the installation.
I would rework it to.If necessary, use the Date & Time screen to configure and confirm
time and date-related settings for your system. This screen is automatically configured
based on the settings you selected in
Installing_Using_Anaconda.adoc#sect-installation-gui-welcome, The Date and Time settings
will determine the timestamps that anaconda uses to create partitions, directories, and
files. 


Regards 
 Leslie
 Leslie Satenstein
Montréal Québec, Canada

 

    On Sunday, August 23, 2020, 9:56:53 p.m. EDT, Chris Murphy
<lists(a)colorremedies.com&gt; wrote:  
 
 Hi,

This doc is in need of updating for the Btrfs by default feature
approved for Fedora 33:
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...
https://fedoraproject.org/wiki/Changes/BtrfsByDefault

I can fork https://pagure.io/fedora-docs/install-guide and submit
PR's. But I don't think that method is interactive, i.e. it's pretty
much accept the PR or reject it, correct? Any other ideas?

I've identified these specific areas:

- Automatic partitioning -  should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Some partition types - notably the /boot and /usr directories and
the BIOS Boot and EFI partitions - can not be placed on Btrfs
subvolumes. Use standard physical volumes for them (or an LVM logical
volume for /usr). See
Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended
for more information.

- Ext4 is the default and recommended file system used by Fedora
Workstation and Cloud.

- Advice on Partitions

- Recommended Partitioning Scheme (recommendations, sizes all need updates)
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Manual partitioning should say Btrfs instead of LVM
https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Ins...

- Silverblue
https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/
https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-informat...

- swap - based on your system parameters
    - unrelated to btrfs, but needs updating for swaponzram feature
https://fedoraproject.org/wiki/Changes/SwapOnZRAM


Original list and discussion appears here:
https://pagure.io/fedora-workstation/issue/158#comment-672898


Thanks,

-- 
Chris Murphy
_______________________________________________
docs mailing list -- docs(a)lists.fedoraproject.org
To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

[Matthew Miller]

On Sun, Aug 23, 2020 at 07:55:45PM -0600, Chris Murphy wrote:
>  I can fork https://pagure.io/fedora-docs/install-guide and submit
>  PR's. But I don't think that method is interactive, i.e. it's pretty
>  much accept the PR or reject it, correct? Any other ideas? 
Sorry, this is slow. But, no -- once create the PR, it can be commented on
in review, and then any changes you push to the branch of your fork from
which you created the PR (whew, that's a mouthful) will be automatically
updated.


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Chris Murphy]

On Wed, Sep 2, 2020 at 12:43 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  On Sun, Aug 23, 2020 at 07:55:45PM -0600, Chris Murphy wrote:
>  > I can fork https://pagure.io/fedora-docs/install-guide and submit
>  > PR's. But I don't think that method is interactive, i.e. it's pretty
>  > much accept the PR or reject it, correct? Any other ideas?
>
>  Sorry, this is slow. But, no -- once create the PR, it can be commented on
>  in review, and then any changes you push to the branch of your fork from
>  which you created the PR (whew, that's a mouthful) will be automatically
>  updated. 
https://pagure.io/fedora-docs/install-guide/pull-request/55
https://pagure.io/fedora-docs/install-guide/pull-request/56

My main strategy is to just fix what's not correct, minimally
invasive, rather than chewing off too much. I created a new branch
with non-btrfs related updates for Installation Destination, because
the UI has changed since Fedora 31. And then made a branch from that
branch with the btrfs related changes.

I thought that this would mean #55 would be non-btrfs; and #56 would
be just the btrfs changes and would be applied on top of #55? :D But
it looks like my imagination doesn't correlate with reality, and
appears #56 contains all the changes (?).

In retrospect, one generic "updates" branch is probably enough. And
keep discretely related changes for each commit.

-- 
Chris Murphy

[Chris Murphy]

Related - there is now a QA Test Case written up for how to reuse an
existing "home" subvolume to mount at /home using Custom partitioning.
https://fedoraproject.org/wiki/QA:Testcase_partitioning_custom_btrfs_pres...

I wonder about the least effort way to incorporate it into docs. Maybe
as a quick doc. And then reference the quick doc as a NOTE inside the
current manual partitioning section of the install guide?
---

A variation on that test case is dual boot Fedora (draft)
https://fedoraproject.org/wiki/User:Sumantrom/Draft/dualboot_f33_btrfs

As in Fedora 33 and Fedora 34 side by side; or Workstation and
Silverblue; or most any mix and match so long as GRUB is the
bootloader. It's the same instructions as reuse /home, but with
emphasis that /boot should not be reformatted or created new, but
shared. This is quite efficient on Btrfs because it's just a different
sysroot subvolume. No repartitioning or reformatting needed to do the
2nd installation.

--
Chris Murphy