Modified:
/wiki/FrameworkWalkThrough.wiki
=======================================
--- /wiki/FrameworkWalkThrough.wiki Wed Oct 1 15:11:06 2008
+++ /wiki/FrameworkWalkThrough.wiki Wed Jul 28 11:04:02 2010
@@ -2,7 +2,7 @@
= Introduction =
-This is a step-by-step walkthrough of the how one would use the framework
to deploy an example appliance. This example cover use of the [Framework
framework] on [http://www.netbsd.org/ NetBSD] 4.0-BETA/i386 to deploy a
terminal server we'll call "ts0".
+This is a step-by-step walk-through of the how one would use the framework
to deploy an example appliance. This example cover use of the [Framework
framework] on [http://www.netbsd.org/ NetBSD] 4.0-BETA/i386 to deploy a
terminal server we'll call "ts0".
= Meta-Steps =
@@ -85,7 +85,7 @@
need to be manually set for the time being (because *cf.conf(5)* is parsed
before
*cf.subr(8)* identifies the platform)
-[file: cf.conf]
+file: cf.conf
{{{
UFQDN=ts0
@@ -300,7 +300,7 @@
== Step: Setup any additional pruning (optional) ==
-This is a nessecary evil on most embedded / appliance platform due to
hardware resource constraints (memory). Identify any additional unessecary
subsystems remaining in _/home/fsimages/dstdir-prof/_ that may be "pruned"
out.
+This is a necessary evil on most embedded / appliance platform due to
hardware resource constraints (memory). Identify any additional
unnecessary subsystems remaining in _/home/fsimages/dstdir-prof/_ that may
be "pruned" out.
For paths in /(root,slash), /var, /etc, /bin, and /sbin, enter the paths
relative to "/" into rd_prune.txt or RD_PRUNE_LIST in *cf.conf(5)*:
@@ -331,7 +331,7 @@
$ sudo vim usr_prune.txt
}}}
-[file: usr_prune.txt]
+file: usr_prune.txt
{{{
bin/make
bin/ld
@@ -554,7 +554,7 @@
assumed that this directory has the boot configuration files, and all
other information necessary for the system to work.
-Root filesystem directory [./rd_root]:
+Root filesystem directory \[./rd_root\]:
----------
Creating image file ./image_rd
21000+0 records in