View Single Post
Old 12-09-2014, 09:02 PM   #14
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Case View Post
Also was force-upgraded to 5.6.1, also have stuff only running as framework now.

I do however still have a working hacked su binary with suid flag set in:
Code:
/var/local/mkk/su
Managed to get my battery status script to work again by editing its menu.json and changing the launch action to start with
Code:
/var/local/mkk/su -c
This is overly hacky though, what am I missing for things to automatically run as root? I have a regular non-hacked /bin/su that is symlinked to busybox and asks for the root password. Should I switch that with the one in /var/local?
**NO**
The busybox and anything else in /bin will be replaced with the next Amazon upgrade ;
The things in /var/local belong to you, they will not be replaced.

Hackish as it may seem, leave the special su where it is and use a full path to it in any scripting - - that is much more likely to be a stable solution.

Last edited by knc1; 12-09-2014 at 09:05 PM.
knc1 is offline   Reply With Quote