Talk:Make a backup file: Difference between revisions
Content added Content deleted
(→why external commands are bad: new section) |
(→Why no copying?: new section) |
||
| Line 20: | Line 20: | ||
the motivation to avoid external commands can be illustrated by an experience i had just recently: |
the motivation to avoid external commands can be illustrated by an experience i had just recently: |
||
on a website a framework uses cvs to manage changes to the contents. yesterday i wanted to add something to that site, and i was presented with this error: ''fork() failed with ENOMEM. Out of memory?''. draw your own conclusions...--[[User:EMBee|eMBee]] 03:18, 11 November 2011 (UTC) |
on a website a framework uses cvs to manage changes to the contents. yesterday i wanted to add something to that site, and i was presented with this error: ''fork() failed with ENOMEM. Out of memory?''. draw your own conclusions...--[[User:EMBee|eMBee]] 03:18, 11 November 2011 (UTC) |
||
== Why no copying? == |
|||
Backup involves copying, and must do since otherwise it is the same file and will be modified by the subsequent update. (Or alternatively it has to have some very special support from the OS; there's no POSIX operation for “checkpoint this file to this other name without copying” IIRC.) The whole strength of backups comes from copying. –[[User:Dkf|Donal Fellows]] 15:42, 11 November 2011 (UTC) |
|||