'Offline System Updates' will come as feature for Fedora 18. Reading<a href="http://freedesktop.org/wiki/Software/systemd/SystemUpdates"> your official page</a>: <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"> The system update script now creates a btrfs snapshot (if possible), then installs all RPMs. After completion (regardless whether the update succeeded or failed) the /system-update symlink is removed. In addition, on failure it reverts to the old btrfs state (modulo the aforementioned symlink), on success it leaves the newly made changes in place. </blockquote><div> BTRFS ? Will 'Offline Updates' be available only with BTRFS ? How will be managed all kernel modules come from extra Fedora repositories (like RPMFusion) ? Will be possible disable completely 'Offline System Updates' ? <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Disadvantages of this approach over in-system updates: 1 The system is rebooted twice. </blockquote></div>This is a very inconvenient. The short boot times obtained with systemd are useless if every update (frequent in Fedora) needs of twice reboot. Regards. -- Antonio Trande "Fedora Ambassador" mail: <a style="color:rgb(153,153,153)" href="mailto:sagitter@fedoraproject.org" title="mailto:sagitter@fedoraproject.org" target="_blank">mailto:sagitter@fedoraproject.org</a> Homepage: <a style="color:rgb(153,153,153)" href="http://www.fedora-os.org" title="http://www.computer-legacy.net" target="_blank">http://www.fedora-os.org</a> Sip Address : sip:sagitter AT <a href="http://ekiga.net" target="_blank">ekiga.net</a> <a href="http://jabber.org/" title="http://jabber.org" target="_blank">Jabber</a> :sagitter AT <a style="color:rgb(153,153,153)" href="http://jabber.org" target="_blank">jabber.org</a> GPG Key: 19E6DF27