<div>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Its partly a question & partly an idea. Sorry if its a repost.The way I look at it when we update, upgrade either from CD or on-line if the power goes down is there some sane way so that the it starts the next part of doing things when you boot up the next time. Also are there some/any way/procedure to make it so that it updates something in sessions, say 100 MB over 6 sessions rather than doing the whole upgrade in one go. The use case is pretty simple, you have a user shirish, who lives in developing world where when the mains will fail is no idea & his UPS only gives 5 minutes as backup time. Now in such situation what is he supposed to do other than try his luck? For e.g. just like we do when we update with Gusty, each day there are 10-15 packages & that hardly takes to update. Something similar so its sees no. of packages to update decided by user. Comments, suggestions, flames all welcome. - -- Shirish Agarwal This email is licensed under <a href="http://creativecommons.org/licenses/by-nc/3.0/"> http://creativecommons.org/licenses/by-nc/3.0/</a> 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: <a href="http://firegpg.tuxfamily.org"> http://firegpg.tuxfamily.org</a> iD8DBQFGQ2qwlQ1T+3KaixcRAuUvAKCSuyyJzT5/KNO5e7Fjb6Hhu+tFwgCeNP00 IcFUNcI/ng3Kbp7AnCeTgDM= =YfSv -----END PGP SIGNATURE----- </div>