Jump to content

Talk:pax (command)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Incomplete Information

[edit]

This article omits a lot of important information and history. "pax" is the name given to the command-line utility mentioned here, but also a POSIX-standardized archive format. Somewhat confusingly, the archive format (and it's specification) came after the utility -- the original pax utility only supported the tar and cpio formats. Even more confusingly, the MirBSD pax utility mentioned in this article still doesn't support the pax archive format. — Preceding unsigned comment added by 82.6.177.154 (talk • contribs) 18:19, 18 April 2016 (UTC)[reply]

  • I was about to note similar omissions and errors in the history. This article as currently written implies that pax was created in 2001, which is quite wrong. In fact, it was in the POSIX-2 draft standard right from its original version in September 1991, which took it from the earlier 1003.1b draft. It had already made it into books on the subject by 1991. Jonathan de Boyne Pollard (talk) 21:18, 16 January 2018 (UTC)[reply]

Confusing article

[edit]

Article often is unclear as to whether it means pax (the POSIX-defined utility) or pax (old 4.4BSD implementation) and that's unfortunate. I might try to correct this but it'd really mean huge changes to the article. Hope that's OK. 73.56.195.48 (talk) 15:00, 5 September 2020 (UTC)[reply]

Infobox says "The Windows NT pax command"

[edit]

The infobox says "The Windows NT pax command", which the article also covers POSIX commands. (I'm not fixing this myself, since I don't know the correct headline to be used for the infobox.)

GNU paxutils

[edit]

There is GNU paxutils project. According to the project page, it was started by François Pinard in 1994 or earlier and he maintained the project until 1999. The project's stated objective is to merge cpio, tar and pax commands under one project, which makes sense given the overlap of supported formats by the three commands. The merger never materialized, and instead, tar command added support for pax archive format.

Links:

--Dan Polansky (talk) 13:10, 9 July 2022 (UTC)[reply]

Pax archive format support in pax packages for Linux

[edit]

pkgs.org[1] shows that some Linux distributions have spax or heirloom pax packages available, and these would have support for pax archive format. Examples include Adélie 1.0: heirloom-pax-1.0-r1.apk, AlmaLinux 8: spax-1.5.3-13.el8.aarch64.rpm, Amazon Linux 2: spax-1.5.2-13.amzn2.0.1.x86_64.rpm, CentOS BaseOS aarch64: spax-1.5.3-13.el8.aarch64.rpm, etc.

Groups:

Related bugs:

Related repository:

I would like to double check that spax (Schily pax) really supports pax format, but don't know how. --Dan Polansky (talk) 15:51, 10 July 2022 (UTC)[reply]

At least, README.pax from github.com/mmatuska/star claims support for pax format: "The following extensions from SVSv3 / POSIX.1-2001 are implemented: [...] - Support for the PSOX.1-2001 [sic] extended TAR header format called 'pax'. --Dan Polansky (talk) 17:36, 10 July 2022 (UTC)[reply]

And here is star (Schily tar) SourceForge project: https://sourceforge.net/projects/s-tar/ and possibly related snapshots: https://sourceforge.net/projects/schilytools/files/ .

It seems spax is part of star; at least the downloadable source code archive of star has pax.c and spax.1. --Dan Polansky (talk) 17:04, 10 July 2022 (UTC)[reply]

Pax bugs

[edit]

I found the following bugs reported relating to pax, all of which seem related to MirBSD pax:

MirBSD bugs are further indicated here:

  • pax.1 in MirBSD/mircpio, github.com - which can be seen as HTML probably here - sections STANDARDS and BUGS

Problems with spax from star (Schily tar) can be assessed in part from here:

--Dan Polansky (talk) 12:45, 11 July 2022 (UTC)[reply]

Retrieved from "https://wiki.riteme.site/w/index.php?title=Talk:Pax_(command)&oldid=1204559315"