[qubes-devel] Fedora 34 approaching EOL; Fedora 35 templates available
Dear Qubes Community, Fedora 34 is scheduled to reach EOL (end-of-life [1]) on 2022-06-07, and new Fedora 35 templates are now available for both Qubes 4.0 and 4.1. We strongly recommend that all Qubes users upgrade [2] their Fedora 34 templates and standalones to Fedora 35 before Fedora 34 reaches EOL. We provide fresh Fedora 35 template packages through the official Qubes repositories, which you can install in dom0 by following the standard installation instructions [3]. Alternatively, we also provide step-by- step instructions for performing an in-place upgrade [4] of an existing Fedora template. After upgrading your templates, please remember to switch all qubes that were using the old template to use the new one [5]. For a complete list of template releases that are supported for your specific Qubes release, see our supported template releases [6]. Please note that no user action is required regarding the OS version in dom0. For details, please see our note on dom0 and EOL [7]. [1] https://fedoraproject.org/wiki/End_of_life [2] https://www.qubes-os.org/doc/templates/fedora/#upgrading [3] https://www.qubes-os.org/doc/templates/fedora/#installing [4] https://www.qubes-os.org/doc/templates/fedora/ [5] https://www.qubes-os.org/doc/templates/#switching [6] https://www.qubes-os.org/doc/supported-releases/#templates [7] https://www.qubes-os.org/doc/supported-releases/#note-on-dom0-and-eol This announcement is also available on the Qubes website: https://www.qubes-os.org/news/2022/05/26/fedora-34-approaching-eol-fedora-35-templates-available/ -- Andrew David Wong Community Manager The Qubes OS Project https://www.qubes-os.org -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/93cf3502-aa23-11b2-fe20-565a493bc803%40qubes-os.org.
Re: [qubes-devel] Write access to standalone's Lv
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, May 26, 2022 at 08:36:29AM -0700, Pin dev wrote: > Hello, after an update I don't have qubes-core-agent anymore on a Debian > standalone VM. > However, I did not set a password to the user "user" and root account is > disabled, so I cannot login anymore. > I tried to losetup loop43 /dev/qubes_dom0/vm-dev-root but it appears to be > busy. > After that, I tried to mount /dev/qubes_dom0/vm-dev-root /mnt but it says > wrong fs type. > > Is there any chance I could get back write access to that private volume? Take a look at this doc: https://www.qubes-os.org/doc/mount-lvm-image/ But also, if you haven't restarted that template too many times, you may be able to revert the last update: https://www.qubes-os.org/doc/volume-backup-revert/ - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmKPrWUACgkQ24/THMrX 1yyXsgf/ang8jKCUVKvM8y5Y0VZykp8T4V5ur7S+PAzYRqozefZkbe8HlAEL2el7 yWGlX+bHvb640O3bNZA/BZiQ9NnkJV1hpcbHBFSo1buKTWc37bDGGvfawLZl0bhe weLlU9+uLoR2J/s38b5awDQshGeQN8Af3Y5v8Eb9rd3Cmi/Y0c3n12Qmxn2DPnHw irIzHBf5vHMNYN5HSALcPA/RpOXcvZsG8lmfbVhe2UKnmrrZlYeNuj7x9FobcOtK 1s42h60kyuuvuFOyqlJsZU0hn2NmERxqZn3wkL/xSwMDRiy9hKXxT8T7nI+4cTP8 fStkhMrmDOzDD4LiW1eqn5uRwaB1Gw== =3u48 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/Yo%2BtZsed8Szk4s%2BT%40mail-itl.
[qubes-devel] Write access to standalone's Lv
Hello, after an update I don't have qubes-core-agent anymore on a Debian standalone VM. However, I did not set a password to the user "user" and root account is disabled, so I cannot login anymore. I tried to losetup loop43 /dev/qubes_dom0/vm-dev-root but it appears to be busy. After that, I tried to mount /dev/qubes_dom0/vm-dev-root /mnt but it says wrong fs type. Is there any chance I could get back write access to that private volume? Thank you in advance -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20018131-6540-4578-adc2-8ebc79bf31c0n%40googlegroups.com.
