src/usr.sbin/sysinstall/help, branch release/7.0.0_cvs

Fix a number of documentation-lags-behind-reality bugs in sysinstall(8).

2007-06-25T16:37:17+00:00

While here, fix a couple of comments too.

Submitted by:	Oliver Fromme 
Approved by:	re (kensmith)

Another update for reality: "dangerously dedicated" mode is now

2006-02-06T00:06:39+00:00

achieved by hitting 'F', which is no longer undocumented.

PR:		bin/92533
Submitted by:	Rudolf Cejka

Bring these files somewhat into the present.

2006-02-05T18:46:46+00:00

Perform some rewording while here.

Remove register.hlp, since the code that deals with it was removed
nearly 7 years ago.

Join the 21st century: Cryptography is no longer an optional component

2004-08-06T07:27:08+00:00

of releases.  The -DNOCRYPT build option still exists for anyone who
really wants to build non-cryptographic binaries, but the "crypto"
release distribution is now part of "base", and anyone installing from a
release will get cryptographic binaries.

Approved by:	re (scottl), markm
Discussed on:	freebsd-current, in late April 2004

Re-linewrap help file on securelevels in sysinstall: sysinstall is

2003-12-16T22:55:28+00:00

mostly used on 80x25 displays, and the actual window is about ten
characters narrower than that, resulting in the need for horizontal
scrolling.  No functional change.

RELENG_5_2 candidate.

Add a Securelevel sub-menu to the Security configuration menu,

2003-11-29T21:44:51+00:00

permitting the administrator to select a securelevel top operate
at.  Include a helpfile summarizing some of the information from
init(8).  This allows for explicit configuration of securelevels,
which was previously implicit in Security Profile selection.
Currently, there are no checkboxes for the active securelevel,
because sysinstall's facilities for deriving "current settings"
from rc.conf may use only one variable, not two, and I opted for
the simplest approach at this point.

Approved by:	re (scottl)

Remove security profiles from sysinstall. Currently, security profile

2003-11-28T18:47:45+00:00

selection is used to drive two configuration parameters:

(1) Default enable/disable for sshd
(2) Default enable/disable for securelevels

Replace this with an explicit choice to enable/disable sshd.  A
follow-up commit will add a configuration option to the Security
post-install configuration menu to set the securelevel in rc.conf
explicitly.  This should reduce the level of foot-shooting associated
with accidental enabling of securelevels, make the nature and
implications of the securelevel configuration options more explicit,
as well as make the choice to enable/disable sshd more explicit.

Approved by:	re (scottl)

Don't use UFS2 by default during the install process on PC98, as the

2003-04-21T20:57:20+00:00

PC98 boot blocks don't support UFS2.  We keep newfs(8) defaulting to
UFS2.

Warn users that FreeBSD can only boot from a root file system smaller
than 1.5TB; hopefully this will get fixed by the patches currently
floating around on -CURRENT.

Reviewed by:	nyan

Throw the switch--change to UFS2 as our default file system format for

2003-04-20T14:08:05+00:00

FreeBSD 5.1-RELEASE and later:

- newfs(8) will now create UFS2 file systems unless UFS1 is specifically
  requested (-O1).  To do this, I just twiddled the Oflag default.

- sysinstall(8) will now select UFS2 as the default layout for new
  file systems unless specifically requested (use '1' and '2' to change
  the file system layout in the disk labeler).  To do this, I inverted
  the ufs2 flag into a ufs1 flag, since ufs2 is now the default and
  ufs1 is the edge case.  There's a slight semantic change in the
  key behavior: '2' no longer toggles, it changes the selection to UFS2.

This is very similar to a patch David O'Brien sent me at one point, and
that I couldn't find.

Approved by:	re (telecon)
Reviewed by:	mckusick, phk, bmah

If you don't create a /usr filesystem, / will need 200MB.

2003-01-13T21:57:07+00:00