burrow-pi-img/README.md

#Dependencies

`sudo apt-get update && sudo apt-get install git quilt kpartx realpath qemu-user-static debootstrap zerofree pxz zip dosfstools bsdtar libcap2-bin -y
cd ../
sudo git clone https://github.com/dride/drideOS-image-generator
cd drideOS-image-generator
sudo ./build.sh
`

#Stage Anatomy


# drideOS (Raspbian) Stage Overview

The build of Raspbian is divided up into several stages for logical clarity
and modularity.  This causes some initial complexity, but it simplifies
maintenance and allows for more easy customization.

 - Stage 0, bootstrap.  The primary purpose of this stage is to create a
   usable filesystem.  This is accomplished largely through the use of
   `debootstrap`, which creates a minimal filesystem suitable for use as a
   base.tgz on Debian systems.  This stage also configures apt settings and
   installs `raspberrypi-bootloader` which is missed by debootstrap.  The
   minimal core is installed but not configured, and the system will not quite
   boot yet.

 - Stage 1, truly minimal system.  This stage makes the system bootable by
   installing system files like `/etc/fstab`, configures the bootloader, makes
   the network operable, and installs packages like raspi-config.  At this
   stage the system should boot to a local console from which you have the
   means to perform basic tasks needed to configure and install the system.
   This is as minimal as a system can possibly get, and its arguably not
   really usable yet in a traditional sense yet.  Still, if you want minimal,
   this is minimal and the rest you could reasonably do yourself as sysadmin.

 - State 2, lite system.  This stage produces the Raspbian-Lite image.  It
   installs some optimized memory functions, sets timezone and charmap
   defaults, installs fake-hwclock and ntp, wifi and bluetooth support,
   dphys-swapfile, and other basics for managing the hardware.  It also
   creates necessary groups and gives the pi user access to sudo and the
   standard console hardware permission groups.

- Stage 3, Install Dride related softwere.
Update README.md 2016-04-11 06:25:30 +00:00			`#Dependencies`

Update README.md 2017-04-16 07:28:30 +00:00			`sudo apt-get update && sudo apt-get install git quilt kpartx realpath qemu-user-static debootstrap zerofree pxz zip dosfstools bsdtar libcap2-bin -y
			`cd ../`
			`sudo git clone https://github.com/dride/drideOS-image-generator`
			`cd drideOS-image-generator`
			`sudo ./build.sh`
			`
README.md: Working toward basic documentation (#10) * README.md: document config file Still pretty sparse, but as this bit is necessary to actually use pi-gen, here it is. * README.md: Overview of Raspbian's stages * README.md: Stages -> Raspbian Stages + heading Decided that the Stages heading probably made more sense as being retitled to refer specifically to Raspbian since it has no direct bearing on pi-gen itself which could produce any Debianish system for the pi, and also that there ought to be a Stage Anatomy section first talking about the nuts and bolts of what goes into these stages. Stage Anatomy is just a heading for now. * README.md: Make Config section less conversational Left the stage overview as it was since it's intended more as a plain language explanation than a technically complete look. I believe that kind of information is useful to have, but perhaps as README.md becomes longer it may be advisable to move it to another location. 2016-09-05 04:02:39 +00:00
			`#Stage Anatomy`



Update README.md 2017-02-02 19:49:03 +00:00			`# drideOS (Raspbian) Stage Overview`
README.md: Working toward basic documentation (#10) * README.md: document config file Still pretty sparse, but as this bit is necessary to actually use pi-gen, here it is. * README.md: Overview of Raspbian's stages * README.md: Stages -> Raspbian Stages + heading Decided that the Stages heading probably made more sense as being retitled to refer specifically to Raspbian since it has no direct bearing on pi-gen itself which could produce any Debianish system for the pi, and also that there ought to be a Stage Anatomy section first talking about the nuts and bolts of what goes into these stages. Stage Anatomy is just a heading for now. * README.md: Make Config section less conversational Left the stage overview as it was since it's intended more as a plain language explanation than a technically complete look. I believe that kind of information is useful to have, but perhaps as README.md becomes longer it may be advisable to move it to another location. 2016-09-05 04:02:39 +00:00
			`The build of Raspbian is divided up into several stages for logical clarity`
			`and modularity. This causes some initial complexity, but it simplifies`
			`maintenance and allows for more easy customization.`

			`- Stage 0, bootstrap. The primary purpose of this stage is to create a`
			`usable filesystem. This is accomplished largely through the use of`
			`debootstrap`, which creates a minimal filesystem suitable for use as a
			`base.tgz on Debian systems. This stage also configures apt settings and`
			installs `raspberrypi-bootloader` which is missed by debootstrap. The
			`minimal core is installed but not configured, and the system will not quite`
			`boot yet.`

			`- Stage 1, truly minimal system. This stage makes the system bootable by`
			installing system files like `/etc/fstab`, configures the bootloader, makes
			`the network operable, and installs packages like raspi-config. At this`
			`stage the system should boot to a local console from which you have the`
			`means to perform basic tasks needed to configure and install the system.`
			`This is as minimal as a system can possibly get, and its arguably not`
			`really usable yet in a traditional sense yet. Still, if you want minimal,`
			`this is minimal and the rest you could reasonably do yourself as sysadmin.`

			`- State 2, lite system. This stage produces the Raspbian-Lite image. It`
			`installs some optimized memory functions, sets timezone and charmap`
			`defaults, installs fake-hwclock and ntp, wifi and bluetooth support,`
			`dphys-swapfile, and other basics for managing the hardware. It also`
			`creates necessary groups and gives the pi user access to sudo and the`
			`standard console hardware permission groups.`

Update README.md 2017-02-02 19:49:03 +00:00			`- Stage 3, Install Dride related softwere.`