Re: chflags(1) unaware utilties
On Tue Aug 10 10, ill...@gmail.com wrote: On 9 August 2010 14:00, Alexander Best arun...@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 [1]. 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 [1] 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. -- -- -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: chflags(1) unaware utilties
On 9 August 2010 14:00, Alexander Best arun...@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 [1]. 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 [1] 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!) Is cpio chflags-aware? -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: chflags(1) unaware utilties
On Tue, Aug 10, 2010 at 05:22:47PM -0400, ill...@gmail.com wrote: On 9 August 2010 14:00, Alexander Best arun...@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? snip in fact the pax(1) manual states that `pax -p e` will preserve everything. this is plain wrong! 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 be sure you have backed up _all_ possible features (flags, extended attributes c) of a UFS filesystem is to use dump(8) restore(8). Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpaV8xQRT0xb.pgp Description: PGP signature
Re: chflags(1) unaware utilties
Roland Smith rsm...@xs4all.nl writes: On Tue, Aug 10, 2010 at 05:22:47PM -0400, ill...@gmail.com wrote: On 9 August 2010 14:00, Alexander Best arun...@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? snip in fact the pax(1) manual states that `pax -p e` will preserve everything. this is plain wrong! 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 be sure you have backed up _all_ possible features (flags, extended attributes c) of a UFS filesystem is to use dump(8) restore(8). Since when did the thread switch to UFS-specific tools? Unless I'm missing smth dump(8)/restore(8) don't work on ZFS. You can use bsdtar(1) in order to save/restore chflags, ACLs and extattrs in a FS-agnostic way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: chflags(1) unaware utilties
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 be sure you have backed up _all_ possible features (flags, extended attributes c) of a UFS filesystem is to use dump(8) restore(8). Since when did the thread switch to UFS-specific tools? The point I was trying to make is that the way to make the most accurate backup is to use the tools native to the filesystem. To the best of my knowledge, only UFS and ZFS actually supports the flags used by chflags(2), and since I don't use ZFS, I used UFS as my example, which means dump/restore. For ZFS you could use 'zfs send' on a snapshot. Unless I'm missing smth dump(8)/restore(8) don't work on ZFS. You can use bsdtar(1) in order to save/restore chflags, ACLs and extattrs in a FS-agnostic way. Since bsdtar is based on libarchive, it has restrictions depending on the type of format you use. See libarchive-formats(5). If you are sure that your filesystem is not using any features that cannot be stored in the libarchive format of your choosing, then by all means, go ahead. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpStmKHpeKqO.pgp Description: PGP signature
chflags(1) unaware utilties
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 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 [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/135516 -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
