Re: Reasons for backing up
- From: "void * clvrmnky()" <clvrmnky-uunet@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Feb 2006 16:13:28 -0500
On 22/02/2006 12:50 PM, Randy Howard wrote:
aaJoe wrote[...]
(in article <noemail-9CA147.10532922022006@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>):
So we have basically 3 different reasons to backup: - To archive our work (incremental backup)
- To restore our OS after a hardware failure (clone)
- To restore our OS after a software failure (backdated clone so you don't copy the problem to your new installation and Preference settings for all programs saved - if you know where they are. Where ARE most of them?)
Am I missing anything?
-- you decide to try out the console for the first time, su to root, and for some inexplicable reason type:
# rm -rf /
# cd /tmp
# ls -a
..403403.tmp
..REMOVE_ME_LCK_FILE
..blah
# rm -rf .*
....
And hilarity ensues. This particular nasty may no longer be valid on a lot of POSIX systems, but it taught me to use "echo" before dangerous rm commands from then on.
If it isn't clear why this command might make you sad, consider that ".." will match that file expression. On the SCO box I maintained (!), /dev was the first to go. Lucky for me, as this soon killed all the devices that let commands run.
.
- Follow-Ups:
- Re: Reasons for backing up
- From: Richard E Maine
- Re: Reasons for backing up
- References:
- Reasons for backing up
- From: aaJoe
- Re: Reasons for backing up
- From: Randy Howard
- Reasons for backing up
- Prev by Date: Re: Mac friendly html? one page for the internet
- Next by Date: Re: Reasons for backing up
- Previous by thread: Re: Reasons for backing up
- Next by thread: Re: Reasons for backing up
- Index(es):
Relevant Pages
|
