summaryrefslogtreecommitdiff
path: root/how_to_archive_with_posix_tar_cpio_and_pax.html
diff options
context:
space:
mode:
Diffstat (limited to 'how_to_archive_with_posix_tar_cpio_and_pax.html')
-rw-r--r--how_to_archive_with_posix_tar_cpio_and_pax.html8
1 files changed, 5 insertions, 3 deletions
diff --git a/how_to_archive_with_posix_tar_cpio_and_pax.html b/how_to_archive_with_posix_tar_cpio_and_pax.html
index e24b8d8..ead23c7 100644
--- a/how_to_archive_with_posix_tar_cpio_and_pax.html
+++ b/how_to_archive_with_posix_tar_cpio_and_pax.html
@@ -11,11 +11,13 @@
<title>How to Archive With POSIX tar, cpio and pax</title>
-<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
+<header>
+<nav><a href="https://ignore.pl">ignore.pl</a></nav>
+<time>22 July 2020</time>
+<h1>How to Archive With POSIX tar, cpio and pax</h1>
+</header>
<article>
-<h1>How to Archive With POSIX tar, cpio and pax</h1>
-<p class="subtitle">Published on 2020-07-22 22:30:00+02:00, last modified on 2022-01-26 19:10:00+01:00
<p>The usual answer to archive anything is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I
intentionally linked to the GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow
and extend POSIX'es standard for tar utility. Or so you would think.