mirror of
https://github.com/opnsense/src.git
synced 2026-06-11 01:30:30 -04:00
Just a little last-minute stylistic cleanup.
This commit is contained in:
parent
ad63b51399
commit
02e5217ba0
2 changed files with 33 additions and 30 deletions
|
|
@ -3,11 +3,11 @@
|
|||
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 enjoy the brief history lesson.
|
||||
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.
|
||||
|
|
@ -15,22 +15,22 @@ you may enjoy the brief history lesson.
|
|||
|
||||
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 manageble
|
||||
chunks, or partitions. It works, but only just. To better understand
|
||||
why, first a brief bit of history:
|
||||
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.
|
||||
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 things. What it had was a way to install
|
||||
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? A long time ago, to be sure!).
|
||||
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
|
||||
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
|
||||
|
|
@ -48,10 +48,13 @@ 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. 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.
|
||||
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
|
||||
|
|
@ -256,4 +259,4 @@ Mountpoint Filesystem size
|
|||
/usr/X11R6 50Mb If you load the entire XFree86 binary kit.
|
||||
|
||||
|
||||
$Id: DISKSPACE.FAQ,v 1.1 1994/11/05 05:54:21 phk Exp $
|
||||
$Id: DISKSPACE.FAQ,v 1.2 1994/11/05 06:54:49 jkh Exp $
|
||||
|
|
|
|||
|
|
@ -12,15 +12,15 @@ enhancements from NetBSD, 386BSD, and the Free Software Foundation.
|
|||
|
||||
Since our first release of FreeBSD 1.0 almost 18 months ago, FreeBSD
|
||||
has changed almost entirely. A new port from the Berkeley 4.4 code
|
||||
base was done, bringing the legal status of the system out of the
|
||||
shadows with the blessing of Novell (new owners of USL and UNIX). The
|
||||
base was done and brought the legal status of the system out of the
|
||||
shadows with the blessings of Novell (new owners of USL and UNIX). The
|
||||
port to 4.4 has also brought in a host of new features, filesystems
|
||||
and networking support. With our new code base, we have every hope of
|
||||
being able to confidently release quality operating systems without
|
||||
further legal encumbrance for some time to come!
|
||||
and driver support. With our new unencumbered code base, we have every
|
||||
reason to hope that we'll be able to release quality operating systems
|
||||
without further legal encumbrance for some time to come!
|
||||
|
||||
FreeBSD 2.0 represents the culmination of almost 2 years of work and
|
||||
many thousands of man hours put in by our all-volunteer working group.
|
||||
many thousands of man hours put in by an international development team.
|
||||
We hope you enjoy it!
|
||||
|
||||
Many packages have also been upgraded or added, such as XFree86 3.1,
|
||||
|
|
@ -29,7 +29,7 @@ utilities have been ported and are now available as add-ons. See the
|
|||
next section of this document for more details.
|
||||
|
||||
For a list of contributors, please see the files "CONTRIB.FreeBSD" and
|
||||
"CONTRIB.386BSD", which should be bundled with your distribution.
|
||||
"CONTRIB.386BSD", which should be bundled with your bindist distribution.
|
||||
|
||||
Also see the new "REGISTER.FreeBSD" file for information on registering
|
||||
with the "Free BSD user counter". We've also provided a list of who's
|
||||
|
|
@ -315,4 +315,4 @@ hope you enjoy this release of FreeBSD!
|
|||
|
||||
The FreeBSD Core Team
|
||||
|
||||
$Id: RELNOTES.FreeBSD,v 1.1 1994/11/04 02:22:41 jkh Exp $
|
||||
$Id: RELNOTES.FreeBSD,v 1.1 1994/11/05 08:11:22 jkh Exp $
|
||||
|
|
|
|||
Loading…
Reference in a new issue