Installation in an Android Chroot

Install Arch Linux ARM on other devices.

Re: Installation in an Android Chroot

Postby marcelgore » Fri Jan 18, 2013 10:44 am

Hi.

I'm pretty new to this chroot stuff and I'm trying to chroot Arch-Linux on a Nexus 7.
Everything works fine but when i reboot my device, content of arch/ is removed.

Is that normal?

Thanks.
marcelgore
 
Posts: 1
Joined: Fri Jan 18, 2013 10:40 am

Re: Installation in an Android Chroot

Postby Draringi » Sat Feb 16, 2013 11:10 pm

You need to reform the loop device, and then remount it.
Draringi
 
Posts: 1
Joined: Sat Feb 16, 2013 11:07 pm

Re: Installation in an Android Chroot

Postby ScriptJunkie » Sat Mar 09, 2013 8:46 pm

I'm trying to do this on a Nexus 4, what image should I use? I was thinking the armv7 omap 3/4

Any other ideas?
ScriptJunkie
 
Posts: 1
Joined: Sat Mar 09, 2013 8:41 pm

systemctl in chroot

Postby gyurman » Sat Jul 20, 2013 6:22 pm

Hello,

I had a probe with this. But i got a problem:
$this->bbcode_second_pass_code('', 'systemctl status sshd.service
Running in chroot, ignoring request')
Why I can't run any service from chroot?
Could you get me better solution?
Thanks
gyurman
 
Posts: 1
Joined: Sat Apr 20, 2013 5:32 pm

Re: Installation in an Android Chroot

Postby workdowg » Mon Jul 22, 2013 10:45 pm

$this->bbcode_second_pass_quote('', 'W')hy I can't run any service from chroot?
Could you get me better solution?
Thanks
gyurman

Systemd only work on live, running systems that boot with systemd. Looks like I will have to goto another disto for my arm chroot....
workdowg
 
Posts: 16
Joined: Tue Apr 17, 2012 10:57 pm

Re: Installation in an Android Chroot

Postby tincman » Tue Jul 30, 2013 4:50 pm

$this->bbcode_second_pass_quote('gyurman', 'H')ello,

I had a probe with this. But i got a problem:
$this->bbcode_second_pass_code('', 'systemctl status sshd.service
Running in chroot, ignoring request')
Why I can't run any service from chroot?
Could you get me better solution?
Thanks


For sshd I usually start this as the chroot program instead of bash (then use VX ConnectBot to connect to my chroot). This works well enough for me. (aka 'chroot /path/to/chroot sshd'). This forks into the background and properly detaches, so you can close out your terminal and keep sshd running (the downside being a 'kill' command is the only way to shut it down).

As for systemd and/or other services, I think workdawg is correct that systemd only works as process 0. However, there is plenty on using systemd to start chroots and such, it's frustrating there doesn't seem functionalty to run it in a chroot.

For me, this doesn't impact my Arch experience too extensively--most services I would start are for handling network and power and such (which Android handles in this case).
tincman
 
Posts: 25
Joined: Sat Feb 23, 2013 5:27 pm

Previous

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 8 guests