Changes between Version 3 and Version 4 of newport/ubuntu

Timestamp:

12/15/2017 09:59:42 PM (7 years ago)

Author:

Tim Harvey

Comment:

removed kernel installation from debootstrap steps and add steps for creating images

newport/ubuntu

@@ -176 +176 @@
  * Note that by default root ssh access is disabled for security. See [#ssh below] for info on enabling it
 
-10. install Gateworks pre-built kernel:
-{{{#!bash
-apt-get install wget
-cd /
-wget http://svn.gateworks.com/newport/images/gateworks-linux-arm64-4.14.tar.bz2
-tar -xvf gateworks-linux-arm64-4.14.tar.bz2
-}}}
-
-11. exit the chroot shell and remove files we no longer need
+10. exit the chroot shell and remove files we no longer need
 {{{
 #!bash
@@ -191 +183 @@
 }}}
 
-12. install to bootable media:
- * For a removable block storage device supported by your board such as a USB Mass Storage device, a microSD, an mSATA SSD the example below will create a single ext4 rootfs partition on a removable block storage device. Ensure you set DEVICE properly for your system. We use the 'udisks' application for mount/unmount so that the mount-point is obvious - if you know what your doing you could use standard mount/unmount as well:
-{{{
-#!bash
-DEVICE=/dev/sdc
-# unmount all auto-mounted partitions for this device
-sudo umount ${DEVICE}?
-# partition disk - single ext partition
-printf ",,L,,\n" | sudo sfdisk -uS ${DEVICE}
+At this point you have a directory containing a root filesystem (without kernel) and likely want to install it onto removable storage or the on-board FLASH of a target board. Some intermediate formats that are useful to keep around would be a tarball, perhaps an ext4 filesystem image, or a compressed disk image suitable for flashing in the U-Boot bootloader.
+
+To create a tarball which is the most flexible storage format and can be used for a variety of future installation uses:
+{{{#!bash
+sudo tar --numeric-owner -cvJf xenial-newport.tar.xz rootfs/ .
+}}}
+
+To create a 'Compressed Disk Image' using this tarball see [#disk-images above] and to install this onto a board's embedded FLASH see [wiki:newport#serial-ethernet here].
+
+
+=== ext4 filesystem ===
+If desired you can create an ext4 filesystem from the directory or tarball. This requires you choose a size for the filesystem. This size can be increased at runtime using {{{resize2fs}}} as long as the partition table has room for it to grow. The advantage of using an as small as possible size is that the time necessary to flash it onto storage is reduced to a minimum (when flashing you have to write the entire ext4 fs but when formatting or resizing it only has to write periodic markers to FLASH).
+
+For a given size (see SIZEMB variable below) you can create a rootfs with:
+{{{#!bash
+SIZEMB=1536 # 1.5GB - expandable later with resize2fs
+OUT=xenial-newport.ext4
+# create a file of specific size
+truncate -s ${SIZEMB}M ${OUT}
+# format it as an ext4 filesystem
+mkfs.ext4 -q -F -L rootfs ${OUT}
+# mount it to a temporary mount point
+tmp_mnt=$(mktemp -d -p/tmp)
+mount ${OUT} ${tmp_mnt}
+# copy files to it
+cp -rup rootfs/* ${tmp_mnt}
+# and/or extract files from a tarball
+tar -C ${tmp_mnt} -xf linux-newport.tar.xz
+# unmount temporary mount point
+umount ${tmp_mnt}
 sync
-sudo mkfs.ext4 -L rootfs ${DEVICE}1
-# mount partition (will mount to /media/rootfs/)
-sudo udisks --mount ${DEVICE}1
-# copy the root filesystem
-sudo cp -rupv $target/*  /media/rootfs/
-# unmount the disk
-sudo udisks --unmount ${DEVICE}1
-}}}
+# compress it
+gzip -k -f ${OUT}
+}}}