chflags(1) unaware utilties
arundel at freebsd.org
Wed Aug 11 10:08:47 UTC 2010
On Tue Aug 10 10, illoai at gmail.com wrote:
> On 9 August 2010 14:00, Alexander Best <arundel at freebsd.org> wrote:
> > hi there,
> > chflags(1) mentions that a few utilities including pax(1) aren't chflags aware yet. is there a list of all those utilties available somewhere?
> > also: i don't quite understand why this is in the BUGS section of chflags(1) and not in the pax(1) manual itself . this doesn't seem very logical, since the bug doesn't exist in chflags, but in pax not supporting chflags.
> > so if someone decides to use pax and wants to know if there are any problem with it, there's no way for the average user to stumble upon the fact that chflags isn't supported in pax.
> > in fact the pax(1) manual states that `pax -p e` will "preserve everything". this is plain wrong!
> > cheers.
> > alex
> >  http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/135516
> AFIK, pax is a POSIX thing, and as such working
> correctly or sanely would violate its posix nature.
> (POSIX is an anagram of "Pox? Si!")
POSIX specs issue 7 state that `pax -p e` should:
"Preserve the user ID, group ID, file mode bits (see XBD File Mode Bits ), access time, modification time, and any other implementation-defined file characteristics."
don't chflags fall under "other implementation-defined file characteristics"?
> Is cpio chflags-aware?
hmm...no idea. sorry.
More information about the freebsd-questions