Various updates for the ccd chapter to take into account 5.0: we no

longer accept a "units" argument to the kernel configuration entry.
Devfs now does all the device management, eschew use of MAKEDEV.

Note: I haven't yet tested all the commands here, I suspect some
instances of "ccd0c" may need to become simply "ccd0".
This commit is contained in:
Robert Watson 2002-12-05 15:56:53 +00:00
parent 5c8f4cdd6d
commit 9241c2dd38
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15173

View file

@ -421,6 +421,11 @@ ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlist
<programlisting>pseudo-device ccd 4</programlisting>
<note><para>In FreeBSD 5.0, it is not necessary to specify
a number of ccd devices, as the ccd device driver is now
cloning -- new device instances will automatically be
created on demand.</para></note>
<para><application>ccd</application> support can also be
loaded as a kernel loadable module in FreeBSD 4.0 or
later.</para>
@ -480,6 +485,10 @@ disklabel -e ad3</programlisting>
<programlisting>cd /dev
sh MAKEDEV ccd0</programlisting>
<note><para>In FreeBSD 5.0, &man.devfs.5; will automatically
manage device nodes in <filename>/dev</filename>, so use of
<command>MAKEDEV</command> is not necessary.</para></note>
<para>The next argument <command>ccdconfig</command> expects
is the interleave for the file system. The interleave
defines the size of a stripe in disk blocks, normally five
@ -931,6 +940,11 @@ scsibus1:
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>sh MAKEDEV acd0t99</userinput></screen>
<note><para>In FreeBSD 5.0, &man.devfs.5; will automatically
create and manage entries in <filename>/dev</filename>
for you, so it is not necessary to use
<command>MAKEDEV</command>.</para></note>
</step>
<step>
@ -1103,6 +1117,9 @@ scsibus1:
<filename>/dev</filename>. To do it, you can issue:</para>
<screen>&prompt.root; <userinput>cd /dev && ./MAKEDEV "fd*"</userinput></screen>
<note><para>In FreeBSD 5.0, &man.devfs.5; will automatically
manage device nodes in <filename>/dev</filename>, so use of
<command>MAKEDEV</command> is not necessary.</para></note>
</sect2>
<sect2>