View Single Post
Old 10-24-2012, 06:13 PM   #39
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Quote:
Originally Posted by geekmaster View Post
That is strange, but interesting. I and others have experienced locked up kindles when using loop mounts on /mnt/us. But I thought we were supposed to avoid using /mnt/base-us/.

Can somebody please explain the difference between /mnt/us and /mnt/base-us, and when we should use which one, and why the startup scripts generally use /mnt/us?

Is there a reason why a loop mount would hang on /mnt/us but work on /mnt/base-us, or is that just coincidental here?

Thanks.
When they are mounted /mnt/us has exec permissions and the other does not.

That is of course only from my reading of the DIAGS monolithic startup script.
but I have to believe the code is cut-pasted from the main startup. but in terms of mounting details the permissions are set differently

permissions based nomenclature. If there was another permission I missed then you can find it in the upstarts mount section but that was the big difference I noticed between the two calls.

Last edited by twobob; 10-24-2012 at 08:37 PM. Reason: put in some names
twobob is offline   Reply With Quote