File: README.pax

package info (click to toggle)
star 1.5a67-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 5,600 kB
  • ctags: 4,715
  • sloc: ansic: 37,601; sh: 3,198; makefile: 200
file content (66 lines) | stat: -rw-r--r-- 2,432 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
The new command 'spax' implements a POSIX.1 pax style command line interface
on top of star. The command is basically SUSv2/UNIX-98 

The following extensions from SVSv3 / POSIX.1-2001 are implemented:

-	The options -H and -L

-	Support for the PSOX.1-2001 extended TAR header format
	called 'pax'. This makes 'spax' the first pax like command that
	supports this infinitely extensible and highly portable archive
	format.

The following limitations currently apply:

-	No support for the -l option (create hard links if possible
	in copy mode).

-	The privilleges option -pa is ignored

-	The privilleges option -pm will not only not set the mtime
	but also not set the atime in extract and copy mode.

-	without  -po SUID/SGID permission bits are not masked off.

-	Pattern matching for command line type args is not yet POSIX/PAX
	compliant. It should emulate the shell's way of matching file names
	where '/' is not part of the pattern and each path name component
	needs to match separately, but it treats a filename like an unstructured
	piece of text.

A man page is currently missing. Until the man page is ready, use spax -help
or have a look at the POSIX standard.

Although there are several limitations, spax should be POSIX compliant enough
for the everyday work.

Rationale: spax only implements a limited set of options to grant best POSIX
compliance. Anything you can do with spax may also be done with star. To be able
to do this, a new set of options has been added to star for this reason.

/*--------------------------------------------------------------------------*/

The following non POSIX related CPIO limitations currently apply:

-	Reading the -c and -Hcrc formats does not work
	if there are hard links in the archive.

-	When writing the -c and -Hcrc formats, hard links are written
	as separate files.

-	The checksum with the -Hcrc format is not evaluated in extract mode.

-	Reading the binary cpio format is not yet fully supported.
	This format suffers from design related byte order problems.
	Star thus is unable to auto-detect the byte order status in
	all cases. Auto-detection should work if the string lenght
	if the first filename is odd.

-	There is no write support for the binary cpio format

-	Append & Update (star -r & star -u) does not yet work for
	CPIO archives.


These CPIO limitations would be of interest if we would create a 'cpio'
command line program from the star sources.