Which makes me ask... INSTEAD of using sipxconfig to "perform an update", how about an option to "PREPARE SYSTEM FOR UPDATE".
- Full backup in separate folder that won't be purged in 30 days or whatever. - Snapshot. - etc. Then you can do an update/upgrade from the CLI. Easier to force a backup than rely on users to do one. I realize this is an improvement request, but... On Tue, Aug 17, 2010 at 1:16 PM, Douglas Hubler <dhub...@ezuce.com> wrote: > On Tue, Aug 17, 2010 at 12:51 PM, Jim Canfield <jcanfi...@emstar.com> > wrote: > > On Tue, Aug 17, 2010 at 11:28 AM, Douglas Hubler <dhub...@ezuce.com> > wrote: > >> > >> On Tue, Aug 17, 2010 at 12:09 PM, Jim Canfield <jcanfi...@emstar.com> > >> wrote: > >> > Considering these are "optional" will these be separate RPM files? > > It's not feasible to keep every update on downloads.sipfoundry.org so > folks may want to keep mirrored copy. > > Also, taking a snapshot before update is a good idea. > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
