Re^2: [OT] Tar file with non-identical duplicate files and no paths?

Does this help any?

c:\pgsql>tar -tvf DBD-Pg-2.10.0-Perl5.8.tar
-rwSrwSrw- unknown/unknown   0 2008-08-27 18:45 .exists
-rwSrwSrw- unknown/unknown   0 2008-08-27 18:45 .exists
-rwSrwSrw- unknown/unknown   0 2008-08-27 18:45 Pg.bs
-rwSrwSrw- unknown/unknown 233472 2008-08-27 18:45 Pg.dll
-rwSrwSrw- unknown/unknown    380 2008-08-27 18:45 Pg.dll.manifest
-rwSrwSrw- unknown/unknown    743 2008-08-27 18:45 Pg.exp
-rwSrwSrw- unknown/unknown   1854 2008-08-27 18:45 Pg.lib
-rwSrwSrw- unknown/unknown 568320 2008-08-27 18:45 Pg.pdb
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 Pg
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 auto
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 arch
-rwSrwSrw- unknown/unknown      0 2008-08-27 18:45 .exists
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 bin
-rwSrwSrw- unknown/unknown   2040 2008-08-27 18:46 Pg.html
drwsrwsrwx unknown/unknown      0 2008-08-27 18:46 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 Bundle
-rwSrwSrw- unknown/unknown 225260 2008-08-27 18:46 Pg.html
drwsrwsrwx unknown/unknown      0 2008-08-27 18:46 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:46 lib
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 site
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 html
-rwSrwSrw- unknown/unknown      0 2008-08-27 18:45 .exists
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 Pg
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 auto
-r-Sr-Sr-- unknown/unknown    545 2008-08-20 19:41 Pg.pm
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 Bundle
-rwSrwSrw- unknown/unknown      0 2008-08-27 18:45 .exists
-r-Sr-Sr-- unknown/unknown 160452 2008-08-22 22:25 Pg.pm
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 DBD
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 lib
-rwSrwSrw- unknown/unknown      0 2008-08-27 18:45 .exists
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 script
drwsrwsrwx unknown/unknown      0 2008-08-27 18:45 blib
[download]

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^2: [OT] Tar file with non-identical duplicate files and no paths? Download Code

Replies are listed 'Best First'.
Re^3: [OT] Tar file with non-identical duplicate files and no paths? by LesleyB (Friar) on Sep 13, 2008 at 09:39 UTC
Can you get that tar file to somewhere with a GUI? I don't often use a GUI approach to untarring on Linux but I have 7-zip on a 'doze box. That whole tar file might display okay in a GUI e.g. KDE's Konqueror if you have KDE or 7-Zip on 'doze. Then you could extract the files manually.	[reply]
Re^3: [OT] Tar file with non-identical duplicate files and no paths? by eosbuddy (Scribe) on Sep 13, 2008 at 12:19 UTC
The reason you have all those multiple files is because of the sticky bit set: `rwSrwSrw-` [download] The `S` means that they're immutable so the system creates new ones whenever you untar the files. I would suggest using a GUI and extracting the tar ball and copying just the files you need - after that you will need to modify the properties so that the sticky bit is unset (apologies for not finding an easy way out). Alternatively, you could write a perl script to grab the files you want and delete the folder after untarring (making sure the tar file is extracted into a new folder than in the current working directory).	[reply] [d/l] [select]
Re^4: [OT] Tar file with non-identical duplicate files and no paths? by broomduster (Priest) on Sep 13, 2008 at 12:59 UTC
The reason you have all those multiple files is because of the sticky bit set Actually, `S` indicates (in this case) that the setuid and setgid bits are set AND that the file is not executable by either owner or group. The sticky bit governs certain access permissions for "other" (or "world") and is indicated by a `t` or `T` in the mode string. And none of this really has anything to do with "immutability" of files (which is governed by write permissions for the files and the directory they are being un-tarred to). See man pages for `chmod`, `sticky` and `ls` for the full story.	[reply] [d/l] [select]