Custom Software Deployment with EMAC OE - Revision history

Bserrano at 21:07, 2 April 2014

2014-04-02T21:07:49Z

Bserrano at 20:39, 27 March 2014

2014-03-27T20:39:51Z

Bserrano at 22:33, 4 March 2014

2014-03-04T22:33:11Z

Mgloff at 18:57, 24 December 2013

2013-12-24T18:57:38Z

Kyoungmeyer at 21:02, 19 December 2013

2013-12-19T21:02:29Z

Mdean: Marked for review.

2013-12-19T17:28:25Z

Marked for review.

Mdean: /* Launching Software Automatically on Boot */ Fixed link title.

2013-12-19T17:25:24Z

‎Launching Software Automatically on Boot: Fixed link title.

Mdean: First draft.

2013-12-18T19:11:46Z

First draft.

Mdean: /* Deployment Checklist */ Added info.

2013-12-18T17:37:14Z

‎Deployment Checklist: Added info.

Mdean: /* Preparing a Filesystem for a Snapshot */ Updated link.

2013-12-18T17:31:33Z

‎Preparing a Filesystem for a Snapshot: Updated link.

@@ Line 1: / Line 1: @@
-{{todo|SEOKWREV (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+);(03.04.14-16:30->BS-);(03.27.14-15:40->BS+)|Mike Dean|project=oe 4,oe 5,md,ky,mg,bs,SEOKWREV}}
+{{todo|SEOKWREV (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+);(03.04.14-16:30->BS-);(03.27.14-15:40->BS+);(04.02.14-16:05->BS+)|Mike Dean|project=oe 4,oe 5,md,ky,mg,bs,SEOKWREV}}
 {{#seo:
 |title=Custom Software Deployment with EMAC OE
 |titlemode=append
-|keywords=Custom Software Deployment,Filesystem Considerations,Root Filesystem,Data Partition,Filesystem Image
+|keywords=Linux Filesystem,Linux Root Filesystem,Linux Data Partition,Linux Filesystem Image
 |description=Provide guidance regarding the decisions relevant to deployment on EMAC OE systems.
 }}

← Older revision		Revision as of 20:39, 27 March 2014
Line 1:		Line 1:
−	{{todo\|~~SEOKWTODO~~ (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+);(03.04.14-16:30->BS-)\|Mike Dean\|project=oe 4,oe 5,md,ky,mg,bs,~~SEOKWTODO~~}}	+	{{todo\|SEOKWREV (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+);(03.04.14-16:30->BS-);(03.27.14-15:40->BS+)\|Mike Dean\|project=oe 4,oe 5,md,ky,mg,bs,SEOKWREV}}

		+	{{#seo:
		+	\|title=Custom Software Deployment with EMAC OE
		+	\|titlemode=append
		+	\|keywords=Custom Software Deployment,Filesystem Considerations,Root Filesystem,Data Partition,Filesystem Image
		+	\|description=Provide guidance regarding the decisions relevant to deployment on EMAC OE systems.
		+	}}
	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.		There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.

← Older revision		Revision as of 22:33, 4 March 2014
Line 1:		Line 1:
−	{{todo\|~~Complete~~ (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+)\|Mike Dean\|project=oe 4,oe 5,md,ky,mg,~~Complete~~}}	+	{{todo\|SEOKWTODO (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+);(03.04.14-16:30->BS-)\|Mike Dean\|project=oe 4,oe 5,md,ky,mg,bs,SEOKWTODO}}

	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.		There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.

← Older revision		Revision as of 18:57, 24 December 2013
Line 1:		Line 1:
−	{{todo\|~~Final Draft~~ (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+)\|Mike Dean\|project=oe 4,oe 5,md,~~finaldraft~~,ky}}	+	{{todo\|Complete (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+);(12.14.13-12:55->MG+)\|Mike Dean\|project=oe 4,oe 5,md,ky,mg,Complete}}

	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.		There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.

