Lines Matching refs:ARCHIVE
63 * routines which implement archive and file buffering
82 off_t wrlimit; /* # of bytes written per archive vol */
101 * archive that might be hard to read elsewhere. If all ok, we then
102 * open the first archive volume
118 * we only allow wrblksz to be used with all archive operations
131 * set up buffering system to read an archive
161 * open the archive
185 * Set up the buffering system to append new members to an archive that
186 * was just read. The last block(s) of an archive may contain a format
188 * removed from the archive. The first byte of the trailer is replaced by
189 * the start of the header of the first file added to the archive. The
191 * backwards in the archive to be positioned BEFORE the trailer. Two
195 * back several records (the number depends on the size of the archive
204 * in the archive.
222 tty_warn(0, "Cannot append to an archive that may have flaws.");
227 * in the last archive volume read. (If a is set we still use rdblksz
291 * ARCHIVE mode (write) conditions
295 act = ARCHIVE;
299 tty_warn(1, "Unable to rewrite archive trailer, cannot append.");
305 * A read error occurred on this archive volume. Resync the buffer and
327 "Unable to append when there are archive read errors.");
356 * the poor (and upset user at this point) for the next archive
358 * can extract out of the archive.
362 "Archive read error limit (%d) reached",maxflt);
375 * push the data used during the archive id phase back into the I/O
394 * skip forward in the archive during an archive read. Used to get quickly
397 * 0 if ok, -1 failure, and 1 when EOF on the archive volume was detected.
410 * move within the archive without doing the expensive reads on data we
465 * lot easier to recover if the archive is damaged. zero padding SHOULD
497 * write buffer fills, flush it to the archive and continue
522 * number of bytes copied to the buffer, 0 indicates EOF on archive volume,
597 * file descriptor to the file and the archive structure that describes the
599 archive.
602 * bigger, so reading to the end of file would create an improper archive,
604 * archive if we can avoid it. Of course trying to archive files that are
608 * 0 ok, -1 if archive write failure. a short read of the file returns a
656 tty_warn(1, "File %s was modified during copy to archive",
664 * extract the contents of a file from the archive. If we are unable to
667 * many bytes to skip past to find the next archive header. If the failure
668 * was due to an archive read, we will catch that when we try to skip. If
675 * the performance hit is small. As of this writing, no archive supports
678 * 0 ok, -1 if archive read failure. if we cannot write the entire file,
711 * Copy the archive to the file the number of bytes specified. We have
712 * to assume that we want to recover file holes as none of the archive
755 * if we failed from archive read, we do not want to skip
762 * calculated crc to the crc stored in the archive
876 * the archive volume.
893 * try to fill the buffer. on error the next archive volume is
904 * errors require resync, EOF goes to next archive
923 * force the write buffer to the archive. We are passed the number of
938 * if we have reached the user specified byte count for each archive
945 "User specified archive volume byte limit reached.");
954 * The new archive volume might have changed the size of the
970 * We have enough data to write at least one archive block
1016 * All done, go to next archive
1023 * The new archive volume might also have changed the block
1035 * write failed, stop pax. we must not create a bad archive!
Indexes created Wed Oct 22 06:10:02 GMT 2025