[SOLVED] Strange file permissions?

edbarx · 05-24-2014, 02:19 PM

After extracting android-studio to my home directory, I found that the file ownership of its file hierarchy are like these.

Code:

ls -l
total 48
drwxrwxr-x  2 12275 5000  4096 May 24 10:06 bin
-rw-r--r--  1 12275 5000    14 Mar 18 16:42 build.txt
-rw-r--r--  1 12275 5000  1688 Mar 18 16:42 Install-Linux-tar.txt
drwxrwxr-x  5 12275 5000  4096 May 24 10:06 lib
drwxrwxr-x  2 12275 5000  4096 May 24 10:06 license
-rw-r--r--  1 12275 5000 11358 Mar 18 16:42 LICENSE.txt
-rw-r--r--  1 12275 5000   127 Mar 18 16:42 NOTICE.txt
drwxrwxr-x 23 12275 5000  4096 May 24 10:06 plugins
drwxrwxr-x  8 12275 5000  4096 May 24 10:06 sdk
drwxrwxr-x  8 root  root  4096 Mar 21 16:43 sdk2

What does 12275 5000 mean? I am also getting permission denied errors which obviously prevent files from being accessed by the IDE.

I was tempted to use chown to change the file permissions recursively to something more Debian-like.

Emerson · 05-24-2014, 02:29 PM

That means there is no corresponding user and group in your system.

edbarx · 05-24-2014, 02:39 PM

Actually, there are at least two users, myself as an unprivileged user and root.

Emerson · 05-24-2014, 02:45 PM

Try cat /etc/passwd, is there an user with UID 5000?

edbarx · 05-24-2014, 02:54 PM

Code:

$ cat /etc/passwd | grep 5000

Didn't output anything.

Emerson · 05-24-2014, 03:05 PM

So that is the very reason you do not see user and see the UID instead. Same goes for GID.

edbarx · 05-24-2014, 03:10 PM

Should I use chown recursively to change the ownership of the files? I am on Debian Wheezy v7.5

Firerat · 05-24-2014, 03:11 PM

Some distros start the UID at 500, some 1000

I'd just cat ( or less ) said passwd file, and look

you might want to do that in the old environment, to find the names, then get appropriate uid for new system

E.g.
Old system

Code:

cat /etc/{passwd,group} | grep -E "12275|5000"

Then switch out the numbers for names on new one

Firerat · 05-24-2014, 03:15 PM

Quote:

Originally Posted by edbarx

Should I use chown recursively to change the ownership of the files? I am on Debian Wheezy v7.5

Personally I would investgate each file first,

But if they all have same pattern, then yes chown -R

See previous post to get right {u,g}id

jpollard · 05-24-2014, 03:22 PM

I would suggest checking on the Android lists.

It is possible that for the purpose of development there should be an android account used for this.

Alternatively, it is possible these files are supposed to be owned by the user doing development, and the only reason these got odd UID/GID assignments was that the files were untarred by root into the users home directory.

Normally, for files in the users account, the users account would be used to untar them - and thus get owned by the user. This is because tar uses --same-owner by default for root, which is useful for restoring from backup files produced by tar.

edbarx · 05-24-2014, 03:29 PM

The tgz pacakage archive I downloaded, is, I presume according to what I read a Slackware package. I used alien to convert it into a Debian .deb package. Then, used dpkg -i to install it. Oddly enough, the installed files were copied to /android-studio! So, I moved /android-studio to my home directory where there are less privileges.

Firerat · 05-24-2014, 03:32 PM

You know, I totaly missed the android bit.

Android uids are tracked differently

See

Code:

cat /data/system/packages.list

You need root.

becareful with chown -R

Some things in /data/data/org.package.foo/ may be symlinks to files in /data/app-lib
And must remain install:install

edbarx · 05-24-2014, 03:40 PM

I am on Debian Wheezy and there is no /data directory. I know that using chown recursively can ruin an entire installation. I know there is something wrong because, Debian does not install programs to the root directory. These headaches are because the package wasn't properly ported to Debian.

Firerat · 05-24-2014, 03:48 PM

Quote:

Originally Posted by edbarx

I am on Debian Wheezy and there is no /data directory. I know that using chown recursively can ruin an entire installation.

Sorry, my fault I was reacting to Android ..

/data/ is a directory on android systems which holds all of the app configurations along with some 'system' configs etc..

Not entirely certain as to what you are doing

But as jpollard sugested you may just need to untar ( assuming a tar archive) as a standard user

In general it is a bad idea to use a root account to do anything, unless you 'have to’ and know why

edbarx · 05-24-2014, 05:21 PM

Actually, the solution was to change the file ownership recursively! After, the change I was able to create a new project and the full IDE loaded successfully. The only error that I am receiving is that libz.so.1 is not found although it exists.

EDIT:
For the benefit of anyone reading this thread, the solution for the missing libz.so.1 was to install lib32z1. Since, my computer's RAM is limited I opted out of installing the complete set of 32 bit libraries.

So, in short, the solution was to change the file ownership using chown recursively. Anyone using chown in this way, should be aware of the command's potential to destroy an entire installation, so, be aware of the danger and use with caution.

Other than that, enjoy your shiny apps using android-studio. As a last advice, don't use the device (mobile phone) emulator because it is very slow even on good hardware.