John Lenz  committed 88be2fe

Add draft on arch on nexus 10

  • Participants
  • Parent commits 0da09f4

Comments (0)

Files changed (1)

File drafts/2013-03-09-arch-latex-and-nexus-10.markdown

+title: Arch Linux and LaTeX on the Nexus 10
+author: John Lenz
+tags: android
+date: March 9, 2013
+# Arch
+Now that we have access to root, we can install Arch.  I mostly followed [this
+guide](, although there are some changes
+since newer versions of Android changed some things around.
+#### Terminal Environment
+First, we need a working terminal environment.  By far the best is a combination of
+* [Terminal Emulator](
+* [Busybox](
+* [Hacker's
+  Keyboard](
+especially as they are all open source.  Install these three apps.  Also, I have a bluetooth
+keyboard which I use for heavy terminal work: the hacker's onscreen keyboard works well though and I
+actually used the hacker's onscreen keyboard for my entire install of Arch since I didn't have my
+bluetooth keyboard yet.
+Busybox will request superuser access and have some stuff about two ways of installing: simple and
+smart install.  How the busybox app works is by installing a single binary busybox and then creating
+a bunch of symlinks to it.  The single busybox binary contains implementations of many tools like
+"cp", "mv", "sed", "awk", "bzip2", "tar", etc.  Busybox knows which command you want to execute
+in two ways: you can either run something like
+~~~ {.bash}
+$ busybox tar <normal tar flags>
+which launches the busybox executable with tar as the first argument.  Or you can create a symlink
+from "tar -> busybox" and then just run tar.  This will still run the busybox executable but busybox
+will check argv[0] and see "tar" in argv[0] and know that it should be acting like tar.  (Busybox
+combining all these tools into a single executable is how it saves so much space.)
+What the busybox android app does is switch to root, temporarily remount the / filesystem
+read-write, copy the busybox binary, create some symlinks, then remount read-only. The busybox
+"smart install" lets you control exactly which symlinks get created and if you want to actually
+replace any of the existing android tools with a symlink to busybox.  (For example, android already
+has an executable "cp" and with smart install you can decide to replace android's cp with a symlink
+to busybox.)  I did not use smart install and instead just pressed the install button.  This creates
+symlinks to all tools that don't already exist and does not replace any of Android's tools.  The
+built in android tools are pretty crappy and don't always support all the command line options
+(which is why you might want to replace them), but when that happens I just run "busybox <tool>
+<options>" instead of using it through the symlink.