1.1 --- a/README.txt Sun Apr 07 20:59:13 2013 +0200
1.2 +++ b/README.txt Thu May 09 23:40:12 2013 +0200
1.3 @@ -27,7 +27,24 @@
1.4
1.5 apt-get update
1.6
1.7 -...and then try to install such a newer version. If no readily available newer version exists in a usable repository, you may need to backport the package from a later Debian release. Such an activity is currently outside the scope of this document.
1.8 +...and then try to install such a newer version. If no readily available newer version exists in a usable repository, you may need to backport the package from a later Debian release. Such an activity is currently outside the scope of this document, but the following package versions have been used for certain distributions:
1.9 +
1.10 +{| border="1" cellspacing="0" cellpadding="5"
1.11 +! Host Distribution
1.12 +! Target Distribution
1.13 +! Multistrap Version
1.14 +! Notes
1.15 +|-
1.16 +| Debian Squeeze
1.17 +| Emdebian Squeeze/Debian Squeeze
1.18 +| 2.1.20
1.19 +| Source package obtained from Debian Sid (unstable) and built for Squeeze
1.20 +|-
1.21 +| Debian Squeeze
1.22 +| Emdebian Wheezy-Grip/Debian Wheezy
1.23 +| 2.1.22
1.24 +| Source package obtained from Debian Sid (unstable) and built for Squeeze
1.25 +|}
1.26
1.27 ==== Downloads ====
1.28
1.29 @@ -70,9 +87,11 @@
1.30
1.31 This minimal configuration installs a base system from Emdebian Grip packages, which should be smaller than conventional Debian packages, using such conventional packages for those which are not present in the Grip repository. In addition, the <code>udev</code> and <code>busybox-static</code> packages are added; this latter package is essential for the initial configuration of the system.
1.32
1.33 +For Debian Wheezy, various details must be changed in the configuration and an example file is provided in the [http://hgweb.boddie.org.uk/qi-emdebian/file qi-emdebian distribution] for guidance.
1.34 +
1.35 === Preparing a Root Filesystem ===
1.36
1.37 -With a suitable configuration file called, for example, <code>multistrap-squeeze-mipsel.conf</code> a root filesystem can be constructed in a location such as <code>rootfs</code> as follows. Note that you should really be <code>root</code> or use <code>sudo</code> for this to work properly:
1.38 +With a suitable configuration file called, for example, <code>multistrap-squeeze-mipsel.conf</code> a root filesystem can be constructed in a location such as <code>rootfs</code> as follows. Note that you must be <code>root</code> or use <code>sudo</code> for this to work properly:
1.39
1.40 multistrap -f multistrap-squeeze-mipsel.conf -d rootfs
1.41
1.42 @@ -87,21 +106,23 @@
1.43 A number of configuration files, missing from the root filesystem, must be defined for the installation:
1.44
1.45 * <code>/etc/fstab</code>
1.46 +* <code>/etc/hostname</code>
1.47 * <code>/etc/network/interfaces</code>
1.48 -
1.49 -Such files can be placed in a directory called, for example, <code>configfiles</code> while retaining the necessary filesystem structure, so that <code>fstab</code> would reside at <code>configfiles/etc/fstab</code>, and so on. This reflects their typical locations in a real system.
1.50 +* <code>/etc/resolv.conf</code>
1.51
1.52 -==== Pre-initialisation Files ====
1.53 +Such files can be placed in a directory called, for example, <code>files</code> while retaining the necessary filesystem structure, so that <code>fstab</code> would reside at <code>files/etc/fstab</code>, and so on. This reflects their typical locations in a real system.
1.54
1.55 -Two additional files called <code>preinit</code> and <code>preinit-config</code> are required that "glue" the kernel to the Debian system on the first boot of the system. These files must reside in the current directory when running the script below.
1.56 +==== Pre-Initialisation Files ====
1.57 +
1.58 +Two additional files called <code>preinit</code> and <code>preinit-config</code> are required that "glue" the kernel to the Debian system on the first boot of the system. These files must reside in the current directory when running the script below. The <code>preinit</code> file is a convention apparently employed by the OpenWrt distribution used on the NanoNote, and where kernels from other origins are to be used, it is important that the appropriate conventions for invoking the system <code>init</code> program are followed. Thus, if you switch to a different kernel from another project, you may need to change the <code>qi-emdebian-postsetup</code> script to install these files into other locations, potentially giving them different names.
1.59
1.60 ==== Running the Script ====
1.61
1.62 With the missing files now defined, a script written to automate the remaining configuration activity can be run as follows. Again, it may help to be <code>root</code> or to use <code>sudo</code> to be able to copy the necessary files into the root filesystem:
1.63
1.64 - qi-emdebian-postsetup rootfs openwrt-xburst-qi_lb60-uImage.bin configfiles
1.65 + qi-emdebian-postsetup rootfs openwrt-xburst-qi_lb60-uImage.bin files
1.66
1.67 -Here, <code>rootfs</code> is the root filesystem created above, <code>openwrt-xburst-qi_lb60-uImage.bin</code> is the kernel image obtained above, and <code>configfiles</code> is the directory containing the missing configuration files.
1.68 +Here, <code>rootfs</code> is the root filesystem created above, <code>openwrt-xburst-qi_lb60-uImage.bin</code> is the kernel image obtained above, and <code>files</code> is the directory containing the missing configuration files.
1.69
1.70 === Formatting the Boot Medium ===
1.71
1.72 @@ -118,7 +139,21 @@
1.73
1.74 fdisk -l /dev/sdb
1.75
1.76 -To add a new partition, run <code>fdisk</code>, use the <code>n</code> command to make a primary partition, and then the <code>w</code> command to write the partition table.
1.77 +If the microSD card already has partitions, you should check to see if they have been mounted by the system:
1.78 +
1.79 + mount
1.80 +
1.81 +If so, you must first unmount the corresponding devices as follows (as <code>root</code> or using <code>sudo</code>):
1.82 +
1.83 + umount /dev/sdb1
1.84 +
1.85 +To preserve existing partitions, you can copy them from the card to your system as follows (as <code>root</code> or using <code>sudo</code>):
1.86 +
1.87 + dd if=/dev/sdb1 of=sdb1.backup
1.88 +
1.89 +To add a new partition, run <code>fdisk</code>, use the <code>n</code> command to make a primary partition, and then the <code>w</code> command to write the partition table. Since <code>fdisk</code> will probably suggest a reasonable start of a partition, perhaps the biggest concern is the size of the partition. Choosing <code>+1024M</code> to indicate a partition of 1024MB or 1GB is not unreasonable for modern microSD cards and current Emdebian installations.
1.90 +
1.91 +It is also possible to accept the partition size suggested by <code>fdisk</code> and assign all the space on the card to a partition as well. This may not be sensible, however, since it may make some operations slower and hinder alternative uses for the space (like the creation of other partitions for purposes like backups).
1.92
1.93 === Completing the Installation ===
1.94