From 7d35f5f18c2f9f72c530777790df1afdd5fd56aa Mon Sep 17 00:00:00 2001 From: jkh Date: Thu, 20 Mar 1997 13:15:41 +0000 Subject: Reinstating stuff that fell out after jeorg's update... Submitted-By: pds --- share/doc/FAQ/FAQ.sgml | 87 +++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 79 insertions(+), 8 deletions(-) (limited to 'share') diff --git a/share/doc/FAQ/FAQ.sgml b/share/doc/FAQ/FAQ.sgml index c509ce0..5886ff5 100644 --- a/share/doc/FAQ/FAQ.sgml +++ b/share/doc/FAQ/FAQ.sgml @@ -1,5 +1,5 @@ - +
@@ -7,7 +7,7 @@ Maintainer: Peter da Silva -$Date: 1997/03/19 17:17:59 $ +$Date: 1997/03/19 18:31:59 $ This is the FAQ for FreeBSD systems version 2.X All entries are assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted. @@ -211,6 +211,58 @@ Any entries with a <XXX> are under construction. Releases are made about every 6 months on average. + How do I make my own custom release? +

+ To make a release you need to do three things: First, you need to + be running a kernel with the +pseudo-device vn #Vnode driver (turns a file into a device) + + + Second, you have to have the whole CVS repository at hand. + To get this you can use + + but your tag value, if any, should be `.' and your release name + should be cvs: + + +*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 + + + Then run /some/big/filesystem, and from the example + above you've got the CVS repository in /home/ncvs: + + +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 + + + An entire release will be built in + /some/big/filesystem/release + and you will have a full FTP-type installation in + /some/big/filesystem/release/R/ftp + when you're done. If you want to build your SNAP along some other + branch than -current, you can also add Is FreeBSD only available for PCs?

At present, yes. If your machine has a different architecture, we @@ -523,6 +575,19 @@ Any entries with a <XXX> are under construction. system was almost unusable though :-)) + I've got some other special requirements, can I make my own + custom install floppy? +

+ 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 + /usr/src/release/floppies/Makefile 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 + . + + Can Windows 95 co-exist with FreeBSD?

@@ -1921,14 +1986,20 @@ pseudo-device vn #Vnode driver (turns a file into a device) 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). + + 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. - 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. + 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. - You may have to run with no on-board cache. This isn't a disaster, - but it's certainly less than ideal. + There's an extensive FAQ on this at + Help! X Window menus and dialog boxes don't work right! -- cgit v1.1