gruso
thunderbox
I'm after some help getting my SnapSnap screenshot PND working on systems running from a boot SD. Currently I'm using a script provided by Caine to determine the SD path for creation of a screenshots folder:
This is not working on boot SDs. I have a dirty workaround, but it relies on a certain partition configuration (per Dave1234's SD installer) so is not useful enough to release.
Seems to me that the cleanest solution would be to detect where the OS is running from, and if it's SD, simply save screenshots to the homedir. In reading up on this I was led to compare the contents of /dev in each scenario. There are unique entries when running from NAND, namely 'ubi0', 'ubi1' etc.
I'm thinking the script could check for the presence of one of these, to deduce where the OS is running from. Is this reliable, or even sensible? Is there a better way (probably)?
Code:
dir=$(mount | awk '/^\/dev\/mmcblk0p/ {print $3}')
This is not working on boot SDs. I have a dirty workaround, but it relies on a certain partition configuration (per Dave1234's SD installer) so is not useful enough to release.
Seems to me that the cleanest solution would be to detect where the OS is running from, and if it's SD, simply save screenshots to the homedir. In reading up on this I was led to compare the contents of /dev in each scenario. There are unique entries when running from NAND, namely 'ubi0', 'ubi1' etc.
I'm thinking the script could check for the presence of one of these, to deduce where the OS is running from. Is this reliable, or even sensible? Is there a better way (probably)?
Last edited by a moderator: