This post is more than 5 years old
33 Posts
0
51026
May 14th, 2015 07:00
Cannot create directories (Venue 7840).
Okay, lets try this a third time. This time on my Sager Laptop running Arch Linux. Unlike my DELL tablet, this doesn't crash.
I am trying to create a directory on the SD card in my Venue 7840, however I have been unable to do so due to permissions errors. I find this odd since it should be formated with FAT32. I first tried
cd /storage/sdcard1
mkdir HumbleBooks
in terminal, but failed due to permissions. I then tried in other locations which I assumed would be less likely to be protected. Again failure. I then tried locations that should be protector, and was rewarded with exactly what I expected -- failure. I then installed Cheetah Media's file manager and did the same with that, but each attempt only ended in failure.
How am I suppose to do this? I want to make a directory for my HumbleBundle music and another for books on the SD card, but I can't seem to.
xBIGREDDx
19 Posts
1
May 14th, 2015 14:00
I just tried this with ES File Explorer, and it made me select the SD card through an Android system popup before it would let me create a folder. It's possible that your Cheetah Media app hasn't been updated to support Lollipop's SD card access restrictions. Same story for the terminal app you used.
You can read more about this change in this article from Android Central.
nstgc
33 Posts
1
May 14th, 2015 19:00
Thank you, that worked. I can't believe terminal didn't. The command line should be at the heart of any Linux system.
xBIGREDDx
19 Posts
0
May 14th, 2015 20:00
Well the command line you get from an app is still a limited user-level interface. I imagine a terminal app could be written which requests the right SD card access.
nstgc
33 Posts
0
May 14th, 2015 20:00
No. The issue is in the program mkdir, not the terminal. mkdir should have the appropriate privileges. Google just doesn't care. That is all there is to it.
xBIGREDDx
19 Posts
0
May 14th, 2015 20:00
Each app on an Android system acts as a limited user in the Linux system. It has a username (com.amazon.shopping or com.whoever.terminalemulator). If you've connected over ADB, the ADB shell has its own user as well.
On your sdcard, you'll find a folder tree "Android/data" which contains folders named after various apps. These are equivalent to /home folders on a traditional system. If you open the one named after your terminal app (assuming it's created one) you will have write permission there. Nothing is wrong with mkdir; your terminal app asks mkdir to create a directory, then mkdir checks if your terminal app (a user) has write permission there. Imagine how mkdir works when I ask it to write to /home/nstgc. It tells me I don't have permission. Same situation.
vampirefo
102 Posts
0
May 14th, 2015 21:00
It is a permission problem once you all get root modify platform.xml to allow writing to external sdcard.
xBIGREDDx
19 Posts
0
May 15th, 2015 08:00
Well then you'd better find a new name for the console interface on your desktop Linux box because that's exactly the same way it works...
nstgc
33 Posts
0
May 15th, 2015 08:00
A terminal being restricted like that is no terminal at all. *sigh* GOOGLE, WHAT HAVE YOU DONE!!? Oh well, still better than iOS or Windows...
xBIGREDDx
19 Posts
0
May 15th, 2015 09:00
So you're telling me that if I logged into a shared server and tried to write to.your home directory, there would be no restriction from doing that? If I wanted to take a brand new user account, and I didn't know the admin password, I would still be able to edit the sudoers file? You work on some weird systems.
nstgc
33 Posts
0
May 15th, 2015 09:00
In 14 years I've not once run into such restrictions. Programs or data may be restricted, but not the terminal emulator itself. Certainly not the Getty, which Android lacks all together.
nstgc
33 Posts
0
May 15th, 2015 09:00
Indeed because these are not restrictions on the terminal. They are restrictions on the data. From what I am hearing, the restrictions seem to be on the terminal itself.