diff --git a/share/doc/handbook/booting.sgml b/share/doc/handbook/booting.sgml index 105c36268ed6..c75acf7e37db 100644 --- a/share/doc/handbook/booting.sgml +++ b/share/doc/handbook/booting.sgml @@ -3,7 +3,7 @@ This conversion has been made by Ollivier Robert. - $Id: booting.sgml,v 1.3 1995/06/14 18:38:50 jfieber Exp $ + $Id: booting.sgml,v 1.4 1995/06/30 17:37:31 jfieber Exp $ @@ -30,28 +30,25 @@ determine the root filesystem and initialize user-land things. This leads to some interesting possibilities shown below. - Loading a kernel + Loading a kernel

- We presently have three basic mechanisms for loading the kernel: - - biosboot - dosboot - netboot - - Each will be described in detail below. They all pass some + We presently have three basic mechanisms for loading the + kernel as described below: + They all pass some information to the kernel to help the kernel decide what to do next. - Biosboot -

+ + Biosboot + Biosboot is our ``bootblocks'', it consists of two files, which will be installed in the first 8Kbytes of the floppy or hard-disk slice to be booted from. Biosboot can load a kernel from a FreeBSD filesystem. - Dosboot -

+ Dosboot + Dosboot was written by DI. Christian Gusenbauer, and is unfortunately at this time one of the few pieces of code that isn't compilable under FreeBSD itself because it is written for @@ -63,53 +60,51 @@ high memory on MS/DOS systems and usually wins them for it's case. - Netboot -

+ Netboot + Netboot will try to find a supported ethernet card, and use BOOTP, TFTP and NFS to find a kernel file to boot. + - Determine the root filesystem + + Determine the root filesystem

Once the kernel is loaded and the boot-code jumps to it, the kernel will initialize itself, trying to determine what hardware is present and so on, and then it needs to find a root filesystem. Presently we support the following types of rootfilesystems: - - UFS - MSDOS - MFS - CD9660 - NFS - - UFS -

+ + UFS + This is the most normal type of root filesystem. It can reside on a floppy or on harddisk. - MSDOS -

+ MSDOS + While this is technically possible, it isn't particular useful, because of ``FAT'' filesystems inability to make links, device nodes and such ``UNIXisms''. - MFS -

+ MFS + This is actually a UFS filesystem which has been compiled into the kernel. That means that the kernel does not really need any disks/floppies or other HW to function. - CD9660 -

+ CD9660 + This is for using a CD-ROM as root filesystem. - NFS -

+ NFS + This is for using a fileserver as root filesystem, basically making it a diskless machine. + - Initialize user-land things + + Initialize user-land things

To get the user-land going, when the kernel has finished initialization, it will create a with ``Interesting combinations + Interesting combinations

Boot a kernel with a MFS in it with a special /sbin/init which... diff --git a/share/doc/handbook/contrib.sgml b/share/doc/handbook/contrib.sgml index 036ae2c3ec27..847ad7d9a224 100644 --- a/share/doc/handbook/contrib.sgml +++ b/share/doc/handbook/contrib.sgml @@ -1,9 +1,9 @@ - + -FreeBSD contributor list

This software was originally derived from William F. Jolitz's 386BSD release 0.1, though almost none of the @@ -21,7 +21,7 @@ BSD based operating systems on people's computers! We wish the NetBSD group every success in their endevors. - Hardware contributors + Hardware contributors

A special thank-you to Walnut Creek CDROM for providing the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are @@ -42,7 +42,7 @@ contributing his floppy tape streamer for experimental work. - The FreeBSD core team

(in alphabetical order by first name): @@ -64,7 +64,7 @@ Søren Schmidt <sos@FreeBSD.org> - Who is responsible for what + Who is responsible for what

- Additional FreeBSD contributors + Additional FreeBSD contributors

(in alphabetical order by first name): @@ -196,7 +196,7 @@ Yves Fonk <yves@cpcoup5.tn.tudelft.nl> - 386BSD Patch kit patch contributors + 386BSD Patch kit patch contributors

(in alphabetical order by first name): diff --git a/share/doc/handbook/ctm.sgml b/share/doc/handbook/ctm.sgml index 9d411dc63649..93cf5a70a3fe 100644 --- a/share/doc/handbook/ctm.sgml +++ b/share/doc/handbook/ctm.sgml @@ -3,7 +3,7 @@ # # Converted by Ollivier RObert # -# $Id: ctm.sgml,v 1.2 1995/06/30 17:37:32 jfieber Exp $ +# $Id: ctm.sgml,v 1.3 1995/07/06 14:24:56 jfieber Exp $ # # ---------------------------------------------------------------------------- # "THE BEER-WARE LICENSE" (Revision 42): @@ -25,7 +25,7 @@ this time on the process of creating deltas, so talk to &a.phk; for more information should you wish to use Why should I use Why should I use

. - What do I need to use What do I need to use

You will need two things: The ``Starting off with Starting off with

Before you can start using Using Using

To apply the deltas, simply say cd /where/ever/you/want/the/stuff @@ -130,7 +130,7 @@ make a copy. - Future plans for Future plans for

Tons of them: @@ -155,7 +155,7 @@ The bad news is that I am very busy, so any help in doing this will be most welcome. And don't forget to tell me what you want also... - Miscellaneous stuff + Miscellaneous stuff

All the ``DES infected'' (e.g. export controlled) source is not included. You will get the ``international'' version only. If @@ -178,7 +178,7 @@ for details. - Thanks! + Thanks!

@@ -37,7 +37,7 @@ in a UNIX-like environment, and how to look up manual pages on the system. As discussed below, you'll need certain versions of FreeBSD, and knowledge of some terminology & modem and cabling. -FreeBSD Version +FreeBSD Version

First, it is assumed that you are using FreeBSD version 1.1 or higher @@ -47,7 +47,7 @@ device driver (Terminology +Terminology

A quick rundown of terminology: @@ -74,7 +74,7 @@ transitions that may be made in a period of time, while External vs. Internal Modems +External vs. Internal Modems

External modems seem to be more convenient for dialup, because @@ -89,7 +89,7 @@ may be limited only to setting DIP switches. If your internal modem has any signal indicator lights, it is probably difficult to view the lights when the system's cover is in place. -Modems and Cables +Modems and Cables

A background knowledge of these items is assumed @@ -149,7 +149,7 @@ watching for status reports from the modem. If you are familiar with connecting modems to PC-based bulletin board systems, this may seem awkward. -Serial Interface Considerations +Serial Interface Considerations

FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based EIA @@ -163,7 +163,7 @@ devices, 16550A-based serial interface cards are much prefered. If the system has many active serial ports or will have a heavy load, 16550A-based cards are better for low-error-rate communications. -Quick Overview +Quick Overview

Here is the process that FreeBSD follows to accept dialup logins. A @@ -192,7 +192,7 @@ by asking for the user's password and then starting the user's shell. Let's dive into the configuration... -Kernel Configuration +Kernel Configuration

FreeBSD kernels typically come prepared to search for four serial @@ -278,7 +278,7 @@ program Device Special Files +Device Special Files

Most devices in the kernel are accessed through ``device special @@ -297,7 +297,7 @@ and Making Device Special Files +Making Device Special Files

A shell script called /dev directory @@ -330,7 +330,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01 These permissions allow the user Configuration Files +Configuration Files

There are three system configuration files in the /etc @@ -376,7 +376,7 @@ The author will try to give balanced configuration information, but is biased towards having the modem's data rate follow the connection rate. -/etc/gettytab +/etc/gettytab

/etc/gettytab is a Locked-Speed Config +Locked-Speed Config

If you are locking your modem's data communications rate at a particular speed, you probably won't need to make any changes to /etc/gettytab. -Matching-Speed Config +Matching-Speed Config

You'll need to setup an entry in /etc/gettytab to give @@ -472,7 +472,7 @@ If you have a slow CPU or a heavily loaded system and you don't have 16550A-based serial ports, you may receive sio ``silo'' errors at 57.6 Kbps. -/etc/ttys +/etc/ttys

/etc/ttys is the list of Locked-Speed Config +Locked-Speed Config

For a locked-speed configuration, your std. entry for /etc/gettytab for your modem's data rate. -Matching-Speed Config +Matching-Speed Config

In a matching-speed configuration, your -/etc/rc.serial or /etc/rc.local +/etc/rc.serial or /etc/rc.local

High-speed modems, like V.32, V.32bis, and V.34 modems, need to use @@ -590,7 +590,7 @@ Since there isn't an initialization device special file on FreeBSD 1.1, one has to just set the flags on the sole device special file and hope the flags aren't cleared by a miscreant. -Modem Settings +Modem Settings

If you have a modem whose parameters may be permanently set in @@ -664,7 +664,7 @@ prompt to a modem that is in command mode and the modem echoes the command or returns a result code. I've heard this sequence can result in a extended, silly conversation between Locked-speed Config +Locked-speed Config

For a locked-speed configuration, you'll need to configure the modem @@ -678,7 +678,7 @@ ATZ AT&B1&W -Matching-speed Config +Matching-speed Config

For a variable-speed configuration, you'll need to configure your @@ -693,7 +693,7 @@ ATZ AT&B2&W -Checking the Modem's Configuration +Checking the Modem's Configuration

Most high-speed modems provide commands to view the modem's current @@ -706,13 +706,13 @@ switch settings), use the commands Troubleshooting +Troubleshooting

Here are a few steps you can follow to check out the dialup modem on your system. -Checking out the FreeBSD system +Checking out the FreeBSD system

Hook up your modem to your FreeBSD system, boot the system, and, if @@ -755,7 +755,7 @@ messages, triple-check the configuration files /etc/ttys and files /dev/ttyd?, for any mistakes, missing entries, or missing device special files. -Try Dialing In +Try Dialing In

Try dialing into the system; be sure to use 8 bits, no parity, 1 stop @@ -794,7 +794,7 @@ perhaps you can send an electronic mail message to FreeBSD-Questions@freebsd.org describing your modem and your problem, and the good folks on the list will try to help. -Acknowledgements +Acknowledgements

Thanks to these people for comments and advice: diff --git a/share/doc/handbook/hw.sgml b/share/doc/handbook/hw.sgml index 9b6fd55ae0b3..0d6d9c32da77 100644 --- a/share/doc/handbook/hw.sgml +++ b/share/doc/handbook/hw.sgml @@ -1,4 +1,4 @@ - + + Installing FreeBSD - MS-DOS user's Questions and Answers + MS-DOS user's Questions and Answers

Help! I have no space! Do I need to delete everything first? @@ -63,7 +63,7 @@ - Supported Configurations

FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus based PC's, ranging from 386sx to @@ -81,7 +81,7 @@ configurations may very well work, and we have simply not received any indication of this. - Disk Controllers + Disk Controllers

@@ -171,7 +171,7 @@ difficulty. - Ethernet cards + Ethernet cards

@@ -211,7 +211,7 @@ Semiconductor are also supported. - Misc + Miscellaneous devices

@@ -246,13 +246,13 @@ materializing. Details will be posted as the situation develops. - Preparing for the installation + Preparing for the installation

There are a number of different methods by which FreeBSD can be installed. The following describes what preparation needs to be done for each type. - Before installing from CDROM + Before installing from CDROM

If your CDROM is of an unsupported type, such as an IDE CDROM, then please skip to section 2.3: MS-DOS @@ -297,7 +297,7 @@ on a more writable media! - Before installing from Floppy + Before installing from Floppy

If you must install from floppy disks, either due to unsupported hardware or just because you enjoy doing @@ -339,7 +339,7 @@ that. - Before installing from a MS-DOS partition + Before installing from a MS-DOS partition

To prepare for installation from an MS-DOS partition, copy the files from the distribution into a directory @@ -371,7 +371,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ which would copy all the subdirectories of E:\DISTS to C:\FREEBSD. - Before installing from QIC/SCSI Tape + Before installing from QIC/SCSI Tape

Installing from tape is probably the easiest method, short of an on-line install using FTP or a CDROM @@ -398,7 +398,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ tape. -Before installing over a network +Before installing over a network

You can do network installations over 3 types of communications links: @@ -462,7 +462,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ Once you have a network link of some sort working, the installation can continue over NFS or FTP. - Preparing for NFS installation + Preparing for NFS installation

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution files you're interested @@ -494,7 +494,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ properly! - Preparing for FTP Installation + Preparing for FTP Installation

FTP installation may be done from any mirror site containing a reasonably up-to-date version of FreeBSD @@ -521,7 +521,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ the Options menu to select Active mode transfers. - Installing FreeBSD + Installing FreeBSD

Once you've taken note of the appropriate preinstallation steps, you should be able to install @@ -577,7 +577,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\ - The installation menu + The installation menu

You can do anything you like in this menu without altering your system except for "Commit", diff --git a/share/doc/handbook/relnotes.sgml b/share/doc/handbook/relnotes.sgml index f0b9e5c49f3e..d85f2992ccef 100644 --- a/share/doc/handbook/relnotes.sgml +++ b/share/doc/handbook/relnotes.sgml @@ -1,11 +1,11 @@ - + - About this release

Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD has changed dramatically. Since @@ -88,7 +88,7 @@ work and many thousands of man hours put in by an international development team. We hope you enjoy it! - New feature highlights + New feature highlights

The following features were added or substantially improved between the release of 2.0 and this 2.0.5 @@ -98,7 +98,7 @@ regarding the new functionality should be directed to them first. - Kernel + Kernel

@@ -197,9 +197,9 @@ - New device support + New device support - SCSI and CDROM devices + SCSI and CDROM devices

@@ -251,7 +251,7 @@ - Serial devices + Serial devices

@@ -281,7 +281,7 @@ - Networking + Networking

@@ -366,7 +366,7 @@ - Miscellaneous drivers + Miscellaneous drivers

@@ -427,7 +427,7 @@ - Experimental features + Experimental features

@@ -457,7 +457,7 @@ + + Setting up user PPP

This document assumes you're in roughly this position: @@ -80,7 +80,7 @@ In addition, I've assumed that because your connection to the Internet is not full time you are not running a name server (named(8)). -Building a ppp ready kernel +Building a ppp ready kernel

As the description states, ``ppp'' uses the kernel ``tun'' device. It is necessary to make sure that your kernel has support for this device compiled @@ -97,7 +97,7 @@ pseudo-device tun 1 should add the line, re-compile and then re-install the kernel. Boot from this new kernel. -Check the tun device +Check the tun device

My experiences with ppp have only been with one ``tun'' device (tun0). If you have used more (i.e., a number other than `1' in the pseudo-device line @@ -111,7 +111,7 @@ pseudo-device tun 1 # ./MAKEDEV tun0 -PPP Configuration +PPP Configuration

The meat of the problem. @@ -134,7 +134,7 @@ pseudo-device tun 1 whether you are using static or dynamic IP addresses. -Configure the resolver(5) +Configure the resolver(5)

The resolver is the part of the networking system that turns IP addresses into hostnames. It can be configured to look for maps that describe IP to @@ -165,7 +165,7 @@ bind namedflags="NO" -Create the /etc/hosts(5) file +Create the /etc/hosts(5) file

This file should contain the IP addresses and names of machines on your network. At a bare minimum it should contain entries for the machine @@ -186,7 +186,7 @@ namedflags="NO" -Create the /etc/resolv.conf file +Create the /etc/resolv.conf file

/etc/resolv.conf contains some extra information required when you are not running a nameserver. It points the resolver routines at real @@ -202,7 +202,7 @@ nameserver 158.152.1.65 Which are Demon Internet's two nameservers. Add as many ``nameserver'' lines as your ISP provides nameservers. -PPP and static IP addresses +PPP and static IP addresses

Probably the easiest to configure for. You will need to create three files in the /etc/ppp directory. @@ -283,7 +283,7 @@ x.x.x.x: may or may not want to do this, depending on how many people have access to your ppp system. -PPP and Dynamic IP configuration +PPP and Dynamic IP configuration

If you service provider does not assign static IP numbers, @@ -294,7 +294,7 @@ set ifaddr 0 0 See the ppp(8) manual page for more detailed information. -Final system configuration +Final system configuration

You now have PPP configured, but there's a few more things to do before it's ready to work. They all involve editing the /etc/sysconfig file.