Re: chflags(1) unaware utilties

2010-08-11 Thread Alexander Best
On Tue Aug 10 10, ill...@gmail.com wrote: > On 9 August 2010 14:00, Alexander Best 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

Re: chflags(1) unaware utilties

2010-08-10 Thread Roland Smith
On Wed, Aug 11, 2010 at 01:59:50AM +0400, Anonymous wrote: > >> 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!") > >> > >> Is cpio chflags-aware? > > > > To the best of my knowledge the _only_ way to

Re: chflags(1) unaware utilties

2010-08-10 Thread Anonymous
Roland Smith writes: > On Tue, Aug 10, 2010 at 05:22:47PM -0400, ill...@gmail.com wrote: >> On 9 August 2010 14:00, Alexander Best 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 availa

Re: chflags(1) unaware utilties

2010-08-10 Thread Roland Smith
On Tue, Aug 10, 2010 at 05:22:47PM -0400, ill...@gmail.com wrote: > On 9 August 2010 14:00, Alexander Best 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? > > in fact th

Re: chflags(1) unaware utilties

2010-08-10 Thread ill...@gmail.com
On 9 August 2010 14:00, Alexander Best 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

chflags(1) unaware utilties

2010-08-09 Thread Alexander Best
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 [1]. this doesn't seem very lo