7:47 p.m.
On 1/4/22 18:20, Slade Watkins via users wrote:
hi,
> Until when will Fedora 34 be supported?
if I recall correctly, the End of Life (EOL) date is May 17th, 2022. someone else on the
list can correct me if I am wrong though.
> Is it highly recommended that I upgrade to Fedora 35 at this point?
would worry about it closer to EOL.
Three approaches:
Upgrade 1 release close to the EOL of current release. This way you are
moving to a mature release.
Upgrade 2 releases typically at EOL of current release. This lessens
the number of upgrades, but means moving to a immature release.
Upgrade 2 releases some 3 months past EOL of current release. This
lessens the number of upgrades, and you move to a somewhat mature
release. But means operating without any updates (especially security
related) for this period of time.
Choose your poison.
I normally go with choice 2 but often delay and end up with choice 3.
8:03 p.m.
New subject: support term for Fedora 34
On Wed, 5 Jan 2022 20:47:06 -0500
Robert Moskowitz wrote:
Three approaches:
I go with the 4th approach: Keep two separate boot partitions and
upgrade right away in one of them so I can go back to previous
version trivially if it turns out something is horribly wrong.
I running fedora 35 now with no problems, when 36 comes along I'll
install it where 34 currently lives (and hasn't been used since I switched
to 35).
8:12 p.m.
New subject: support term for Fedora 34
On 1/5/22 21:03, Tom Horsley wrote:
On Wed, 5 Jan 2022 20:47:06 -0500
Robert Moskowitz wrote:
> Three approaches:
I go with the 4th approach: Keep two separate boot partitions and
upgrade right away in one of them so I can go back to previous
version trivially if it turns out something is horribly wrong.
I running fedora 35 now with no problems, when 36 comes along I'll
install it where 34 currently lives (and hasn't been used since I switched
to 35).
that sounds interesting, but don't you also need separate / partitions
with all the release specific software?
And only /home and swap partitions can be shared?
8:25 p.m.
New subject: support term for Fedora 34
On Wed, 5 Jan 2022 21:12:04 -0500
Robert Moskowitz wrote:
that sounds interesting, but don't you also need separate /
partitions
with all the release specific software?
Yep. My actual scheme has a tiny grub2 stand alone partition
which uses the "configfile" grub command to be able to boot
one or the other. I install by installing inside a KVM virtual
machine from the DVD image, then use guestmount and rsync to copy
the virtual image to the partion I want it in. Edit a few places
that refer to UUIDs and I can boot it in the new location. The
/ partition is setup with /boot under it, so the KVM install
is just to /, no other partitions created.
I have no idea if this scheme could work under EFI, bur it works
great with old DOS BIOS.
8:49 p.m.
New subject: support term for Fedora 34
On 1/5/2022 8:47 PM, Robert Moskowitz wrote:
Three approaches:
Upgrade 1 release close to the EOL of current release. This way you are moving to a
mature release.
I generally like to recommend staying 1 release behind for stability... but as you note:
Choose your poison.
it's ultimately up to you.
slade
12:12 p.m.
New subject: support term for Fedora 34
On Wed, 5 Jan 2022 21:25:10 -0500
Tom Horsley <horsley1953(a)gmail.com> wrote:
On Wed, 5 Jan 2022 21:12:04 -0500
Robert Moskowitz wrote:
> that sounds interesting, but don't you also need separate /
> partitions with all the release specific software?
Yep. My actual scheme has a tiny grub2 stand alone partition
which uses the "configfile" grub command to be able to boot
one or the other. I install by installing inside a KVM virtual
machine from the DVD image, then use guestmount and rsync to copy
the virtual image to the partion I want it in. Edit a few places
that refer to UUIDs and I can boot it in the new location. The
/ partition is setup with /boot under it, so the KVM install
is just to /, no other partitions created.
I have no idea if this scheme could work under EFI, bur it works
great with old DOS BIOS.
It doesn't work with EFI, because EFI only allows a single version of
any OS; so only a single fedora version. Systemd-boot *does* allow
booting multiple versions of an OS, but *only* EFI.
It can be made to work under EFI by running mkconfig in the EFI
version, and then booting the legacy versions via the EFI menu. Clumsy
for updating kernels, since mkconfig has to be run in both versions
of the OS in order for the EFI mkconfig to pick the changes up.
9:09 p.m.
New subject: support term for Fedora 34
On Jan 6, 2022, at 13:14, stan via users <users(a)lists.fedoraproject.org> wrote:
It doesn't work with EFI, because EFI only allows a single version of
any OS; so only a single fedora version. Systemd-boot *does* allow
booting multiple versions of an OS, but *only* EFI.
That’s not really a limit with EFI. It’s more that the Fedora packages for the EFI data
choose /boot/efi/EFI/fedora, so if you have only one EFI volume, only one fedora directory
can exist.
But you can have multiple EFI volumes, and with boot loader spec configuration, you don’t
need a lot of special configuration in the EFI volume anymore, so I bet you can get away
with multiple EFI executables in different directories on a single EFI volume.
--
Jonathan Billings
5:07 a.m.
New subject: support term for Fedora 34
On Thu, 6 Jan 2022 at 14:13, stan via users <users(a)lists.fedoraproject.org>
wrote:
On Wed, 5 Jan 2022 21:25:10 -0500
Tom Horsley <horsley1953(a)gmail.com> wrote:
> On Wed, 5 Jan 2022 21:12:04 -0500
> Robert Moskowitz wrote:
>
> > that sounds interesting, but don't you also need separate /
> > partitions with all the release specific software?
>
> Yep. My actual scheme has a tiny grub2 stand alone partition
> which uses the "configfile" grub command to be able to boot
> one or the other. I install by installing inside a KVM virtual
> machine from the DVD image, then use guestmount and rsync to copy
> the virtual image to the partion I want it in. Edit a few places
> that refer to UUIDs and I can boot it in the new location. The
> / partition is setup with /boot under it, so the KVM install
> is just to /, no other partitions created.
>
> I have no idea if this scheme could work under EFI, bur it works
> great with old DOS BIOS.
It doesn't work with EFI, because EFI only allows a single version of
any OS; so only a single fedora version. Systemd-boot *does* allow
booting multiple versions of an OS, but *only* EFI.
It can be made to work under EFI by running mkconfig in the EFI
version, and then booting the legacy versions via the EFI menu. Clumsy
for updating kernels, since mkconfig has to be run in both versions
of the OS in order for the EFI mkconfig to pick the changes up.
For UEFI you can have the old OS on an external drive. The main
annoyance on my system is that when you use the "BIOS" option to
select a boot device you get "Fedora" twice with no indication
of which entry is the external drive.
--
George N. White III
10:15 a.m.
New subject: support term for Fedora 34
On Thu, 6 Jan 2022 22:09:42 -0500
Jonathan Billings <billings(a)negate.org> wrote:
But you can have multiple EFI volumes, and with boot loader spec
configuration, you don’t need a lot of special configuration in the
EFI volume anymore, so I bet you can get away with multiple EFI
executables in different directories on a single EFI volume.
Thanks for the information, but you lost me at the multiple EFI
executables in different directories. How would boot know which
executable to choose? I thought it was the /boot/efi/EFI/fedora that
cued it that this is the system to boot. Would there be
/boot/efi/EFI/fedora1, fedora2, etc.? Or maybe
/boot/efi/EFI1/fedora? Would it only show up in the BIOS boot menu?
2:55 p.m.
New subject: support term for Fedora 34
On Jan 7, 2022, at 11:16, stan via users <users(a)lists.fedoraproject.org> wrote:
Thanks for the information, but you lost me at the multiple EFI
executables in different directories. How would boot know which
executable to choose? I thought it was the /boot/efi/EFI/fedora that
cued it that this is the system to boot. Would there be
/boot/efi/EFI/fedora1, fedora2, etc.? Or maybe
/boot/efi/EFI1/fedora? Would it only show up in the BIOS boot menu?
EFI boot entries are built based on the UUID of the volume and then a path to the EFI
executable, so you would just need to create another EFI entry, either for a different EFI
volume with a standard path or the same EFI volume with a different path.
For example, an EFI entry looks like this:
HD(1,800,61800,6d98f360-cb3e-4727-8fed-5ce0c040365d)File(\EFI\fedora\bootx64.efi)
(Just an example I grabbed from the internet)
—
Jonathan Billings
9:48 a.m.
New subject: support term for Fedora 34
On Fri, 7 Jan 2022 15:55:06 -0500
Jonathan Billings <billings(a)negate.org> wrote:
EFI boot entries are built based on the UUID of the volume and then
a
path to the EFI executable, so you would just need to create another
EFI entry, either for a different EFI volume with a standard path or
the same EFI volume with a different path.
For example, an EFI entry looks like this:
HD(1,800,61800,6d98f360-cb3e-4727-8fed-5ce0c040365d)File(\EFI\fedora\bootx64.efi)
(Just an example I grabbed from the internet)
Thanks for that, now I have a string to follow and something I can play
with.
845
days inactive
849
days old
10 comments
6 participants
participants (6)
-
George N. White III -
Jonathan Billings -
Robert Moskowitz -
Slade Watkins -
stan -
Tom Horsley