Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #135105 > unrolled thread
| Started by | David Meyer <papa@sdf.org> |
|---|---|
| First post | 2026-05-30 10:57 +0900 |
| Last post | 2026-05-31 19:08 +0000 |
| Articles | 6 — 4 participants |
Back to article view | Back to comp.lang.forth
Gforth Android file access trouble David Meyer <papa@sdf.org> - 2026-05-30 10:57 +0900
Re: Gforth Android file access trouble Martin Nicholas <reply-2026@mgn.org.uk> - 2026-05-30 09:00 +0100
Re: Gforth Android file access trouble Daniel Cerqueira <dan.list@lispclub.com> - 2026-05-30 13:51 +0100
Re: Gforth Android file access trouble David Meyer <papa@sdf.org> - 2026-05-31 08:52 +0900
Re: Gforth Android file access trouble Bernd Paysan <bernd@net2o.de> - 2026-05-31 07:45 +0000
Re: Gforth Android file access trouble Bernd Paysan <bernd@net2o.de> - 2026-05-31 19:08 +0000
| From | David Meyer <papa@sdf.org> |
|---|---|
| Date | 2026-05-30 10:57 +0900 |
| Subject | Gforth Android file access trouble |
| Message-ID | <874ijp1wxb.fsf@localhost> |
I'm running the Gforth 0.7.9_20251001 app on Android 16 smartphone. A few months ago, Bernd helped me here to get around Android's golden caging by creating a directory under /storage/emulated/0/Download for copying files in and out of the Gforth app, and adding that directory to fpath. That worked well at that time, but yesterday I copied a new file into that shared directory (/storage/emulated/0/Download/gforth on my phone) and Gforth cannot find the file with either include or 'sh ls', even though files I copied into the directory months ago still show up as expected. Permissions on all the files in the directory, old and new, is 660 (read+wrote for owner and group). I tried changing perms to 666 (add world read+write), but it had no effect, and permissions were reset to 660 after I restarted the phone. Any idea what's going on with the new file? -- David Meyer Takarazuka, Japan papa@sdf.org
[toc] | [next] | [standalone]
| From | Martin Nicholas <reply-2026@mgn.org.uk> |
|---|---|
| Date | 2026-05-30 09:00 +0100 |
| Message-ID | <20260530090043.70ca3d84@dsklinux.internal> |
| In reply to | #135105 |
On Sat, 30 May 2026 10:57:36 +0900 David Meyer <papa@sdf.org> wrote: > I'm running the Gforth 0.7.9_20251001 app on Android 16 smartphone. > > A few months ago, Bernd helped me here to get around Android's golden > caging by creating a directory under /storage/emulated/0/Download for > copying files in and out of the Gforth app, and adding that directory > to fpath. > > That worked well at that time, but yesterday I copied a new file into > that shared directory (/storage/emulated/0/Download/gforth on my > phone) and Gforth cannot find the file with either include or 'sh > ls', even though files I copied into the directory months ago still > show up as expected. > > Permissions on all the files in the directory, old and new, is 660 > (read+wrote for owner and group). I tried changing perms to 666 (add > world read+write), but it had no effect, and permissions were reset to > 660 after I restarted the phone. > > Any idea what's going on with the new file? > Dying SD-cards silently go read-only all by themselves. Possibly all types of flash memory do this too. Maybe that's it? Android/Linux, I seem to remember, silently re-mounts the disk read-only. -- Regards, Martin Nicholas. E-mail: reply-202605@mgn.org.uk (Address will be valid throughout May). Free Usenet posting accounts are available through: https://www.eternal-september.org/
[toc] | [prev] | [next] | [standalone]
| From | Daniel Cerqueira <dan.list@lispclub.com> |
|---|---|
| Date | 2026-05-30 13:51 +0100 |
| Message-ID | <87o6hx6oxj.fsf@lispclub.com> |
| In reply to | #135106 |
[Multipart message — attachments visible in raw view] — view raw
Martin Nicholas <reply-2026@mgn.org.uk> writes: > On Sat, 30 May 2026 10:57:36 +0900 > David Meyer <papa@sdf.org> wrote: > [...] > Android/Linux, I seem to remember, silently re-mounts the disk > read-only. This last sentence is very confusing for anyone. Does "Android/Linux" mean both the operating systems "Android" and "GNU" (which is also -- wrongly -- called "Linux") ? Or does "Android/Linux" simply mean one operating system, the "Android" ? Maybe skip adding the kernel to the name of the operating system, maybe unless is an operating system that can support different kernel-types, such as the PC operating system "GNU" (with, or "Hurd", or "Linux"). I you meant to say the kernel "Linux" instead, then just say, or "Linux", or "the kernel Linux". People who can /not/ call the proper names to things made this confusion exist, to begin with... Don't take me wrong, I think it is worth this intervention of mine. Cheers, -- The pioneers of a warless world are the youth that refuse military service. ~ Albert Einstein
[toc] | [prev] | [next] | [standalone]
| From | David Meyer <papa@sdf.org> |
|---|---|
| Date | 2026-05-31 08:52 +0900 |
| Message-ID | <87zf1g4fr7.fsf@localhost> |
| In reply to | #135105 |
I tried reinstalling the Gforth app. Now Gforth can see none of the files in .../Download/gforth, new nor old. :( Are my choices to either rooting the phone or running Gforth inside Termux? -- David Meyer Takarazuka, Japan papa@sdf.org
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd@net2o.de> |
|---|---|
| Date | 2026-05-31 07:45 +0000 |
| Message-ID | <10vgove$1cu8p$1@dont-email.me> |
| In reply to | #135105 |
Am Sat, 30 May 2026 10:57:36 +0900 schrieb David Meyer: > Any idea what's going on with the new file? I recently updated Android, too, and can reproduce this. I suppose Google tightened the screws again. What still works is using the one single privileged file browser (the one that comes with the device) to copy such a file into /storage/emulated/0/ Android/data/gnu.gforth/gforth/home and load it from there. IMHO the best way to spend my time on this enshittification of Android is to get net2o's DVCS working good enough that you can edit your files on a PC, and then sync them over to Android with tools all embedded within the Gforth app. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd@net2o.de> |
|---|---|
| Date | 2026-05-31 19:08 +0000 |
| Message-ID | <10vi0vp$1o7cp$1@dont-email.me> |
| In reply to | #135112 |
Am Sun, 31 May 2026 07:45:51 -0000 (UTC) schrieb Bernd Paysan: > Am Sat, 30 May 2026 10:57:36 +0900 schrieb David Meyer: >> Any idea what's going on with the new file? > > I recently updated Android, too, and can reproduce this. I suppose > Google tightened the screws again. Checking for possible workarounds: If Gforth creates the file, it can see and read it even when the file manager edited it. So you might want to define a "touch" command that allows you to quickly create files there, and then overwrite/edit them with the file browser. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://bernd-paysan.de/
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.forth
csiph-web