diff --git a/en_US.ISO8859-1/articles/solid-state/article.sgml b/en_US.ISO8859-1/articles/solid-state/article.sgml
index 3bfb5737ac..36e474745b 100644
--- a/en_US.ISO8859-1/articles/solid-state/article.sgml
+++ b/en_US.ISO8859-1/articles/solid-state/article.sgml
@@ -55,12 +55,12 @@
2001
+ 2009
The FreeBSD Documentation Project
&tm-attrib.freebsd;
- &tm-attrib.m-systems;
&tm-attrib.general;
@@ -109,22 +109,13 @@
temperature of the environment.
Specifically, we will be discussing ATA compatible compact-flash
- units and the M-Systems &diskonchip; flash memory unit. ATA compatible
- compact-flash cards are quite popular as storage media for digital
+ units, which 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.
+ (albeit small).
Other solid state disk solutions do exist, but their expense,
obscurity, and relative unease of use places them beyond the scope of
@@ -153,11 +144,6 @@
options MFS # Memory Filesystem
options MD_ROOT # md device usable as a potential root device
pseudo-device md # memory disk
-
- Second, if you will be using the M-Systems &diskonchip; product, you
- must also include this line:
-
- device fla0 at isa?
@@ -250,12 +236,9 @@ pseudo-device md # memory disk
Building a File System From Scratch
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
- instructions are needed.
+ mfsroot floppies or from a CD.
However, even a small installation of FreeBSD using normal
installation procedures can produce a system in size of greater than 200
@@ -274,11 +257,7 @@ pseudo-device md # memory disk
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 fla option detailed
- in compiled into it. Please see
- for instructions on creating a new kernel for
- kern.flp.
+ the fixit floppy.
@@ -294,9 +273,7 @@ pseudo-device md # memory disk
type of the partition, make sure the value is set to
165. Now write this partition table to the disk
by pressing the w key (this is a hidden option on
- this screen). When presented with a menu to choose a boot manager,
- take care to select None 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 q key to quit the partition menu. You will be
shown the boot manager menu once more - repeat the choice you made
@@ -310,35 +287,12 @@ pseudo-device md # memory disk
installation menu choose the fixit option. After
entering the fixit environment, enter the following commands:
-
-
-
-
- ATA compatible
-
- &diskonchip;
-
-
-
-
- &prompt.root; mknod /dev/ad0a c 116 0
+ &prompt.root; mknod /dev/ad0a c 116 0
&prompt.root; mknod /dev/ad0c c 116 2
-&prompt.root; disklabel -e /dev/ad0c
-
- &prompt.root; mknod /dev/fla0a c 102 0
-&prompt.root; mknod /dev/fla0c c 102 2
-&prompt.root; disklabel -e /dev/fla0c
-
-
-
-
+&prompt.root; disklabel -e /dev/ad0c
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 ESDI to
- DOC2K. 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 a: line at the end of the file. This
a: line should look like:
@@ -351,26 +305,8 @@ pseudo-device md # memory disk
sure that fstype is 4.2BSD. Save the file and
exit.
-
-
-
-
- ATA compatible
-
- &diskonchip;
-
-
-
-
- &prompt.root; disklabel -B -r /dev/ad0c
-&prompt.root; newfs /dev/ad0a
-
- &prompt.root; disklabel -B -r /dev/fla0c
-&prompt.root; newfs /dev/fla0a
-
-
-
-
+ &prompt.root; disklabel -B -r /dev/ad0c
+&prompt.root; newfs /dev/ad0a
@@ -378,24 +314,7 @@ pseudo-device md # memory disk
Mount the newly prepared flash media:
-
-
-
-
- ATA compatible
-
- &diskonchip;
-
-
-
-
- &prompt.root; mount /dev/ad0a /flash
-
- &prompt.root; mount /dev/fla0a /flash
-
-
-
-
+ &prompt.root; mount /dev/ad0a /flash
Bring this machine up on the network so we may transfer our tar
file and explode it onto our flash media filesystem. One example of
@@ -438,53 +357,6 @@ pseudo-device md # memory disk
-
- Building a <filename>kern.flp</filename> Installation Floppy with
- the fla Driver
-
-
- This section of the article is relevant only to those using
- M-Systems &diskonchip; flash media.
-
-
- It is possible that your kern.flp boot floppy
- does not have a kernel with the fla 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
- fla driver in your kernel.
-
- After you have built a kernel with fla
- support that is smaller than 1.4 megabytes, you can create a custom
- kern.flp floppy image with it by following these
- instructions:
-
-
-
- Obtain an existing kern.flp image file
-
-
-
- &prompt.root; vnconfig vn0c kern.flp
-
-
-
- &prompt.root; mount /dev/vn0c /mnt
-
-
-
- Place your kernel file into /mnt, replacing
- the existing one
-
-
-
- &prompt.root; vnconfig -d vn0c
-
-
-
- Your kern.flp file now has your new kernel on it.
-
-
System Strategies for Small and Read Only Environments