diff --git a/FAQ/freebsd-faq.sgml b/FAQ/freebsd-faq.sgml index 308a22def9..bff1217137 100644 --- a/FAQ/freebsd-faq.sgml +++ b/FAQ/freebsd-faq.sgml @@ -4,7 +4,7 @@
@@ -140,6 +156,9 @@ Any entries with a <XXX> are under construction.
FreeBSD.
+ FreeBSD 2.1.0 does not install with 4 MB. To be exact: it does
+ not install with 640 kB base + 3 MB extended memory. If your
+ motherboard can remap some of the ``lost'' memory out of the
+ 640kB to 1MB region, then you may still be able to get FreeBSD
+ 2.1.0 up.
+
+ Try to go into your BIOS setup and look for a ``remap'' option.
+ Enable it. You may also have to disable ROM shadowing.
+
+ It may be easier to get 4 more MB just for the install. Build a
+ custom kernel with only the options you need and then get the 4
+ MB out again.
+
+ You may also install 2.0.5 and then upgrade your system to 2.1.0
+ with the ``upgrade'' option of the 2.1.0 installation program.
+
+ After the installation, if you build a custom kernel, it will run
+ in 4 MB. Someone has even succeded in booting with 2 MB (the
+ system was almost unusable though :-))
+
+
If your machine is already running DOS and has little or no free
@@ -354,7 +397,15 @@ Any entries with a <XXX> are under construction.
kind of installation you want.
+ Install Windows 95 first, after that FreeBSD. FreeBSD's boot
+ manager will then manage to boot Win95 and FreeBSD.
+
+
No. If you are using a utility such as Stacker(tm) or
@@ -421,6 +472,35 @@ Any entries with a <XXX> are under construction.
called ``tools/dos-tools
subdirectory) which can be used for this purpose.
+
+ Connect the two computers using a Laplink parallel cable to use
+ this feature:
+
+
+
+ It doesn't. You might mean ``why does my swap seem full?''. If
+ that is what you really meant, it's because putting stuff in swap
+ rather than discarding it makes it faster to recover than if the
+ pager had to go through the file system to pull in clean
+ (unmodified) blocks from an executable.
+
+ The actual amount of dirty pages that you can have in core at
+ once is not reduced; the clean pages are displaced as necessary.
+
+
You have to use either ``
No, but we have done numerous taste tests on blindfolded
volunteers who have also had 250 micrograms of LSD-25
@@ -1343,7 +1447,13 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
now, working on their new ``scratch and sniff'' GUI. It's a
funny old business we're in!
-
Yes! You'll see frequent references to ``daemons'' in the BSD
documentation, and what most people don't know is that this
@@ -1362,15 +1472,6 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
control over your machine to the eternal damnation of your soul.
Given a choice, I think I'd prefer to get used to the scratchy
noises, myself!
-
- /usr/src/share/examples/sup/*-supfile, or you may grab
- updated supfiles from:
-
-
+ The panic indicates that the system ran out of virtual memory for
+ network buffers (specifically, mbuf clusters). You can increase
+ the amount of VM avaliable for mbuf clusters by adding:
+
+
Several different groups have expressed interest in working on
+ options "NMBCLUSTERS=
+
+ ...to your kernel config file, where <n> is a number in the
+ range 512-4096, depending on the number of concurrent TCP
+ connections you need to support. I'd recommend trying 2048 - this
+ should get rid of the panic completely. You can monitor the
+ number of mbuf clusters allocated/in use on the system with
+
+