[ast-developers] |O_XATTR| support in AST pax(1) ... / was: Re: cd(1) still broken on Solaris/AIX/etc. ...

[Roland Mainz]

[snip]

ok, but why should/shouldn't the other commands mentioned above be able to the same?

Because it's a rare and rarely used ability and feature to deal with
resource forks/XATTR files? I do understand why Roland did it and
Cedric and my people own like it. We're both Apple shops in our labs
and the admins need a way to access file files in emergencies. But I'm
not convinced that putting resource fork/XATTR support into every
utility is a good idea.

maybe I want to pax resource forks and everything
or, don't tell me, read(2)/write(2) don't work on resource forks

open(), read(), write(), mmap() all works for resource forks/XATTR.
They just don't have a name relative to / because neither Apple,
Microsoft or Novell came up with a naming scheme, likely because forks
are 'private' to the parent file they are a child node of.
Solaris /usr/bin/tar can backup resource forks/XATTR files, but I
don't know how to do that. Roland likely knows.

Grumpf... I don't know all the details... but Solaris tar(1)'s source
code is here: http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/tar/
... follow the |atflag| variable:
http://src.illumos.org/source/search?q=atflag&path=%2Fillumos-gate%2Fusr%2Fsrc%2Fcmd%2Ftar%2F&project=illumos-gate
(the page may take a while to load... ;-/ ) ...

The only other source of information is the tar(3head) manpage...
accessible on Solaris via $ man -l3head tar #:
-- snip --
NAME
tar.h, tar - extended tar definitions

SYNOPSIS
#include <tar.h>


DESCRIPTION
The <tar.h> header defines header block definitions as fol-
lows.


General definitions:


Name Value Description
_____________________________________________________________
TMAGIC "ustar" ustar plus null byte
TMAGLEN 6 length of the above
TVERSION "00" 00 without a null byte
TVERSLEN 2 length of the above



Typeflag field definitions:



Name Value Description
_____________________________________________________________
REGTYPE '0' regular file
AREGTYPE '\0' regular file
LNKTYPE '1' link
SYMTYPE '2' symbolic link
CHRTYPE '3' character special
BLKTYPE '4' block special
DIRTYPE '5' directory
FIFOTYPE '6' FIFO special
CONTTYPE '7' reserved



Mode field bit definitions (octal):



Name Value Description
_______________________________________________________________________________
TSUID 04000 set UID on execution
TSGID 02000 set GID on execution
TSVTX 01000 on directories, restricted
deletion flag
TUREAD 00400 read by owner
TUWRITE 00200 write by owner special
TUEXEC 00100 execute/search by owner
TGREAD 00040 read by group
TGWRITE 00020 write by group
TGEXEC 00010 execute/search by group
TOREAD 00004 read by other
TOWRITE 00002 write by other
TOEXEC 00001 execute/search by other



Types used in ancillary files:



Name Value Description
ACL_HDR 'A' Access Control List
LBL_TYPE 'L' Trusted Extensions file label
DIR_TYPE 'D' Trusted Extensions directory label



Attribute types used in Trusted Solaris ancillary files that
are interpreted by Trusted Extensions for backward compati-
bility:



Name Value Description
SLD_TYPE 'S' Single-level directory component
PATH_TYPE 'P' Path component
MLD_TYPE 'M' Multi-level directory component
FILE_TYPE 'F' Must handle files differently
APRIV_TYPE 'P' Allowed privileges data type in file
FPRIV_TYPE 'p' Forced privileges data type in file
COMP_TYPE 'C' Path components, use for MLD
ATTR_FLAG_TYPE 'F' File attribute flag bytes data type
LK_COMP_TYPE 'K' Link data path component


ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:

____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Interface Stability | See below. |
|_____________________________|_____________________________|



The general definitions, the typeflag field definitions, and
the mode field bit definitions are Standard. The types used
in ancillary files and the attribute types used in Trusted
Solaris ancillary files are Evolving.

SEE ALSO
pax(1), attributes(5), standards(5)
-- snip --

----

Bye,
Roland