On Wed, 24.08.11 13:39, Bill Nottingham (nott...@redhat.com) wrote: > > r /upgrade > > > > That way we can be sure that the flag file is removed as soon as the > > root fs is writable. > > > > The rest of the earlier suggestion would stay the same. > > So, thinking about the UI of this, I'm assuming the flow would be. > > 1. PK notices updates that require this mechanism > 2. PK asks 'Upgrade Now?' > 2a. Yes -> step 4 > 2a. No -> continue session. (Perhaps a persistent notification here.) > 3. On user-initiated shutdown/restart, ask again. > 3a. Yes -> step 4 > 3b. No, reboot as normal. Notification returns on next login. > 4. PK drops the flag in > 5. PK reboots into upgrade > 6. Upgrade reboots into system once done > > The main points I'm addressing here: > > 1) You don't want to have to try and get all the infrastructure up to > ask what the user wants to do on boot; do this in the normal session. > 2) You don't want to offer to upgrade on the next reboot, have the user > keep working, have a system crash/battery die/whatever, and then start > upgrading when the user reboots to finish their document. > > You may already be heading this way in the design, but the gnome.org page > wasn't clear yet.
I generally agree with your ideas, except maybe that I'd drop 3, and just keep the request in the message tray as long as the user didn't agree to it. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
