d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Typos fixed by Michael E. and Gary J. Thanks, guys!

Browse Source 
Submitted by:	me,gj
This commit is contained in:
jkh 1994-11-11 07:39:40 +00:00
parent 8c7bac183a
commit 586fbcb8a7
2 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
share/FAQ/DISKSPACE.FAQ
View File

@ -19,7 +19,7 @@ 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 manageble chunks, or partitions. It works, but only just.
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
@ -94,7 +94,7 @@ A: FreeBSD always has an MBR slice with type 0xa5 (each of the 4 slices can
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 secondard boot code for FreeBSD,
(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
@ -102,7 +102,7 @@ C: The 'C' partition in the FreeBSD disklabel corresponds to the entire
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 a artificially created FreeBSD disklabel. This is useful
'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:
@ -260,4 +260,4 @@ Mountpoint Filesystem size
/usr/X11R6 50Mb If you load the entire XFree86 binary kit.
$Id: DISKSPACE.FAQ,v 1.3 1994/11/07 10:35:54 jkh Exp $
$Id: DISKSPACE.FAQ,v 1.4 1994/11/09 02:51:19 jkh Exp $

22
share/FAQ/RELNOTES.FreeBSD
View File

@ -6,7 +6,7 @@
---------------------
FreeBSD is a freely available, full source 4.4 BSD Lite based release
for Intel i386/i486/Pentium (or compatable) based PC's. It is based
for Intel i386/i486/Pentium (or compatible) based PC's. It is based
primarily on software from U.C. Berkeley's CSRG group, with some
enhancements from NetBSD, 386BSD, and the Free Software Foundation.
@ -60,7 +60,7 @@ to deal with. If you're outside (or even inside) the U.S., give it a try!
4.4 Lite
--------
As previously stated, this release is based entirely on CSRG's
latest (and last) BSD release - 4.4 Lite. This features as number
latest (and last) BSD release - 4.4 Lite. This features a number
of improvements over 4.2BSD (Net/2), not least of which are:
o Legal approval of Novell & U.C. Berkeley. After the settlement
@ -147,7 +147,7 @@ Sources involved: lib/libskey, usr.bin/key* (plus patches to others)
TCP/IP over parallel (printer) port
-----------------------------------
You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
have a interrupt-driven printerport. The interface is named "lp0"
have an interrupt-driven printerport. The interface is named "lp0"
where '0' is the same as the lpt# unit number. This is not compatible
with PLIP. If you run NFS, try setting MTU to 9180, otherwise leave
it at 1500 unless you have a good reason to change it. Speed varies
@ -185,8 +185,8 @@ Sources involved: kern/imgact_gzip.c kern/inflate.c
Diskless booting
----------------
Diskless booting it in 2.0 and much improved since 1.1.5. The boot-program
is in src/sys/i386/boot/netboot, and can be run from a MSDOS system or
Diskless booting in 2.0 and much improved since 1.1.5. The boot-program
is in src/sys/i386/boot/netboot, and can be run from an MSDOS system or
burned into an EPROM. Local swapping is possible. Presently WD, SMC and
Novell cards are supported.
@ -233,7 +233,7 @@ FreeBSD now supports running iBCS2 compatible binaries (currently
SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
The iBCS2 emulator is in its early stages, but it is functional, we
havn't been able to do exhaustive testing (lack of commercial apps),
but allmost all of SCO's 3.2.2 binaries are working, so is an old
but almost all of SCO's 3.2.2 binaries are working, so is an old
INFORMIX-2.10 for SCO. Further testing is nessesary to complete this
project. There is also work under way for ELF & XOUT loaders, and
most of the svr4 syscall wrappers have been written.
@ -285,8 +285,8 @@ With all supported SCSI controllers, full support is provided for
SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM
interface card) is the only way a CD ROM drive may be currently
attached to a FreeBSD system; we do not support SoundBlaster CDROM
interface, or other "non-SCSI" adapters. The ProAudio Spectrum
attached to a FreeBSD system; we do not support SoundBlaster (non-SCSI)
CDROM interface, or other "non-SCSI" adapters. The ProAudio Spectrum
SCSI and SoundBlaster SCSI controllers are supported.
Some controllers have limitations with the way they deal with >16MB of
@ -298,7 +298,7 @@ they're configured to emulate an ISA card, which they then do in *all*
respects. This problem is avoided entirely by IDE controllers (which
do not use DMA), true EISA controllers (like the UltraStor or Adaptec
1742A) and most VLB (local bus) controllers. In the cases where it's
necessary, the system will use "bounce buffers" to to talk to the
necessary, the system will use "bounce buffers" to talk to the
controller so that you can still use more than 16Mb of memory without
difficulty.
@ -400,7 +400,7 @@ Your suggestions, bug reports and contributions of code are always
valued - please do not hesitate to report any problems you may find
(preferably with a fix attached if you can!).
The prefered method to submit bug reports from a machine with internet
The preferred method to submit bug reports from a machine with internet
mail connectivity is to use the sendbug command. Bug reports will be
dutifully filed by our faithful bugfiler program and you can be sure
that we'll do our best to respond to all reported bugs as soon as
@ -505,4 +505,4 @@ hope you enjoy this release of FreeBSD!
The FreeBSD Core Team
$Id: RELNOTES.FreeBSD,v 1.7 1994/11/10 03:51:18 jkh Exp $
$Id: RELNOTES.FreeBSD,v 1.8 1994/11/10 04:11:58 jkh Exp $