From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/elisp/files-and-storage.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 devdocs/elisp/files-and-storage.html (limited to 'devdocs/elisp/files-and-storage.html') diff --git a/devdocs/elisp/files-and-storage.html b/devdocs/elisp/files-and-storage.html new file mode 100644 index 00000000..a5064be8 --- /dev/null +++ b/devdocs/elisp/files-and-storage.html @@ -0,0 +1,6 @@ +

Files and Secondary Storage

After Emacs changes a file, there are two reasons the changes might not survive later failures of power or media, both having to do with efficiency. First, the operating system might alias written data with data already stored elsewhere on secondary storage until one file or the other is later modified; this will lose both files if the only copy on secondary storage is lost due to media failure. Second, the operating system might not write data to secondary storage immediately, which will lose the data if power is lost.

Although both sorts of failures can largely be avoided by a suitably configured file system, such systems are typically more expensive or less efficient. In more-typical systems, to survive media failure you can copy the file to a different device, and to survive a power failure you can use the write-region function with the write-region-inhibit-fsync variable set to nil. See Writing to Files.

+

+ Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
+ https://www.gnu.org/software/emacs/manual/html_node/elisp/Files-and-Storage.html +

+
-- cgit v1.2.3