diff options
| author | Tim Kientzle <kientzle@acm.org> | 2016-09-04 09:36:39 -0700 |
|---|---|---|
| committer | Tim Kientzle <kientzle@acm.org> | 2016-09-04 09:36:39 -0700 |
| commit | 6fd583026d4b335a2af7018058c34877f9c192e9 (patch) | |
| tree | 1bee6910fba2c54f7f85cebebe6e612ecae86f56 /README.md | |
| parent | 24e2f6ba8b43c70c0b2e06c78f1649665a9a28b8 (diff) | |
| download | libarchive-6fd583026d4b335a2af7018058c34877f9c192e9.tar.gz | |
Convert README to markdown
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 11 |
1 files changed, 8 insertions, 3 deletions
@@ -185,7 +185,8 @@ questions we are asked about libarchive: * In particular, libarchive's modules to read or write a directory tree do use `chdir()` to optimize the directory traversals. This can cause problems for programs that expect to do disk access from - multiple threads. + multiple threads. Of course, those modules are completely + optional and you can use the rest of libarchive without them. * The library is _not_ thread aware, however. It does no locking or thread management of any kind. If you create a libarchive @@ -213,5 +214,9 @@ questions we are asked about libarchive: to read/write entries to disk, there are convenience functions to make this especially easy. -* Note: "pax interchange format" is really an extended tar format, - despite what the name says. +* Note: The "pax interchange format" is a POSIX standard extended tar + format that should be used when the older _ustar_ format is not + appropriate. It has many advantages over other tar formats + (including the legacy GNU tar format) and is widely supported by + current tar implementations. + |