hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2024-12-30 15:38:06 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Begin reorg of FAQ directory.

Browse Source
This commit is contained in:
Gary Clark II 1995-01-03 15:48:52 +00:00
parent 091611b3ab
commit 0772155343
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=5357
9 changed files with 2233 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

987
share/FAQ/FreeBSD-1.X/FreeBSD-1.1.FAQ Normal file
View File

@ -0,0 +1,987 @@
FreeBSD
Frequently Asked Questions
For Versions 1.1 and below
Please mail all suggestions and additions to <FreeBSD-FAQ@FreeBSD.ORG>
Revision: $Id: FreeBSD-1.1.FAQ,v 1.5 1994/11/23 10:21:59 gclarkii Exp $
All entries are assumed to be relevant to both FreeBSD 1.1 and FreeBSD 1.1.5,
unless otherwise noted.
Table of Contents
-----------------
0 Preface
1 Installation
2 Hardware Compatibility
3 Commercial applications
4 User Applications
5 Miscellaneous Questions
6 Kernel Configuration
7 System Administration
8 Networking
9 Serial Communications
0 Preface
---------
Welcome to the FreeBSD 1.1 FAQ! This document tries to answer some of
the most frequently asked questions about FreeBSD 1.1 (or later,
unless specifically indicated). If there's something you're having
trouble with and you just don't see it here, then please send mail to:
<questions@FreeBSD.ORG>
Some of the instructions here will also refer to auxiliary utilities
in the /usr/src/share/FAQ directory. CDROM purchasers and net folks
who've grabbed the FreeBSD current `srcdist' will have these files. If
you don't have the source distribution, then you can either grab the
whole thing from:
ftp.FreeBSD.ORG:pub/FreeBSD/FreeBSD-current/src
0.1: What is FreeBSD?
FreeBSD is a UN*X type operating system based on William Jolitz's port
of U.C. Berkeley's Networking Release 2 to the i386, 386BSD. It is no
longer correct to say that FreeBSD is only 386BSD with the patchkit
applied! There have been many additions and bug fixes made throughout
the entire system, some of the highlights of which are:
More robust and extensive PC device support
System V-style IPC, messaging and semaphores
Shared Libraries
Much improved virtual memory code
Better console driver support
Network booting (diskless) support
/proc filesystem
Yellow Pages support
`LDT' support for WINE (primitive but developing Windows emulation)
Too many additional utilities and applications to mention
0.2: My friends told me that FreeBSD was illegal and I shouldn't use it.
Is this really true?
FreeBSD versions up to and including 1.1 have included code from
Berkeley's Net/2 distribution. UNIX Systems Laboratories (now Novell)
sued Berkeley claiming that Net/2 included some code that belonged to
USL. In February of 1994, USL and Berkeley announced a settlement in
which neither side admitted to doing anything wrong, but UCB agreed to
stop distributing the disputed software.
Since Berkeley will no longer defend this code, we have been requested
to stop distributing it, and will be integrating all the improvements
we have made in the VM system and i386-specific code into Berkeley's
4.4-Lite distribution; the result will form the basis of FreeBSD 2.0.
We expect the integration to take place over a period of three to six
months, during which time we will have to stop work on 1.1 and
concentrate all our efforts on the merge, and we expect to make more
information available on the status of the merge effort as the situation
progresses.
However, to answer the question, "No. FreeBSD is not illegal." We
have been allowed by USL to distribute 1.1 as the last Net/2 derived
version, after which we have committed to move to 4.4 as previously
stated.
We expect to make more information available on the status of the
merge effort as the situation progresses.
0.3: What are the FreeBSD mailing lists, and how can I get on them?
The following mailing lists are provided for FreeBSD users and
developers. For more information, send to
<majordomo@FreeBSD.ORG> and include a single line saying
``help'' in the body of your message.
announce: For announcements about or on FreeBSD.
hackers: Useful for persons wishing to work on the internals.
questions: General questions on FreeBSD.
bugs: Where bugs should be sent.
commit: This list carries the commit messages for freefall. Useful
for tracking ongoing work.
SCSI: Mailing list for SCSI developers.
current: This list is for persons wishing to run FreeBSD-current
and carries announcements and discussions on current.
ports: Discussion of "/usr/ports"
hardware: Types of hardware FreeBSD runs on
security: Security issues
platforms: Porting to non-Intel platforms
Please see also the FreeBSD mailing list FAQ in:
/usr/src/share/FAQ/FreeBSD.mailing-list.FAQ
0.4: What are the various FreeBSD news groups?
While there are no groups currently dedicated to FreeBSD, you may find
the following groups useful.
comp.os.386bsd.announce: For announcements
comp.os.386bsd.apps: For applications
comp.os.386bsd.questions: For questions
comp.os.386bsd.development: For working on the internals
comp.os.386bsd.bugs: About bugs
comp.os.386bsd.misc: For items that don't fit anywhere else
NOTE: These groups cover all the *BSDs (FreeBSD, NetBSD, 386BSD).
1 Installation
--------------
1.1: I just installed my system and rebooted. Now I can't find the
extract or configure programs, where did they go?
These two commands are just shell functions defined in /.profile. To
get these back, boot FreeBSD with a `-s' at the boot prompt.
1.2: I want to install FreeBSD onto a SCSI disk that has more than
1024 cylinders. How do I do it?
This depends. If you don't have DOS (or another operating system) on
the system, you can just keep the drive in native mode and simply make
sure that your root partition is below 1024 so the BIOS can boot the
kernel from it. It you also have DOS/some other OS on the drive then
your best bet is to find out what parameters that it thinks you have
before installing FreeBSD. When FreeBSD's installation procedure
prompts you for these values, you should then enter them rather than
simply going with the defaults.
There is a freely available utility distributed with FreeBSD called
`pfdisk' (located in the tools/ subdirectory) which can be used for
this purpose.
1.3: When I boot FreeBSD it says ``Missing Operating System''.
See question 1.2. This is classically a case of FreeBSD and DOS or
some other OS conflicting over their ideas of disk geometry. You will
have to reinstall FreeBSD, but obeying the instructions given above
will almost always get you going.
1.4: I have an IDE drive with lots of bad blocks on it and FreeBSD doesn't
seem to install properly.
FreeBSD's bad block (bad144) handling is still not 100% (to put it
charitably) and it must unfortunately be said that if you've got an
IDE or ESDI drive with lots of bad blocks, then FreeBSD is probably
not for you! That said, it does work on thousands of IDE based
systems, so you'd do well to try it first before simply giving up.
IDE drives are *supposed* to come with built-in bad-block remapping;
if you have documentation for your drive, you may want to see if this
feature has been disabled on your drive. However, ESDI, RLL, and
ST-506 drives normally do not do this.
<1.1.5>
FreeBSD-current has better bad block handling due to improvments made
to the wd driver.
1.5: I have 32MB of memory, should I expect any special problems?
If you have an IDE controller, no. Likewise, if you have a full EISA
system with EISA disk controller or a working local bus controller
(read further) you'll have no problems. If you have an ISA system, or
an EISA system with an ISA disk controller then you will most
certainly have problems with the upper 16MB of memory due to the ISA
24 bit DMA limitation (which ISA cards in EISA systems will also
exhibit). If you have a local bus disk controller, then you should be
OK, UNLESS it's a Buslogic Bt445S with a revision less than `D' (BIOS
3.36 or earlier).
<1.1.5>
1.1.5 has bounce-buffer support that make all of the above scenarios work
with a full 32MB of memory or more. You are therefore advised to simply pull
16MB of memory out, install, and then see about upgrading to FreeBSD 1.1.5
so that you can put it back.
1.6: Do I need to install the complete sources?
In general, no. However, we would strongly recommend that you
install, at a minimum, the `base' source kit, which includes several
of the files mentioned here, and the `sys' (kernel) source kit, which
includes sources for the kernel. There is nothing in the system which
requires the presence of the sources to operate, however, except for
the kernel-configuration program config(8). With the exception of the
kernel sources, our build structure is set up so that you can
read-only mount the sources from elsewhere via NFS and still be able
to make new binaries. (Because of the kernel-source restriction, we
recommend that you not mount this on /usr/src directly, but rather in
some other location with appropriate symbolic links to duplicate the
top-level structure of the source tree.)
Having the sources on-line and knowing how to build a system with them
will make it much easier for you to upgrade to future releases of
FreeBSD.
1.7: DES encryption software can not be exported from the United
States. If I live outside the US, how can I encrypt passwords?
Since the DES encryption algorithm, which is used by passwd(1) and
friends to encrypt passwords cannot legally be exported from the US,
non-US users should not download this software from US FTP sites.
There is however a replacement libcrypt available, based on sources
written in Australia by David Burren. This code is now available on
some non-US FreeBSD mirror sites. Sources for the unencumbered
libcrypt, and binaries of the programs which use it, can be obtained
from the following FTP sites:
South Africa: braae.ru.ac.za:/pub/FreeBSD/securedist/
owl.und.ac.za (currently uncertain)
Iceland: ftp.veda.is:/pub/crypt/FreeBSD/
The non-US securedist can be used as a direct replacement for the
encumbered US securedist. This securedist package is installed the
same way as the US package (see installation notes for details). If
you are going to install DES encryption, you should do so as soon as
possible, before installing other software.
Non-US users should please not download any encryption software from
the USA. This can get the maintainers of the sites from which the
software is downloaded into severe legal difficulties.
A non-US distribution of Kerberos is also being developed, and current
versions can generally be obtained by anonymous FTP from
braae.ru.ac.za.
There is also a mailing list for the discussion of non-US encryption
software. For more information, send an email message with a single
line saying ``help'' in the body of your message to
<majordomo@braae.ru.ac.za>.
1.8 HELP! My keyboard locked up during the install!
Some keyboard controllers are not a friend to FreeBSD. Among these are
those on certain models of Gateway, IBM and AST machines. The most frequent
symptom encountered in such cases is that the keyboard refuses to respond
to input when at the `kcopy>' prompt in the second phase of bootstrapping
FreeBSD. Fortunately, there is a work-around that may get you all the
way home. Reset the machine and boot the kcopy floppy again, but this
time, as the kernel is booting, tap periodically on the num-lock key
until the kcopy prompt appears. Your keyboard should respond properly.
Once your system is on the hard disk the problem generally goes away.
Some folks for whom the problem persists even after this stage find
relief in switching to the SYSCONS console driver (see /sys/i386/conf/SYSCONS),
which is in any case far more featureful than pccons and a recommended
upgrade.
2 Hardware compatibility
------------------------
2.1: What kind of hard drives does FreeBSD run on?
FreeBSD supports ST-506 (sometimes called ``MFM''), RLL, and ESDI
drives, which are usually connected to WD-1002, WD-1003, or WD-1006
controllers (although clones should also work). FreeBSD also supports
IDE and SCSI hard drives.
2.2: What SCSI controllers are supported?
FreeBSD supports the following SCSI controllers:
Adaptec AH-1542 Series <ISA>
AH-1742 Series <EISA>
Buslogic BT-445 Series <VLB> (but see section 1.5)
BT-545 Series <ISA>
BT-742 Series <EISA>
BT-747 Series <EISA>
Future Domain TMC-8XX/950 Series <ISA> (1.1.5 ONLY)
Seagate ST-01/02 Series <ISA> (1.1.5 ONLY)
UltraStor UH-14f Series <ISA>
UH-34f Series <EISA/VLB>
There is supposed to be a UltraStor 24f driver floating around, but
we're not sure where (could someone please point us at it?).
2.3: What CD-ROM drives are supported by FreeBSD?
Any SCSI drive connected to a supported controller. Mitsumi
LU002(8bit), LU005(16bit) and FX001D(16bit 2x Speed).
FreeBSD does NOT support drives connected to a Sound Blaster or
non-SCSI SONY or Panasonic drives. A general rule of thumb when
selecting a CDROM drive for FreeBSD use is to buy a very standard SCSI
model; they cost more, but deliver very solid performance in return.
Do not be fooled by very cheap drives that, in turn, deliver VERY LOW
performance! As always, you get what you pay for.
The Mitsumi driver is known to be extremely slow compared to SCSI
drives.
2.4: What multi-port serial cards are supported by FreeBSD?
AST/4 and BOCA 4/8/16 port cards. Some unnamed clone cards have also
been known to work, especially those that claim to be AST compatible.
Check the sio(4) man page to get more information on configuring such
cards.
2.5: Does FreeBSD support the AHA-2742 SCSI adapter from Adaptec?
No, FreeBSD does not. This is due to Adaptec's unwillingness to
supply programming information under other than non-disclosure. This
is unfortunate, but there's nothing we can do about it.
2.6: I have a Mumbleco bus mouse. Is it supported and if so, how do I set
it up for XFree86?
FreeBSD supports the Logitech and ATI Inport bus mice. You need to
add the following line to the kernel config file and recompile for the
Logitech and ATI mice:
device mse0 at isa? port 0x23c tty irq6 vector mseintr
2.7: I have a PS/2 mouse (`keyboard' mouse) [Alternatively: I have a
laptop with a track-ball mouse]. How do I use it?
<1.1.5>: The PS/2 mouse is part of the system. See the psm0 driver
description in /sys/doc/options.doc.
2.8: What types of tape drives are supported under FreeBSD?
FreeBSD supports SCSI, QIC-02 and QIC-40/80 (Floppy based) tape
drives. This includes 8-mm (aka Exabyte) and DAT drives.
2.9: What sound cards are supported by FreeBSD?
FreeBSD supports the SoundBlaster, SoundBlaster Pro, Pro Audio
Spectrum 16, AdLib and Gravis UltraSound sound cards. There is also
limited support for MPU-401 and compatible MIDI cards. The
SoundBlaster 16 and SoundBlaster 16 ASP cards are not yet supported.
NOTE: This is only for sound! This driver does not support CD-ROMs,
SCSI or joysticks on these cards.
2.10: What network cards does FreeBSD support?
There is support for the following cards:
`ed' driver:
NE2000 and 1000
WD/SMC 8003, 8013 and Elite Ultra (8216)
3Com 3c503
And clones of the above
`ie' driver:
AT&T EN100/StarLAN 10
`is' driver:
Isolan AT 4141-0
Isolink 4110
`ep' driver:
3com 3c509 (*)
(*)The `ep' driver is known to have some problems; see the
/usr/src/KNOWNBUGS file for more details.
2.11: I have a 386/486sx/486SLC machine without a math co-processor.
Will this cause me any problems?
Generally no, but there are circumstances where you will take a hit,
either in performance or accuracy of the math emulation code (see
section 4.1). In particular, drawing arcs in X will be VERY slow. It
is highly recommended that you lay out the $50 or so for a math
co-processor; it's well worth it. NOTE: Some math co-processors are
better than others. It pains us to say it, but nobody ever got fired
for buying Intel. Unless you're sure it works with FreeBSD, beware of
clones.
2.12: I am about to buy a new machine to run FreeBSD on and
want an idea of what other people are running. Is there list
of other systems anywhere?
Yes. Please look at the file FAQ/Systems-1.1.FAQ. This file
is a listing of hardware that people are running in their machines.
Please note, this is a raw listing of equipment that other users
have sent in.
3 Commercial Applications
-------------------------
Note: This section is still very sparse, though we're hoping, of
course, that companies will add to it! :) The FreeBSD group has no
financial interest in any of the companies listed here but simply
lists them as a public service (and feels that commercial interest in
FreeBSD can have very positive effects on FreeBSD's long-term
viability). We encourage commercial software vendors to send their
entries here for inclusion.
3.1: Where can I get Motif for FreeBSD?
Sequoia International provides commercial quality Motif 1.2.3
development kits for FreeBSD 1.1 (with full shared library support)
under the product name of `SWiM'. Due to licensing restrictions from
the OSF, and the fact that Sequoia needs to make a living, these are
NOT FREE, but nonetheless quite reasonably priced in comparison to
many other commercial Motif distributions. Send electronic mail to
<info@seq.com> for further information.
3.2: What about other commercial quality development systems for FreeBSD?
ParcPlace Systems, Inc., who currently provides their excellent
`Object Interface & Object Builder' GUI development environment free
of charge to Linux users, is considering the the FreeBSD platform and
will make their intentions known fairly shortly.
4 User Applications
-------------------
4.1: I want to run X, how do I go about it?
First, get the XFree86 distribution of X11R5 from XFree86.cdrom.com.
The version you want for FreeBSD 1.1 and later is XFree86 2.1. Follow
the instructions for installation carefully. You may then wish to read
the documentation for the ConfigXF86 tool, which assists you in
configuring XFree86 for your particular graphics card/mouse/etc.
4.1: I've been trying to run ghostscript on a 386 (or 486sx) with no
math co-processor and I keep getting errors. What's up?
<1.1.5>: For 1.1.5 you may add the following to your kernel config file and
it will be compiled in.
options GPL_MATH_EMULATE
NOTE: You will need to remove the MATH_EMULATE option when you do this.
4.2: If I want something like seyon, term, Kermit, emacs or any one of
hundreds of popular freeware utilities, is there a good place to
search through first?
Yes, the FreeBSD `ports collection' was put together for just that
purpose. It contains some of the most often requested languages,
editors, mail and news reading programs, network software and many
many megabytes of other types of useful goodies. CDROM people will
probably have the ports collection already in /usr/ports, other folks
can get at the latest snapshot of the entire collection in:
ftp.FreeBSD.ORG:pub/FreeBSD/FreeBSD-current/ports
Note that this FTP server permits getting entire directories as one
(optionally gzipped or compressed) tar file. Read the FTP welcome
banner carefully for details.
4.3: I want all this neat software, but I haven't got the space or
CPU power to compile it all myself. Is there any way of getting
binaries?
Yes. We support the concept of a `package', which is essentially a
gzipped binary distribution with a little extra intelligence embedded
in it for doing any custom installation work required. Packages can
also be installed or deinstalled again easily without having to know
the gory details. CDROM people will have a packages/ directory on
their CD, others can get the currently available packages from:
ftp.FreeBSD.ORG:pub/FreeBSD/packages-1.1
Note that all ports may not be available as packages, and that new
packages are constantly being added. It is always a good idea to
check periodically to see which packages are available. A README file
in the packages directory provides more details on the care and
feeding of the package software, so no explicit details will be given
here.
4.4: I'm trying to get Perl to work properly, but I keep getting
errors about dbm failures when I test it. How can I fix this?
The problem here is that the tests are written for an older version of
the dbm code. There is nothing wrong with perl and the errors can
be ignored.
4.5: I've been trying to get GCC 2.6.0 running on my system and it
keeps bombing. What can I do about?
Due to problems with 2.6.0 and the advent of FreeBSD 2.0, we do not
support GCC 2.6.0 and suggest that you wait for 2.0.
5 Miscellaneous Questions
----------------
5.1: I've heard of something called FreeBSD-current. How do I run it, and
where can I get more information?
Read the file /usr/src/share/FAQ/FreeBSD.current.policy,
it will tell you all you need to know.
5.2: What is this thing called `sup', and how do I use it?
SUP stands for Software Update Protocol, and was developed by CMU for
keeping their development trees in sync. We use it to keep remote
sites in sync with our central development sources.
To use it, you need to have direct internet connectivity (not just
mail or news). First, pick up the sup_bin.tgz package from:
ftp.FreeBSD.ORG:pub/FreeBSD/packages-1.1
Second, read the file /usr/src/share/FAQ/FreeBSD.sup.faq.
This file describes how to setup sup on your machine. You may also
want to look at /usr/src/contrib/FAQ/FreeBSD.*.supfile,
which are a set of supfiles for supping from FreeBSD.ORG
5.3: How do I create customized installation disks that I can give
out to other people at my site?
The entire process of creating installation disks and source and
binary archives is automated by various targets in
/usr/src/etc/Makefile. The information there should be enough to get
you started.
5.4: How do I re-build my system without clobbering the existing
installed binaries?
If you define the environment variable DESTDIR while running `make
world' or `make install', the newly-created binaries will be deposited
in a directory tree identical to the installed one, rooted at
${DESTDIR}. Some random combination of shared libraries modifications
and program rebuilds can cause this to fail in `make world', however.
5.5: When my system booted, it told me that ``(bus speed defaulted)''.
What does that mean?
The Adaptec 1542 SCSI host adapters allow the user to configure their
bus access speed in software. Previous versions of the 1542 driver tried
to determine the fastest usable speed and set the adapter to that. We
found that this breaks some users' systems, so you now have to define
the ``TUNE_1542''' kernel configuration option in order to have this
take place. Using it on those systems where it works may make your
disks run faster, but on those systems where it doesn't, your data could
be corrupted.
5.6: I would like to track changes to current and do not have net access.
Is there any way besides downloading the whole tree?
Yes, Poul-Henning has set up a source tracking list. Please email
majordomo@ref.tfs.com with a body of "get ctm-src-cur README" for
futher information.
5.7: How do I split up large binary files into smaller 240k files
like the distribution does?
Newer BSD based systems have a "-b" option to split that allows them to
split files on arbitary byte bondaries.
Here is an example from /usr/src/Makefile.
bin-tarball:
(cd ${DISTDIR}; \
tar cf - . \
gzip --no-name -9 -c | \
split -b 240640 - \
${RELEASEDIR}/tarballs/bindist/bin_tgz.)
5.8: I'm running Syscons and every morning my console locks up. What
is going on here?
This sounds like the "kill -1 syslogd" problem. Make sure that the
following is correct on your system.
1. The attributes of the following nodes are correct.
/dev/console
crw------- 1 root 0, 0 May 23 15:32 /dev/console
/dev/ttyv0
crw------- 1 root 12, 0 May 23 15:32 /dev/ttyv0
The part you are concerned with are the major and minor device numbers.
2. Make sure that getty is running on ttyv0 and NOT console.
3. If /dev/vga exists that it is a symlink to /dev/ttyv0.
5.9: I've had a couple of system panics and would like to be able
browse the system dumps. The normal kernel is stripped and
I don't want to run a bloated kernel. What can I do?
Please retrieve the file FAQ/FreeBSD.kdebug.FAQ. This
file covers the instructions for looking at system dumps.
5.10: I've got a Buslogic BT-946c with an Intel motherboard and
right after the kernel probes, my system hangs. How do I
fix it?
Two things here.
1. Some intel motherboards have fixed PCI INT pins and you will have
to match the BT-946c's INT to match the motherboards.
2. FreeBSD 1.1.5.1 expects the INT on a non-standard pin and you
will have to also match this one.
6 Kernel Configuration
----------------------
6.1: When I compile a kernel with multi-port serial code, it tells me
that only the first port is probed and the rest skipped due to
interrupt conflicts. How do I fix this?
The problem here is that FreeBSD has code built-in to keep the kernel
from getting trashed due to hardware or software conflicts. The way
to fix this is to leave out the IRQ settings on other ports besides
the first. Here is a example:
#
# Multiport high-speed serial line - 16550 UARTS
#
device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr
device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr
device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr
device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr
6.2: FreeBSD is supposed to come with support for QIC-40/80 drives but
when I look, I can't find it.
You need to uncomment the following line in the generic config file
(or add it to your config file) and recompile.
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fdc0 drive 0
disk fd1 at fdc0 drive 1
#tape ft0 at fdc0 drive 2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You will have a device called /dev/ft0, which you can write to through
a special program to manage it called `ft' - see the man page on ft for
further details. Versions previous to -current also had some trouble dealing
wiht bad tape media; if you have trouble where ft seems to go back and forth
over the same spot, try grabbing the latest version of ft from /usr/src/sbin/ft
in current and try that.
6.3: Does FreeBSD support IPC primitives like those in System V?
Yes, FreeBSD supports System V-style IPC. This includes shared
memory, messages and semaphores. You need to add the following lines
to your kernel config to enable them.
options SYSVSHM
options "SHMMAXPGS=64" # 256Kb of sharable memory
options SYSVSEM # enable for semaphores
options SYSVMSG # enable for messaging
Recompile and install.
6.4: Are there any utilities that make configuring a kernel easier?
Well, yes and no. Look in /sys/i386/doc/options.doc (/sys/doc on post
1.1 systems) for a list of kernel options you can set, and what they
do. For a friendlier front-end to the process, see
/usr/src/contrib/configit
6.5: Will FreeBSD ever support other architectures?
Several different groups have expressed interest in working on
multi-architecture support for FreeBSD. If you are interested in
doing so, please contact the developers at
<hackers@FreeBSD.ORG> for more information on our
strategy for porting.
6.6: I just wrote a device driver for a Foobar Systems, Inc.
Integrated Adaptive Gronkulator card. How do I get the
appropriate major numbers assigned?
This depends on whether or not you plan on making the driver publicly
available. If you do, then please send us a copy of the driver source
code, plus the appropriate modifications to files.i386, a sample
configuration file entry, and the appropriate MAKEDEV code to create
any special files your device uses. If you do not, or are unable to
because of licensing restrictions, then character major number 32 and
block major number 8 have been reserved specifically for this purpose;
please use them. In any case, we'd appreciate hearing about your
driver on <hackers@FreeBSD.ORG>.
6.7: I'm wanting to switch console drivers to Syscons. I changed my
kernel config file to run Syscons, but when I reboot the system
locks up! How do I fix it?
There are four things that need to be done to properly install syscons
on a system.
1. Add the following line to your kernel config file while deleting the
line for pccons.
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
(Note the changed vector 'scintr'. It is a common error to change the
device name but NOT the vector.
2. Add the following option to your config file.
options "NCONS=6" # Change to reflect the number of consoles
3. Modify /etc/ttys to enable gettys on ttyv0 - ttyv??. Here is an
example line.
ttyv0 "/usr/libexec/getty Pc" Pc3 on secure
Please make sure that you have disabled the getty on /dev/console.
4. Create the device nodes in /dev. This is done useing the MAKEDEV
script located in that directory. Here is a command line that will create
6 virtual consoles.
MAKEDEV vty6
If /dev/vga exists, it should now be a symlink to /dev/ttyv0.
NOTE: If you are going to be running X, you will need an unused vty that
has no getty running on it.
7 System Administration
-----------------------
7.1: How do I add a user easily? I read the man page and am more confused
than ever! [Alternatively: I didn't read the man page, I never read
man pages! :-) ]
Look at Gary Clark's Perl package ``AddIt'', which may be found in
/usr/src/contrib/adduser. This is a first attempt at solving the
problem and may be replaced with a more complex but capable solution
later.
7.2: I'm trying to use my printer and keep running into problems. I tried
looking at /etc/printcap, but it's close to useless. Any ideas?
Yes, you can pick up Andreas Klemm's apsfilter package from:
ftp.germany.eu.net:pub/comp/i386/Linux/Local.EUnet/People/akl/apsfilter-1.11.gz
This is a complete package for printing text, PS and DVI files. It
requires ghostscript and dvips.
If you are looking for a simple printcap just for PS and text files,
try picking up the printcap01 sources in:
/usr/src/contrib/FAQ/code/printcap01
NOTE: We're looking for printcap entries for all printers. If you
have one, or a filter for one, please send it or mail us a pointer to
<FreeBSD-FAQ@FreeBSD.ORG>. Thanks!
7.3: Help! I've lost my root password! How do I log in now?
Alternatively: I botched something bad in my root partition
that keeps me from booting, how do I fix it!?
Follow these steps:
1. First off, you need to boot the system single-user: Do this by rebooting
or resetting the machine, and when you come to the very first boot prompt
(the one you probably generally just hit `return' at or wait for it to
time-out) type:
386bsd -s
This will send the `-s' flag to init(1) telling it to not bring you up all
the way into multi-user mode. The system should come up single-user and
present you with a simple `#' prompt.
2. Now is probably a good time to type `fsck' and make sure your filesystems
are alright. If problems on your root filesystem are found and fixed, I would
recommend hitting the reset switch again and going back to step 1. Your
filesystems should all check fine the second time.
3. At this point, your root filesystem is mounted *read only* for safety.
If the problems you must fix are not on the root fs then I recommend that
you simply leave it this way and fix the other problems. If you need to
write to the root fs (fixing passwords requires this, for one thing) and
you're using SCSI for your root fs then type:
mount -u /dev/sd0a /
If you're using IDE/ESDI for your rootfs, then instead type:
mount -u /dev/wd0a /
This will remount your root filesystem read/write and allow you to make
your changes. Once you have done so, I recommend another reboot. -Jordan
8 Networking
------------
8.1: Where can I get information booting FreeBSD `diskless', that is
booting and running a FreeBSD box from a server rather than having
a local disk?
Please read /sys/i386/netboot/netboot.doc.
8.2: I've heard that you can use a FreeBSD box as a dedicated network
router - is there any easy support for this?
Internet standards and good engineering practice prohibit us from
providing packet forwarding by default in FreeBSD. You can enable
this support by adding `options GATEWAY' to your kernel configuration
file and recompiling. In most cases, you will also need to run a
routing process to tell other systems on your network about your
router; FreeBSD comes with the standard BSD routing daemon routed(8),
or for more complex situations you may want to try GateD (available by
FTP from gated.Cornell.edu). FreeBSD is supported as of 3_5Alpha7.
It is our duty to warn you that, even when FreeBSD is configured in
this way, it does not completely comply with the Internet standard
requirements for routers; however, it comes close enough for ordinary
usage.
There is a standard `router floppy' that you can boot on a FreeBSD
machine to configure it as a network router. Please look in:
freefall.cdrom.com:pub/incoming/freertr
and follow the instructions.
8.3: Does FreeBSD support SLIP and PPP?
Yes. See the man pages for slattach(8) and/or pppd(8) if you're using
FreeBSD to connect to another site. If you're using FreeBSD as a
server for other machines, look at the man page for sliplogin(8).
You may also want to take a look at the slip FAQ in:
FAQ/FreeBSD.slip.dialup.faq
8.4: How do I set up NTP?
NTP configuration is so complex and widely variable from site to site
that it would be impossible to make a blanket statement here. Your
best bet is to ask whoever's in charge of NTP at your site or network
provider; chances are that they are running a similar version of NTP
to the one that we provide, and they can probably provide you with the
right configuration files to get things going.
If you can't find anyone in charge, you should examine the files in
/usr/src/contrib/xntpd/doc and see if they help any. If not, you
could ask on the comp.protocols.time.ntp newsgroup, or the
<ntp@ni.umd.edu> mailing-list.
8.5: How do I get my network set up? I don't see how to make my
/dev/ed0 device!
In the Berkeley networking framework, network interfaces are only
directly accessible by kernel code. Please see the /etc/netstart file
and the manual pages for the various network programs mentioned there
for more information. If this leaves you totally confused, then you
should pick up a book describing network administration on another
BSD-related operating system; with few significant exceptions,
administering networking on FreeBSD is basically the same as on SunOS
4.0 or Ultrix.
8.6: How do I get my 3C503 to use the other network port?
Use `ifconfig ed0' to see whether the ALTPHYS flag is set, and then
use either `ifconfig ed0 altphys' if it was off, or `ifconfig ed0
-altphys' if it was on.
8.7: I'm having problems with NFS to/from FreeBSD and my Wuffotronics
Workstation / generic NFS appliance, where should I look first?
Certain PC network cards are better than others (to put it mildly) and
can sometimes cause problems with network intensive applications like
NFS. See /usr/src/share/FAQ/NFS.FAQ for more information on this
topic.
8.8: I want to enable IP multicast support on my FreeBSD box, how do I do it?
[Alternatively: What the heck IS multicasting and what applications
make use of it?]
First off, to you'll need to rebuild a kernel with multicast support in it.
This requires that you have the sources to at least the kernel and the config
utility. See /usr/src/sys/i386/conf/LINT for its comments on multicast; you'll
need to set the MROUTING and MULTICAST options as shown there.
Further reading/exploration for those interested in multicast:
Product Description Where
--------------- ----------------------- ---------------------------------------
faq.txt Mbone FAQ ftp.isi.edu:/mbone/faq.txt
imm/immserv IMage Multicast ftp.hawaii.edu:/paccom/imm.src.tar.Z
for jpg/gif images.
nv Network Video. ftp.parc.xerox.com:
/pub/net-reseach/exp/nv3.3alpha.tar.Z
vat LBL Visual Audio Tool. ftp.ee.lbl.gov:
/conferencing/vat/i386-vat.tar.Z
wb LBL White Board. ftp.ee.lbl.gov:
/conferencing/wb/i386-wb.tar.Z
mmcc MultiMedia Conference ftp.isi.edu:
Control program /confctrl/mmcc/mmcc-intel.tar.Z
rtpqual Tools for testing the ftp.psc.edu:/pub/net_tools/rtpqual.c
quality of RTP packets.
vat_nv_record Recording tools for vat ftp.sics.se:archive/vat_nv_record.tar.Z
and nv.
[Many thanks to Jim Lowe for providing multicast support for FreeBSD, and this
information]
9 Serial Communications
-----------------------
9.1: When I do a set line in Kermit it locks up, what's the problem?
The problem here is that FreeBSD thinks it's talking to a incoming
modem connection, and is waiting for carrier to come up on it before
completing the open. To disable modem control, do an:
stty -f /dev/ttyXX clocal
(Where `ttyXX' is the tty port you're using). If you use a given port
only for outgoing connections, you may wish to put this command in
your /etc/rc.local to avoid having to do it every time you reboot your
system.
NOTE: Anyone wishing to submit a FAQ entry on how to get tip and cu working
would have it much appreciated! We all use Kermit over here! :-)
-----------------------------------------------------------------------------
If you see a problem with this FAQ, or wish to submit an entry, please
mail us at <FreeBSD-FAQ@FreeBSD.ORG>. We appreciate your
feedback, and cannot make this a better FAQ without your help!
FreeBSD Core Team
-----------------------------------------------------------------------------
ACKNOWLEDGMENTS:
Gary Clark II - Our head FreeBSD FAQ maintenance man
Jordan Hubbard - Janitorial services (I don't do windows)
Garrett Wollman - Networking and formatting
Robert Oliver, Jr. - Ideas and dumb questions (That made me think)
Ollivier Robert - Invaluable feedback and contributions
The FreeBSD Team - Kvetching, moaning, submitting data
And to any others we've forgotten, apologies and heartfelt thanks!

266
share/FAQ/FreeBSD-1.X/Systems-1.1.FAQ Normal file
View File

@ -0,0 +1,266 @@
Systems FAQ
For FreeBSD
Last Modified: $Id: Systems-1.1.FAQ,v 1.1 1994/09/16 18:24:40 gclarkii Exp $
This FAQ is a list of systems that people have sent to the FAQ maintnance
person for inclusion. If you have a system you would like to be included
please send it to FreeBSD-FAQ@freefall.cdrom.com.
Disclaimer: This document is composed of systems that people have sent to
the FAQ maintnance person. It is the not to be taken as an endorsement
for any system or manufacture.
1.
386DX/20 real AMI, ISA
Oak SVGA (no X)
8MB
Adaptec 1542B, WD1007V ESDI
Wren VI and Miniscribe 660MB 20Mbit/sec ESDI
WD 8013EBT
2.
486DX/25 clone, AMI BIOS, ISA
Orchid PCIII gas plasma (yes, VGA16)
8MB
Adaptec 1542B
Micropolis 1684 SCSI
SMC 8013EEWC
3.
??? OPTI chipset AMI BIOS 486/50 ISA
ISA ET4000 w/ X11 (not so slow)
16 Mb - 48 Mb swap
ISA aha1542 B
ISA no-name IDE w/ floppies
FUJITSU M2623S-512 405MB set to SCSI2
SEAGATE ST3283N 237MB SCSI2
SANYO CRD-400I SCSI2 cdromcdrom
4.
Lipizzan LDO-1 486DX-33 motherboard
Orchid ProIIs (1M) video
8 MB memory
Generic 2S/1P/2FD/IDE controller:
Maxtor 7213 AT
WDC AC2420H
PAS-16 + Sony CDU31A CD drive (Fusion 16 package).
*** The CD drive does not currently work with FreeBSD.
5.
Asus VL/ISA-486SV2 (ISA-VLB as you can see)
Orchid Fahrenheit 1280+ VLB (yes)
20MB
Some no-name IDE VLB controller
Conner CP30504 (I think....the 540MB IDE one)
Zoltrix 14.4/14.4 Fax/Modem on tty01
Intel 486DX2/66 CPU + fan
Conner CP30104 (120MB....for DOS)
6.
AIR 486El (running with AMD486/40)
ATI Graphics Ultra Pro running XFree862.1
16M
Adaptec 1742
Micropolis 2217
Wangtec 6130FS DAT drive (Some problems)
7.
Compudyne 486 DX2/66
ATI Local Bus GUP w/ 2megs
16 Megs Memory
504 IDE Hard Drive
Colorado 250 meg QIC-80 tape drive
8.
American Megatrends Enterprise III, 486DX2-66
ATI VLB Mach 32 (with X)
16 meg
Adaptec 1742 EISA SCSI with floppy
Toshiba 5030 SCSI-II
Toshiba 5157 SCSI-II
SMC Elite16T ISA Ethernet (ISA)
9.
American Megatrends Enterprise III, 486DX
ATI VLB Mach 32 (with X)
32 meg
Adaptec 1742 EISA SCSI with floppy
Maxtor P0-12S SCSI
Digital DSP5200S SCSI-II
Pro Audio Spectrum 16
Wonder Board, 4 serial (16550), 3 parallel, each on a different interrupt
10.
NoName 486DX/33, Intel Chipset, EISA-Bus
ATI Graphics Ultra Pro EISA,
17" Nanao (Eizo) F550-i Monitor
Running the Mach32 X-Server XFree86-2.1.1 with fonts created from source.
16 MB RAM (planning to add another 8 MB).
AHA1742A
Conner CP3100
Fujitsu 520 MB
Archive 525MB streamer tape.
Gravis UltraSound - works for mod-files.
11.
ASUS SP3 PCI Board with i486 DX/2 66 MHz
ISA ET4000 (I already tested a S3 805 PCI card successfully)
Adaptec 1542B
Toshiba XM3301TA CD-Rom
CDC Harddisk, 572 MB (I don't know the exact specs)
12.
Mylex MAE486/33 EISA Motherboard
16MB memory
Actix GE32+ S3 801 gfx
Adaptec 1742A controller
Seagate ST3160 drive
Seagate ST5120 drive
Archive Viper 150MB tape
Roland SCC-1 sound card
Gravis Ultrasound card
Longshine SMC/Novell compatable ethernet card
13.
Model: DECpc LPv 466d2
Config: Local (Motherboard) S3 801 gfx, IDE controller, PS/2 mouse, 12MB memory
14.
??? 486/DX266 EISA/VLB Motherboard
16MB memory
#9 GXE L12 VLB 3MB graphics card
Bt445S VLB disk controller
DEC DSP3105S drive
MAXSTOR P-17S drive
Tandberg 525MB tape drive
Toshiba XM3301 CDROM
Soundblaster 2.0
Longshine SMC/Novell compatable ethernet card
15.
M407 PC chips with 33Mhz 486.
Had to disable external cache due to DMA problems. Board uses write-through
cache unless a second chip is added to allow write-back.write-back.
Orchid ProDesigner II (yes)
16Mb
IDE
Maxtor 7213 AT and Maxtor 7120 AT
2 BICC Isolans (Lance based cards)
16.
Gigabyte EISA/VLB motherboard with SIS chipset, AMI bios, 32 MB ram
Adaptec 1742 SCSI 2 controller with floppy controller enabled
Spea/V7 Mirage - S3/805 based localbus graphics card with 1 MB d-ram
no name wd8013 compatible ethernet card
Gravis Ultrasound card with 1 MB ram
2 Fujitsu 400 MB and 1 Seagate 500 MB SCSI 2 harddisks
5 1/4 + 3 1/2 inch floppy drives
Tandberg TDC3600 60 MB + Tandberg TDC3800 525 MB Streamer (these don't work
quite properly yet)
17.
i486DX33, 16 Mb RAM, 256 Kb external cache, VLB board
no-name IDE/floppy controller
Western Digital Caviar 2340 (325 Mb)
Kalok KL-343 (40 Mb)
Chips & Technologies 451 SuperVGA card (800x600, 16 colours, 256Kb)
18.
no name EISA i486DX/33 board, 16 MB RAM
Adaptec AHA-1540*A* (not knowing if the current -current might cause
problems, my kernel is from end of march)
Maxtor MXT-1240S, 1.2Gig very fast SCSI disk
Seagate ST-1144A, just to boot off the beast (also has a messdos partition yet)
Archive Viper 150 tape; has a firmware braindeadness when appending files,
works very well otherwise
ELSA Winner 1000 ISA/EISA, 1MB VRAM, S3 86C928 (unfortunately, D-step chip)
Nokia 447-B 17in monitor, running ~ 1100x800 resolution, very nice
true `Mouse Systems' optical mouse, fine thing!
sometimes a Toshiba XM-3301 CDROM, rather old, but solid & reliable
19.
older south-east Asia made notebook, i386SX/16, 5 MB RAM (where the 384 k hole
can be re-mapped, so all the 5 MB are useable)
Seagate ST-9145AG, 120 MB 2.5in IDE disk, very low power consumption, but
rather slow transfer rate, only about 350 K/s, so paging is a mess
640x480 LCD, ~ 16 gray tones distinguishable, Cirrus Logic CL-GD610/620
chipset; runs generic VGA-Mono and VGA-16 XFree86[tm] servers; needs
some hacks in rc.local to give full contrast when running with the
pcvt display driver (due to their different default attribute handling)
20.
Data General Dasher 386sx/16, 8 MB RAM
Adaptec AHA-1542B
Seagate ST-3655N, 525 MB SCSI disk
Conner CP-3044, 40 MB IDE disk
has been working with a Western Digital WD-1007V ESDI controller (on
secondary wdc address), and a Micropolis 1664-7 330 MB ESDI disk -
but this beast was terribly slow, loud (& unreliable) and therefore
had to go
ET-3000 based 512 K VGA, slow (wrt. XFree86), but reliable
3Com 3C503 Ethernet adaptor, suffers from the `do not nfs mount with
too large packets' problem, but works well otherwise
`Mouse Systems' optical mouse
Toshiba XM-3301 CDROM
already ran with a Micropolis 1664-3 330 MB SCSI disk (same drive as
above, but different interface)
already ran with an IBM 2Gig SCSI disk (don't remember the type)
21.
Mylex MNA 486/33 EISA Motherboard
16Mb of Memory
1.2 GB Toshiba 538 SCSI disk
400Mb IBM SCSI disk
150/250Mb Tandberg SCSI tape drive
Toshiba 3401 SCSI CD-ROM
Tseng 4000 Video Controller
Logitech Bus Mouse
Mediavision Pro Audio Stereo Sound Card
Adaptech 1742A SCSI controller
WD8013EBT Ethernet Card
22.
386DX-40 w/Cyrix math co-processor
ET-4000 running X
16MB
IDE
540MB Western Digital
WD8003EP

265
share/FAQ/diskspace.FAQ Normal file
View File

@ -0,0 +1,265 @@
How to assign disk space to FreeBSD.
1.0 Getting started.
---------------------
After a general introduction, you will find some explanation on what you
need to do to assign space to FreeBSD on your disk(s). This is done
through the "sysinstall" program, which lives on the inital boot floppy.
Those already expert with PCs may wish to skip ahead to section 1.2, the
rest of you may (or may not) enjoy the brief history lesson.
1.1 The ins and outs of allocating disk storage on your PC.
------------------------------------------------------------
Modern hard disk drives are now getting big enough that people don't want
to allocate all of one to just one operating system anymore, especially
given the increasing size of disk drives (the latest 9.0 Gbyte models
holding the equivalent of some six thousand 1.44MB floppies!) and the
virtual explosion of operating system options available for the PC. To
solve this problem, IBM came up with a scheme for "slicing" the disks
into more manageable chunks, or partitions. It works, but only just.
To better understand why, first a brief bit of history:
MS-DOS, when hard disk support was unceremoniously grafted on back in the
late eighties, didn't have such "slices". What it had was a way to install
Xenix and MS-DOS on the same disk (Remember when Microsoft were in the UNIX
business?).
In the first sector on the disk was a piece of "primary boot code" and a
table with four entries. Each of those entries pointed at an arbitrary
slice of the disk, with one of them was marked "active". The machine would
boot by reading the first sector containing the boot code into RAM and then
jumping to it. The job of this small piece of boot code was to look at
the 4 entry table and decide which OS was to be booted by looking
for the "active" flag. It would go and load the first sector of that slice
of the disk into RAM and then and jump to it in turn. This bit of boot
code was called the "secondary boot", and could be specific to a given
operating system. The primary boot code and 4-entry table is known
as the Master Boot Record, or MBR, and is very important to the proper
operation of your PC! We will discuss the MBR in more detail later.
It was later realized, with the hindsight that IBM is famous for, that disks
could be bigger than the 32Mb that the early DOS FAT-12 file system could
handle, so they added a kludge: They had two MSDOS slices, a "Primary" and
a "Secondary". The primary could still only be 32Mb, but the Secondary had
no size limit. And the trick was that the secondary had ANOTHER "table
entry" so that now suddenly up to 5 slices could be available to MS-DOS.
The Secondary boot record was later made recursive, thus effectively
avoiding any fixed limit. Of course, they were still stuck with a maximum
of 26 slices given the use of "drive letters" in DOS. They also reserved
only 10 bits for cylinder addressing, limiting DOS to being able to address
a maximum of 1024 cylinders (and cause of the dreaded "cylinder translation"
kludges, the misconfiguration of which many users have seen as the notorious
"Missing Operating System" message). Yes, truly DOS was and is an utterly
terrible operating system, which of course explains its amazing degree of
success. Anyway, this all brings us up to today, which is where FreeBSD
comes in:
1.2 What FreeBSD does
----------------------
FreeBSD has, like any other UNIX-like operating system, the concept of
"partitions." Partitions are used to implement its own "slicing"
abstraction, and although there is no real difference between a slice and a
partition as such, we use the two words to distinguish between these two
different levels of slicing.
The result is that we have a two-tier structure on the disk:
+-----------+
| MBR-table |
+-----------+ +---------+
| Slice 1 | -----> | MSDOS |
+-----------+ +---------+
| Slice 2 |
+-----------+ +-------------------+
| Slice 3 | -----> | FreeBSD-disklabel |
+-----------+ +-------------------+ +-----------------+
| Slice 4 | | Partition A | -----> | Root-filesystem |
+-----------+ +-------------------+ +-----------------+
| Partition B | ---
+-------------------+ \ +----------------+
| Partition C | --> | swap-partition |
+-------------------+ +----------------+
| ... |
Here are the rules that FreeBSD plays by:
A: FreeBSD always has an MBR slice with type 0xa5 (each of the 4 slices can
also have a unique integer identifier so you can tell your DOS slices
from your FreeBSD slices from your Linux slices, etc). This means that
there should always be an MBR record, even in the case where FreeBSD
occupies the entire disk.
B: The FreeBSD slice contains the FreeBSD disklabel in the second sector
(remember, the first sector contains the secondary boot code for FreeBSD,
which is what prints that FreeBSD prompt at you when you first boot
FreeBSD from a floppy or hard disk).
C: The 'C' partition in the FreeBSD disklabel corresponds to the entire
FreeBSD slice.
D: The 'D' partition corresponds to the entire physical disk.
E: Should a disk not have a FreeBSD slice (because there simply is no
FreeBSD on it anywhere), then the MBR slices are mapped into partitions
'E' to 'H' of an artificially created FreeBSD disklabel. This is useful
for getting at DOS-only disks.
Therefore, to get FreeBSD onto your disk, you need to do the following:
Step FreeBSD utility
------------------------------------------------------------ ---------------
1. Make an MBR slice for FreeBSD (FDISK)
2. Partition the diskspace in the MBR slice into partitions (DISKLABEL)
3. Assign mountpoints to the partitions. (DISKLABEL)
2. The sysinstall utility
--------------------------
The sysinstall utility is the program you first see when you boot
FreeBSD's install floppy. It is responsible for partitioning your
disk, creating an MBR slice for FreeBSD, setting up the disklabel
within that slice and creating filesystems for each FreeBSD partition
you create within that slice. It is composed of a number of screens.
These are described below.
2.1 The main screen
--------------------
The main screen shows you the current status, It shows you which disks
FreeBSD has found, how big they are and how much of it is assigned to
FreeBSD in a FreeBSD MBR slice. It also shows the partitions which have
had a mountpoint assigned to them (not necessarily FreeBSD partitions;
FreeBSD is perfectly capable of mounting DOS disks directly).
(H)elp -- shows you this file.
(F)disk -- enters the Fdisk editor, where you can change the MBR record.
This is what you want to use to assign some part of the disk to FreeBSD.
(D)isklabel -- enters the Disklabel editor, here you can change how the
FreeBSD slice is partitioned for FreeBSD.
(P)rocede -- will continue the installation process.
(Q)uit -- Go back to the entry screen.
2.2 FDISK - how to make an MBR slice
-------------------------------------
There are some rules to follow here since altering your MBR is a potential
minefield. There is really no way for the sysinstall program to genuinely
know that you have a valid MBR, so you have to be extra careful in what
you edit. Failure to do this properly can and will destroy your other
operating system entries!
Even if you don't plan to have MSDOS on a disk, make an MSDOS slice
using the MSDOS's FDISK.COM program. The reason for this is that if you
do it that way, you are 100% sure that FreeBSD will use the same number
of heads, sectors and cylinders as MSDOS would use. If you really don't
plan to have MSDOS on the disk, just (D)elete the slice in the FreeBSD's
(F)disk editor.
From the main screen press 'F' to enter the MBR editor. You have five
commands available:
(H)elp -- Shows you this file.
(D)elete -- Deletes a slice entirely.
(E)dit -- Allows you to edit a slice. It will ask how many megabytes
you want to assign to the slice, and will suggest the maximum possible
as a default. It might say zero, even though there is disk space
available, in which case you will probably need to delete and recreate the
other partitions to get it to see where the free space is.
It will then ask you what type to give the slice, for which the default is
0xa5 (a FreeBSD slice). You can enter any other number here too, which
can be useful as a placeholder for some other OS you plan to install
later. Finally, it will ask you about the "boot flag". 0x80 means "boot
from this" slice by default, and anything else means "don't".
If you specified a FreeBSD slice, any existing slices with the 0xa5
type will be reset to 0x00 "unused". FreeBSD only supports one slice
per disk for FreeBSD.
(R)eread -- This is your "undo" function. It will read the data of the
disk again, disposing of any changes you may have made.
(W)rite -- When you are satisfied with the data, this function will write
the new MBR to the disk.
(Q)uit -- Go back to the main screen.
2.3 Disklabel - How to divide up the FreeBSD slice.
----------------------------------------------------
The disklabel screen provides the following commands:
(H)elp -- Shows you this file.
(S)ize -- Resizes a partition for you, it will suggest as a default the
maximum amount of diskspace it can find. This algorithm isn't too smart
and may say zero, even though there is diskspace available. If it
does, delete and resize the other partitions.
(A)ssign -- Here you assign where the filesystem in a partition is to
be mounted. `b' partitions will always be made into "swap" partitions.
(D)elete -- Delete a partition.
(R)eread -- The undo function. It will reread the current disklabel from
the kernel.
(W)rite -- This will write the disklabel to the disk. You must always write
before you quit, otherwise your changes will be lost.
(Q)uit -- Exit back to the main screen.
2.4. Hints on partition sizing
-------------------------------
While it's impossible to say how much space you're going to want to
make your various partitions without knowing more about your intended
applicatins, here are some good rules of thumb to follow:
1. Root (/) should be at least 18MB, and probably no more than 50MB unless
you have some special reason for making your root partition really
large. Remember that the root filesystem is only supposed to contain
vital system files and little else.
2. Swap should be at least 2*memory. That is to say if you have 8MB of
memory, then you probably want 16MB of swap. Even more swap space
certainly doesn't hurt, if you can afford to allocate it, and you should
also think ahead a little to any planned memory upgrades you may have
in mind since increasing this later can be very painful!
If you're going to run the X Window System (XFree86), you should also
consider having a *minimum* of 16MB of swap, since X tends to really
use it up.
3. /usr can take up the rest of your disk, though some people like to create
extra partitions for user home directories and the like. Be sure to make
your /usr big enough to contain the system software (about 50MB) and
perhaps some of your own, unless you're going to use symbolic links to
point things like /usr/local (or /usr/src) somewhere else.
Here are some suggested filesystem names and sizes, just for reference:
Mountpoint Filesystem size
-------------------------------
/var 10Mb
/usr 50Mb
/ 16Mb
/usr/src 120Mb If you want to have the sources online
/usr/obj 100Mb If you want to compile all of them at one time
/usr/X11R6 50Mb If you load the entire XFree86 binary kit.
$Id: DISKSPACE.FAQ,v 1.7 1994/11/21 01:30:03 jkh Exp $

7
share/FAQ/extras/ports-supfile Normal file
View File

@ -0,0 +1,7 @@
ports-editors release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-lang release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-mail release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-net release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-shells release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-utils release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old
ports-x11 release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/ports delete old

14
share/FAQ/extras/standard-supfile Normal file
View File

@ -0,0 +1,14 @@
base release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
bin release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
etc release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
games release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
gnu release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
include release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
sys release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
lib release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
libexec release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
sbin release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
#secure release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
share release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
usrbin release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old
usrsbin release=current host=FreeBSD.ORG hostbase=/home base=/usr prefix=/usr/src delete old

77
share/FAQ/nfs.FAQ Normal file
View File

@ -0,0 +1,77 @@
FreeBSD and NFS [for a FAQ]
Certain Ethernet adapters for ISA PC systems have limitations which
can lead to serious network problems, particularly with NFS. This
difficulty is not specific to FreeBSD, but FreeBSD systems are affected
by it.
The problem nearly always occurs when (FreeBSD) PC systems are networked
with high-performance workstations, such as those made by Silicon Graphics,
Inc., and Sun Microsystems, Inc. The NFS mount will work fine, and some
operations may succeed, but suddenly the server will seem to become
unresponsive to the client, even though requests to and from other systems
continue to be processed. This happens to the client system, whether the
client is the FreeBSD system or the workstation. On many systems, there is
no way to shut down the client gracefully once this problem has manifested
itself. The only solution is often to reset the client, because the NFS
situation cannot be resolved.
Though the "correct" solution is to get a higher performance and capacity
Ethernet adapter for the FreeBSD system, there is a simple workaround that
will allow satisfactory operation. If the FreeBSD system is the SERVER,
include the option "wsize=1024" on the mount from the client. If the
FreeBSD system is the CLIENT, then mount the NFS file system with the
option "rsize=1024". These options may be specified using the fourth
field of the fstab entry on the client for automatic mounts, or by using
the "-o" parameter of the mount command for manual mounts.
In the following examples, "fastws" is the host (interface) name of a
high-performance workstation, and "freebox" is the host (interface) name of
a FreeBSD system with a lower-performance Ethernet adapter. Also,
"/sharedfs" will be the exported NFS filesystem (see "man exports"), and
"/project" will be the mount point on the client for the exported file
system. In all cases, note that additional options, such as "hard" or
"soft" and "bg" may be desireable in your application.
Examples for the FreeBSD system ("freebox") as the client:
in /etc/fstab on freebox:
fastws:/sharedfs /project nfs rw,rsize=1024 0 0
as a manual mount command on freebox:
mount -t nfs -o rsize=1024 fastws:/sharedfs /project
Examples for the FreeBSD system as the server:
in /etc/fstab on fastws:
freebox:/sharedfs /project nfs rw,wsize=1024 0 0
as a manual mount command on fastws:
mount -t nfs -o wsize=1024 freebox:/sharedfs /project
Nearly any 16-bit Ethernet adapter will allow operation without the above
restrictions on the read or write size.
For anyone who cares, here is what happens when the failure occurs, which
also explains why it is unrecoverable. NFS typically works with a "block"
size of 8k (though it may do fragments of smaller sizes). Since the maximum
Ethernet packet is around 1500 bytes, the NFS "block" gets split into
multiple Ethernet packets, even though it is still a single unit to the
upper-level code, and must be received, assembled, and ACKNOWLEDGED as a
unit. The high-performance workstations can pump out the packets which
comprise the NFS unit one right after the other, just as close together as
the standard allows. On the smaller, lower capacity cards, the later
packets overrun the earlier packets of the same unit before they can be
transferred to the host and the unit as a whole cannot be reconstructed or
acknowledged. As a result, the workstation will time out and try again,
but it will try again with the entire 8K unit, and the process will be
repeated, ad infinitum.
By keeping the unit size below the Ethernet packet size limitation, we
ensure that any complete Ethernet packet received can be acknowledged
individually, avoiding the deadlock situation.
Overruns may still occur when a high-performance workstations is slamming
data out to a PC system, but with the better cards, such overruns are
not guarranteed on NFS "units". When an overrun occurs, the units affected
will be retransmitted, and there will be a fair chance that they will be
received, assembled, and acknowledged.
--
John Lind, Starfire Consulting Services
E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417

368
share/FAQ/ppp.FAQ Executable file
View File

@ -0,0 +1,368 @@
Info about setting up pppd daemon on FreeBSD-2.0
Before you start setting up PPP on your machine make
sure that pppd is located in /usr/sbin and directory /etc/ppp
exists.
pppd can work in two modes:
i) as a "client" , i.e. you want to connect your machine to outside
world via PPP serial connection or modem line.
ii) as a "server" , i.e. your machine is located on the network and
used to connect other computers using PPP.
In both cases you will need to set up an options file ( /etc/ppp/options
or ~/.ppprc if you have more then one user on your machine that uses
PPP ).
You also will need some modem/serial software ( preferably kermit )
so you can dial and establish connection with remote host.
1) Working as a PPP client
I used the following options to connect to CISCO terminal server PPP
line.
----/etc/ppp/options-------
crtscts # enable hardware flow control
modem # modem control line
noipdefault # remote PPP server must supply your IP address.
# if the remote host doesn't send your IP during IPCP
# negotiation , remove this option
passive # wait for LCP packets
domain ppp.foo.com # put your domain name here
:<remote_ip> # put the IP of remote PPP host here
# it will be used to route packets via PPP link
# if you didn't specified the noipdefault option
# change this line to <local_ip>:<remote_ip>
defaultroute # put this if you want that PPP server will be your
# default router
-------------------------
To connect:
i) Dial to the remote host using kermit ( or other modem program )
enter your user name and password ( or whatever is needed to enable PPP
ont the remote host )
ii) Exit kermit. ( without hanging up the line )
iii) enter:
/usr/src/usr.sbin/pppd.new/pppd /dev/tty01 19200
( put the appropriate speed and device name )
Now your computer is connected with PPP. If the connection fails for some
reasons you can add the "debug" option to the /etc/ppp/options file
and check messages on the console to track the problem
Following script will make all 3 stages automatically:
-----/etc/ppp/pppup--------
#!/bin/sh
ps ax |grep pppd |grep -v grep
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing pppd, PID=' ${pid}
kill ${pid}
fi
ps ax |grep kermit |grep -v grep
pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing kermit, PID=' ${pid}
kill -9 ${pid}
fi
ifconfig ppp0 down
ifconfig ppp0 delete
kermit -y /etc/ppp/kermit.dial
pppd /dev/tty01 19200
-----------------------------
/etc/ppp/kermit.dial is kermit script that dials and makes all
necessary authorization on the remote host.
( Example of such script is attached to the end of this document )
Use the follwing script to disconnect the PPP line:
-----/etc/ppp/pppdown--------
#!/bin/sh
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
if [ X${pid} != "X" ] ; then
echo 'killing pppd, PID=' ${pid}
kill -TERM ${pid}
fi
ps ax |grep kermit |grep -v grep
pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing kermit, PID=' ${pid}
kill -9 ${pid}
fi
/sbin/ifconfig ppp0 down
/sbin/ifconfig ppp0 delete
kermit -y /etc/ppp/kermit.hup
/etc/ppp/ppptest
------------------------------
Check if PPP is still running:
-----/etc/ppp/ppptest---------
#!/bin/sh
pid=`ps ax| grep pppd |grep -v grep|awk '{print $1;}'`
if [ X${pid} != "X" ] ; then
echo 'pppd running: PID=' ${pid-NONE}
else
echo 'No pppd running.'
fi
set -x
netstat -n -I ppp0
ifconfig ppp0
-----------------------------
Hangs up modem line:
-----/etc/ppp/kermit.hup-----
set line /dev/tty01 ; put your modem device here
set speed 19200
set file type binary
set file names literal
set win 8
set rec pack 1024
set send pack 1024
set block 3
set term bytesize 8
set command bytesize 8
set flow none
pau 1
out +++
inp 5 OK
out ATH0\13
echo \13
exit
----------------------------
2) Working as a PPP server
------/etc/ppp/options------
crtscts # Hardware flow control
netmask 255.255.255.0 # netmask ( not required )
192.114.208.20:192.114.208.165 # ip's of local and remote hosts
# local ip must be different from one
# you assigned to the ethernet ( or other )
# interface on your machine.
# remote IP is ip address that will be
# assigned to the remote machine
domain ppp.foo.com # your domain
passive # wait for LCP
modem # modem line
----------------------------
Following script will enable ppp server on your machine
-----/etc/ppp/pppserv-------
#!/bin/sh
ps ax |grep pppd |grep -v grep
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing pppd, PID=' ${pid}
kill ${pid}
fi
ps ax |grep kermit |grep -v grep
pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing kermit, PID=' ${pid}
kill -9 ${pid}
fi
# reset ppp interface
ifconfig ppp0 down
ifconfig ppp0 delete
# enable autoanswer mode
kermit -y /etc/ppp/kermit.ans
# run ppp
pppd /dev/tty01 19200
----------------------------
Use this script to stop ppp server:
-----/etc/ppp/pppservdown---
#!/bin/sh
ps ax |grep pppd |grep -v grep
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing pppd, PID=' ${pid}
kill ${pid}
fi
ps ax |grep kermit |grep -v grep
pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
if [ "X${pid}" != "X" ] ; then
echo 'killing kermit, PID=' ${pid}
kill -9 ${pid}
fi
ifconfig ppp0 down
ifconfig ppp0 delete
kermit -y /etc/ppp/kermit.noans
----------------------------
Following kermit script will enable/disable autoanswer mode
on your modem:
-----/etc/ppp/kermit.ans----
set line /dev/tty01
set speed 19200
set file type binary
set file names literal
set win 8
set rec pack 1024
set send pack 1024
set block 3
set term bytesize 8
set command bytesize 8
set flow none
pau 1
out +++
inp 5 OK
out ATH0\13
inp 5 OK
echo \13
out ATS0=1\13 ; change this to out ATS0=0\13 if you want to disable
; autoanswer mod
inp 5 OK
echo \13
exit
-----------------------------
This script is used for dialing and authorizing on remote host.
You will need to customize it for your needs.
Put your login and password in this script , also you'll need
to change input statement depending on responces from your modem
and remote host.
-----/etc/ppp/kermit.dial----
;
; put the com line attached to the modem here:
;
set line /dev/tty01
;
; put the modem speed here:
;
set speed 19200
set file type binary ; full 8 bit file xfer
set file names literal
set win 8
set rec pack 1024
set send pack 1024
set block 3
set term bytesize 8
set command bytesize 8
set flow none
set modem hayes
set dial hangup off
set carrier auto ; Then SET CARRIER if necessary,
set dial display on ; Then SET DIAL if necessary,
set input echo on
set input timeout proceed
set input case ignore
def \%x 0 ; login prompt counter
goto slhup
:slcmd ; put the modem in command mode
echo Put the modem in command mode.
clear ; Clear unread characters from input buffer
pause 1
output +++ ; hayes escape sequence
input 1 OK\13\10 ; wait for OK
if success goto slhup
output \13
pause 1
output at\13
input 1 OK\13\10
if fail goto slcmd ; if modem doesn't answer OK, try again
:slhup ; hang up the phone
clear ; Clear unread characters from input buffer
pause 1
echo Hanging up the phone.
output ath0\13 ; hayes command for on hook
input 2 OK\13\10
if fail goto slcmd ; if no OK answer, put modem in command mode
:sldial ; dial the number
pause 1
echo Dialing.
output atdt9,550311\13\10 ; put phone number here
assign \%x 0 ; zero the time counter
:look
clear ; Clear unread characters from input buffer
increment \%x ; Count the seconds
input 1 {CONNECT }
if success goto sllogin
reinput 1 {NO CARRIER\13\10}
if success goto sldial
reinput 1 {NO DIALTONE\13\10}
if success goto slnodial
reinput 1 {\255}
if success goto slhup
reinput 1 {\127}
if success goto slhup
if < \%x 60 goto look
else goto slhup
:sllogin ; login
assign \%x 0 ; zero the time counter
pause 1
echo Looking for login prompt.
:slloop
increment \%x ; Count the seconds
clear ; Clear unread characters from input buffer
output \13
;
; put your expected login prompt here:
;
input 1 {Username: }
if success goto sluid
reinput 1 {\255}
if success goto slhup
reinput 1 {\127}
if success goto slhup
if < \%x 10 goto slloop ; try 10 times to get a login prompt
else goto slhup ; hang up and start again if 10 failures
:sluid
;
; put your userid here:
;
output ppp-login\13
input 1 {Password: }
;
; put your password here:
;
output ppp-password\13
input 1 {Entering SLIP mode.}
echo
quit
:slnodial
echo \7No dialtone. Check the telephone line!\7
exit 1
; local variables:
; mode: csh
; comment-start: "; "
; comment-start-skip: "; "
; end:
------------------------
###################################################################
Gennady B. Sorokopud ( gena@NetVision.net.il ) 24/10/94 12:00

190
share/FAQ/slip.FAQ Normal file
View File

@ -0,0 +1,190 @@
***********************************************************************
*** How to Set Up SLIP on FreeBSD ***
***********************************************************************
Updated for 1.1.5(.1) support by Satoshi Asami, 8/6/94.
The following is I (asami) set up my FreeBSD machine for SLIP on a
static host network. For dynamic hostname assignments (i.e., your
address changes each time you dial up), you probably need to do
something much fancier.
This is just "what I did, and it worked for me". I'm sharing this
just for your reference, I'm no expert in SLIP nor networking so your
mileage may vary.
Note: for 1.1 systems (not 1.1.5), you need to use /dev/tty01 instead
of /dev/cua01. substitute all the occurences of "cua" in this document
with "tty".
Note: the default 1.1.5(.1) system only comes with cua/ttyd pairs for
the last two ports (2 and 3), so if your modem is at sio0/sio1
(COM1/COM2), you need to make the devices. Try "cd /dev; sh MAKEDEV
cua01" to make the new special files for sio1 (ditto for sio0). This
will delete tty01, but you shouldn't need it anymore...or you can make
a symbolic link /dev/tty01 -> ttyd1 if you don't want to hunt down all
occurences of tty01 in your setup files.
I actually have a symbolic link /dev/modem -> cua01 (and /dev/mouse ->
ttyd0). I use only the modem/mouse names in my configuration files.
This helped a lot when I switched from 1.1 to 1.1.5.1 (tty01 => cua01)
and when I had to move my modem temporarily to sio2 to enable the
RS-232C port on the serial card. It can become quite cumbersome when
you need to fix a bunch of files in /etc and .kermrc's all over the
system!
First, make sure you have
pseudo-device sl 2
in your kernel's config file. It is included in the GENERIC, GENERICAH
and GENERICBT kernels, so this won't be a problem unless you deleted it.
Things you have to do only once:
(1) Add your home machine, the gateway and nameservers to your
/etc/hosts file. Mine looks like this:
127.0.0.1 localhost loghost
136.152.64.181 silvia.HIP.Berkeley.EDU silvia.HIP silvia
136.152.64.1 inr-3.Berkeley.EDU inr-3 slip-gateway
128.32.136.9 ns1.Berkeley.edu ns1
128.32.136.12 ns2.Berkeley.edu ns2
By the way, silvia is the name of the car that I had when I was
back in Japan (it's called 2?0SX here in U.S.).
(2) Make sure you have "hosts" before "bind" in your /etc/host.conf.
Otherwise, funny things may happen.
(3) Edit the /etc/netstart and add this to the end of the file:
# set up slip
gateway=slip-gateway
ifconfig sl0 inet $hostname $gateway netmask 0xffffff00
route add default $gateway
Note that because of the "slip-gateway" entry in /etc/hosts, there
is no local dependency in the netstart file. Also, you might want
to un-comment the "route add $hostname localhost" line.
(3') Make a file /etc/resolv.conf which contains:
domain HIP.Berkeley.EDU
nameserver 128.32.136.9
nameserver 128.32.136.12
As you can see, these set up the nameserver hosts. Of course, the
actual addresses depend on your environment.
(4) Set the password for root and toor (and any other accounts that
doesn't have a password). Use passwd, don't edit the passwd or
passwd.master files!
(5) Edit /etc/myname and reboot the machine.
How to set up the connection:
(6) Dial up, type "slip" at the prompt, enter your machine name and
password. The things you need to enter depends on your
environment. I use kermit, with a script like this:
# kermit setup
set modem hayes
set line /dev/cua01
set speed 57600
set parity none
set flow rts/cts
set terminal bytesize 8
set file type binary
# The next macro will dial up and login
define slip dial 643-9600, input 10 =>, if failure stop, -
output slip\x0d, input 10 Username:, if failure stop, -
output silvia\x0d, input 10 Password:, if failure stop, -
output ***\x0d, echo \x0aCONNECTED\x0a
(of course, you have to change the hostname and password to fit
yours). Then you can just type "slip" from the kermit prompt to
get connected.
Note: leaving your password in plain text anywhere in the
filesystem is generally a BAD idea. Do it at your own risk. I'm
just too lazy.
Note: If you have an 1.1 machine, and kermit doesn't give you a
prompt, try "stty -f /dev/tty01 clocal". I put this in
/etc/rc.local so that it works the first time I boot the machine.
This doesn't apply to 1.1.5(.1) systems, as cua0? are already
configured for dialouts.
(7) Leave the kermit there (you can suspend it by "z") and as root,
type
slattach -h -c -s 57600 /dev/cua01
if you are able to "ping" hosts on campus, you are connected!
If it doesn't work, you might want to try "-a" instead of "-c".
(8) Happy slipping!
How to shutdown the connection:
(9) Type "ps gx" (as root) to find out the PID of slattach, and use
"kill -INT" to kill it.
Then go back to kermit ("fg" if you suspended it) and exit from it
("q").
The slattach man page says you have to use "ifconfig sl0 down" to
mark the interface down, but this doesn't seem to make any
difference for me. ("ifconfig sl0" reports the same thing.)
Some times, your modem might refuse to drop the carrier (mine
often does). In that case, simply start kermit and quit it again.
It usually goes out on the second try.
When you want to connect again, go back to (6). You may have to
watch out for clocal mode. If "stty -f /dev/tty01" doesn't tell
you it's clocal, you need to re-set it before kermitting. Again,
this is only for 1.1 machines.
TROUBLESHOOTING:
If it doesn't work, feel free to ask me. The things that people
tripped over so far:
* Not using "-c" or "-a" in slattach (I have no idea why this can be
fatal, but adding this flag solved the problem for at least one
person)
* Using "s10" instead of "sl0" (might be hard to see the difference on
some fonts :)
Try "ifconfig sl0" to see your interface status. I get:
silvia# ifconfig sl0
sl0: flags=10<POINTOPOINT>
inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00
Also, "netstat -r" will give the routing table, in case you get the
"no route to host" messages from ping. Mine looks like:
silvia# netstat -r
Routing tables
Destination Gateway Flags Refs Use IfaceMTU Rtt
Netmasks:
(root node)
(root node)
Route Tree for Protocol Family inet:
(root node) =>
default inr-3.Berkeley.EDU UG 8 224515 sl0 - -
localhost.Berkel localhost.Berkeley UH 5 42127 lo0 - 0.438
inr-3.Berkeley.E silvia.HIP.Berkele UH 1 0 sl0 - -
silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
(root node)
(this is after transferring a bunch of files, your numbers should be
smaller).

59
share/FAQ/systems.FAQ Normal file
View File

@ -0,0 +1,59 @@
Systems FAQ
for FreeBSD 2.0
This FAQ lists systems (and componets) known to work with FreeBSD 2.0. None
of these lists should be seen as a recomandation for a manufacture.
Revision: $Id: Systems.FAQ,v 1.6 1994/12/05 08:02:15 gclarkii Exp $
i386:
Motherboard: Magitronics 386DX-40
CPU: i386DX-40
Busses: ISA and VLB (VLB not tested)
Ram: 20 Megs
Video: Generic 1MB Tseng 4000 (ISA)
Disks:
2 - Segate ST1126 (SCSI)
1 - Seagate ST1480 (SCSI)
1 - Toshiba MK-234FC-C (IDE)
Controllers:
Generic IDE
Adaptec AH-1542CF
Motherboard: Magitronics 386SX-40
CPU: i386SX-40
Busses: ISA
Ram: 4 Megs
Video: Monochrome
Disks:
1-Seagate ST1126 (SCSI)
Controllers:
Future Domain 850
Notes: Slow but useable
i486:
Motherboard: Gateway 2000 Handbook 486 HB486DX2-40
CPU: i486SL DX2/40
BUS(S): PCMCIA, one type II
Video Card: Monochrome VGA.
Are you running X on this?: no, havn't really tried.
Types of Disks (manufacture and bus): 130Mb builtin. <Areal A130 U>
If you wish to be credited: Poul-Henning Kamp phk@freefall.cdrom.com
NOTES:
This is a 3 pound portable. Runs perfect. Suspend works great. Has one
serial and one parallel/floppy port, which can drive either a floppy or
a parallel port, but not at the same time. Builtin "EZ" mouse-thinge.
Highly recommended for people on the road.
Credits:
FreeBSD Core Team
Gary Clark II
Poul-Henning Kamp