shared memory question
JanuszChmiel opened this issue · 8 comments
I have found out, that startarch script contain special command to emulate sharing memory by creating virtual folder /dev/shm. Does it mean, that in this case, build in C library, which is The part of ArchLinux can fully support shared memory? Or is it still necessary to load .so special library to support this feature?
Stale issue message
startarch script contain special command to emulate sharing memory by creating virtual folder /dev/shm
This is created by function _PR00TSTRING_
in variable PROOTSTMNT
which in turn creates the folder for /dev/shm
when it is NOT readable on smartphone. If it is writable on the smartphone, it will simply bind with the device in the smartphone. I would like to hear your feedback about this newly working yay
command.
fully support shared memory?
Possibly, I don't know how setupTermuxArch
configures on all the devices, and have not tested all the possible Arch Linux programs. At present everything appear to be automated properly.
necessary to load .so special library to support this
The automation has currently advanced to the point of being able to make yay
on smartphone easily with the newly TermuxArch created command makeyay
. To answer precisely, no it is not necessary to load .so library as far as I can tell. I would like to know more about the shared object libraries present inside the smartphone:
find -L /system -type f -iname "*.*so" 2>/dev/null|wc -l
1059
Do you have any advice or links to literature regarding how to find out how these shared object files can be analyzed, and what their capabilities are when employed on device?
Previously, shmget and similar function really required special .so library
to work.
Can you enumerate the programs that did not work @JanuszChmiel? A short list, if you could provide one. Thank you for replying quickly.
required special .so library
It is actually unset. Array entry FLHDR1[4]="unset LD_PRELOAD"
unsets the special .so library in the user's/bin
directory. To find out how many times this project unsets, you can use this grep -w unset *.bash
command:
printoutstatements.bash:FLHDR1[4]="unset LD_PRELOAD"
setupTermuxArch.bash:unset LD_PRELOAD
setupTermuxArch.bash: else # unset functions and variables
setupTermuxArch.bash: unset -f $(grep \_\( "$WFILE"|cut -d"(" -f 1|sort -u|sed ':a;N;$!ba;s/\n/ /g')
setupTermuxArch.bash: unset "$NNSET"
When you have started with termuxarch scripts 3 years ago
We were using much earlier versions of Android then. Its' SELINUX requirements and Termux was not as robust as it is today.
Some developers declare that if shared memory works as it should apps should run faster.
Speed can be tested with this stdoutbench.sh
script. If you would like to help develop it, stdoutbench.sh
is at this site.