[GRASS5] Owner of source files

  I tried working on the metadata system in (on my system)
/opt/grass/src/scripts/contrib/metadata. When I tried to save a README file
with my notes on what each file appeared to be doing, I couldn't save it. So
I checked the permissions.

  Turns out that this directory (at least) is owned by user "103" in group
"vmware98"! Where did this come from?

  Tracing this through:

  /opt/grass root.root
  /opt/grass/src 103.vmware98

  This is the CVS weekly snapshot from 17 July.

Rich

Dr. Richard B. Shepard, President

                       Applied Ecosystem Services, Inc. (TM)
            2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
                 Making environmentally-responsible mining happen.

Rich Shepard wrote:

  I tried working on the metadata system in (on my system)
/opt/grass/src/scripts/contrib/metadata. When I tried to save a README file
with my notes on what each file appeared to be doing, I couldn't save it. So
I checked the permissions.

  Turns out that this directory (at least) is owned by user "103" in group
"vmware98"! Where did this come from?

  Tracing this through:

  /opt/grass root.root
  /opt/grass/src 103.vmware98

  This is the CVS weekly snapshot from 17 July.

This reflects the UID/GID on the system on which the .tar.gz file was
made. I suspect that the tar file contains numeric UID/GID
information, with the numeric GID stored in the tar file being
allocated to "vmware" on your system ("tar tv ..." to check).

If you perform the extraction as a normal user rather than root (this
would require write permission on /opt, or /opt/grass if it is created
first), you will own all of the files.

--
Glynn Clements <glynn.clements@virgin.net>

On Sun, 29 Jul 2001, Glynn Clements wrote:

This reflects the UID/GID on the system on which the .tar.gz file was
made. I suspect that the tar file contains numeric UID/GID
information, with the numeric GID stored in the tar file being
allocated to "vmware" on your system ("tar tv ..." to check).

  I realize that the permissions come from the source machine, but I was
curious why the number. What you wrote makes sense: tar took the UID rather
than the username. However, I have no idea why the GID was picked,
apparently at random. Strange!

If you perform the extraction as a normal user rather than root (this
would require write permission on /opt, or /opt/grass if it is created
first), you will own all of the files.

  /opt is owned by root; whenever I install software there the entire tree
is owned by root.users.

  Wierd stuff, that tar.

Thanks,

Rich

Dr. Richard B. Shepard, President

                       Applied Ecosystem Services, Inc. (TM)
            2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
                 Making environmentally-responsible mining happen.