Date: Wed, 3 Apr 2002 09:03:49 +0200 From: "Anthony Atkielski" <anthony@atkielski.com> To: "Giorgos Keramidas" <keramida@ceid.upatras.gr> Cc: <chat@freebsd.org> Subject: Re: Anti-Unix Site Runs Unix Message-ID: <018301c1dadd$b5a2af90$0a00000a@atkielski.com> References: <20020402113404.A52321@lpt.ens.fr> <3CA9854E.A4D86CC4@mindspring.com> <20020402123254.H49279@lpt.ens.fr> <009301c1da83$9fa73170$0a00000a@atkielski.com> <20020403022446.GB33624@hades.hell.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Giorgos writes: > Err, pardon my ignorance, but I always > thought this is what backups were > invented for. I could be wrong though, > so don't hold it against me :) You're excused. I used to work in technical support, so I know. Yes, you can restore things from backups, but what do you restore, exactly? And how do you know that what you are restoring isn't just a backup of whatever is causing the current problem? When you reinstall, you _know_ what you are putting on the machine (and more importantly, technical support knows). When you restore from backup, you and technical support don't necessarily have any idea what you are putting on the machine, so it may just be wasted time. Backups are for saving _data_, not _programs_. The backup for the software you use is the installation CD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?018301c1dadd$b5a2af90$0a00000a>