![]() ![]() Would result from writing its output, which is not something it shouldĭo. TTY after a crash means that dnf would need to ignore the Tmux/ screen, but that's " far outside the scope ofĪ package manager", Chris Adams said. ![]() In order to do that, though,ĭnf would need to add the functionality of ![]() Sam Varshavchik pointed out that tmux canĪlready handle a crash of the X server, so it should be possible to makeĭnf itself more resistant to those kinds of problems using those Many different experts at system updates have looked at this problemĪnd just say, yeah no, not anymore of that. Snapper, with very fine rollback capabilities. Noses, getting completely atomic updates working with Btrfs and It's why openSUSE has spent a ton of resources, and a few bloody Microsoft and Apple don't allow anything other than offline updates. Ostree>rpm-ostree>atomic host, which affects the entire build system,ĭeployments, updates, and eventually all of the mirrors. Sufficiently impractical that it's not possible. Path required a reboot: " As far as rebooting after every update? Huh? Who does that? Are we Windows?" Trigger the offline update (for GNOME, the desktop simply gives the option Rather avoid that step and that, for servers, it isn't even obvious how to Leaving the system in an indeterminate state.īut rebooting every time there are updates is a pretty heavy-handed ![]() Meant to minimize the possibility of the update breaking something and It then boots to a minimal environment, which is That processĭownloads the packages in the background, then lets the user choose when to Update process has been available since Fedora 18. Robustness against desktop crashes, ssh connection loss, KillUserProcs, andīut Stephen Gallagher thought that would be System-level service (transient or otherwise)? This would greatly increase How hard would it be to make dnf do the rpm transaction inside a proper "duplicated packages" and other messages when trying to rerun the update. Williamson reported that users were getting Update process with them-which may leave that process in an If X, GNOME, or the terminal program crashes, they will take the Number of components that could crash (or restart) due to the update Terminal under GNOME, KDE, or some other desktop environment, there are a The underlying problem is that when running an update in a graphical Users are quite surprised (and unhappy) that it isn't a supported option. The discussion around Williamson's note, however, makes itĬlear that the command is commonly run that way and that at least some It turns out thatĭoing so has never truly been supported-though it works the vast majority " dnf update" within desktop environments. Williamson to post a note to fedora-develĪnd other mailing lists warning people away from running Zypper, or Fedora's yum-or its successor dnf).Ī series of crashes during system updates on Fedora 24 led Adam Line (using tools like Debian's apt-get, openSUSE's Discord: discord.Updating a Linux distribution has historically been done from the command.Post content regarding Fedora Project or Linux in general.This subreddit is not affiliated with or endorsed by the Fedora Project. A community for users, developers and people interested in the Fedora Project and news and information about it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |