|
Lines 134-140
Link Here
|
| 134 |
<para>First, all embedded FreeBSD systems that use flash memory as system |
134 |
<para>First, all embedded FreeBSD systems that use flash memory as system |
| 135 |
disk will be interested in memory disks and memory filesystems. Because |
135 |
disk will be interested in memory disks and memory filesystems. Because |
| 136 |
of the limited number of writes that can be done to flash memory, the |
136 |
of the limited number of writes that can be done to flash memory, the |
| 137 |
disk and the filesystems no the disk will most likely be mounted |
137 |
disk and the filesystems on the disk will most likely be mounted |
| 138 |
read-only. In this environment, filesystems such as |
138 |
read-only. In this environment, filesystems such as |
| 139 |
<filename>/tmp</filename> and <filename>/var</filename> are mounted as |
139 |
<filename>/tmp</filename> and <filename>/var</filename> are mounted as |
| 140 |
memory filesystems to allow the system to create logs and update |
140 |
memory filesystems to allow the system to create logs and update |
|
Lines 204-210
Link Here
|
| 204 |
read-only. Remember that in <xref linkend="intro"> we detailed the |
204 |
read-only. Remember that in <xref linkend="intro"> we detailed the |
| 205 |
limitations of flash memory - specifically the limited write capability. |
205 |
limitations of flash memory - specifically the limited write capability. |
| 206 |
The importance of not mounting filesystems on flash media read-write, |
206 |
The importance of not mounting filesystems on flash media read-write, |
| 207 |
and the importance of not using a swap file cannot be overstated. A |
207 |
and the importance of not using a swap file, cannot be overstated. A |
| 208 |
swap file on a busy system can burn through a piece of flash media in |
208 |
swap file on a busy system can burn through a piece of flash media in |
| 209 |
less than one year. Heavy logging or temporary file creation and |
209 |
less than one year. Heavy logging or temporary file creation and |
| 210 |
destruction can do the same. Therefore, in addition to removing the |
210 |
destruction can do the same. Therefore, in addition to removing the |
|
Lines 290-296
Link Here
|
| 290 |
by pressing the <keycap>w</keycap> key (this is a hidden option on |
290 |
by pressing the <keycap>w</keycap> key (this is a hidden option on |
| 291 |
this screen). When presented with a menu to choose a boot manager, |
291 |
this screen). When presented with a menu to choose a boot manager, |
| 292 |
take care to select <literal>None</literal> if you are using an |
292 |
take care to select <literal>None</literal> if you are using an |
| 293 |
M-Systems Disk-On-Chip. If you are using a ATA compatible compact |
293 |
M-Systems Disk-On-Chip. If you are using an ATA compatible compact |
| 294 |
flash card, you should choose the FreeBSD Boot Manager. Now press |
294 |
flash card, you should choose the FreeBSD Boot Manager. Now press |
| 295 |
the <keycap>q</keycap> key to quit the partition menu. You will be |
295 |
the <keycap>q</keycap> key to quit the partition menu. You will be |
| 296 |
shown the boot manager menu once more - repeat the choice you made |
296 |
shown the boot manager menu once more - repeat the choice you made |
|
Lines 333-340
Link Here
|
| 333 |
of the file from <literal>ESDI</literal> to |
333 |
of the file from <literal>ESDI</literal> to |
| 334 |
<literal>DOC2K</literal>. Next, regardless of whether you are using |
334 |
<literal>DOC2K</literal>. Next, regardless of whether you are using |
| 335 |
Disk-On-Chip or ATA compatible compact flash media, you need to add |
335 |
Disk-On-Chip or ATA compatible compact flash media, you need to add |
| 336 |
an a: line at the end of the file. This <literal>a:</literal> line |
336 |
an <literal>a:</literal> line at the end of the file. This |
| 337 |
should look like:</para> |
337 |
<literal>a:</literal> line should look like:</para> |
| 338 |
|
338 |
|
| 339 |
<programlisting>a: <replaceable>123456</replaceable> 0 4.2BSD 0 0</programlisting> |
339 |
<programlisting>a: <replaceable>123456</replaceable> 0 4.2BSD 0 0</programlisting> |
| 340 |
|
340 |
|
|
Lines 455-461
Link Here
|
| 455 |
|
455 |
|
| 456 |
<procedure> |
456 |
<procedure> |
| 457 |
<step> |
457 |
<step> |
| 458 |
<para>Obtain an existing kern.flp image file</para> |
458 |
<para>Obtain an existing <filename>kern.flp</filename> image file</para> |
| 459 |
</step> |
459 |
</step> |
| 460 |
|
460 |
|
| 461 |
<step> |
461 |
<step> |
|
Lines 553-559
Link Here
|
| 553 |
|
553 |
|
| 554 |
<para>To make it possible to enter a ports directory and successfully |
554 |
<para>To make it possible to enter a ports directory and successfully |
| 555 |
run <command>make install</command>, it is necessary for the file |
555 |
run <command>make install</command>, it is necessary for the file |
| 556 |
<filename>/var/db/port.mkversion</filename> to exist, and that it have |
556 |
<filename>/var/db/port.mkversion</filename> to exist, and that it has |
| 557 |
a correct date in it. Further, we must create a packages directory on |
557 |
a correct date in it. Further, we must create a packages directory on |
| 558 |
a non-memory filesystem that will keep track of our packages across |
558 |
a non-memory filesystem that will keep track of our packages across |
| 559 |
reboots. Because it is necessary to mount your filesystems as |
559 |
reboots. Because it is necessary to mount your filesystems as |
|
Lines 599-606
Link Here
|
| 599 |
|
599 |
|
| 600 |
<para>Apache keeps pid files and logs in |
600 |
<para>Apache keeps pid files and logs in |
| 601 |
<filename><replaceable>apache_install</replaceable>/logs</filename>. |
601 |
<filename><replaceable>apache_install</replaceable>/logs</filename>. |
| 602 |
Since this directory no doubt exists on a read-only filesystem, this |
602 |
Since this directory, without a doubt, exists on a read-only filesystem, |
| 603 |
will not work. It is necessary to add a new directory to the |
603 |
this will not work. It is necessary to add a new directory to the |
| 604 |
<filename>/etc/rc.diskless2</filename> list of directories to create |
604 |
<filename>/etc/rc.diskless2</filename> list of directories to create |
| 605 |
in <filename>/var</filename>, to link |
605 |
in <filename>/var</filename>, to link |
| 606 |
<filename><replaceable>apache_install</replaceable>/logs</filename> to |
606 |
<filename><replaceable>apache_install</replaceable>/logs</filename> to |