jimzah/freebsd-src
1
0
Fork 0
mirror of https://github.com/freebsd/freebsd-src.git synced 2024-12-02 04:13:39 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

More missing help files. Please review!

Browse Source
This commit is contained in:
Jordan K. Hubbard 1995-06-04 10:42:17 +00:00
parent 8d811fe3b3
commit 19566a0c18
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=9025
4 changed files with 210 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
release/sysinstall/help/en_US.ISO8859-1/partition.hlp Normal file
View File

@ -0,0 +1,77 @@
This is the FreeBSD DiskLabel Editor.
If you're new to this installation, then you should first understand
how FreeBSD 2.0.5's new "slices" paradigm for looking at disk storage
works. It's not very hard to understand. A "fully qualified slice name",
that is the name of the file we open in /dev to talk to the slice,
is optionally broken into 3 parts:
First you have the disk name. Assume we have two SCSI
drives in our system, which gives us `sd0' and `sd1'.
Next you have the "Slice" (or "Master Partition") number,
as seen in the Partition Editor. Assume that our sd0 contains
two slices, a FreeBSD slice and a DOS slice. This gives us
sd0s1 and sd0s2. Let's also say that sd1 is completely devoted
to FreeBSD, so we have only one slice there: sd1s1.
Next, if a slice is a FreeBSD slice, you have a number of
(confusingly named) "partitions" you can put inside of it.
These FreeBSD partitions are where various filesystems or swap
areas live, and using our hypothetical two-SCSI-disk machine
again, we might have something like the following layout on sd0:
Name Mountpoint
---- ----------
sd0s1a /
sd0s1b <swap space>
sd0s1e /usr
Because of historical convention, there is also a short-cut,
or "compatibility slice", that is maintained for easy access
to the first FreeBSD slice on a disk for those programs which
still don't know how to deal with the new slice scheme.
The compatibility slice names for our filesystem above would
look like:
Name Mountpoint
---- ----------
sd0a /
sd0b <swap space>
sd0e /usr
FreeBSD automatically maps the compatibility slice to the first
FreeBSD slice it finds (in this case, sd0s1). You may have multiple
FreeBSD slices on a drive, but only the first one may be the
compatibility slice!
The compatibility slice will eventually be phased out, but
it is still important right now for several reasons:
1. Some programs, as mentioned before, still don't work
with the slice paradigm and need time to catch up.
2. The FreeBSD boot blocks are unable to look for
a root file system in anything but a compatibility
slice right now. This means that our root will always
show up on "sd0a" in the above scenario, even though
it really lives over on sd0s1a and would otherwise be
referred to by its full slice name.
Once you understand all this, then the label editor becomes fairly
simple. You're either carving up the FreeBSD slices displayed at the
top of the screen into smaller pieces (displayed in the middle of the
screen) and then putting FreeBSD file systems on them, Or you're just
mounting existing partitions/slices into your filesystem hierarchy;
this editor lets you do both. Since a DOS partition is also just
another slice as far as FreeBSD is concerned, you can mount one into
in your filesystem hierarchy just as easily with this editor. For
FreeBSD partitions you can also toggle the "newfs" state so that
the partitions are either (re)created from scratch or simply checked
and mounted (the contents are preserved).
When you're done, type `Q' to exit.
No actual changes will be made to the disk until you (C)ommit from the
Install menu! You're working with what is essentially a copy of
the disk label(s), both here and in the Master Partition Editor.

28
release/sysinstall/help/en_US.ISO8859-1/slice.hlp Normal file
View File

