Merge branch 'vagga'

Conflicts:
	README.md

Author: piranna

.gitignore

@@ -1,8 +1,3 @@
 npm-debug.log
 out/
-obj/
-deps/
-bzImage
-initramfs.cpio.gz
-rootfs.iso
-usersfs.img
+.vagga/

Dockerfile

@@ -0,0 +1,5 @@
+FROM usersfs
+
+MAINTAINER Jesús Leganés Combarro 'piranna' <piranna@gmail.com>
+
+ENTRYPOINT ["/init"]

README.md

@@ -5,8 +5,8 @@
 Lightweight operating system using [Node.js](http://nodejs.org) as userspace.
 
 NodeOS is an operating system build entirely in Javascript and managed by
-[npm](https://www.npmjs.com/). Any package in npm is a NodeOS package, which at
-last count was 201,871 packages. The goal of NodeOS is to provide just enough to
+[npm](https://www.npmjs.com). Any package in npm is a NodeOS package, which at
+last count was 206,609 packages. The goal of NodeOS is to provide just enough to
 let npm provide the rest. Since anyone can contribute to npm, anyone can create
 NodeOS packages.
 
@@ -20,50 +20,52 @@ and the Granada University [2nd Free Projects prize](http://osl.ugr.es/bases-de-
 
 ## find us
 
-- Web: please use [github issues](https://github.com/NodeOS/NodeOS/issues) for discussion
+- Web: please use [github issues](https://github.com/NodeOS/NodeOS/issues) for
+  discussion
 - IRC: join `#node-os` on Freenode
 
 ## introduction
 
 NodeOS is a Node.js based operating system, built-off of the Linux kernel.
 The eventual goal of NodeOS is to produce images that can be run on
 
-- **real hardware** like desktop PCs, servers or Raspberry Pi
+- **real hardware** like desktop PCs, laptops, servers or Raspberry Pi
 - **cloud providers** like Joyent, Amazon or Rackspace
 - **virtual machines** like QEmu, VirtualBox, VMWare and KVM
 - **PaaS providers** like Heroku or Joyent's Manta
-- **container providers** like Docker
+- **container providers** like Docker or vagga
 
 Core development is being done in layers. There could be some differences to
 adjust better to each target platform, but the general structure is:
 
 - *barebones* custom Linux kernel with an initramfs that boots to a Node.js REPL
-- *initramfs* Initram environment to mount the users partition & root filesystem
+- *initramfs* Initram environment to mount the users partition & boot the system
 - *rootfs*    Read-only partition image to host Linux kernel and initramfs files
 - *usersfs*   multi-user environment with the same behaviour of traditional OSes
 
 ### Booting process
 
-All the layers are bootable, leading *barebones* to a Node.js
-[REPL](http://nodejs.org/api/repl.html) prompt. *initramfs* (and by extension
-*rootfs*) lead to a Node.js REPL by default if not using a custom one. In all
-the cases, it will be used an initramfs as root filesystem and all the changes
-will be lost when powered-off.
+All the layers are bootable, leading *barebones* to a raw naked Node.js
+[REPL](http://nodejs.org/api/repl.html) prompt as PID 1. *initramfs* (and by
+extension *rootfs*) lead to a Node.js REPL where `/dev` and `/proc` filesystems
+are mounted. In all the cases, it will be used an initramfs as root filesystem
+and all the changes will be lost when powered-off.
 
 If a users partition is being set at boot time, it will be mounted and the
 system will considerate each one of the folders there as the home folder for a
-valid user on the system and executing a ```init``` file in the root of each of
-them. If found, ```root``` user will be the first to be considerated and will
-have access to all the home directories.
+valid user on the system and will execute a `init` file in the root of each of
+them. If found, `root` user will be the first to be considerated and will have
+access to all the home directories, but by design it will not be possible to
+elevate permissions once the system has booted.
 
 ### Hacking
 
 If you are hacking on NodeOS as a somewhat production server, you are likely
 building *usersfs* images since each user is isolated of others, but you can be
 able to customize all layers. For example, you could be able to modify
 *initramfs* to login the users and mount their home folders from a cloud service
-or craft a system without global services (no ```root``` user) or also dedicate
-a full NodeOS instance to a single application.
+or craft a system without global services (no `root` user) or also dedicate a
+full NodeOS instance to a single Node.js application.
 
 
 # Pre-build images
@@ -77,57 +79,54 @@ The *iso* can be written to a CD-R or flashed to an USB pendrive, but will only
 provide the read-only rootfs and the changes will be done in memory loosing them
 after reboot, so you'll need to set manually a read-write usersfs partition if
 you want to persist them. On the other hand, if you want to flash it to an USB
-pendrive, it's recomended to so it by using ```bin/istallUSB``` command so it
-will create automatically a read-write usersfs partition to fill the remaining
-space so your changes will persist.
+pendrive, it's recomended to so it by using `bin/istallUSB` command so it will
+create automatically a read-write usersfs partition to fill the remaining space
+so your changes will persist.
 
 # Build NodeOS in three steps
 
 NodeOS require to have first installed some build tools, on a Ubuntu based
-system you can install them by executing the file ```bin/install-dependencies```
+system you can install them by executing the file `bin/install-dependencies`
 
 1. Download the project source code and build NodeOS for QEmu:
-
-    ```bash
-    git clone git@github.com:NodeOS/NodeOS.git
-    cd NodeOS
-    npm install
-    ```
-By default it generate some files that can be used with QEmu, compiled for your
-current architecture. You can be able to configure the build process by passing
-some environment variables. For example, to force to build for 32 bits, use
-```PLATFORM=qemu_32 npm install``` instead.
-
+   ```bash
+   git clone git@github.com:NodeOS/NodeOS.git
+   cd NodeOS
+   npm install
+   ```
+   By default it generate some files that can be used with QEmu, compiled for
+   your current architecture. You can be able to configure the build process by
+   passing some environment variables. For example, to force to build for 32
+   bits, use `PLATFORM=qemu_32 npm install` instead.
 2. Pick some microwave pop-corn and go to see a movie. No, really, do it.
 3. Exec your fresh compiled NodeOS image:
-
-    ```bash
-    npm start
-    ```
-It will automatically detect what CPU architecture will need to be used on QEmu.
+   ```bash
+   npm start
+   ```
+   It will automatically detect what CPU architecture will need to be used on
+   QEmu.
 
 ...and profit! :-D
 
 If you encounter an error when building NodeOS, take a look at
 [the wiki](https://github.com/NodeOS/NodeOS/wiki/Fixing-NodeOS-Build-Errors) or
 open an [issue](https://github.com/NodeOS/NodeOS/issues).
 
-# NodeOS on Docker
+# NodeOS on LXC containers (Docker and vagga)
 
-Currently Docker support is unmaintained. There are some NodeOS images on Docker
-Hub, but they are outdated. If you are interested on help or testing, you can
+Currently LXC containers support is unmaintained due to imposibility of mount
+filesystems from inside them. There are some NodeOS images on Docker Hub, but
+they are totally outdated. If you are interested on help or testing, you can
 build them from source code.
 
 ## Quick Start
 
 1. [Install Docker](http://docs.docker.io/en/latest/installation/)
 2. One Liner
-
-    ```bash
-    sudo docker run -t -i nodeos/nodeos
-    ```
-
-or learn how to make a [Custom Build](http://node-os.com/blog/get-involved/)
+   ```bash
+   sudo docker run -t -i nodeos/nodeos
+   ```
+   or learn how to make a [Custom Build](http://node-os.com/blog/get-involved/)
 
 ## Build from Source
 

bin/install-dependencies

@@ -1,26 +1,41 @@
-#! /usr/bin/env sh
+#! /usr/bin/env bash
+
+set -o pipefail
+
+
+APT='apt-get -qq -y'
+
 
 #
 # Install Ubuntu dependencies
 # The dependencies of one level would also be needed for the next ones
 #
 
 # Update cache
-dpkg --add-architecture i386
-apt-get update -qq || exit 1
+dpkg --add-architecture i386 &&
+$APT update                  || exit 1
+
+
+# Ubuntu 14.04 LTS has an old version of qemu-user (2.0.0)
+# Install the one from the Vivid repository
+wget -P deps \
+  http://security.ubuntu.com/ubuntu/pool/universe/q/qemu/qemu-user_2.2+dfsg-5expubuntu9.5_amd64.deb &&
+dpkg -i deps/*.deb || exit 2
 
 
 # cross-compiler
-apt-get install -qq -y gcc texinfo || exit 10
+$APT install gcc texinfo || exit 10
 
 # barebones
-apt-get install -qq -y bc qemu-system || exit 11
-
-# initramfs
-apt-get install -qq -y nodejs-legacy || exit 12
+$APT install bc qemu-system qemu-user || exit 11
 
 # rootfs
-apt-get install -qq -y genisoimage libuuid1:i386 || exit 13
+$APT install genisoimage libuuid1:i386 || exit 12
 
 # usersfs
-apt-get install -qq -y autoconf automake || exit 14
+$APT install autoconf automake || exit 13
+
+
+# Update Node.js to v0.12 from the NodeSource repository
+curl -sL https://deb.nodesource.com/setup_0.12 | bash &&
+$APT install nodejs                                   || exit 20