Re: Are there typical ways Fedora tends to break? part 2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Although I personally use a snapshot+rollback mechanism, I think for most users a rescue environment is more useful, because from my own experience and what I read from last question, many cases when the system end up cannot boot is from users playing with the boot process (eg grub) and make some mistakes. However conventional snapshot mechanism only backup the root/home partition, not boot and efi partition because of the filesystem limitation. A rescue environment would be helpful to at least help the user restore a grub install and provide a default kernel cmdline that can help the system boot. But of course, if /boot can be snapshotted and rolled back, it would be a very good thing (perhaps change boot partition to btrfs? But I don’t know if it is possible)

On Tue, Jul 26, 2022, at 10:39 PM, Chris Murphy wrote:
OK thanks for the responses so far. I have followup questions for everyone, even if you didn't previously respond.

Do you think a graphical rescue environment would be helpful in troubleshooting system problems?

Do you think a graphical rescue environment using volatile storage, would be useful?  i.e. similar to a Live boot, by default no changes to the system or Live user environment would be written to persistent media; e.g. Firefox cache files and history, or even installing software, would be entirely lost on reboot from this graphical rescue environment

Do you think a mechanism for system snapshots and rollbacks would be useful in troubleshooting system problems?

Do you think a snapshot+rollback mechanism would be more or less useful than a graphical rescue environment, for troubleshooting system problems?

Thanks!
--
Chris Murphy
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure


_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux