Recent Notes

Displaying keyword search results 1 - 3
Created by freyo on August 25, 2011 09:07:40    Last update: August 25, 2011 20:45:43
This is a list of built-in Android permission values: Permission Description Since API Level android.permission.ACCESS_CHECKIN_PROPERTIES Allows read/write access to the "properties" table in the checkin database, to change values that get uploaded. 1 android.permission.ACCESS_COARSE_LOCATION Allows an application to access coarse (e.g., Cell-ID, WiFi) location 1 android.permission.ACCESS_FINE_LOCATION Allows an application to access fine (e.g., GPS) location 1 android.permission.ACCESS_LOCATION_EXTRA_COMMANDS Allows an application to access extra location provider commands 1 android.permission.ACCESS_MOCK_LOCATION Allows an application to create mock location providers for testing 1 android.permission.ACCESS_NETWORK_STATE Allows applications to access information about networks 1 android.permission.ACCESS_SURFACE_FLINGER Allows an application to use SurfaceFlinger's low level features 1 android.permission.ACCESS_WIFI_STATE Allows applications to access information about Wi-Fi networks 1 android.permission.ACCOUNT_MANAGER Allows applications to call into AccountAuthenticators. Only the system can get this permission. 5 android.permission.AUTHENTICATE_ACCOUNTS...
Created by magnum on June 23, 2011 20:15:49    Last update: June 23, 2011 20:29:45
Linux services startup order in general: kernel runs /sbin/init /sbin/init reads /etc/inittab and runs script defined by this line: si::sysinit:/etc/init.d/rcS switches to runlevel defined by id:3:initdefault: which causes /etc/init.d/rc to be called with the current run level. /etc/init.d/rc calls the scripts under the /etc/rc <current_run_level> .d directory (symbolic links to actual scripts under /etc/init.d/ ) in this order: The KILL scripts first (scripts with name starting with K, i.e., rc?.d/Knn name ): "script_name stop" then, the START scripts (scripts with name starting with S, i.e., rc?.d/Snn name ): "script_name start" Within each group (KILL or START), run scripts from lower priority number (i.e., the nn in the symlink name) to higher priority number. The Upstart init daemon does not use /etc/inittab . Instead, it...
Created by voodoo on January 17, 2010 00:15:47    Last update: January 17, 2010 00:15:47
A runlevel is used to group the daemons (services) to start. For the Fedora/Redhat based Linux systems, the primary runlevels are: runlevel 1: Single-User Mode runlevel 2: Multi-User Mode runlevel 3: Multi-User Mode with Networking runlevel 5: X11 (runlevel 3 + X Window System) The typical workstation runs in runlevel 5. Servers without X-server runs in runlevel 3. To determine what runlevel you are using: # /sbin/runlevel To determine what runlevel your system will boot with: # cat /etc/inittab | grep :initdefault: id:5:in... To switch runlevels (replace RUNLEVEL with appropriate number): # /sbin/init RUNLEVEL When you switch runlevel, be sure that you are at a text console so that you don't accidentally kill your session when X-server is killed.