← Older revision		Revision as of 21:02, 19 December 2013
Line 1:		Line 1:
−	{{todo\|~~Review~~ (12.17.13-01:25->MD+);(12.19.13-11:30->MD+)\|Mike Dean\|project=oe 4,oe 5,md,~~Review~~,ky}}	+	{{todo\|Final Draft (12.17.13-01:25->MD+);(12.19.13-11:30->MD+);(12.19.13-15:02->KY+)\|Mike Dean\|project=oe 4,oe 5,md,finaldraft,ky}}

−	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide~~. It~~ covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.	+	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide, but it covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.

← Older revision		Revision as of 17:28, 19 December 2013
Line 1:		Line 1:
−	{{todo\|~~InProgress~~ (12.17.13-01:25->MD+)\|Mike Dean\|project=oe 4,oe 5,md,~~InProgress~~}}	+	{{todo\|Review (12.17.13-01:25->MD+);(12.19.13-11:30->MD+)\|Mike Dean\|project=oe 4,oe 5,md,Review,ky}}

	There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide. It covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.		There are many considerations to take into account when deploying software. This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems. This is by no means a complete guide. It covers some of the issues that are easily forgotten or overlooked. This material should be considered a supplement to a full deployment guide.

@@ Line 81: / Line 81: @@
 When software is created for an embedded system, it is often required for the software to start when the machine boots.  The best approach to meeting this requirement is to use the robust initialization system which is part of the Linux filesystem.  Configuring the initialization system to launch an application is performed by creating a simple script, placing it in the correct spot in the filesystem, then creating appropriate symbolic links to the script.
-For more information on this process, see [[EMAC_OE_Boot_Process_Customization]].
+For more information on this process, see [[EMAC OE Boot Process Customization]].
 ===Automatically Sending Code to a Machine===

@@ Line 1: / Line 1: @@
 {{todo|InProgress (12.17.13-01:25->MD+)|Mike Dean|project=oe 4,oe 5,md,InProgress}}
-There are many considerations to take into account when deploying software.  This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems.
+There are many considerations to take into account when deploying software.  This guide was written to provide guidance regarding the decisions relevant to deployment on EMAC OE systems.  This is by no means a complete guide.  It covers some of the issues that are easily forgotten or overlooked.  This material should be considered a supplement to a full deployment guide.
 ==File Locations==
-===Program Files===
+Picking the right locations in which to store files is very important for the following reasons:
-===Configuration Files===
+* Many parts of an embedded filesystem are read-only during normal use, and are therefore unsuitable for storing files which will be written to at runtime.
-===Temporary Files===
+Ensuring that software correctly utilizes the filesystem helps ensure reliability (by not prematurely wearing out the flash), portability and maintainability.  More information is available in [[Linux Filesystem Organization]].

@@ Line 104: / Line 104: @@
 <cl>
 . Does the board boot into the desired state, reliably and repeatedly?
-* Have the ssh keys been removed?
+* Have the ssh keys been removed?  Look in <code>/etc/ssh</code>.
 * Can the image of the filesystem be put on a different machine (with a different MAC address) than the development machine, and boot into the desired state reliably and repeatedly?
 * Is the network configuration of the machine set to the desired default for production machines?

@@ Line 65: / Line 65: @@
 ===Preparing a Filesystem for a Snapshot===
-Prior to taking a snapshot of a filesystem, it must be prepared for deployment.  This preparation process involves cleaning up any temporary files and settings, configuring the desired default settings for the machines produced, and removing any machine-specific information (such as SSH keys) from the filesystem.  The [[Custom_Software_Deployment_with_EMAC_OE#Deployment_Tips| Deployment Tips]] section below provides a checklist of items to address prior to taking a snapshot of a filesystem.
+Prior to taking a snapshot of a filesystem, it must be prepared for deployment.  This preparation process involves cleaning up any temporary files and settings, configuring the desired default settings for the machines produced, and removing any machine-specific information (such as SSH keys) from the filesystem.  The [[Custom_Software_Deployment_with_EMAC_OE#Deployment_Checklist| Deployment Checklist]] section below provides a checklist of items to address prior to taking a snapshot of a filesystem.
 ===Manufacturing Boards with a Filesystem Image===