Error installing sudo (works incorrectly) #237
Comments
|
Thank you for contributing to make this project better😎 Keep up and follow to solve this issue. |
|
Here's my sysinfo: This might be slightly off-topic but although it says |
|
This message crops up on Arch Linux x86_64 in QEMU PRoot in Termux: I do not know why it stopped working as expected since Does this link https://github.com/SDRausty/Termux-Archlinux/issues?q=is%3Aissue+sudo help? |
Here termux/proot#32 is where this work around was created. |
@petkar you might want to repeat this question again https://github.com/termux/proot/issues here. |
|
A google search showed that accessing /proc/stat not possible with the API Levels 26 or higher. Google has restricted this to non-system apps. That concludes why top wasn't accessible. (basically because of android) |
petkar
changed the title
See functions from |
Was resolved SDRausty/termux-archlinux#4 here, and https://github.com/SDRausty/TermuxArch/issues?q=is%3Aissue+sudo here, too. It would be nice to see |
@petkar consider reaching out to Arch Linux arm groups too. |
|
I tried adding the link2symlink option to the user account in the startarch file and this fixed the problem with gcc not installing with sudo on the user account. I don't know what other issues this could bring up. Please do let me know. Unfortunately, this still didn't fix the problem with the sudo and sudo still gets installed incorrectly with errors. Here's the installation after adding link2symlink : |
|
I reinstalled a fresh copy to troubleshoot after purging, and some previously unnoticed errors caught my attention. Notice the highlighted errors: error: could not open file: /etc/mtab: No such file or directory error: could not open file: /etc/mtab: No such file or directory error: could not open file: /etc/mtab: No such file or directory These are the same errors that I get while installing packages from pacman. The workaround to this was to copy |
|
Okay I'm really happy that I was able to resolve the sudo issue and get it running clean. Here's what worked for me :
While I'm glad this worked out for me, I'm also concerned about the issues that might come up due to enabling |
|
@petkar thank you for the update.
Disable CheckSpace in pacman.conf. It does not work in chroots. |
|
This commit TermuxArch/TermuxArch@9cd376d resolves the pacman |
|
Okay I reinstalled arch to test this. Thankfully this did work and I was able to install packages normally after disabling checkspace. |
Thanks to you I can completely skip the first step now. |
*This commit TermuxArch/TermuxArch@d524843 resolves the pacman The repository was update with https://github.com/TermuxArch/TermuxArch/blob/master/.scripts/maintenance/do.sums.bash but should have been updated with https://github.com/TermuxArch/TermuxArch/blob/master/.scripts/maintenance/tgen.bash which rebuilds the install script.
Now you should be able to; it's automated.
This can be done in https://github.com/TermuxArch/TermuxArch/blob/master/knownconfigurations.bash#L120 by removing this fragment of code
The command |
Another way to edit the PRoot init statements is
@petkar thank you for sharing your progress here. |
Thank you very much. This does the job. Everything seems to be resolved now. Only the |
You are welcome. It is a pleasure working with you @petkar
If at first you don't succeed, Try, try, try again; I have noticed this when using QEMU. It works, but it is not a one tap install... |
|
I'm thankful for your developments on making it stable. This might be a bit off topic but it does affect this issue indirectly. Whenever I run the installation script on my phone, it always fails to download the archlinux keyring and returns a 404 error only for the first time. I couldn't determine the reason as to why this happens but I'll test this again with VPN and a different device. |
|
This TermuxArch/TermuxArch@161eaba commit automates adding sudo users. |
I get this error while installing sudo :
Then, I copied
/proc/self/mountsfrom my phone to the root-fs. It managed to install but with some errors. Are they critical or can be ignored?Another issue is that I have to copy
/proc/self/mountsto the root-fs every time I run startarch/or as a user from Termux. I added it to copy every time it starts up in .bashrc. I'm not sure if it's the proper solution. What is the cause of this? Is it because/proc/staton the phone is unreadable?The problem is that when I use sudo (as a regular user) to install gcc, it runs into errors and the installation fails, although it installs perfectly when run as root (from startarch). (even fails when I su from the regular user). Here's the error message :
Is this because sudo was incorrectly installed? If so, is it fixable? Or is it a completely unrelated issue? My phone is an Android 10 Mi Note 8 Pro.
The text was updated successfully, but these errors were encountered: