ubuntu-phone team mailing list archive

[Torsten Sachse <torsten.sachse@xxxxxxxxx>]

I have to admit that this sounds strange to me. Could you please try to 
execute a very simple bash script in your home directory? That should be 
the easiest way to find out whether it's the same problem.

Just to make absolutely sure: is the file CHROOT/bin/bash present? If so, 
can you execute it without going into your chroot in your terminal either 
with or without ssh?

What did you use to create your chroot? I used debootstrap to create a 
debian jessie on an image file that's mounted to my home directory. That 
way I don't waste internal storage but rather have my image, i.e the 
chroot, on the sd card.

On Friday, 15 May 2015 10:01:58 CEST, Louis Holbrook (for subscriptions 
only, don't use) wrote:
> Thanks for the tip.
>
> Sadly, however, it doesn't work with ssh either for me. I get the same
> error.
>
>
>
> On Thu, 2015-05-14 at 14:02 +0200, Torsten Sachse wrote:
> > Hi. I had the same problem. Try turning on the ssh service using "sudo 
> > service ssh start" (if it's not running already), then ssh 
> > into your phone 
> > from the terminal itself "ssh localhost". Dont forget to add 
> > your own ssh 
> > key to authorized_keys. Then try the chroot command again. For 
> > some reason, 
> > the chroot command works from within an ssh session but not from the 
> > terminal itself when the chroot is located in the home 
> > directory. At least 
> > on my BQ that's the case. I have no idea why. Do any of the developers 
> > know? Somehow, exec permissions seem to be missing on the mount. I can't 
> > even execute a script in my home directory when I'm not in an 
> > ssh session 
> > although I set exec permission on the file via chmod.
> >
> > Hope this helps,
> > Torsten
> >
> > Sent from my awesome BQ
> >
> > On Thursday, 14 May 2015 00:30:40 CEST, Louis Holbrook (for 
> > subscriptions 
> > only, don't use) wrote:
> > > Thanks, this looks promising.
> > >
> > > However, the chroot command only yields:
> > >
> > > chroot: failed to run command ‘/bin/bash’: No such file or directory
> > >
> > >
> > >
> > > On Wed, 2015-05-13 at 17:19 -0400, Rodney Dawes wrote:
> > >> If you want to use CLI tools installed via debs, you need 
> > to do it this
> > >> way:
> > >> 
> > >> 
> > https://askubuntu.com/questions/620740/how-to-install-regularcli-deb-packages-on-bq-aquaris-e4-5-ubuntu-edition/623311#623311
> > >> 
> > >> Making the phone writable and installing debs to the root 
> > partition will
> > >> end up with those installs likely being destroyed at some 
> > point when the
> > >> system image is updated, and/or the phone becoming broken 
> > if you try to
> > >> use apt-get upgrade or dist-upgrade to upgrade the phone. 
> > It isn't built
> > >> around using apt, so using apt is not supported.
> > >> 
> > >> Using a chroot will allow you to install and use CLI utilities as you
> > >> need them, and keep such a system in a container away from the main
> > >> system (unless you bind mount things, but even then only limited
> > >> exposure exists).
> > >> 
> > >> 
> > >> On Wed, 2015-05-13 at 22:26 +0200, Louis Holbrook (for subscriptions
> > >> only, don't use) wrote:
> > >> > I wanted to install the dict cmd line client, but package 
> > can't be found
> > >> > through the standard repositories.
> > >> > 
> > >> > Is there a repository that would have a compatible version for
> > >> > AquarisE4.5(r22).
> > >> > 
> > >> > If a downloadable .deb, which compiled format should I 
> > use, or do I have
> > >> > to compile on the phone directly?
> > >> 
> > >
> > >
> > >