files on standard input as an mtree(8) `specfile' specification, and
write or copy only those items in the specfile.
If the file exists in the underlying file system, its permissions and
modification time will be used unless specifically overridden by the
specfile. An error will be raised if the type of entry in the specfile
conflicts with that of an existing file.
Otherwise, it is necessary to specify at least the following parameters
in the specfile: type, mode, gname or gid, and uname or uid, device
(in the case of block or character devices), and link (in the case of
symbolic links). If time isn't provided, the current time will be used.
leaving the ansi stuff)
- use longlong_t instead of quad_t (etc), and rename *uqd*() -> *ull*()
- clean up the NET2_STAT stuff similar to ftpd; provide #defines and
macros which select which cast to use, etc
- clean up the NET2_FTS and NET2_REGEX #define use
a new volume upon premature end-of-volume (e.g. broken pipe). This is
especially useful in automated environments where error recovery cannot
be performed by a human.
string legally (it strdup()s the argument). How pax-as-tar `-o' ever
worked without a coredump is beyond me...
Also modify pax-as-tar `-o' to do three things, which depend on the
create/extract mode:
- write V7 format archives (which, though part of GNU tar, actually
goes along with the following point--after all, old pax-as-tar created
V7 archives by default);
- write archives with "write_opt=nodir", as pax already did, and as
specified by 4.2BSD;
- extract archives with owner/group set to invoking user, as specified
by SUS.
- minor cleanups to the options parsing code.
- add a cpio frontend.
note: a few GNU/svr4 cpio options are not supported yet (#ifdef
notyet), however all x/open ones are.
that the order of arguments is different if the command flags are specified
without a `-'. I've integrated getoldopt.c from John Gilmore's pdtar which
handles argument parsing correctly.
lukem