Freaky File Owner:Group
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Hey, I was just compiling waldherr.org Junkbuster (the one that puts a blank pixel instead of broken icon) and this happened. I # tar -zxpvf ed the archive and WTF? All the files had invalid owner/groups of 6855/401 ! It wouldn't compile. {suspiciously} Does ext3 have something to do with this? Surely the venerable tar wouldn't do this? {/suspiciously} Right after install of 8 I noticed some 65536/65536 files and fixed them. Am I in for an Excedrin Headache? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE81GXPnQ18+PFcZJsRAvWbAJ494NfPHXRp1ufoQ7PfddhAHKMreACdHZvq acVYjyGZ4/Fa9PSDKZq7w9U= =IzW2 -----END PGP SIGNATURE-----
On Sunday 05 May 2002 00:50, AnonymousCoward wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
. Hey, I was just compiling waldherr.org Junkbuster (the one that puts a blank pixel instead of broken icon) and this happened. I # tar -zxpvf ed the archive and
WTF?
All the files had invalid owner/groups of 6855/401 ! It wouldn't compile.
They're not invalid, just undefined on your system. It is the uid/gid of the person who created the package on the system on which it was created. The reason you get it is that you used the "p" flag to tar. "p" means "preserve permissions". If you use the normal tar xvzf you'd get all files owned by you. //Anders
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . OK, thanks guys. In the tar it is swa:learning. The reason I was concerned though, is right after the 8 install, I found a number of files with 65535:65535, which is invalid. And in / two files had number owner:group. Hopefully this is OK -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE81IcFnQ18+PFcZJsRAnsyAJ4kQXkaeANB0Zo/ai9rAIfFS/StoQCfTHuq aVd1t0/do7p9tvYs65ZO2/4= =X7/v -----END PGP SIGNATURE-----
participants (2)
-
Anders Johansson
-
AnonymousCoward