This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - endotherm
Pages: [1]
1
« on: August 12, 2012, 04:52:52 PM »
wonderful, thanks!
I'm certainly getting the impression that this is a rather different beast than the linux I am used to.
so one last question: can you please review these definitions/assertions, and tell me if I am wrong somewhere?
1) flashing: the process of replacing the rom (os) of the device. does not affect userspace storage.
2) unlocking: the process of reconfiguring mount attrib for the system partition to RW mode.
3) rooting: the installation of tools to control access to systemspace resources (files on /)
4) custom recovery: utilies for backing up the rom to the device or remote storage, and for restoring from the backups at boot time.
5) unlocking bootloader: needed to change to new flavor of rom, but not needed to run rooted stock version. once unlocked, may not be able to be relocked effectively, because of hardware switch.
6) fastboot: a bios like startup menu from which you could access custom recovery utils.
7) factory reset does not live on the device, so an initial stock backup is required if you ever want to go back to stock.
that sound about right? I'm suprised at how much there is to learn on this topic, and I'll feel much better once I have the knowledge and confort to always be able to bring my device back to stock, no matter how I abuse it.
Thanks again
2
« on: August 12, 2012, 01:53:28 PM »
Thanks guys, thats really helpful.
I'll admit, much of why I am interested in rooting my tablet is to constrain some of the more outrageous permissions required by some apps, block ads, etc.
From what you have said and what I've heard about unlocking, the protections on the system partition are largely based on mount options. are there more granular filesystem permissions that can be applied (chown/chmod)? how much control can we exercise over the filesystem, users, groups, service accounts, etc?
3
« on: August 11, 2012, 11:17:14 PM »
ok, that answers many questions. I had assumed 'su' was a reference to the *nix Switch User command (which is sometimes incorrectly called 'superuser', because its most commonly used to switch to the root user's shell). this SuperUser app sounds more like sudo or UAC. so, does SuperUser ask the user for permissions when a restricted action is requested, or do you have to instruct the app to run as root?
4
« on: August 11, 2012, 10:07:57 PM »
I'm new to the whole mobile thing, so I've been looking around but I've been having some trouble determining exactly how rooting manifests to the user. I've seen references to 'su' in the tutorials which leads me to believe that the process enables a root account, but I see no reference to setting a password.
So my question is, is it possible to control tightly what apps get root and what can't? can I prevent malware and bad apps from abusing this privlege, whilst granting me and knowngood apps root happiness? is there an interactive sudo\gksu\kdesu kinda layer for invoking root, or is it more like editing your sudoers?
Pages: [1]
|
Top Boards
'Like' And 'Follow' Us!
Nexus 7 Market
Top Posters
|