Internet-in-a-Box (IIAB) 8.2 pre-releases are thoroughly tested, and can be installed from this page! Please read our DRAFT IIAB 8.2 Release Notes.

To install IIAB 8.2 onto Raspberry Pi OS, Ubuntu 22.04+, Linux Mint 21+ or Debian 12+, simply run this 1-line installer:

curl | bash

On a Raspberry Pi, WE RECOMMEND YOU INSTALL THE LATEST RASPBERRY PI OS (64-bit is recommended), using their detailed instructions if necessary. WARNING: THE NOOBS OS IS *NOT* SUPPORTED, as its partitioning is very different. To attempt an IIAB install onto a non-supported Linux distribution (AT YOUR OWN RISK) see also the manual/legacy instructions.

An Ethernet cable is highly recommended during installation. This is more reliable AND allows an internal IIAB hotspot to be set up without confusion. WARNING: IF YOU CONNECT YOUR IIAB'S INTERNAL WI-FI TO THE INTERNET OVER 5 GHz, YOU'LL PREVENT OLDER LAPTOPS/PHONES/TABLETS (WHICH REQUIRE 2.4 GHz) FROM CONNECTING TO YOUR IIAB'S INTERNAL HOTSPOT. For AP+STA mode, set "wifi_up_down: True" in /etc/iiab/local_vars.yml (example).

Thanks For Building Your Own Library To Serve One & All

Please contact us if you find issues, Thank You! Special Thanks to the countries + communities + volunteers working non-stop to bring about IIAB 8.2 !

IIAB Dev Team
http://FAQ.IIAB.IO x86 Images ReadMe

Instructions to install the Clonezilla IIAB/XSCE 6.2 images

For information on the overall Internet-in-a-Box installation process please see IIAB Installation.

If you prefer to do everything yourself, please read the far longer instructions to install from Scratch, using debian-load.txt (or possibly centos-load.txt, etc) instead of an install image.

Note: The clonezilla install proccess is experimental, and relatively untested by users. Please refer to Clonezilla Documentation for additional info.

  1. Download the clonezilla image that is appropriate for your hardware. Recent hardware (those that can run Windows 7+) will be able to boot UEFI, which is preferred. Older hardware may require a MBR (master boot record) image.
  2. Copy the selected image to a blank 8GB USB stick using "dd if=<downloaded img> of=/dev/<sdxx> bs=4m" (determine the sdxx using the linux command lsblk).
  3. Put the USB stick in a machine with a single hard disk (all data on the disk will be destroyed). Configure the BIOS to use the UEFI or "legacy - mbr" boot method.
  4. When Clonezilla menu appears, use up arrow twice to select the item "WARNING this will destroy all data on /dev/sda"
  5. Clonezilla will proceed to operate, checking the image for integrity, and will ask one final time, if you want to destroy the contents of the hard disk, and install the new OS.
  6. After it completes, remove the USB stick, and reboot.
  7. Log on to user: xsce-admin with the password: g0adm1n
  8. You can become root, with the "sudo su" command.
  9. Change the xsce-admin password by runing: passwd

To do a Headless install, without keyboard or monitor:

After 30 seconds, the booted clonezilla application will start up a ssh server, and wait for connections over the network.

It might be a little tricky obtaining the IP address of the headless device. Some strategies:

  1. To log on to the ssh server, use the username: user, and the password: live.
  2. To install to the hard disk via ssh, you must become root. "sudo su -" will do it.
  3. The clonezilla application can be started from the remote terminal via the command: clonezilla
  4. You want to install from an image to a local hard disk.
  5. The source information is located on /dev/sdb2 -- which you can select during the interactive dialog.
  6. The name of the saved image that you want to install is called "bundle.img".

Comments about the clonezilla install process

  1. Clonezilla treats each partition separately, compressing only the used part of the disk, and not the free space.
  2. It remembers the size of each partition, and wants to recreate the same partition structure, before the data is copied in.
  3. This attempt to recreate exactly the same partition structure fails if the new disk is smaller than the original source; even it the data portion will fit on the destination disk.
  4. To get around this difficulty, the source disk is shrunk to a minimun before the image is created. For release 6.2, the destination hard disk must be at least 60GB.
  5. Then once the smaller image is in place and running on the new machine, the last partition is automatically expanded to use all available space.