PRoot 5.1 ARM version + Cached file translation

151 views
Skip to first unread message

paddy

unread,
Feb 2, 2015, 10:30:46 AM2/2/15
to proo...@googlegroups.com
Hello. Thank you for PRoot! Wonderful.

Seems many of us are using it on Android..

1) When will the ARM version be ready.. ? So that ps is correct.

2) Double TAB on the bash command line is slow under PRoot. I assume this is because of the path translation via stat, that you mention is slow ? Will this be fixed by the cached stat call you talk of in the roadmap ?

I have looked at the source code and was wondering if I could implement the cache myself.. ;-p.. is it in path.c ? Couple of pointers would really help..

Thanks again,

paddy   

ced...@reproducible.io

unread,
Feb 17, 2015, 8:45:35 AM2/17/15
to paddy, proo...@googlegroups.com
Hello Patrick (and sorry for the delay),

On Mon, Feb 02, 2015 at 07:30:46AM -0800, paddy wrote:
> Hello. Thank you for PRoot! Wonderful.
> Seems many of us are using it on Android..

Thanks:)


> 1) When will the ARM version be ready.. ? So that ps is correct.

Oops, I forgot that one; thanks for the notification. It is now
fixed.


> 2) Double TAB on the bash command line is slow under PRoot. I assume
> this is because of the path translation via stat, that you mention is
> slow ? Will this be fixed by the cached stat call you talk of in the
> roadmap ?

You are right, this will be fixed once the path translation is cached,
and/or once I make a PRoot version based on kernel namespaces (the
prototype works fine, but its release is not scheduled yet):

https://github.com/cedric-vincent/PRoot/blob/8385c178f56c7e6e8d669c0acb35d4157bd5a7b5/doc/proot/roadmap.txt#L33


> I have looked at the source code and was wondering if I could implement
> the cache myself.. ;-p.. is it in path.c ? Couple of pointers would
> really help..

That would be great! I made some experiments in the past:

https://groups.google.com/forum/?fromgroups#!searchin/proot_me/cache/proot_me/GQU5s8XR_yU/MCocP70HSQMJ

However I trashed them because they was not reliable enough. To be
reliable, I really think that the cache has to be based on a virtual
file-system structure (aka. VFS), that is, not on paths as it's
currently the case in PRoot. I wrote a VFS outside of PRoot to
validate this new approach:

https://github.com/cedric-vincent/vfs

I'd like to replace everything from "proot/src/path" with this VFS
("proot/src/vfs"). I won't be able to work on that topic anytime
soon, so feel free to give it a try :)

Regards,
Cédric.

Patrick Cerri

unread,
Feb 17, 2015, 8:48:26 AM2/17/15
to ced...@reproducible.io, proo...@googlegroups.com
EXCELLENT!
Reply all
Reply to author
Forward
0 new messages