From owner-doc-jp@jp.freebsd.org  Sat Mar 22 02:40:04 1997
Received: by jaz.jp.freebsd.org (8.8.5+2.7Wbeta5/8.7.3) id CAA08693
	Sat, 22 Mar 1997 02:40:04 +0900 (JST)
Received: by jaz.jp.freebsd.org (8.8.5+2.7Wbeta5/8.7.3) with ESMTP id CAA08688
	for <doc-jp@jp.freebsd.org>; Sat, 22 Mar 1997 02:40:03 +0900 (JST)
Received: from localhost.shinshu-u.ac.jp (localhost.shinshu-u.ac.jp [127.0.0.1]) by azusa.shinshu-u.ac.jp (8.7.1+2.6Wbeta4/3.4Wbeta6) with SMTP id CAA02243 for doc-jp@jp.freebsd.org; Sat, 22 Mar 1997 02:39:51 +0900 (JST)
Message-Id: <199703211739.CAA02243@azusa.shinshu-u.ac.jp>
To: doc-jp@jp.freebsd.org
X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
	boundary="--Next_Part(Sat_Mar_22_02:37:32_1997)--"
Content-Transfer-Encoding: 7bit
Date: Sat, 22 Mar 1997 02:39:51 +0900
From: Ichimiya Ryo <ryo@azusa.shinshu-u.ac.jp>
Reply-To: doc-jp@jp.freebsd.org
Precedence: bulk
X-Distribute: distribute [version 2.1 (Alpha) patchlevel=19]
X-Sequence: doc-jp 2714
Subject: [doc-jp 2714] [patch] FAQ.sgml updated to v.1.40
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org

