unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: xiliuya <xiliuya@aliyun.com>
Cc: 61385@debbugs.gnu.org
Subject: bug#61385: 30.0.50; android eshell cannot executable file under ~/ directory
Date: Fri, 10 Feb 2023 10:12:09 +0800	[thread overview]
Message-ID: <875yca46bq.fsf@yahoo.com> (raw)
In-Reply-To: <74B87616-449F-40E7-A0B3-42883B1AA91A@aliyun.com> (xiliuya@aliyun.com's message of "Thu, 09 Feb 2023 17:19:53 +0800")

xiliuya <xiliuya@aliyun.com> writes:

> --text follows this line--
>
> My operation is as follows:
> 1. cp /system/bin/sh .
> 2. chmod 755 sh
> 3. ./sh
> 4. libandroid-emacs.so: /data/data/org.gnu.emacs/files/sh: Permission
> denied

This is described under (emacs)Android Environment.  On Android, system
security policy prevents launching executables from read-write
directories.

Free versions of Android allow you to obtain access as the super user.
In that case, run:

  C-x C-f /su:/data/data/org.gnu.emacs/files RET

and run the binary as the super user instead.





  reply	other threads:[~2023-02-10  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  9:19 bug#61385: 30.0.50; android eshell cannot executable file under ~/ directory xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  2:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-10  4:25   ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 10:59     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 12:49       ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  8:15   ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yca46bq.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61385@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=xiliuya@aliyun.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).