Ticket #1952 (new defect) — at Initial Version
mc cd foo.tar#utar does not handle POSIX ustar archives, only GNU tar vendor-specific/legacy ones
| Reported by: | mirabilos | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 4.8.30 |
| Component: | mc-vfs | Version: | master |
| Keywords: | Cc: | miros-discuss@…, zaytsev, mrmazda@…, nerijus@…, szotsaki@… | |
| Blocked By: | Blocking: | ||
| Branch state: | merged | Votes for changeset: |
Description
Hi,
please see http://www.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_06
for the specification of the POSIX ustar interchange format.
GNU cpio (-Hustar), paxtar, and GNU tar --format=ustar
all create archives of this format; bsdtar probably does
as well. However, I cannot cd#utar or “Enter” them in
both mc-4.6.1-16 (MirPorts?) and mc_3:4.7.0-1 (Debian sid).
After looking at tar.c I think you only support the legacy
or vendor-specific/proprietary GNU tar archive format.
The new boot floppies of MirBSD as of today are ustar
archives, with the bootsector squeezed into an ustar
header and closely following the standard. Introspection
would be nice.
Note: See
TracTickets for help on using
tickets.
