Linux chroot mount scripts

[gasingvar]

The actual creation of an arm linux chroot image is probably out here on teh internetz somewhere, but I can assist with my mounting shell script (which works).
My image is of a debian arm chroot, and the image filesystem is ext2 (a good idea for fewer writes. ie innately non-journaling), has been used extensively on fw DE .17 and I'm currently trying it out on WW .29 (thank you, miloj).

I would upload my debian img somewhere, but I've actually broken it somewhat (it works for my needs, but it's nonetheless a bit too hacked up to be reliable).

I've modified it somewhat for generalization, some of it is probably wrong and/or redundant, and it IS hackish and ugly, but it works for me (tm).

* the chroot image only need a root account (and probably bash installed, but it usually is)
* You need busybox installed.

* You need to upload your chroot image named linux.img to the internal sdcard in a folder named linux

A shell script to set things up is attached.

What you need to do:

push the install script and run it:

adb push installlinuxstuff.sh /data/local/ 
adb shell sh /data/local/installlinuxstuff.sh

Now you can (from adb shell or terminal emulator on device):

su -
/data/local/mnt/linux.sh
/data/local/mnt/notlinux.sh

Feel free to remove the install script at
/data/local/installlinuxstuff.sh
when you've got it up and running.

Alternative way to run the scripts from adb shell:

adb shell su -c /data/local/mnt/linux.sh
adb shell su -c /data/local/mnt/notlinux.sh

I usually symlink start and stop (in my case deb and undeb) shell scripts placed in /data/local/mnt in /system/bin (ie shell scripts with 'su -c /data/local/mnt/whatever.sh' in them) for easy start an stop from terminal emulator, and if you've gotten this far you may welcome the small advice. (in other words - don't do this unless you _really_ know what you're doing)

 

[zamaditix]

Debian ARMHF or ARMEL?

If you would uploaded it (good place is google drive , sharing as public, as there are no ads or bullshit and the download is extremely fast) I would love to try your image - after modifying your script so it can work on a UHS-1 class MicroSD I want to try running this off of (should give it a little more speed).

 

[gasingvar]

Debian ARMHF or ARMEL?

If you would uploaded it (good place is google drive , sharing as public, as there are no ads or bullshit and the download is extremely fast) I would love to try your image - after modifying your script so it can work on a UHS-1 class MicroSD I want to try running this off of (should give it a little more speed).

Armel (I use the same chroot installation on my phone in a smaller image file (with less stuff installed)). I've got loads of personal stuff all over it and besides - it's somewhat broken. I really don't want to try to fix it.

So I'm working on retracing my steps, creating a clean armhf ext2 image (debian wheezy base installation for now) and redo the mount script, but I can't make any promises on a release date.

Anyhu - there are loads of images (armel, at least) on teh internetz (BT5 and too many ubuntu, for instance).

Just check so our kernel can mount the filesystem.

Edit: if not you can just create a new image file with a filsystem that's mountable and copy the chroot files to it.

 

[EndlessDissent]

So the ideal image for this tablet is armhf? If I wanted to create a Gentoo image, I would go with armv7? I'm just not sure exactly which ARM architecture this tablet is.

 

[zamaditix]

So the ideal image for this tablet is armhf? If I wanted to create a Gentoo image, I would go with armv7? I'm just not sure exactly which ARM architecture this tablet is.

The CPU is the Tegra 3 if you want to google it and it is an ARMv7 w/ NEON extensions chip. ARMv7 specification requires hardware fp so naturally it is ARMhf.

Nice to hear, keep us updated on your progress. I'm currently running an armel copy of Ubuntu 12.04 but it has problems with some packages and others are armhf only.

 

[EndlessDissent]

When I run linux.sh, I get an error that /sdcard can't be mounted because it doesn't exist.

mount: mounting /sdcard on /data/local/mnt/linux/sdcard failed: No such file or directory

I also tried changing the script to mount /mnt/sdcard, but that didn't work either.

 

[gasingvar]

When I run linux.sh, I get an error that /sdcard can't be mounted because it doesn't exist.

mount: mounting /sdcard on /data/local/mnt/linux/sdcard failed: No such file or directory

I also tried changing the script to mount /mnt/sdcard, but that didn't work either.

Yes, it is somewhat hackish, like I wrote. My image has got an sdcard folder (/sdcard) inside of it where I mount /sdcard from android. (Ie chroot and mkdir /sdcard)

 

[FlyingPoo]

followed this:
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-rooted-transformer-prime/

make sure you have busybox installed der. Or at least the cp command in /system/bin

works well on my TF300T, Yea its not native but im currently configuring it for kernel building ;-D

 

[/dev/void]

followed this:
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-rooted-transformer-prime/

make sure you have busybox installed der. Or at least the cp command in /system/bin

works well on my TF300T, Yea its not native but im currently configuring it for kernel building ;-D

Why does the mount script remount a non-existing block device with an ancient (according to android) filesystem?

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