----Next_Part(Sat_Mar_22_02:37:32_1997)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

 $B0l5\(B $B$H$$$$$^$9!#(B

 FAQ $B$,Mn$ACe$$$F$$$k$H$O$b$&8@$$$^$;$s(B($BN^(B)$B!#(B
$B$?$C$?0lF|$G7k9=$JJQ99$G$9!#(B($BDI2C$,<g(B)
 $BC4Ev<T$N3'MM$h$m$7$/$*4j$$$7$^$9!#(B
[$B3:Ev2U=j(B]
 FAQ-preface.sgml >$BCf0f(B, $B2V0f(B $BMM(B
 FAQ-install.sgml >$BAa5*(B $BMM(B
 FAQ-misc.sgml    >$BFb@n(B $BMM(B ($B:F$S$h$m$7$/$*4j$$$7$^$9(B)

 
	// Ichimiya Ryo (ryo@azusa.shinshu-u.ac.jp)
	// 	(http://naguisa.shinshu-u.ac.jp/~ryo/)
	//  Dept. of Physics[2nd grade], Faculty of Science,
	//  Shinshu Univ., Matsumoto, Japan

----Next_Part(Sat_Mar_22_02:37:32_1997)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

--- ../faq-jp.v-1.39/FAQ-preface.sgml	Sat Mar 22 01:32:21 1997
+++ ./FAQ-preface.sgml	Sat Mar 22 01:55:32 1997
@@ -1,10 +1,10 @@
 <!-- $FreeBSD$ -->
 <!-- The FreeBSD Japanese Documentation Project -->
-<!-- Original revision: 1.39 -->
+<!-- Original revision: 1.40 -->
 
     <sect>
       <heading>Preface<label id="preface"></heading>
-<p><em>$BLu(B: &a.doc-jp;.<newline>19 March 1997.</em>
+<p><em>$BLu(B: &a.doc-jp;.<newline>20 March 1997.</em>
       <p>
         Welcome to the FreeBSD 2.X FAQ!  
 
@@ -194,6 +194,58 @@
           available...
         <p>
           Releases are made about every 6 months on average.
+
+      <sect1>
+	<heading>How do I make my own custom release?<label id="custrel"></heading>
+	<p>
+	  To make a release you need to do three things: First, you need to
+	  be running a kernel with the <tt/vn/ driver configured in. Add
+	  this to your kernel config file and build a new kernel:
+
+	  <verb>
+pseudo-device   vn              #Vnode driver (turns a file into a device)
+	  </verb>
+
+	  Second, you have to have the whole CVS repository at hand.
+	  To get this you can use
+            <url url="../handbook/cvsup.html" name="CVSUP">
+          but your tag value, if any, should be `.' and your release name
+          should be cvs:
+
+	  <verb>
+*default prefix=/home/ncvs base=/a host=cvsup.FreeBSD.org release=cvs delete compress use-rel=suffix
+
+## Main Source Tree
+src-all
+src-eBones
+src-secure
+
+# Other stuff
+ports-all
+www
+	  </verb>
+
+	  Then run <tt/cvsup -g supfile/ to suck all the good bits into your
+	  box...
+
+	  Finally, you need a chunk of empty space to build into. Let's
+	  say it's in <tt>/some/big/filesystem</tt>, and from the example
+	  above you've got the CVS repository in <tt>/home/ncvs</tt>:
+
+	  <verb>
+setenv CVSROOT /home/ncvs	# or export CVSROOT=/home/ncvs
+cd /usr/src/release
+make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release
+	  </verb>
+
+          An entire release will be built in
+	  <tt>/some/big/filesystem/release</tt>
+	  and you will have a full FTP-type installation in
+	  <tt>/some/big/filesystem/release/R/ftp</tt>
+	  when you're done.  If you want to build your SNAP along some other
+          branch than -current, you can also add <tt/RELEASETAG=SOMETAG/ to
+	  the make release command line above, e.g. <tt/RELEASETAG=RELENG_2_2/
+	  would build an up-to-the- minute 2.2 GAMMA snapshot.
 
       <sect1>
         <heading> Is FreeBSD only available for PCs?</heading>

----Next_Part(Sat_Mar_22_02:37:32_1997)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

--- ../faq-jp.v-1.39/FAQ-install.sgml	Sat Mar 22 01:31:17 1997
+++ ./FAQ-install.sgml	Sat Mar 22 02:01:54 1997
@@ -1,10 +1,10 @@
 <!-- $FreeBSD$ -->
 <!-- The FreeBSD Japanese Documentation Project -->
-<!-- Original revision: 1.39 -->
+<!-- Original revision: 1.40 -->
 
     <sect>
       <heading>Installation<label id="install"></heading>
-<p><em>$BLu(B: &a.doc-jp;.<newline>19 March 1997.</em>
+<p><em>$BLu(B: &a.doc-jp;.<newline>20 March 1997.</em>
       <p>
       <sect1>
         <heading>Which file do I download to get FreeBSD?</heading>
@@ -107,6 +107,19 @@
           After the installation, if you build a custom kernel, it will run
           in 4 MB. Someone has even succeeded in booting with 2 MB (the
           system was almost unusable though :-))
+
+      <sect1>
+        <heading>I've got some other special requirements, can I make my own
+	         custom install floppy?</heading>
+	<p>
+	  Currently there's no way to *just* make a custom install floppy.
+	  You have to cut a whole new release, which will include your
+	  install floppy. There's some code in
+	  <TT>/usr/src/release/floppies/Makefile</TT> that's supposed to let
+	  you *just* make those floppies, but it's not really gelled yet.
+
+	  To make a custom release, follow the instructions
+            <ref id="custrel" name="here">.
 
       <sect1>
 	<heading>Can Windows 95 co-exist with FreeBSD?</heading>

----Next_Part(Sat_Mar_22_02:37:32_1997)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

--- ../faq-jp.v-1.39/FAQ-misc.sgml	Fri Mar 21 01:37:48 1997
+++ ./FAQ-misc.sgml	Sat Mar 22 02:07:02 1997
@@ -1,10 +1,10 @@
 <!-- $FreeBSD$ -->
 <!-- The FreeBSD Japanese Documentation Project -->
-<!-- Original revision: 1.39 -->
+<!-- Original revision: 1.40 -->
 
     <sect>
       <heading>Miscellaneous Questions<label id="misc"></heading>
-<p><em>$BLu(B: &a.doc-jp;.<newline>19 March 1997.</em>
+<p><em>$BLu(B: &a.doc-jp;.<newline>20 March 1997.</em>
       <p>
 
       <sect1>
@@ -256,14 +256,20 @@
           memory as being fine, it's possible for slightly marginal memory
           to pass all memory tests, yet fail under operating conditions
           (such as during busmastering DMA from a SCSI controller like the
-          Adaptec 1542).
+          Adaptec 1542, when you're beating on memory by compiling a kernel,
+	  or just when the system's running particularly hot).
 
-	  Often the guilty party is bad cache RAM or a bad on-board cache
-	  controller. Try disabling the on-board (secondary) cache in the
-	  BIOS setup and see if that solves the problem.
-
-	  You may have to run with no on-board cache. This isn't a disaster,
-	  but it's certainly less than ideal.
+	  The SIG11 FAQ (listed below) points up slow memory as being the
+	  most common problem. Increase the number of wait states in your
+	  BIOS setup, or get faster memory.
+
+	  For me the guilty party has been bad cache RAM or a bad on-board
+	  cache controller. Try disabling the on-board (secondary) cache in
+	  the BIOS setup and see if that solves the problem.
+
+	  There's an extensive FAQ on this at
+	  <url url="http://www.bitwizard.nl/sig11/"
+               name="the SIG11 problem FAQ">
  
       <sect1>
         <heading>Help! X Window menus and dialog boxes don't work right!</heading>

----Next_Part(Sat_Mar_22_02:37:32_1997)----
