PERFORCE change 160093 for review
Rene Ladan
rene at FreeBSD.org
Wed Apr 1 03:16:53 PDT 2009
http://perforce.freebsd.org/chv.cgi?CH=160093
Change 160093 by rene at rene_self on 2009/04/01 10:16:07
Remove references of fla(4) and M-Systems DiskOnChip from the solid state article.
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/solid-state/article.sgml#2 edit
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/solid-state/article.sgml#2 (text+ko) ====
@@ -109,22 +109,14 @@
temperature of the environment.</para>
<para>Specifically, we will be discussing ATA compatible compact-flash
- units and the M-Systems &diskonchip; flash memory unit. ATA compatible
+ units. ATA compatible
compact-flash cards are quite popular as storage media for digital
cameras. Of particular interest is the fact that they pin out directly
to the IDE bus and are compatible with the ATA command set. Therefore,
with a very simple and low-cost adaptor, these devices can be attached
directly to an IDE bus in a computer. Once implemented in this manner,
operating systems such as FreeBSD see the device as a normal hard disk
- (albeit small). The M-Systems &diskonchip; product is based on the same
- underlying flash memory technology as ATA compatible compact-flash
- cards, but resides in a DIP form factor and is not ATA compatible. To
- use such a device, not only must you install it on a motherboard that
- has a &diskonchip; socket, you must also build the `fla` driver into any
- FreeBSD kernel you wish to use it with. Further, there is critical,
- manufacturer-specific data residing in the boot sector of this device,
- so you must take care not to install the FreeBSD (or any other) boot
- loader when using this.</para>
+ (albeit small).</para>
<para>Other solid state disk solutions do exist, but their expense,
obscurity, and relative unease of use places them beyond the scope of
@@ -153,11 +145,6 @@
<programlisting>options MFS # Memory Filesystem
options MD_ROOT # md device usable as a potential root device
pseudo-device md # memory disk</programlisting>
-
- <para>Second, if you will be using the M-Systems &diskonchip; product, you
- must also include this line:</para>
-
- <programlisting>device fla0 at isa?</programlisting>
</sect1>
<sect1 id="ro-fs">
@@ -250,8 +237,8 @@
<title>Building a File System From Scratch</title>
<para>Because ATA compatible compact-flash cards are seen by FreeBSD as
- normal IDE hard drives, as is a M-Systems &diskonchip; product (when you
- are running a kernel with the fla driver built in) you could
+ normal IDE hard drives,
+ you could
theoretically install FreeBSD from the network using the kern and
mfsroot floppies or from a CD. Other than the fact that you should not
write a boot-loader of any kind to the M-Systems device, no special
@@ -274,11 +261,7 @@
installation is not being performed, operations such as partitioning,
labeling, file-system creation, etc. need to be performed by hand. In
addition to the kern and mfsroot floppy disks, you will also need to use
- the fixit floppy. If you are using a M-Systems &diskonchip;, the kernel
- on your kern floppy must have the <literal>fla</literal> option detailed
- in <xref linkend="kernel"> compiled into it. Please see
- <xref linkend="kern.flp"> for instructions on creating a new kernel for
- <filename>kern.flp</filename>.</para>
+ the fixit floppy.</para>
<procedure>
<step>
@@ -294,9 +277,8 @@
type of the partition, make sure the value is set to
<literal>165</literal>. Now write this partition table to the disk
by pressing the <keycap>w</keycap> key (this is a hidden option on
- this screen). When presented with a menu to choose a boot manager,
- take care to select <literal>None</literal> if you are using an
- M-Systems &diskonchip;. If you are using an ATA compatible compact
+ this screen).
+ If you are using an ATA compatible compact
flash card, you should choose the FreeBSD Boot Manager. Now press
the <keycap>q</keycap> key to quit the partition menu. You will be
shown the boot manager menu once more - repeat the choice you made
@@ -311,12 +293,10 @@
entering the fixit environment, enter the following commands:</para>
<informaltable frame="none" pgwide="1">
- <tgroup cols="2">
+ <tgroup cols="1">
<thead>
<row>
<entry align="center">ATA compatible</entry>
-
- <entry align="center">&diskonchip;</entry>
</row>
</thead>
<tbody>
@@ -324,21 +304,15 @@
<entry><para><screen>&prompt.root; <userinput>mknod /dev/ad0a c 116 0</userinput>
&prompt.root; <userinput>mknod /dev/ad0c c 116 2</userinput>
&prompt.root; <userinput>disklabel -e /dev/ad0c</userinput></screen></para></entry>
-
- <entry><para><screen>&prompt.root; <userinput>mknod /dev/fla0a c 102 0</userinput>
-&prompt.root; <userinput>mknod /dev/fla0c c 102 2</userinput>
-&prompt.root; <userinput>disklabel -e /dev/fla0c</userinput></screen></para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>At this point you will have entered the vi editor under the
- auspices of the disklabel command. If you are using &diskonchip;,
- the first step will be to change the type value near the beginning
- of the file from <literal>ESDI</literal> to
- <literal>DOC2K</literal>. Next, regardless of whether you are using
- &diskonchip; or ATA compatible compact flash media, you need to add
+ auspices of the disklabel command.
+ Next,
+ you need to add
an <literal>a:</literal> line at the end of the file. This
<literal>a:</literal> line should look like:</para>
@@ -352,21 +326,16 @@
exit.</para>
<informaltable frame="none" pgwide="1">
- <tgroup cols="2">
+ <tgroup cols="1">
<thead>
<row>
<entry align="center">ATA compatible</entry>
-
- <entry align="center">&diskonchip;</entry>
</row>
</thead>
<tbody>
<row>
<entry><para><screen>&prompt.root; <userinput>disklabel -B -r /dev/ad0c</userinput>
&prompt.root; <userinput>newfs /dev/ad0a</userinput></screen></para></entry>
-
- <entry><para><screen>&prompt.root; <userinput>disklabel -B -r /dev/fla0c</userinput>
-&prompt.root; <userinput>newfs /dev/fla0a</userinput></screen></para></entry>
</row>
</tbody>
</tgroup>
@@ -379,19 +348,15 @@
<para>Mount the newly prepared flash media:</para>
<informaltable frame="none" pgwide="1">
- <tgroup cols="2">
+ <tgroup cols="1">
<thead>
<row>
<entry align="center">ATA compatible</entry>
-
- <entry align="center">&diskonchip;</entry>
</row>
</thead>
<tbody>
<row>
<entry><para><screen>&prompt.root; <userinput>mount /dev/ad0a /flash</userinput></screen></para></entry>
-
- <entry><para><screen>&prompt.root; <userinput>mount /dev/fla0a /flash</userinput></screen></para></entry>
</row>
</tbody>
</tgroup>
@@ -438,53 +403,6 @@
</procedure>
</sect1>
- <sect1 id="kern.flp">
- <title>Building a <filename>kern.flp</filename> Installation Floppy with
- the fla Driver</title>
-
- <note>
- <para>This section of the article is relevant only to those using
- M-Systems &diskonchip; flash media.</para>
- </note>
-
- <para>It is possible that your <filename>kern.flp</filename> boot floppy
- does not have a kernel with the <devicename>fla</devicename> driver
- compiled into it necessary for the system to recognize the &diskonchip;.
- If you have booted off of the installation floppies and are told that no
- disks are present, then you are probably lacking the
- <devicename>fla</devicename> driver in your kernel.</para>
-
- <para>After you have built a kernel with <devicename>fla</devicename>
- support that is smaller than 1.4 megabytes, you can create a custom
- <filename>kern.flp</filename> floppy image with it by following these
- instructions:</para>
-
- <procedure>
- <step>
- <para>Obtain an existing kern.flp image file</para>
- </step>
-
- <step>
- <para><screen>&prompt.root; <userinput>vnconfig vn0c kern.flp</userinput></screen></para>
- </step>
-
- <step>
- <para><screen>&prompt.root; <userinput>mount /dev/vn0c /mnt</userinput></screen></para>
- </step>
-
- <step>
- <para>Place your kernel file into <filename>/mnt</filename>, replacing
- the existing one</para>
- </step>
-
- <step>
- <para><screen>&prompt.root; <userinput>vnconfig -d vn0c</userinput></screen></para>
- </step>
- </procedure>
-
- <para>Your <filename>kern.flp</filename> file now has your new kernel on it.</para>
- </sect1>
-
<sect1 id="strategies">
<title>System Strategies for Small and Read Only Environments</title>
More information about the p4-projects
mailing list