new repository

1 files changed, 6 insertions, 0 deletions

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 @@
+ <h3 class="section">Files and Secondary Storage</h3>  <p>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. </p>  <p>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 <code>write-region</code> function with the <code>write-region-inhibit-fsync</code> variable set to <code>nil</code>. See <a href="writing-to-files">Writing to Files</a>. </p><div class="_attribution">
+  <p class="_attribution-p">
+    Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
+    <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Files-and-Storage.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Files-and-Storage.html</a>
+  </p>
+</div>