Lines 205-214
Link Here
|
205 |
-CURRENT mailing list are sometimes treated with |
205 |
-CURRENT mailing list are sometimes treated with |
206 |
contempt.</para> |
206 |
contempt.</para> |
207 |
|
207 |
|
208 |
<para>Every now and again, a <ulink |
208 |
<para>Every day, <ulink |
209 |
URL="../releases/snapshots.html">snapshot</ulink> release is |
209 |
URL="../releases/snapshots.html">snapshot</ulink> releases are |
210 |
also made of this -CURRENT development code, CDROM |
210 |
made based on the current state of the -CURRENT and |
211 |
distributions of the occasional snapshot even now being made |
211 |
-STABLE branches. Nowadays, |
|
|
212 |
distributions of the occasional snapshot are now being made |
212 |
available. The goals behind each snapshot release are:</para> |
213 |
available. The goals behind each snapshot release are:</para> |
213 |
|
214 |
|
214 |
<itemizedlist> |
215 |
<itemizedlist> |
Lines 218-224
Link Here
|
218 |
</listitem> |
219 |
</listitem> |
219 |
|
220 |
|
220 |
<listitem> |
221 |
<listitem> |
221 |
<para>To give people who would like to run -CURRENT but who |
222 |
<para>To give people who would like to run -CURRENT or |
|
|
223 |
-STABLE but who |
222 |
don't have the time and/or bandwidth to follow it on a |
224 |
don't have the time and/or bandwidth to follow it on a |
223 |
day-to-day basis an easy way of bootstrapping it onto |
225 |
day-to-day basis an easy way of bootstrapping it onto |
224 |
their systems.</para> |
226 |
their systems.</para> |
Lines 238-247
Link Here
|
238 |
</listitem> |
240 |
</listitem> |
239 |
</itemizedlist> |
241 |
</itemizedlist> |
240 |
|
242 |
|
241 |
<para>No claims are made that any snapshot can be considered |
243 |
<para>No claims are made that any -CURRENT snapshot can be considered |
242 |
``production quality'' for any purpose. For stability and |
244 |
“production quality” for any purpose. |
243 |
tested mettle, you will have to stick to full |
245 |
If you want to run a stable and |
244 |
releases.</para> |
246 |
fully tested system, you will have to stick to full |
|
|
247 |
releases, or use the -STABLE snaphosts.</para> |
245 |
|
248 |
|
246 |
<para>Snapshot releases are directly available from <ulink |
249 |
<para>Snapshot releases are directly available from <ulink |
247 |
URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> |
250 |
URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> |
Lines 249-258
Link Here
|
249 |
for 5.0-CURRENT and |
252 |
for 5.0-CURRENT and |
250 |
<ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD"> |
253 |
<ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD"> |
251 |
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots. |
254 |
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots. |
252 |
3-STABLE snapshots can be found at |
255 |
3-STABLE snapshots are not being produced at the time of |
253 |
<ulink url="releng3.FreeBSD.org/pub/FreeBSD"> |
256 |
this writing (May 2000).</para> |
254 |
releng3.FreeBSD.org.</ulink> |
257 |
|
255 |
Snapshots are generated, on the average, once a day for |
258 |
<para>Snapshots are generated, on the average, once a day for |
256 |
all actively developed branches.</para> |
259 |
all actively developed branches.</para> |
257 |
</answer> |
260 |
</answer> |
258 |
</qandaentry> |
261 |
</qandaentry> |
Lines 310-317
Link Here
|
310 |
beyond, the previous 2.2-STABLE branch having been retired |
313 |
beyond, the previous 2.2-STABLE branch having been retired |
311 |
with the release of 2.2.8. 3.4-STABLE has now replaced it, |
314 |
with the release of 2.2.8. 3.4-STABLE has now replaced it, |
312 |
with 3.4-RELEASE being released in mid-December 1999. |
315 |
with 3.4-RELEASE being released in mid-December 1999. |
313 |
4.0-RELEASE released at mid-March 2000 and going to replace |
316 |
4.0-RELEASE was released in March 2000. Although 4-STABLE |
314 |
3.X branch at summer 2000. 5.0-CURRENT is now the "current |
317 |
is the actively developed -STABLE branch, bugfixes are |
|
|
318 |
still being committed to 3-STABLE. It is expected that the |
319 |
3.X branch will be officially obsoleted some time in |
320 |
summer 2000. |
321 |
5.0-CURRENT is now the "current |
315 |
branch", with the no release date planed.</para> |
322 |
branch", with the no release date planed.</para> |
316 |
</answer> |
323 |
</answer> |
317 |
</qandaentry> |
324 |
</qandaentry> |
Lines 335-343
Link Here
|
335 |
<para>Releases are made about every 4 months on average.</para> |
342 |
<para>Releases are made about every 4 months on average.</para> |
336 |
|
343 |
|
337 |
<para>For people needing (or wanting) a little more excitement, |
344 |
<para>For people needing (or wanting) a little more excitement, |
338 |
there are SNAPs released more frequently, particularly during |
345 |
binary snapshots are made every day... see above.</para> |
339 |
the month or so leading up to a release.</para> |
346 |
</answer> |
340 |
</answer> |
|
|
341 |
</qandaentry> |
347 |
</qandaentry> |
342 |
|
348 |
|
343 |
<qandaentry> |
349 |
<qandaentry> |
Lines 393-404
Link Here
|
393 |
|
399 |
|
394 |
<itemizedlist> |
400 |
<itemizedlist> |
395 |
<listitem> |
401 |
<listitem> |
396 |
<para>For the current 2.2-STABLE release, 2.2.8R, see the |
|
|
397 |
<ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.8-RELEASE/">2.2.8-RELEASE</ulink> |
398 |
directory.</para> |
399 |
</listitem> |
400 |
|
401 |
<listitem> |
402 |
<para>For the current 3.X-STABLE release, 3.4-RELEASE, see |
402 |
<para>For the current 3.X-STABLE release, 3.4-RELEASE, see |
403 |
the <ulink |
403 |
the <ulink |
404 |
URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4-RELEASE</ulink> |
404 |
URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4-RELEASE</ulink> |
Lines 406-428
Link Here
|
406 |
</listitem> |
406 |
</listitem> |
407 |
<listitem> |
407 |
<listitem> |
408 |
<para>The current 4.X-STABLE release, 4.0-RELEASE can be |
408 |
<para>The current 4.X-STABLE release, 4.0-RELEASE can be |
409 |
found in <ulink |
409 |
found in the <ulink |
410 |
url="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE"> the 4.0-RELEASE</ulink> directory.</para> |
410 |
url="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE"> the 4.0-RELEASE</ulink> directory.</para> |
411 |
</listitem> |
411 |
</listitem> |
412 |
|
412 |
|
413 |
<listitem> |
413 |
<listitem> |
414 |
<para><ulink |
414 |
<para><ulink |
415 |
URL="ftp://releng3.FreeBSD.org/pub/FreeBSD/">3.X Snapshot</ulink> |
|
|
416 |
releases are also made once a day along the RELENG_3 branch |
417 |
(post 3.0-RELEASE) as it continues on its way towards |
418 |
3.5-RELEASE.</para> |
419 |
</listitem> |
420 |
|
421 |
<listitem> |
422 |
<para><ulink |
423 |
url="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X |
415 |
url="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X |
424 |
snapshots</ulink> are made once a day as well.</para> |
416 |
snapshots</ulink> are usually made once a day.</para> |
425 |
</listitem> |
417 |
</listitem> |
426 |
|
418 |
|
427 |
<listitem> |
419 |
<listitem> |
428 |
<para><ulink |
420 |
<para><ulink |
Lines 570-587
Link Here
|
570 |
|
562 |
|
571 |
<answer> |
563 |
<answer> |
572 |
<para>There is a FreeBSD Documentation Project which you may |
564 |
<para>There is a FreeBSD Documentation Project which you may |
573 |
contact (or even better, join) on the <emphasis |
565 |
contact (or even better, join) at the <emphasis |
574 |
remap=tt>doc</emphasis> mailing list: <ulink |
566 |
remap=tt>freebsd-doc</emphasis> mailing list: <ulink |
575 |
URL="mailto:freebsd-doc@FreeBSD.org"><freebsd-doc@FreeBSD.org></ulink>. |
567 |
URL="mailto:freebsd-doc@FreeBSD.org"><freebsd-doc@FreeBSD.org></ulink>. |
576 |
This list is for discussion of the FreeBSD documentation. For |
568 |
This list is for discussion of the FreeBSD documentation. For |
577 |
actual questions about FreeBSD, there is the <emphasis |
569 |
actual questions about FreeBSD, there is the <emphasis |
578 |
remap=tt>questions</emphasis> mailing list: <ulink |
570 |
remap=tt>freebsd-questions</emphasis> mailing list: <ulink |
579 |
URL="mailto:freebsd-questions@FreeBSD.org"><freebsd-questions@FreeBSD.org></ulink>.</para> |
571 |
URL="mailto:freebsd-questions@FreeBSD.org"><freebsd-questions@FreeBSD.org></ulink>.</para> |
580 |
|
572 |
|
581 |
<para>A FreeBSD ``handbook'' is available, and can be found as: |
573 |
<para>A FreeBSD ``handbook'' is available, and can be found as: |
582 |
<ulink URL="../handbook/index.html">the FreeBSD |
574 |
<ulink URL="../handbook/index.html">the FreeBSD |
583 |
Handbook</ulink>. Note that this is a work in progress, and |
575 |
Handbook</ulink>. Note that this is a work in progress; |
584 |
so parts may be incomplete.</para> |
576 |
some parts may be incomplete or out-of-date.</para> |
585 |
|
577 |
|
586 |
<para>The definitive printed guide on FreeBSD is ``The Complete |
578 |
<para>The definitive printed guide on FreeBSD is ``The Complete |
587 |
FreeBSD'', written by Greg Lehey and published by Walnut Creek |
579 |
FreeBSD'', written by Greg Lehey and published by Walnut Creek |
Lines 593-601
Link Here
|
593 |
URL="http://www.cheapbytes.com">CheapBytes</ulink>, or at your |
585 |
URL="http://www.cheapbytes.com">CheapBytes</ulink>, or at your |
594 |
favorite bookstore. The ISBN is 1-57176-227-2.</para> |
586 |
favorite bookstore. The ISBN is 1-57176-227-2.</para> |
595 |
|
587 |
|
596 |
<para>However, as FreeBSD 2.2.X is based upon Berkeley |
588 |
<para>Since FreeBSD is based upon Berkeley |
597 |
4.4BSD-Lite2, most of the 4.4BSD manuals are applicable to |
589 |
4.4BSD-Lite2, most of the 4.4BSD manuals are applicable to |
598 |
FreeBSD 2.2.X. O'Reilly and Associates publishes these |
590 |
FreeBSD. O'Reilly and Associates publishes the following |
599 |
manuals:</para> |
591 |
manuals:</para> |
600 |
|
592 |
|
601 |
<itemizedlist> |
593 |
<itemizedlist> |
Lines 816-837
Link Here
|
816 |
|
808 |
|
817 |
<itemizedlist> |
809 |
<itemizedlist> |
818 |
<listitem> |
810 |
<listitem> |
819 |
<para>Using CVSUP: You can retrieve the formatted files |
811 |
<para>Using <application>CVSup</application>: |
820 |
using CVSUP from cvsup.FreeBSD.org. Add this line to |
812 |
You can retrieve the formatted files |
821 |
your cvsup file: |
813 |
using <application>CVSup</application>, and connecting |
822 |
|
814 |
to a <application>CVSup</application> server.</para> |
823 |
<literallayout> |
815 |
<para>To retrieve the webpages, please look at the example |
824 |
www release=current hostname=/home base=/usr/local/etc/cvsup |
816 |
supfile, which can be found in |
825 |
prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallayout></para> |
817 |
<filename>/usr/share/examples/cvsup/www-supfile</filename>. |
|
|
818 |
</para> |
826 |
</listitem> |
819 |
</listitem> |
827 |
|
820 |
|
828 |
<listitem> |
821 |
<listitem> |
829 |
<para>Using rsync: See <ulink |
|
|
830 |
URL="http://www.FreeBSD.org/internal/mirror.html">the |
831 |
mirroring page</ulink> for information.</para> |
832 |
</listitem> |
833 |
|
834 |
<listitem> |
835 |
<para>Using ftp mirror: You can download the FTP server's |
822 |
<para>Using ftp mirror: You can download the FTP server's |
836 |
copy of the web site sources using your favorite ftp mirror |
823 |
copy of the web site sources using your favorite ftp mirror |
837 |
tool. Keep in mind that you have to build these sources before |
824 |
tool. Keep in mind that you have to build these sources before |
Lines 851-857
Link Here
|
851 |
<answer> |
838 |
<answer> |
852 |
<para>Well, we can't pay, but we might arrange a free CD or |
839 |
<para>Well, we can't pay, but we might arrange a free CD or |
853 |
T-shirt and a Contributor's Handbook entry if you submit a |
840 |
T-shirt and a Contributor's Handbook entry if you submit a |
854 |
translation of the documentation.</para> |
841 |
translation of the documentation. Before you begin translating |
|
|
842 |
please contact the |
843 |
<emphasis>freebsd-doc</emphasis> mailing list at |
844 |
<email>freebsd-doc@FreeBSD.org</email>; you may find |
845 |
somebody to help with the translation effort. You may also |
846 |
find out there is already |
847 |
a team translating the docs into your chosen language, |
848 |
who surely wouldn't turn down your help. </para> |
855 |
</answer> |
849 |
</answer> |
856 |
</qandaentry> |
850 |
</qandaentry> |
857 |
|
851 |
|
Lines 1156-1167
Link Here
|
1156 |
<qandaentry><question> |
1150 |
<qandaentry><question> |
1157 |
<para>Can I install on a disk with bad blocks?</para></question><answer> |
1151 |
<para>Can I install on a disk with bad blocks?</para></question><answer> |
1158 |
|
1152 |
|
1159 |
<para>FreeBSD's bad block (the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?bad144">bad144</ulink> |
1153 |
<para>Prior to 3.0, FreeBSD included a utility known as |
1160 |
command) handling is still not 100% (to put it charitably) and |
1154 |
<command>bad144</command>, which automatically remapped bad |
1161 |
it must unfortunately be said that if you've got an IDE or ESDI drive |
1155 |
blocks. Because modern IDE drives perform this function themselves, |
1162 |
with lots of bad blocks, then FreeBSD is probably not for you! |
1156 |
<command>bad144</command> has been removed from the FreeBSD source |
1163 |
That said, it does work on thousands of IDE based systems, so |
1157 |
tree. If you wish to install FreeBSD 3.0 or later, we strongly suggest |
1164 |
you'd do well to try it first before simply giving up.</para> |
1158 |
you purchase a newer disk drive. If you do not wish to do this, you |
|
|
1159 |
must run FreeBSD 2.x.</para> |
1160 |
<para>If you are seeing bad block errors with a modern IDE drive, |
1161 |
chances are the drive is going to die very soon (the drive's internal |
1162 |
remapping functions are no longer sufficient to fix the bad blocks, |
1163 |
which means the disk is heavily corrupted); we suggest you by a |
1164 |
new hard drive.</para> |
1165 |
|
1165 |
|
1166 |
<para>If you have a SCSI drive with bad blocks, see <link linkend="awre">this answer</link>.</para> |
1166 |
<para>If you have a SCSI drive with bad blocks, see <link linkend="awre">this answer</link>.</para> |
1167 |
|
1167 |
|
Lines 1193-1201
Link Here
|
1193 |
</listitem> |
1193 |
</listitem> |
1194 |
|
1194 |
|
1195 |
<listitem> |
1195 |
<listitem> |
1196 |
<para>If you're using one of these new-fangled operating systems |
1196 |
<para>If you're using |
1197 |
like Windows95 or Windows NT, did you shut it down and restart |
1197 |
Windows95 or Win98 did you run <command>fdimage</command> or |
1198 |
the system in plain, honest DOS? It seems these OS's can |
1198 |
<command>rawrite</command> in pure DOS mode? These OS's can |
1199 |
interfere with programs that write directly to hardware, which |
1199 |
interfere with programs that write directly to hardware, which |
1200 |
the disk creation program does; even running it inside a DOS |
1200 |
the disk creation program does; even running it inside a DOS |
1201 |
shell in the GUI can cause this problem.</para> |
1201 |
shell in the GUI can cause this problem.</para> |
Lines 1462-1484
Link Here
|
1462 |
|
1462 |
|
1463 |
</answer></qandaentry> |
1463 |
</answer></qandaentry> |
1464 |
|
1464 |
|
1465 |
<qandaentry><question |
|
|
1466 |
id="bigram"> |
1467 |
<para> I have >16MB of RAM. Will this cause any problems? |
1468 |
</para></question><answer> |
1469 |
|
1470 |
<para>Apart from performance issues, no. FreeBSD 2.X comes with bounce |
1471 |
buffers which allow your bus mastering controller access to greater |
1472 |
than 16MB. (Note that this should only be required if you are using |
1473 |
ISA devices, although one or two broken EISA and VLB devices may |
1474 |
need it as well).</para> |
1475 |
|
1476 |
<para>Also look at the section on <link linkend="reallybigram">>64M machines</link> if you have that much memory, |
1477 |
or if you're using a Compaq or other BIOS that lies about |
1478 |
the available memory.</para> |
1479 |
|
1480 |
</answer></qandaentry> |
1481 |
|
1482 |
<qandaentry><question> |
1465 |
<qandaentry><question> |
1483 |
<para>Do I need to install the complete sources?</para></question><answer> |
1466 |
<para>Do I need to install the complete sources?</para></question><answer> |
1484 |
|
1467 |
|
Lines 1505-1513
Link Here
|
1505 |
|
1488 |
|
1506 |
<para>To actually select a subset of the sources, use the Custom |
1489 |
<para>To actually select a subset of the sources, use the Custom |
1507 |
menu item when you are in the Distributions menu of the |
1490 |
menu item when you are in the Distributions menu of the |
1508 |
system installation tool. The <filename>src/install.sh</filename> script |
1491 |
system installation tool.</para> |
1509 |
will also install partial pieces of the source distribution, |
|
|
1510 |
depending on the arguments you pass it.</para> |
1511 |
|
1492 |
|
1512 |
</answer></qandaentry> |
1493 |
</answer></qandaentry> |
1513 |
|
1494 |
|
Lines 2039-2053
Link Here
|
2039 |
</literallayout> |
2020 |
</literallayout> |
2040 |
</para> |
2021 |
</para> |
2041 |
|
2022 |
|
2042 |
<para>In FreeBSD 3.1 or later, the line should be:</para> |
2023 |
<para>In FreeBSD 3.X, the line should be:</para> |
2043 |
|
2024 |
|
2044 |
<para> |
2025 |
<para> |
2045 |
<literallayout> device mse0 at isa? port 0x23c tty irq5 |
2026 |
<literallayout> device mse0 at isa? port 0x23c tty irq5 |
2046 |
</literallayout> |
2027 |
</literallayout> |
2047 |
</para> |
2028 |
</para> |
|
|
2029 |
|
2030 |
<para>And in FreeBSD 4.X and later, the line should read:</para> |
2048 |
|
2031 |
|
2049 |
<para>The bus mouse usually comes with an dedicatd interface card. |
2032 |
<para> |
2050 |
It may allow you to set the port address and the IRQ number other |
2033 |
<literallayout> device mse0 at isa? port 0x23c irq5 |
|
|
2034 |
</literallayout> |
2035 |
</para> |
2036 |
|
2037 |
<para>Bus mice usually comes with dedicated interface cards. |
2038 |
These cards may allow you to set the port address and the IRQ number other |
2051 |
than shown above. Refer to the manual of your mouse and the |
2039 |
than shown above. Refer to the manual of your mouse and the |
2052 |
&man.mse.4; man page for more information.</para> |
2040 |
&man.mse.4; man page for more information.</para> |
2053 |
|
2041 |
|
Lines 2138-2144
Link Here
|
2138 |
</literallayout> |
2126 |
</literallayout> |
2139 |
</para> |
2127 |
</para> |
2140 |
|
2128 |
|
2141 |
<para>In versions 2.2.2 or later, set the following variables in |
2129 |
<para>In versions 2.2.2 to 3.0, set the following variables in |
2142 |
<filename>/etc/rc.conf</filename>.</para> |
2130 |
<filename>/etc/rc.conf</filename>.</para> |
2143 |
|
2131 |
|
2144 |
<para> |
2132 |
<para> |
Lines 2148-2153
Link Here
|
2148 |
</literallayout> |
2136 |
</literallayout> |
2149 |
</para> |
2137 |
</para> |
2150 |
|
2138 |
|
|
|
2139 |
<para>In 3.1 and later, assuming you have a PS/2 mouse, all you need |
2140 |
to is add “moused_enable="YES" to |
2141 |
<filename>/etc/rc.conf</filename>.</para> |
2142 |
|
2151 |
<para>In addition, if you would like to be able to use the mouse |
2143 |
<para>In addition, if you would like to be able to use the mouse |
2152 |
daemon on all virtual terminals instead of just console at boot-time, |
2144 |
daemon on all virtual terminals instead of just console at boot-time, |
2153 |
add the following to <filename>/etc/rc.conf</filename>.</para> |
2145 |
add the following to <filename>/etc/rc.conf</filename>.</para> |
Lines 2431-2437
Link Here
|
2431 |
</answer></qandaentry> |
2423 |
</answer></qandaentry> |
2432 |
|
2424 |
|
2433 |
<qandaentry><question> |
2425 |
<qandaentry><question> |
2434 |
<para>What other devices does 2.X support?</para></question><answer> |
2426 |
<para>What other devices does FreeBSD support?</para></question><answer> |
2435 |
|
2427 |
|
2436 |
<para>See the <ulink URL="../handbook/install.html#INSTALL-MISC">Handbook</ulink> |
2428 |
<para>See the <ulink URL="../handbook/install.html#INSTALL-MISC">Handbook</ulink> |
2437 |
for the list of other devices supported.</para> |
2429 |
for the list of other devices supported.</para> |
Lines 2537-2543
Link Here
|
2537 |
<para>Does FreeBSD support Symmetric Multiprocessing (SMP)? |
2529 |
<para>Does FreeBSD support Symmetric Multiprocessing (SMP)? |
2538 |
</para></question><answer> |
2530 |
</para></question><answer> |
2539 |
|
2531 |
|
2540 |
<para>SMP is supported in 3.0-STABLE and later releases only.</para> |
2532 |
<para>SMP is supported in 3.0-STABLE and later releases only. SMP is |
|
|
2533 |
not enabled in the <emphasis>GENERIC</emphasis> kernel, so you will |
2534 |
have to recompile your kernel to enable SMP. Take a look at |
2535 |
<filename>/sys/i386/conf/LINT</filename> to figure out what options to put in |
2536 |
your kernel config file.</para> |
2541 |
|
2537 |
|
2542 |
</answer></qandaentry> |
2538 |
</answer></qandaentry> |
2543 |
|
2539 |
|
Lines 2604-2610
Link Here
|
2604 |
This is fine for operating systems like DOS that use BIOS code to |
2600 |
This is fine for operating systems like DOS that use BIOS code to |
2605 |
access the disk. However, FreeBSD's disk driver does not go through |
2601 |
access the disk. However, FreeBSD's disk driver does not go through |
2606 |
BIOS, therefore a mechanism, bad144, exists that replaces this |
2602 |
BIOS, therefore a mechanism, bad144, exists that replaces this |
2607 |
functionality. bad144 only works with the wd driver, |
2603 |
functionality. bad144 only works with the wd driver (which means it |
|
|
2604 |
is not supported in FreeBSD 4.0), |
2608 |
it is NOT able to be used with SCSI. bad144 works by entering all bad |
2605 |
it is NOT able to be used with SCSI. bad144 works by entering all bad |
2609 |
sectors found into a special file.</para> |
2606 |
sectors found into a special file.</para> |
2610 |
|
2607 |
|
Lines 2692-2701
Link Here
|
2692 |
firmware for it, you will need to check the position of jumper W1 |
2689 |
firmware for it, you will need to check the position of jumper W1 |
2693 |
to B-C, the default is A-B.</para> |
2690 |
to B-C, the default is A-B.</para> |
2694 |
|
2691 |
|
2695 |
<para>The 742a EISA cards never had the ``>16MB'' problem mentioned in |
|
|
2696 |
the section <link linkend="bigram">on >16 MB machines</link>. This is a |
2697 |
problem that occurs with the Vesa-Local Buslogic SCSI cards.</para> |
2698 |
|
2699 |
</answer></qandaentry> |
2692 |
</answer></qandaentry> |
2700 |
|
2693 |
|
2701 |
<qandaentry><question> |
2694 |
<qandaentry><question> |
Lines 3588-3594
Link Here
|
3588 |
</answer></qandaentry> |
3581 |
</answer></qandaentry> |
3589 |
|
3582 |
|
3590 |
<qandaentry><question> |
3583 |
<qandaentry><question> |
3591 |
<para> When I run a SCO/iBCS2 application, it bombs on <emphasis remap=tt>socksys</emphasis>. |
3584 |
<para> When I run a SCO/iBCS2 application, it bombs on |
|
|
3585 |
<emphasis remap=tt>socksys</emphasis> (FreeBSD 3.0 and older only). |
3592 |
</para></question><answer> |
3586 |
</para></question><answer> |
3593 |
|
3587 |
|
3594 |
<para>You first need to edit the <filename>/etc/sysconfig</filename> |
3588 |
<para>You first need to edit the <filename>/etc/sysconfig</filename> |
Lines 3799-3807
Link Here
|
3799 |
so that all files could be copied with a <command><ulink URL="http://www.FreeBSD.org/cgi/man.cgi?cp(1)">cp</ulink> /usr/src/etc/rc* |
3793 |
so that all files could be copied with a <command><ulink URL="http://www.FreeBSD.org/cgi/man.cgi?cp(1)">cp</ulink> /usr/src/etc/rc* |
3800 |
/etc</command> command.</para> |
3794 |
/etc</command> command.</para> |
3801 |
|
3795 |
|
3802 |
<para><filename>/etc/rc.local</filename> is here as always and may be used to |
3796 |
<para>And, in 3.1 and later, <filename>/etc/rc.conf</filename> has |
3803 |
start up additional local services like <ulink URL="http://www.FreeBSD.org/cgi/ports.cgi?^inn">INN</ulink> |
3797 |
been moved to <filename>/etc/defaults/rc.conf</filename>. <emphasis>Do not edit |
3804 |
or set custom options.</para> |
3798 |
this file!</emphasis> Instead, if there is any entry in |
|
|
3799 |
<filename>/etc/defaults/rc.conf</filename> that you want to change, |
3800 |
you should copy the line into <filename>/etc/rc.conf</filename> and |
3801 |
change it there.</para> |
3802 |
<para>For example, if you wish to start named, the DNS server included |
3803 |
with FreeBSD in FreeBSD 3.1 or later, all you need to do is:</para> |
3804 |
<screen>&prompt.root; <userinput>echo named_enable="YES" >> |
3805 |
/etc/rc.conf</userinput></screen> |
3806 |
|
3807 |
<para>To start up local services in FreeBSD 3.1 or later, place shell |
3808 |
scripts in the <filename>/usr/local/etc.rd</filename> directory. These |
3809 |
shell scripts should be set executable, and end with a .sh. In FreeBSD |
3810 |
3.0 and earlier releases, you should edit the |
3811 |
<filename>/etc/rc.local</filename> file.</para> |
3805 |
|
3812 |
|
3806 |
<para>The <filename>/etc/rc.serial</filename> is for serial port initialization |
3813 |
<para>The <filename>/etc/rc.serial</filename> is for serial port initialization |
3807 |
(e.g. locking the port characteristics, and so on.).</para> |
3814 |
(e.g. locking the port characteristics, and so on.).</para> |
Lines 3809-3842
Link Here
|
3809 |
<para>The <filename>/etc/rc.i386</filename> is for Intel-specifics settings, such |
3816 |
<para>The <filename>/etc/rc.i386</filename> is for Intel-specifics settings, such |
3810 |
as iBCS2 emulation or the PC system console configuration.</para> |
3817 |
as iBCS2 emulation or the PC system console configuration.</para> |
3811 |
|
3818 |
|
3812 |
<para>Starting with 2.1.0R, you can also have "local" startup files in a |
|
|
3813 |
directory specified in <filename>/etc/sysconfig</filename> (or |
3814 |
<filename>/etc/rc.conf</filename>):</para> |
3815 |
|
3816 |
<para> |
3817 |
<literallayout> # Location of local startup files. |
3818 |
local_startup=/usr/local/etc/rc.local.d |
3819 |
</literallayout> |
3820 |
</para> |
3821 |
|
3822 |
<para>Each file ending in <filename>.sh</filename> will be executed in alphabetical order.</para> |
3823 |
|
3824 |
<para>If you want to ensure a certain execution order without changing all |
3825 |
the file names, you can use a scheme similar to the following with |
3826 |
digits prepended to each file name to insure the ordering:</para> |
3827 |
|
3828 |
<para> |
3829 |
<literallayout> 10news.sh |
3830 |
15httpd.sh |
3831 |
20ssh.sh |
3832 |
</literallayout> |
3833 |
</para> |
3834 |
|
3835 |
<para>It can be seen as ugly (or SysV :-)) but it provides a simple and |
3836 |
regular scheme for locally-added packages without resorting to |
3837 |
magical editing of <filename>/etc/rc.local</filename>. Many of the ports/packages |
3838 |
assume that <filename>/usr/local/etc/rc.d</filename> is a local startup directory.</para> |
3839 |
|
3840 |
</answer></qandaentry> |
3819 |
</answer></qandaentry> |
3841 |
|
3820 |
|
3842 |
<qandaentry><question> |
3821 |
<qandaentry><question> |
Lines 3845-3851
Link Here
|
3845 |
<para>Use the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?adduser">adduser</ulink> command. For more complicated usage, the |
3824 |
<para>Use the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?adduser">adduser</ulink> command. For more complicated usage, the |
3846 |
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?pw">pw</ulink> command.</para> |
3825 |
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?pw">pw</ulink> command.</para> |
3847 |
|
3826 |
|
3848 |
<para>To remove the user again, use the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?rmuser">rmuser</ulink> command.</para> |
3827 |
<para>To remove the user again, use the <ulink |
|
|
3828 |
URL="http://www.FreeBSD.org/cgi/man.cgi?rmuser">rmuser</ulink> |
3829 |
command. Once again, <command>pw</command> will work as well.</para> |
3849 |
|
3830 |
|
3850 |
</answer></qandaentry> |
3831 |
</answer></qandaentry> |
3851 |
|
3832 |
|
Lines 4540-4556
Link Here
|
4540 |
|
4521 |
|
4541 |
<para> |
4522 |
<para> |
4542 |
<literallayout> options SYSVSHM |
4523 |
<literallayout> options SYSVSHM |
4543 |
options "SHMMAXPGS=64" # 256Kb of sharable memory |
4524 |
options SYSVSHM # enable shared memory |
4544 |
options SYSVSEM # enable for semaphores |
4525 |
options SYSVSEM # enable for semaphores |
4545 |
options SYSVMSG # enable for messaging |
4526 |
options SYSVMSG # enable for messaging |
4546 |
</literallayout> |
4527 |
</literallayout> |
4547 |
</para> |
4528 |
</para> |
4548 |
|
4529 |
<para><note><para>In FreeBSD 3.2 and later, these options are already part |
4549 |
<para>Recompile and install.</para> |
4530 |
of the <emphasis>GENERIC</emphasis> kernel, which means they should |
|
|
4531 |
already be compiled into your system.</para></note></para> |
4550 |
|
4532 |
|
4551 |
<para><emphasis remap=bf>NOTE:</emphasis> You may need to increase SHMMAXPGS to some |
4533 |
<para>Recompile and install your kernel.</para> |
4552 |
ridiculous number like 4096 (16M!) if you want to run |
|
|
4553 |
GIMP. 256Kb is plenty for X11R6 shared memory.</para> |
4554 |
|
4534 |
|
4555 |
</answer></qandaentry> |
4535 |
</answer></qandaentry> |
4556 |
|
4536 |
|
Lines 5941-5960
Link Here
|
5941 |
box to connect to the Internet and then be able to access the |
5921 |
box to connect to the Internet and then be able to access the |
5942 |
Internet from the Windows95 box through the FreeBSD box. This |
5922 |
Internet from the Windows95 box through the FreeBSD box. This |
5943 |
is really just a special case of the previous question.</para> |
5923 |
is really just a special case of the previous question.</para> |
5944 |
|
5924 |
<para> ... and the answer is yes! In FreeBSD 3.x, user-mode ppp contains a |
5945 |
<para>There's a useful document available which explains how to set |
5925 |
<option>-nat</option> option. If you run <command>ppp</command> with |
5946 |
FreeBSD up as a <ulink URL="http://www.ssimicro.com/~jeremyc/ppp.html">PPP Dialup Router</ulink></para> |
5926 |
the <option>-nat</option>, set <literal>gateway_enable</literal> to |
5947 |
|
5927 |
<emphasis>YES</emphasis> in <filename>/etc/rc.conf</filename>, and |
5948 |
<para><emphasis remap=bf>NOTE:</emphasis> This requires having at least two fixed IP addresses |
5928 |
configure your Windows machine correctly, this should work |
5949 |
available, and possibly three or more, depending on how much |
5929 |
fine.</para> |
5950 |
work you want to go through to set up the Windows box. As an |
5930 |
|
5951 |
alternative, if you don't have a fixed IP, you can use one of |
5931 |
<para>More detailed information about setting this up can be found in |
5952 |
the private IP subnets and install <emphasis remap=bf>proxies</emphasis> such as |
5932 |
the <ulink url="http://www.FreeBSD.org/tutorials/ppp/index.html">Pedantic PPP |
5953 |
<ulink URL="http://squid.nlanr.net/Squid/">SQUID</ulink> and |
5933 |
Primer</ulink> by Steve Sims.</para> |
5954 |
<ulink URL="http://www.tis.com/">the TIS firewall toolkit</ulink> |
5934 |
<para>If you are using kernel-mode ppp, or have an Ethernet connection |
5955 |
on your FreeBSD box.</para> |
5935 |
to the Internet, you will have to use <command>natd</command>. Please |
5956 |
|
5936 |
look at the <link linkend="natd">natd</link> section of this FAQ.</para> |
5957 |
<para>See also the section on <link linkend="natd">natd</link>.</para> |
|
|
5958 |
|
5937 |
|
5959 |
</answer></qandaentry> |
5938 |
</answer></qandaentry> |
5960 |
|
5939 |
|
Lines 6380-6397
Link Here
|
6380 |
</answer></qandaentry></qandaset> |
6359 |
</answer></qandaentry></qandaset> |
6381 |
</chapter> |
6360 |
</chapter> |
6382 |
|
6361 |
|
6383 |
|
|
|
6384 |
|
6385 |
|
6386 |
|
6387 |
|
6388 |
|
6389 |
|
6390 |
|
6391 |
|
6392 |
|
6393 |
|
6394 |
|
6395 |
<chapter id="ppp"> |
6362 |
<chapter id="ppp"> |
6396 |
<title>PPP</title> |
6363 |
<title>PPP</title> |
6397 |
<qandaset> |
6364 |
<qandaset> |
Lines 8027-8036
Link Here
|
8027 |
<para> Why use (what are) a.out and ELF executable formats? |
7994 |
<para> Why use (what are) a.out and ELF executable formats? |
8028 |
</para></question><answer> |
7995 |
</para></question><answer> |
8029 |
|
7996 |
|
8030 |
<para>To understand why FreeBSD uses the <filename>a.out</filename> format, you must |
7997 |
<para>To understand why FreeBSD uses the <filename>ELF</filename> format, you must |
8031 |
first know a little about the 3 currently "dominant" executable |
7998 |
first know a little about the 3 currently "dominant" executable |
8032 |
formats for UNIX:</para> |
7999 |
formats for UNIX:</para> |
8033 |
|
8000 |
|
|
|
8001 |
<para><note><para>Prior to FreeBSD 3.x, FreeBSD used the a.out format.</para></note></para> |
8002 |
|
8034 |
<para> |
8003 |
<para> |
8035 |
<itemizedlist> |
8004 |
<itemizedlist> |
8036 |
|
8005 |
|
Lines 8483-8489
Link Here
|
8483 |
</para></question><answer> |
8452 |
</para></question><answer> |
8484 |
|
8453 |
|
8485 |
<para>There are currently three active/semi-active branches in the FreeBSD |
8454 |
<para>There are currently three active/semi-active branches in the FreeBSD |
8486 |
<ulink URL="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS Repository</ulink>:</para> |
8455 |
<ulink URL="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS |
|
|
8456 |
Repository</ulink> (the RELENG_2 branch is probably only changed twice |
8457 |
a year, which is why there are only three active branches of development):</para> |
8487 |
|
8458 |
|
8488 |
<para> |
8459 |
<para> |
8489 |
<itemizedlist> |
8460 |
<itemizedlist> |
Lines 8507-8513
Link Here
|
8507 |
</itemizedlist> |
8478 |
</itemizedlist> |
8508 |
</para> |
8479 |
</para> |
8509 |
|
8480 |
|
8510 |
<para><acronym>HEAD</acronym> is not an actual branch tag, like the other two, it's |
8481 |
<para><acronym>HEAD</acronym> is not an actual branch tag, like the other two; it's |
8511 |
simply a symbolic constant for |
8482 |
simply a symbolic constant for |
8512 |
<emphasis>"the current, non-branched development stream"</emphasis> which we simply |
8483 |
<emphasis>"the current, non-branched development stream"</emphasis> which we simply |
8513 |
refer to as <option>-CURRENT</option>.</para> |
8484 |
refer to as <option>-CURRENT</option>.</para> |