Edit: I read all the scripts, and they all mount that crap. It's not made for transformers, and on the android device it's made for it leaves /system mounted rw after you've run it, and WHEN run (installed) it modifies too much in /system/bin

# At first it copies loads of crap to /system/bin, and then: 
cd /system/bin/
chmod 4777 *

It's not even "hackish" - it's just... wrong...

Will loop1 work every mount?

mknod /dev/loop1 b 7 0
losetup /dev/block/loop1

I'm almost only asking, since this thread was supposed to be about scripts?

 

[EndlessDissent]

Yes, it is somewhat hackish, like I wrote. My image has got an sdcard folder (/sdcard) inside of it where I mount /sdcard from android. (Ie chroot and mkdir /sdcard)

Thanks. I created /sdcard, and it works almost perfectly now. However, mounting devpts at /dev/pts doesn't seem to work. I replaced that line with

mount --bind /dev $mnt/dev

and it seems to work fine. Is there anything wrong with my method?

Why does the mount script remount a non-existing block device with an ancient (according to android) filesystem?

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

Edit: I read all the scripts, and they all mount that crap. It's not made for transformers, and on the android device it's made for it leaves /system mounted rw after you've run it, and WHEN run (installed) it modifies too much in /system/bin

# At first it copies loads of crap to /system/bin, and then: 
cd /system/bin/
chmod 4777 *

It's not even "hackish" - it's just... wrong...

Will loop1 work every mount?

mknod /dev/loop1 b 7 0
losetup /dev/block/loop1

I'm almost only asking, since this thread was supposed to be about scripts?

I'm assuming you're talking about the link in the post you quoted, even though you seem to be referencing the OP's use of the word "hackish". The script in the OP doesn't do any of that stuff. It just creates a few directories in /data/local/mnt/ and writes the mount/unmount scripts, which themselves only un/mount appropriate directories for the tablet. As for your question, I'm not nearly experienced enough to answer it. Sorry.

 

[/dev/void]

Thanks. I created /sdcard, and it works almost perfectly now. However, mounting devpts at /dev/pts doesn't seem to work. I replaced that line with

mount --bind /dev $mnt/dev

and it seems to work fine. Is there anything wrong with my method?

AFAIK your mount seems to be more complete, ie more android hardware goodies accessable from the chroot environment. However - that means more things possibly going wrong (like writing to a device who's critical to the android environment).
Personally I'd try to find what "hardware goodies" and whatnot I'd need to get the chroot environment working optimally, and not mount ALL of /dev.

I'm assuming you're talking about the link in the post you quoted, even though you seem to be referencing the OP's use of the word "hackish". The script in the OP doesn't do any of that stuff. It just creates a few directories in /data/local/mnt/ and writes the mount/unmount scripts, which themselves only un/mount appropriate directories for the tablet. As for your question, I'm not nearly experienced enough to answer it. Sorry.

Yes, and the OP is very honest about his script(s) being "hackish", which I interpret to mean 'not optimal, possibly redundant but working', all of which it is (and I applaud the early release, since for instance I could get things rolling), but the ubuntu image installation and mounting scripts from the other poster ( whom I was addressing ) are plain faulty.

 

[zamaditix]

I am looking for a armhf build of ubuntu or debian that I can chroot (newer the better), if anyone knows of such a build that would be fantastic but if not does anyone know of an easy to follow guide to compile such a thing?

 

[EndlessDissent]

I found two pretty good guides. I mostly followed THIS ONE, but I found that it doesn't mount enough before "first boot", so what I did was follow the guide until the point where you move the image to the tablet. Then I ran the OP's installlinux.sh script, and then the mount script. However, the mount/unmount scripts need to be edited before using them. Comment out the sdcard line and probably the devpts line (mounting devpts didn't work; Bash complained that devpts didn't exist; I had to replace it with the line I mentioned a few posts above, but as /dev/void says, it could be problematic, so be careful). Mount the image, make the /sdcard directory, exit, unmount, and edit the scripts again to mount/unmount /sdcard.

Next time you enter the chroot, feel free to run the

sh /debootstrap/debootstrap --second-stage

command to build the image, and follow the linked guide until the next time it tells you to exit the session (NOTE: The second echo "whatever" > sources.list command is wrong; it should be echo "whatever" >> sources.list; Also, remember to replace "squeeze" with the appropriate Debian version, in my case, "testing"). Instead of exiting right after the apt-get update, I'd recommend playing around with the chroot and configuring whatever apps you install. You can just use the OP's scripts now and ignore the script in the linked guide.

When the guide I linked above gets to this line:

sudo debootstrap --verbose --arch armel --foreign squeeze /mnt/squeeze/ http://ftp.debian.org/debian

just replace armel with armhf, and if you want a testing image, replace squeeze with testing.

Sorry I'm not attaching my image. I made it gigantic (5GB), so I don't really have anywhere to store it, and you probably wouldn't want to download a file that big. Plus, it already has Openbox and a bunch of other things you probably don't want installed. I'm assuming you'd want GNOME or KDE instead.