@ -0,0 +1,28 @@
This is the Main Partition (or ``Slice'') Editor.
Possible commands are printed at the bottom, the Master Boot Record
contents at the top. You can move up and down with the arrow keys
and can (C)reate a new partition whenever the "bar" is over a partition
who's type is set to "unused".
The flags field has the following legend:
'=' -- Partition is properly aligned.
'>' -- The partition doesn't end before cylinder 1024
'R' -- Has been marked as containing the root (/) filesystem
'B' -- Partition employs BAD144 bad-spot handling
'C' -- This is the FreeBSD 2.0-compatibility partition (default)
'A' -- This partition is marked active.
If you select a partition for Bad144 handling, it will be scanned
for bad blocks before any new filesystems are made on it.
If no partition is marked Active, you will need to either install
a Boot Manager (the option for which will be presented later in the
installation) or set one Active before leaving this screen.
To leave this screen, type `Q'.
No actual changes will be made to the disk until you (C)ommit from the
Install menu! You're working with what is essentially a copy of
the disk label(s), both here and in the Label Editor.

77
release/sysinstall/help/en_US.ISO_8859-1/partition.hlp Normal file
View File

@ -0,0 +1,77 @@
This is the FreeBSD DiskLabel Editor.
If you're new to this installation, then you should first understand
how FreeBSD 2.0.5's new "slices" paradigm for looking at disk storage
works. It's not very hard to understand. A "fully qualified slice name",
that is the name of the file we open in /dev to talk to the slice,
is optionally broken into 3 parts:
First you have the disk name. Assume we have two SCSI
drives in our system, which gives us `sd0' and `sd1'.
Next you have the "Slice" (or "Master Partition") number,
as seen in the Partition Editor. Assume that our sd0 contains
two slices, a FreeBSD slice and a DOS slice. This gives us
sd0s1 and sd0s2. Let's also say that sd1 is completely devoted
to FreeBSD, so we have only one slice there: sd1s1.
Next, if a slice is a FreeBSD slice, you have a number of
(confusingly named) "partitions" you can put inside of it.
These FreeBSD partitions are where various filesystems or swap
areas live, and using our hypothetical two-SCSI-disk machine
again, we might have something like the following layout on sd0:
Name Mountpoint
---- ----------
sd0s1a /
sd0s1b <swap space>
sd0s1e /usr
Because of historical convention, there is also a short-cut,
or "compatibility slice", that is maintained for easy access
to the first FreeBSD slice on a disk for those programs which
still don't know how to deal with the new slice scheme.
The compatibility slice names for our filesystem above would
look like:
Name Mountpoint
---- ----------
sd0a /
sd0b <swap space>
sd0e /usr
FreeBSD automatically maps the compatibility slice to the first
FreeBSD slice it finds (in this case, sd0s1). You may have multiple
FreeBSD slices on a drive, but only the first one may be the
compatibility slice!
The compatibility slice will eventually be phased out, but
it is still important right now for several reasons:
1. Some programs, as mentioned before, still don't work
with the slice paradigm and need time to catch up.
2. The FreeBSD boot blocks are unable to look for
a root file system in anything but a compatibility
slice right now. This means that our root will always
show up on "sd0a" in the above scenario, even though
it really lives over on sd0s1a and would otherwise be
referred to by its full slice name.
Once you understand all this, then the label editor becomes fairly
simple. You're either carving up the FreeBSD slices displayed at the
top of the screen into smaller pieces (displayed in the middle of the
screen) and then putting FreeBSD file systems on them, Or you're just
mounting existing partitions/slices into your filesystem hierarchy;
this editor lets you do both. Since a DOS partition is also just
another slice as far as FreeBSD is concerned, you can mount one into
in your filesystem hierarchy just as easily with this editor. For
FreeBSD partitions you can also toggle the "newfs" state so that
the partitions are either (re)created from scratch or simply checked
and mounted (the contents are preserved).
When you're done, type `Q' to exit.
No actual changes will be made to the disk until you (C)ommit from the
Install menu! You're working with what is essentially a copy of
the disk label(s), both here and in the Master Partition Editor.

28
release/sysinstall/help/en_US.ISO_8859-1/slice.hlp Normal file
View File

@ -0,0 +1,28 @@
This is the Main Partition (or ``Slice'') Editor.
Possible commands are printed at the bottom, the Master Boot Record
contents at the top. You can move up and down with the arrow keys
and can (C)reate a new partition whenever the "bar" is over a partition
who's type is set to "unused".
The flags field has the following legend:
'=' -- Partition is properly aligned.
'>' -- The partition doesn't end before cylinder 1024
'R' -- Has been marked as containing the root (/) filesystem
'B' -- Partition employs BAD144 bad-spot handling
'C' -- This is the FreeBSD 2.0-compatibility partition (default)
'A' -- This partition is marked active.
If you select a partition for Bad144 handling, it will be scanned
for bad blocks before any new filesystems are made on it.
If no partition is marked Active, you will need to either install
a Boot Manager (the option for which will be presented later in the
installation) or set one Active before leaving this screen.
To leave this screen, type `Q'.
No actual changes will be made to the disk until you (C)ommit from the
Install menu! You're working with what is essentially a copy of
the disk label(s), both here and in the Label Editor.