Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am on termux with root permission.
My phone has aarch64 cpu architecture.
I'm trying to chroot a ubuntu filesystem with amd64 architecture
i've seen and this https://unix.stackexchange.com/a/222981
here's my command
sudo chroot ubuntu /bin/qemu-x86_64-static /bin/bash --login
i logged in successfully but when i run command
ls or any
it's give an error like Exec format error
then i tried that command with qemu-x86_64-static like qemu-x86_64-static /bin/ls it's execute successfully
any idea for this???
i think i can add alias for all command for starts with qemu-x86_64-static but that's not good idea...
You need to tell the kernel that when it sees an arm64 binary it should run it by launching QEMU. The mechanism for this is called "binfmt-misc", and to configure it you need to write data in the correct format to special files in the host system's /proc/sys/fs/binfmt_misc/ directory. Most Linux distros will do this for you automatically when you install their QEMU packages, but obviously Android won't do this for you.
First check that your phone's kernel has binfmt-misc support compiled in at all: there should be a file /proc/sys/fs/binfmt_misc/status and if you cat its contents it should read enabled. If not, try modprobe binfmt_misc. If after that the status file is still not there then you won't be able to get this working unless you can somehow build a new kernel for your phone.
If the support is present in your phone's kernel, you can try the qemu-binfmt-conf.sh script that upstream QEMU ships as a mechanism for registering QEMU with the binfmt-misc machinery:
https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh
(This is just a script which writes the correct lines of data to /proc/sys/fs/binfmt_misc/register.)
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 12 months ago.
Improve this question
I've got a problem on Debian 10.11 (but I think it's not only Debian related) with onboot mounting Windows share.
cifs-utils 2:6.8-2 amd64 Common Internet File System utilities
cat /etc/fstab | grep share2
gives
//10.100.0.204/share2 /home/share2 cifs auto,vers=default,rw,file_mode=0775,dir_mode=0775,noperm,gid=100,username=user1,password=passwordhard 0 0
When I type:
command mount /home/share2 Works as expected.
dmesg gives me an errors:
[ 5.045482] CIFS VFS: Error connecting to socket. Aborting operation.
[ 5.046471] CIFS VFS: cifs_mount failed w/return code = -101
I think that linux tries too early to mount samba shares.
What can I do about it?
I know that I can use crontab and:
#reboot root sleep 15; mount /home/share2
as workaround but I like resolving problems at source.
If the problem is indeed samba service is loading too fast.
It is possible to edit samba service file.
Add Requires=<a service-name that need to be loaded prior to samba>
This trick is the official pattern to control/manage/order systemd service loading.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am using GPT/UEFI system. I installed KDE Neon and I was using it without any problem since the summer. Then today, I deleted /EFI/ubuntu/ and after I reboot the system, it stuck at grub command line "grub> ".
1- I can boot the system by writing following command to the grub command line
configfile (hd0,gpt1)/EFI/neon/grub.cfg
2- Also following command works
configfile (hd0,gpt2)/boot/grub/grub.cfg
3- Also following command works
set prefix=(hd0,gpt2)/boot/grub
set root=(hd0,gpt2)/boot
normal
4- I tried followings to fix by booting the system but non of them works
- boot-repair program
- update-grub
- apt install --reinstall grub-efi && update-grub
So this is the situation. How can I fix the problem ?
Thanks in advance.
I have just fixed the problem!
I boot the system manually by entering command to grub> command line. (one of the command that I mentioned in the question)
I opened a terminal.
cd /boot/efi/EFI
cp -r ./neon ./ubuntu
Reboot and it works fine.
I think the problem is specific for KDE Neon because it gave me exactly same problem when I installed it to a new computer. Grub is not looking inside the "/EFI/neon" directory. Instead, it is looking inside "/EFI/ubuntu" but cannot find it so it causes problem.
BTW, the reason I named new folder as "ubuntu" is that KDE Neon is Ubuntu based.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
After kernel update, the version of kernel in uname is not updated itself.
It is a problem because all the modules are loaded through it, so I had to rename the folder with new modules to the old version (as a temporary solution) but I would like to solve this problem properly.
~: pacman -Q linux
linux 4.9.11-1
~: uname -r
4.9.8-1-ARCH
Have you replace the kernel image (bzImage or vmlinuz)?. If yes then there is some issue with your grub conf parameter. Otherwise you need to replace the kernel image as well as.
Below are the steps which you need to update the kernel:
1) Replace your kernel image (vmlinuz or bzImage you can check the name from your grub conf parameters) with the existing kernel image..
2) Copy the new module folder (containing all new modules) into the /lib/modules folder..
3) Sometimes there may be issue during module loading. So you can run the depmod -a command inside your new module folder.
4) Reboot the board and check the kernel version and your kernel image details (like kernel version and date of compiled kernel image) though uname -a command.*
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I'm running ubuntu 14.04 on an EC2
After running apt-get upgrade
I'm prompted with a screen that asks me to reinstall GRUB boot loader
The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices.
How do I know which device should I select?
What if I have mounted on my machine some additional EBS, should I select them as well?
Can I avoid this prompt, during the upgrade or supply some defaults to the command?
The following prompt is
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.
install the package maintainer's version
keep the local version currently installed
show the differences between the versions
show a side-by-side difference between the versions
show a 3-way difference between available versions
do a 3-way merge between available versions (experimental)
start a new shell to examine the situation
The same q's here:
How do I know which one should I select?
Can I avoid this prompt, during the upgrade or supply some defaults to the command?
I had similar problem.
1) If you take a look man apt-get, you will find a configuration option-o.
It allows to set options for Debian package manager dpkg.
2) In the manual man dpkg you can find set of options --force-confdef(force to keep default option without prompting) and --force-confold (force to keep old conf files)
In some sources I found, that people pass env variable DEBIAN_FRONTEND=noninteractive as well, but I could not find it in any manual.
So, the final command in .sh script, that I use to run upgrade:
sudo DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" upgrade
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
As far as I know, Linux container is different from virtual machine. It's lightweight virtualization technology. So I'm wondering if it can be run on a virtual machine which provisioned by hypervisor like xen, kvm or vmware?
I was trying setup a Linux container(docker + LXC userspace tool) on a virtual machine based on zex. It failed.
[root#docker lib]# service docker start
Starting cgconfig service: Error: cannot mount cpuset to /cgroup/cpuset: Device or resource busy
/sbin/cgconfigparser; error loading /etc/cgconfig.conf: Cgroup mounting failed
Failed to parse /etc/cgconfig.conf [FAILED]
Starting docker: [ OK ]
and if trying to run a container:
root#docker lib]# docker run -i -t ubuntu /bin/echo hello world
lxc-start: error while loading shared libraries: liblxc.so.1: cannot open shared object file: No such file or directory
2014/03/27 14:03:27 Error: start: Cannot start container da0d674d3e31a7c36a9e352f64fd84986cbb872e526cb2dd6adb7473d4f5a430: exit status 127
Actually, I followed a blog to do, the author made it, while I screw it.
Any one can explain that? Or simply tell me it can not be ran on a virtual machine. Really appreciate.
Yes, it can. If your VM's operating system supports the appropriate filesystems, and have containers. I suggest you go though as suggested on https://www.docker.io/gettingstarted/ and use a recent Ubuntu release, since that is known to work.