Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

MFC r228682:

In usr.sbin/sade/install.c and usr.sbin/sade/label.c, fix a few warnings
about format strings not being literals.

MFC r228683:

Forgot to add usr.sbin/sade/label.c in the previous commit.

Copy head to stable/9 as part of 9.0-RELEASE release cycle.

Approved by: re (implicit)

Partitions are only meaningful for i386 and amd64 architectures, so disable
these code on other architectures.

Make sade(8) WARNS=3 clean.

Say welcome to 'sade', the SysAdmins Disk Editor. It's the fdisk and disklabel part
of sysinstall. So sysinstall may retire now, we have the important non-install part
of it covered.

ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, ...), but patches
to change this and to clean it up internally are more than welcome.

Submitted by: mami@nyitolap.hu

Forced commit to note repo copy from sysinstall.

Repo copy by: markm

Disable an SMP detection on pc98.

missed a case that needs WITH_SMP

Noticed by: kensmith

Revamp base system packaging of kernels to enable up/smp selection
at runtime and to support distributing additional kernels:
o remove kernel from the base tarball
o add new kernel tarballs
o build + package both SMP and GENERIC kernels when an <arch>/conf/SMP
config file is present
o add sysinstall support for multiple kernels
o update sysinstall to probe for the number of cpus on a system
and auto-select smp/up kernel accordingly
o add a post-kernels install hook to fixup /boot/kernel
o add -ldevinfo to boot crunch for sysinstall's cpu probing logic

Notes:
1. On HEAD this code is not currently used because GENERIC kernels
include SMP. This work is mainly intended for RELENG_6 where the
GENERIC kernel is UP. If HEAD changes to match then just enable
WITH_SMP in sysinstall/Makefile.
2. The cpu probing support is done with acpi and MPTable; this means
some systems will require work for auto-detection to work.
3. The handling of /boot/kernel may need to be revisited; for now
we rename one kernel at the last moment (SMP if installed, otherwise
GENERIC). There are other, possibly better, approaches.

Lots of help from ru, emaste, scottl, and jhb.

An i386 machine with 32MB of RAM requires a 700MB disk for auto-layout to
succeed, whilst an i386 with 256MB of RAM requires more. Up the amount
of disk hinted at as a minimum requisite for auto-layout.

MFC after: 1 week

Automatically switch to ttyv3 where the fixit shell is running when using
the standard console and any fixit mode.

MFC after: 1 day

- Fix a bug in sysinstall related to mounting CD-ROMs. If mount(2) fails
with EBUSY and a cdrom is not mounted at /cdrom, sysinstall fails to
treat it as an error and thinks that the disk mounted ok. However, it
doesn't find a cdrom.inf file so it complains. Later when it tries to
unmount the disk due to a mediaClose() umount(2) returns an error, and it
never clears its internal mounted flag. The fix here is to properly
handle EBUSY as an error if there isn't a CD already mounted at /cdrom.
- Add a new CDROMInitQuiet variable that can be used to shut up the dialog
box about the mount(2) system call failing when trying to mount a CD-ROM.
This is used by the feature described below.
- When using a fixit CD, first try to see if we can mount the disc in the
drive now and use it as a fixit CD. If not, then prompt the user to
insert the disc and try again. If we do succeed on the first "silent"
probe then we don't ask the user to eject the disk after leaving fixit
mode.
- Add a simple file existence test to make sure that the disc that we mount
really is a livefs disc.
- Explicitly switch back to ttyv0 when using the standard console after
the fixit shell dies. Previously this behavior worked accidentally
because all the fixit modes popped up a dialog box which contained a
hidden switch to ttyv0.

MFC after: 1 day

Remove /stand when we are done with it.

Submitted by: Ryan Sommers <ryans@gamersimpact.com>

Removed bitrot.

Remove support for configuring the X server from sysinstall. General
concensus seems to be that is best left for doing post-install.

Discussed on: freebsd-current@
Tested with: make release
Approved by: re@
MFC after: 3 days

o Save pointers to the chunks for root, home, swap, usr, var and tmp in
global variables. On ia64, save a pointer to the efi chunk as well.
o At the same time, change checkLabels() to define these globals instead
of having the caller of checkLabels() pass addresses to variables for
these. Change the two callers correspondingly.
o Spent a bit more time adjusting try_auto_label() to prepate for having
the EFI partition created on ia64.
o Remove efi_mountpoint(). The EFI chunk is now available without having
to iterate over the disks and chunks to find it every time we need it.
o On ia64, now that the root chunk is globally available, set the
vfs.root.mountfrom tunable in loader.conf. This avoids that one cannot
boot into FreeBSD after an install. The kernel cannot find the root
device without a little help...

Join the 21st century: Cryptography is no longer an optional component
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

ia64 specific:
o Remove the code that creates the boot directory on the EFI file
system after it has been mounted, as well as remove the code
that creates the symlink from /boot -> /efi/boot (*). As a result,
/boot will be extracted onto the root file system.
o Add a function efi_mountpoint() that returns the mount point of
the EFI file system or NULL if no EFI partition is created. This
function is used to both check whether there's an EFI file system
and to return what its mount point is.
o When there's no EFI file system, ask the user if this is what he
or she wants. Since we extract /boot onto the root file system,
we do not actually need an EFI file system for the installation to
work. Whether one wants to install without an EFI partition is
of course an entirely different question. We allow it...
o When we're done installing and need to fix up the various bits
and pieces, check if there's an EFI partition and if yes, move
/boot to /efi/boot and create a symlink /boot -> /efi/boot (*).
This is a much more reliable way to get /boot onto the EFI
partition than creating the symlink up front and hope its being
respected. It so happened that we never had the boot directory
end up on the EFI partition. We make the symlink relative.

(*) /efi is a place holder for the actual EFI mount point of course.

Move the inclusion of libdisk.h from sysinstall.h to the source files
that actually need it. This makes it easier for a platform porter to
find the files that may need tweaking to support whatever MD specific
partitioning is needed. It also helps to prevent that the libdisk API
gets exposed and/or used where it's not needed.

Mods for powerpc.

Submitted by: Suleiman Souhlal <refugee@segfaulted.com>

Minor fixes for ia64 installs:
- Don't look for partitions inside a FreeBSD chunk on ia64 when mounting
the filesystems just before the chroot and install.
- Write entries out to /etc/fstab for filesystems that aren't inside a
FreeBSD chunk, but are a top-level chunk under the disk.

Remove unused variables.

In checkLabels(), deal with the fact that on ia64 we do not have a
disklabel.

Teach the Fixit environment how to deal with a dynamic root. Symlink
/libexec to /mnt2/libexec, and execute /mnt2/rescue/ldconfig to add
the /mnt2/lib and /mnt2/usr/lib library directories. Thanks to John Baldwin
for working to track this down.

Submitted by: jhb

Remove security profiles from sysinstall. Currently, security profile
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)

Various NFS-related bug fixes (mostly related to using variable_get()
instead of variable_cmp() to test boolean rc.conf variables).

Submitted by: hmp

Add a new variable 'skipPCCARD'. This variable will cause sysinstall
to ignore all PC Card devices.

Submitted by: Anders Nordby
PR: bin/37650

MFC After: 2 weeks

Remove the vestiges of the old pre-"X_AS_PKG" way we used to handled the
installing XFree86 (version 3.3.6 and before).

Reviewed by: jhb

Instead of unconditionally refusing to install if no swap partitions
are specified, prompt the user with a yes/no box.

Teach sysinstall to recognize if acpi was turned off from the bootloader,
and then ask the user if this should be made permanent.

Approved by: re

Add __amd64__ ifdefs to enable the bootblock handling code, slices, etc.

Approved by: re (murray)
Obtained from: obrien

Reword the infamouse mouse dialog to ask if you have a PS/2, serial, or
bus mouse instead of if you have a non-USB mouse.

Requested by: many
Prodded by: dougb
Approved by: re (scottl)

Throw the switch--change to UFS2 as our default file system format for
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

s/to try and retry/to retry/

PR: misc/48226
Submitted by: Gary W. Swearingen <swear@attbi.com>
MFC After: 2 days
Approved by: murray (mentor)

- Rename installFixupBin to installFixupBase to finish up the 'bin' to
'base' dist rename.
- Rework struct dist to allow for different types of dists. There are
currently three types of dists: DT_TARBALL, the traditonal gzipped and
split tar file; DT_PACKAGE, a package; and DT_SUBDIST, a meta-dist in
the tree that has its own array of dists as its contents. For example,
the 'base' dist is a DT_TARBALL dist, the 'perl' dist is a DT_PACKAGE
dist, and the 'src' dist is a DT_SUBDIST dist with its own dist table
that contains 'sbase', 'ssys', etc.
- Add helper macros for defining array entries for the different types of
dists to try and make the statically defined dist table in dist.c more
readable.
- Split the logic to deal with a DT_TARBALL dist out of distExtract()
and into its own distExtractTarball() function. distExtract() now
calls other functions to extract each dist.
- Tweak the percentage complete calculation in distExtractTarball() to
do the multiply prior to the divide so it doesn't have to use floating
point.
- Axe the installPackage() function along with the special handling for
the perl and XFree86 dists in distExtractAll() since distExtract()
handles package dists directly now.
- Add back in subdists for the X packages based on the split up packages
that XFree86-4 uses that as closely map to the X dists we used with
X 3.3.x.
- Lots of things like distSetX() and the X dist masks are no longer
#ifndef X_AS_PKG since we use them in both cases now.
- Make the entire installFixupXFree() function #ifndef X_AS_PKG, we only
call it in that case anyways, and it's not suitable for the X_AS_PKG
case.
- Add in X dist menus for the X_AS_PKG case.

Approved by: re

Reformulate how sysinstall handles file system options in the label
editor, in order to support specifying UFS2 as a newfs option.

(1) Support three different newfs types: NEWFS_UFS, NEWFS_MSDOS, and
NEWFS_CUSTOM. Don't mix up the arguments to them: you can't use
soft updates on an msdos file system.

(2) Distinguish adding new arguments to the newfs command line from
replacing it. Permit the addition of new arguments by the user for
NEWFS_UFS. If we entirely replace the command line provided by
sysinstall, call it NEWFS_CUSTOM. 'N' will now add additional
arguments; 'Z' will opt to replace the newfs command line entirely,
but will prompt the user with their current command line as a
starting point.

(3) Construct the newfs command line dynamically based on the options
provided by the user at label-time. Right now, this means selecting
UFS1 vs. UFS2, and the soft updates flag. Drop in some variables
to support ACLs and MAC Multilabel in the future also, but don't
expose them now.

This provides sysinstall with the ability to do more "in band" editing
of the newfs command line, so we can provide more support for the user,
but doesn't sacrifice the ability to entirely specify the newfs command
line of the user is willing to give up on the cushiness factor. It
also makes it easier for us to specify defaults in the future, and
define conditional behavior based on user configuration selections.
For now, we default to UFS1, and permit UFS2 to be used as the root
only on non-i386 systems.

While I was there, I dropped the default fragment and block sizes,
since newfs has much more sensible defaults now.

Reviewed by: jhb, marcel
Approved by: re
ia64 bits from: marcel

Rename installX11package() to installPackage() and tweak it so that it
can be used to install any arbitrary package.

Approved by: re

ia64 specific.
o Mount the EFI file system as msdosfs and not ufs as it's a FAT
file system. Introduce Mount_msdos() for this to go side-by-side
with Mount().
o Also, since mounting is performed as a command (which means it's
queued, sorted, lost, found and executed), we cannot create a
directory on the file system by calling mkdir. We must make sure
the mkdir happens after the mount. Introduce Mkdir_command() to
allow mkdir operations to be queued, sorted, lost, found and
executed as well.

Approved by: re (jhb, rwatson)

ia64: make link /boot->efi/boot relative.

Approved by: re (murray)

- Use WITH_SLICES to conditionalize the fdisk editor during install instead
of an explicit list of architecture defines.
- Tweak the message prior to the label editor in the !WITH_SLICES case to
make it slightly less awkward since this is the first dialog we see after
starting an install.
- Only offer to customize syscons settings if WITH_SYSCONS.
- Offer to enable Linux compat if WITH_LINUX. Before we only did this for
i386.
- On the alpha, offer to enable OSF/1 compat after asking about Linux
compat.
- Only offer to configure moused(8) if WITH_MICE is defined.

Tested on: i386, alpha, sparc64
Approved by: re

Create a link /boot -> /<efi>/boot, where <efi> is the mountpoint
of the EFI file system. This makes the EFI partition non-optional.
I don't think that the links are actually correct, given that all
the mount points are under /mnt when sysinstall is run as init.
(ie a non-upgrade). Thus: I think I need to go in once more, but
at least this doesn't get lost...

Add conditional code specific to ia64 to allow newfs(8)-ing FAT
partitions marked as being of type efi. This change adds code to
1. actually run the newfs command at mount time (install.c),
2. display the newfs state on screen (label.c)
3. allow toggling of the newfs state (label.c)

Even though newfs(8)-ing FAT partitions can be of use on i386
machines in general, it has been opted to minimize impact for
now.

Also test for type efi everywhere we currently test for type fat.
With this change there's no a priori difference between EFI and
FAT partitions. With this change and the corresponding change to
libdisk, we can create EFI partitions, just like regular FAT
partitions.

Confirmed kill: "Bogon #1" is dead, killed by DEVFS.

Comment out more MAKEDEV bogosity ("BOGON #1" as Jordan put it :-)

Fix cut&paste mistake.

Remove more private MAKEDEV kludges.

Give a real error on failure to mount DEVFS.

Pick up a prototyp from libdisk.h instead of having our own.

DEVFS has been nmountified, so use nmount(2) to mount it.

* Negative #if's are harder to read as they don't tell exactly what arch
something applies to. So change #ifndef to an explicit list of defines.
* Treate sparc64 and ia64 as 64-bit platforms, which means larger roots.
* sparc64 should halt back to the firmware, not reset.
* sparc64 doesn't need to play MS-DOS/BIOS partition crap games.

Reviewed by: jake

Create symlink for /etc/group. MAKEDEV file will use this file (group name
to gid conversion).

PR: 43455
Submitted by: n-kogane@syd.odn.ad.jp
X-MFC after: immediately if re@ permits, or after 4.7-RELEASE is out

Switch to using XFree86 version 4. We do this thru installing the package,
so know we have proper PKG registration and dependency information.

This is a WIP for 5.0 DP #1, so it is still rough around the edges and
does not GC the old XFree86 3.3.6 handling stuff that should be GC'ed.
Sponsored by: FreeBSD Mall, Inc.

Our persistent-state, large temporary file dir is /VAR/tmp, not /USR/tmp.

Reword the ``Please remove the FreeBSD fixit CDROM now.'' to
``Please remove the FreeBSD fixit CDROM/DVD now.''.

MFC after: 2 weeks

Unbreak installation for the CD-ROM and possiblhy other media types.

Obtained from: LOMAC project
Sponsored by: DARPA, NAI Labs

Revert rev 1.316 now that the bootstrap issues with filesystems using
block sizees larger than 8192 bytes have been resolved, as per the
following deltas:

rev 1.34 src/sys/boot/i386/boot2/boot2.c
rev 1.5 src/sys/boot/alpha/boot1/sys.c

According to jhb, the alpha bootstrap code depends on the root
filesystem using a block size of 8192. Since this seems unlikely to
be fixed soon (specifically in time for 4.5-RELEASE on the RELENG_4
branch), fall back to the old default block and frag sizes of 8192 and
1024 in sysinstall on the alpha.

Reported by: jhb

Update the default newfs block and fragment sizes from 8192/1024 to
16384/2048.

Following recent discussions on the -arch mailing list, involving dillon
and mckusick, this change parallels the one made over a decade ago when
the default was bumped up from 4096/512.

This should provide significant performance improvements for most
folks, less significant performance losses for a few folks and
wasted space lost to large fragments for many folks.

For discussion, please see the following thread in the -arch archive:

Subject: Using a larger block size on large filesystems

The discussion ceases to be relevant when the issue of partitioning
schemes is raised.

Fix the mouse question again to only run the mouse menu if a user doesn't
have a USB mouse. Here's the deal on how this works: USB mouse have
moused run for them automatically by usbd so we don't need to setup moused
for them. We do need to setup moused for other mice though, so if the
user has a USB mouse, we don't need to do anything. Hence the wording
"Do you have a non-USB mouse installed?" for the question. The question
can be reworded as "Do you have a PS/2 or Serial mouse installed?" instead
if that is preferred.

Add auto-fill-on-delete. When deleting an 'A'uto created partition
sysinstall will automatically expand the previous partition to take up
the freed up space. So you can 'D'elete /home and /usr will get the
combined space, or you can 'D'elete /tmp and /var will get the combined space.

This gives the user, developer, or lay person a huge amount of flexibility
in constructing partitions from an 'A'uto base. It takes only 3 or 4
keystrokes to achieve virtually any combination of having or not having
a /tmp and/or /home after doing an 'A'uto create.

Change 'A'uto creation of /var/tmp to 'A'uto creation /tmp, which should
be less controversial.

MFC after: 6 days

Cleanup sysinstall's 'A'uto partitioning mode to provide more reasonable
defaults both in regards to the size of the partitions that are created
and in regards to safety and functional separation.

Still TODO: extend the previous partition to cover a deleted partition
if the previous partiton was auto-created, and supply some sort of
solution for /tmp.

Reviewed by: Just about everyone
Approved by: Nobody except maybe my pet mouse fred
Obtained from: God, so complain to HIM
MFC after: 1 week

Sysinstall cleanups for installation:
1) Use devfs to mount filesystems. If mounting devfs is fail,
fallback to old code.
2) When fscking filesystems, use 'fsck_ffs' explicitly. As a
result, we no longer need 'fsck' the wrapper program.

Reviewed by: jkh

Remove kget() feature, which is removed from 5-current kernel.

Since userconfig feature is implemented by tweaking variables (hint.*)
with loader(8), we can put back an equivalent feature. Maybe the first
step for this is to commit yokota-san's patch (add userconfig command
for loader).

Approved by: jkh

Remove the ``-c 22'' option from newfs command line. Changes in newfs(8)
makes that obsolete. The jury^W-arch is still out about the block and fragment
sizes so I'll that for later.

Reminded by: obrien
MFC after: 2 days

DTRT in the restart case

Silence more warnings.

Add missing {}. This made most/all scripted installs fail.

Approved by: jkh

Update the inetd configuration prompt for clarity.

Submitted by: chern
Committed from: "Make sysinstall suck less party", D1031 WRS campus, Alameda

Revisions 1.117 and 1.118 of tcpip.c fixed the logic dealing with DHCP
and RTSOL in sysinstall. If the respective TRY_FOO variable is set to
"YES" then it will be tried without prompting the user.

However, if the TRY_FOO variable is set to "NO" then the user will not
be prompted for a choice. This is the correct behavior, since we want
people to be able to script sysinstall in either case.

However, the default TRY_FOO variable has been "NO" since 1999. This
is incorrect, and when the logic was corrected in tcpip.c this has the
effect of never giving the user a choice to use DHCP or IPv6. The
value should be undefined until it is set by a script or by the user.

Submitted by: Randy Pratt, Chern Lee, many others.

Since we now install sysinstall in /usr/sbin, encourage the user to
run that version, rather than the copy in /stand.

o Improve terminology consistency for security profile functionality:
the name for the moderate security profile is "moderate", not
"medium", so update this one reference to it as "medium".

This is a 4.4-RELEASE MFC candidate.

MFC after: 2 days

Compensate for default disabling of network services in inetd.conf(5)
by providing the opportunity to edit inetd.conf during the system
installation process. The following modifications were made:

(1) Expand the Anonymous FTP description dialog to indicate that inetd
and ftpd must be enabled before it can be used.

(2) Introduce a new configInetd() pair of dialogs, the first describing
inetd, giving a couple of examples of services that require it, and
hinting at potential risk, then asking the user if they wish to
enable it. The second indicates that inetd.conf must be configured
to enabled specific services, and asks if the user would like to
load inetd.conf into the editor to modify it. Add this
configuration action to the index.

There are some further improvements that might be considered:

(1) Provide a more inetd.conf-specific configuration tool that speaks
inetd.conf(5). However, this is made difficult by the "yet another
configuration format" nature of inetd.conf, as well as its use of
commenting to disable services, rather than an in-syntax way to
disable a service without commenting it out. Submissions here
would probably be welcome.

(2) There's some overlap between settings in the somewhat obtuse
Security Profile mechanism and other settings, including the inetd
setting, and NFS server configuration. As features become
individually tunable, they should probably be removed from the
security profile mechanism. Otherwise, somewhat counter-intuitively,
sysinstall (in practice) queries multiple times whether inetd, nfsd,
etc, should be enabled/disabled. A possible future direction might
be to drive profiles not by degree of paranoia, rather, the set
of services desired. Or simply to remove the Security Profile
mechanism and resort to feature-driven configuration.

Reviewed by: imp, chris, jake, nate, -arch, -stable

Add ability to configure console terminal type in /etc/ttys

Reviewed by: audit, jkh's silence

Fix the type of the NULL arg to execl()

Idea from: Theo de Raadt <deraadt@openbsd.org>

Bring back part of rev. 1.296 I accidently reverted in the previous
commit.

Introduce DEVICE_INIT, DEVICE_GET, and DEVICE_SHUTDOWN macros. As the
names suggest, they perform methods on Device's. In addition, they
check that the pointer passed to them is valid; if it isn't, they
pretend that the action failed. This fixes some crashes due to NULL
dereferences (e.g., PR 26509).

Approved by: jkh (some time ago)

Various changes to the messages so that they are now appropriate for both
CD and DVD releases of FreeBSD.

- sys/msdosfs moved to sys/fs/msdosfs
- msdos.ko renamed to msdosfs.ko
- /usr/include/msdosfs moved to /usr/include/fs/msdosfs

Make /compat a relative symlink instead of an absolute symlink.

Requested by: jens

Mirror the newfs(8) defaults change I made in rev 1.33 of newfs.c where
I made `22' the default number of cylinders per group.

Switch from lynx to "links" as the default doc browser.

Submitted by: jim

Allow a script-using to disable the emergency holographic shell as
a security measure.

Requested by: "David E. Cross" <crossd@enterprise.cs.rpi.edu>

Support setting soft updates from the label editor.

Fix an informational message a little and properly check status of a yes/no
question which I bollicked up in my previous commit.

Adapt sysinstall to use the new msgNoYes() function which assumes
no as a default. Sysinstall should be both less dangerous and less
annoying as a result of this change, though that's just my opinion
(since they're the defaults which annoy ME the least :).

Remove extra ")".

Back out change to prepend /sbin:/bin to $PATH, just overwrite $PATH
with these in the normal case.

Set MAKEDEVPATH in sysinstall to include the /mnt2 stuff before starting
the fixit shell.

Changes have been made to support a concept of VAR_FIXIT_TTY being
standard or serial. This change needs to be done to the entire system that
depends on this. This way we don't have some code using OnVTY checks
and other doing
strcmp(variable_get(VAR_FIXIT_TTY), "standard") == 0
checks. Also we need to set VAR_FIXIT_TTY to "serial" if we come up on
a serial console.

Also fixed a dialog problem in that dialog was used when dialog was
disabled causing some troubles such as not letting the cursor keys
work when exiting the fixit mode on media (ie. not the fixit shell but
for example fixit on a floppy).

Submitted by: Doug Ambrisko <ambrisko@whistle.com>
PR: 22352

If user selects no distributions at all, assume "User" as
a default. This should prevent people from whacking return at
the Distributions menu and getting nothing selected as a result
(a minimal "standard" system will at least install).

Flagged as big tech support headache by: Chris Shumway <cshumway@osd.bsdi.com>

Adjust for new location and name of kernel.

PR: 21423
Reported by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>

Fix a small bogon with a boolean yes/no question check.

One small tweak on the security profile code; don't be verbose if
setting up default values for an express/custom install. It would
be confusing to see the informational popup completely out of context.

One whack at the idea of having "security profiles" which select the
appropriate(?) defaults for "low", "medium" and "high" security
environments. Medium is basically what we currently have with a little
seat-belt tightening where it made sense. Low is the same as medium but
without the tightening. High is positively fascist with nothing turned
on by default and an automatic call to 911 if it can find a modem.

MFS: sync with -stable by removing the now-vestigal X_AS_PKG stuff.

Terminate, with extreme prejudice, the USAResident hack which
does bad things to /etc/make.conf in certain situations. Also
soften the "don't install crypto from the USA!" messages since,
except for RSA (which is still noted), that's not so true anymore.

Add a terminal entry for xterm; a lot of people are using xterms
in the serial-installation of FreeBSD.

Allow the Fix-it functionality to detect that we are on a serial console,
and DTRT rather than start the fixit shell on a non-existant vty.

PR: 19837
Submitted by: Doug Ambrisko <ambrisko@whistle.com>
Approved by: JKH

IPv6 support.
IPv6 configuration is only done by rtsol. Does someone really
need manual configuration? :-)
You can specify IPv6 DNS server as well.
We have only one server ftp7.jp.freebsd.org that speaks IPv6
in this time. ftp7.jp speaks IPv4 as well and also listed as
Japan #7.

Approved by: jkh

Finish the /dev/rXXX removal job. With the libdisk fixes, this should
actually work again.

Add an option to select the Fix-it tty. The current behavior is utterly
*useless* on serial consoled machines.

Add support for USB to sysinstall. This includes running usbd and
setting 'usbd_enable' in rc.conf during nwe installs if USB is detected.
Also, since usbd already handles USB mice automatically, note that the
mouse setup section in sysinstall only applies to non-USB mice.

Sigh, it would have been nice but I just can't make the rsaref
hack work until we figure out some better way of handling package
interaction.

We still need a hack for rsaref package; add it. This doesn't
affect CDs since they don't contain the rsaref package anyway.

Make the "can't find an rsafoo package" messages more informative.

Remove PkgInteractive hack - it won't work like this.

s/chose/choose/ in all the relevant places.

Noticed by: John Reynolds <jjreynold@home.com>

o Add support for loading the rsaref or rsaintl packages, depending
on locale.

o Allow use of "G" in label editor to stand for gigabytes. This
is actually an unrelated patch which I meant to commit separately
but what the heck, it's late.

Partially submitted by: phk

Revise this for the brave new world of "crypto"

Submitted by: markm
Approved by: me!

If user says they're in the USA, record that fact in /etc/make.conf

no need to fix moused setting here; fix in defaults

Whoops, forgot to delete the ! operator in the reversed conditional
for anonftp. Fix.

Invert the meaning of two questions in the Standard installation so just
whapping "Yes" by default does not turn you into an anonymous FTP-supporting
gateway machine. Those aren't the right "defaults."

Don't call it a Novice install, call it Standard.
Also say thousands of packages, not hundreds.

* add SVR4 and OSF/1 enabling in the Start Up config menu
* deals with X11 install when all we have is the Port (such as on the Alpha)

Ok'ed by: JKH

MFC: can't stop tweaking this compulsively.

cosmetics missed in last commit.

In retrospect, msgNotify() should leave its contents on the screen
longer to give the user something to look at while things are happening.
Change it to do so and insert the appropriate screen saves elsewhere.

Put up some more helpful dialog boxes.
Adjust some text to make more sense.

Completely rip-out and redesign sysinstall's refresh model as well
as redoing all the menus to have proper, or at least non-hallucinogenic,
keyboard accelerators.

This requires my recent update to libdialog to work properly and will
probably also exhibit some other "interesting" behavior while the last
few missing screen clears are found (which is why I'm not going to MFC
immediately). At least now, however, sysinstall does not gratuitously
redraw random screens at the drop of a hat and drive serial console
installers out of their minds.

I shouldn't have incremented PART_OFF; it was wrong and broke label
display to boot. Also fix some various warning fluff while I'm in
here cleaning up.

minor bugfix to loader.conf code.

Clean up the loader.conf write-out code.

execute a strategic clear.

Apparently, it's not console=serial to set the serial console,
it's serial=comconsole. I wish it were easier to figure this
stuff out. :)

Submitted by: jfieber

o Catch up with pnp changes - kget no longer saves pnp data.
o Catch up with ncurses updates - some internal function names have changed.

Oh crud, did I ever screw the pooch! Rather than sync this with -stable,
I backed-out the changes in -current and didn't touch stable at all (I
thought I had my patch order reversed, not what actually happened).
AIEEE! I can't even blame the crack for this one since I broke my
crack pipe a few weeks ago. I think sleep deprivation gets the blame
for this one.

Medal for noticing this one goes to: Jim Bloom <bloom@acm.org>

MFC: Catch 3.2-stable sysinstall up to 4.0-current level functionality,
bringing in DHCP support. The only thing I left out were Poul-Henning's
newfs changes since I'm not sure if he's brought the rest of that support
into -stable yet. If it turns out that this is the case, I'll MFC those
changes too.

$Id$ -> $FreeBSD$

Make the newfs parameters a global option.

The default is still "-b 8192 -f 1024" but my experiments show that
"-b 16384 -f 4096 -c 100" is a more sensible value for modern
disksizes.

Stay on the serial console if installed that way.

Requested by: max

Some additional optimizations for using DHCP.

Re-enable DHCP client support again (but optional and turned off by default
for the time being) for debugging purposes.

Fix bug in options selection.

Don't ask about Linux emulation on the alpha (for now).

Add an option for more fully enabling linux compatibility.

Add bits of PAO that are non-controversial.

Submitted by: Tatsumi HOSOKAWA

Do a clean-up pass on error/warning messages.

Completely change the way package_add() does its work. Now we
handle dependencies at a lower level and use package add for this.
Also made index searches stricter.

Make saving kernel configuration info disable-able (may be useful in certain
situations).

Another round of updates for -current and 3.2

Deal with new loader syntax in determining how/when to load a userconfig
script.

Submitted by: "Daniel C. Sobral" <dcs@newsguy.com>
Avoided by: jkh
Demanded by: The Users

o Make package matching for specific package loading use the Latest/
feature of packages now so that no version info is embedded.

o Add a default X desktop menu offering afterstep, enlightenment, KDE, GNOME
and Windowmaker desktops instead of the boring twm(1) based one if the
user so chooses. This will require a little testing.

Remove the registration stuff; we're redoing this and the emailed
registrations have a high failure rate for various reasons.

Make proper symlinks for fixit mode and ELF binaries.

Noticed by: jdp

Unbreak the fixit floppy.
Clean up some of the media handling to use common routines.

Fix incorrect initial state for two variables.

Write changes out to /etc/rc.conf again; rc.conf.site is dead!

Totally change the way variables are accounted for in sysinstall.
Now we know which variables are internal and which need to be
backed to /etc/rc.conf.site. rc.conf is not touched now.

Also kget kernel change information back properly and set up a loader.rc
file to use it.

More support for Alpha installs.

Submitted by: dfr

Write changes out to /etc/rc.conf.site now rather than mucking with
rc.conf. There were many different ways I could have done this, some of
them "cleaner", but this represented the lowest impact.

Replace old SAVE_USERCONFIG code with a customized version of Andrzej's
kget code. Also collapse a redundant case in cdrom code.

Remove obsolete dset code. It's an ELF/3-stage boot world now and there
are cleaner ways of doing this that don't involve stomping on kernel
binaries directly.

Adapt sysinstall more fully to the alpha (deal with proper boot signatures,
don't present label editor, etc).

Submitted by: dfr

Fix an exceedingly *stupid* error in my floppy selection logic
which was hosing the fixit functionality.

PR: 8983
Fixed and embarassed by: Nobuyuki Koganemaru <kogane@koganemaru.co.jp>
:-)

Adios version.h / RELEASE_NAME hack. Do this right.

o Break fixups into binary fixups and XFree86 based fixups.
o Move fixups into extraction routine so all consumers don't have to duplicate
the right behavior.
o Make some things more orthogonal (just for asthetics sake)
o Add option to go back and do it again if XF86Setup fails (possibly with
a different setup - this one has always annoyed me).

fix spelling error.
Submitted by: Pomegranate <daver@flag.blackened.net>

fix brainos in earlier commit.

Whoops; fix my X11R6 fixup. Now the package should be marked
as installed correctly.

Make floppy media code more generic so that fixit floppy can use it.

More save_userconfig to a more appropriate spot.

Add in a kludge for registering the "package" version of XFree86 so
various ports don't complain about it. It also requires that the pkg
registration bits be stick into the Xbin tarball so that they'll be
present in /usr/X11R6/lib/X11/pkgreg.tar.gz. The registration tarball
is removed upon first use to prevent it later spamming a genuine build
from ports if inadvertently extracted again.

Always do fixups, even if some minor dist failed to install.
Noticed by: luigi

Don't set the router_enable variable by default.

MF22: Paul Traina's changes.

Sync with 2.2-stable branch.

MF22: installEnvironment() fix, reshuffle, vidcontrol on correct vty.

Remove deprecated XIG support - that project never
happened.

Totally change the way that devices are made in the MFS and subsequently
probed in sysinstall. Rather than make template devices and use up lots
of inodes, also restricting the number of devices that can be dealt with,
mknod all necessary devices as necessary using built-in information.
This removes a number of constraints on the number and type of devices
that sysinstall can see.

Adapt to new mount(2) argument syntax.
Submitted by: bde

gateway -> gateway_enable

Pointed out by: Susie Ward <sward@voltage.net>

Ask for extra confirmation if a newfs has been requested during
an upgrade.
PR: 3368

Separate the siamese twins that were the partition and label editor.
Now you can use one without entering the other and it will DTRT.
These changes just allowed me to do the most straight-forward new disk
installation I've ever managed with sysinstall.

Add an extra sanity check to previous commit.

This should put boot.help in its rightful place (finally!)

Get boot.help from a different place.

Install boot.help a little more skillfully; now it works without a src
dist installed. :)

Fix fstab sequence number bug.
Add a few more strategic screen clears.
Fix registration form bug.

YAMF22 - /boot.foo fixups.

Also close PR#4151 by running newaliases (forgot to mention this
in my RELENG_2_2 commit, but it's there).

Repair missing quote.

ln /compat to /usr/compat on initial installation; this will
prevent the later addition of compat libs from overflowing /

Eliminate Samba configuration. Sorry, but this was another one of
those ideas that, like the Apache server setup, was well-intentioned
but doomed to fail in the face of change. That and the fact that it
shouldn't be part of the installation tool, it should be part of the
post-installation setup tool (which we need to write). Combining the
two utilities into one utility was my first conceptual mistake.

Apologies also to Coranth Gryphon, who worked hard on the Apache
and Samba server setup code. These features were quite useful
for awhile, if that's any consolation, I just simply had the wrong
ideas about where to put them. :-(

Change the way that X configuration method is selected.

Add a couple of strategic screen clears.

1. Add a noWarn flag so that scripts can turn warnings off.
2. If hostname not set from script, bring up interactive dialog anyway.

YAMF22

Fix typos (of the printed output kind).

Be more bullish about saving configuration information.

Actually, rethink last commit and simply remove the apache configuration
entirely, as promised earlier (it's outdated now and doesn't really belong
in sysinstall).

Adapt routing configuration glue to rc.conf format.

Add in some more config file support -- add variables to shut up
sysinstall about the dangerously dedicated message, and other
variables to allow pre-configuring the distribution sets.

Still todo: add a variable to define an initial set of packages that
should be loaded.
Reviewed by: jkh

Adapt to rc.conf file format.

Make all this work under -current again.
Submitted-By: Chuck Robey <chuckr@glue.umd.edu>

Sync up to current state of development.

YAMF22

Be consistent with the handbook and the release notes and specify all
mailing list addresses as freebsd-*@FreeBSD.org.

Pointed out by: Kenneth R. Westback <krw@tcn.net>

Sync with 2.2.

Add a registration screen so we can finally start counting our little user
puppies.

YAMF22

YAMF22

YAMF22

Revert $FreeBSD$ to $Id$

Finally DTRT with tcpOpenDialog(); it should have never diddled
mediaDevice directly.

Don't nuke localtime and timezone files so aggressively now.
This is tzsetup's job (and only if you don't cancel out, which
is why having sysinstall remove them was so bogus).

1. Always write out /etc/hosts.
2. Back out my change to ask about UTC/Localtime here. This *really* needs
to be done in tzsetup instead since putting it here only handles about
1/4 of the places where it needs to be.

Read /etc/resolv.conf information as well as /etc/sysconfig info, making
this a little more robust.

-#include <ufs/ufs/ufsmount.h>

This was a temporary measure I took to deal with John's 4.4L2 changes
which should not have crept in.

Save /etc/sysconfig data at the very very end, so that it can be
used post-install time as a configuration tool as well.

Update comments about a kernel recompile being necessary for PS/2 mice.

Allow the user to choose UTC or local time.

DTRT with a release string of "none" and use the correct (updated)
mountpoint name for fixit.
Submitted-By: joerg

OK, I've got two ideas to file in the "really seemed like a good idea
at the time, but on further reflection..." bucket with these changes.

1. Checking the media before frobbing the disks was a fine idea, and
I wish it could have worked, but that leads to a rather difficult
situation when you need to mount the media someplace and you're about
to:

a) Chroot away from your present root.
b) Newfs the root to be.

You're basically screwed since there's no place to stick the mount
point where it will be found following the newfs/chroot (and eliminating
the chroot in favor of just using the "root bias" feature would work
great for the distributions but not the pkg_add calls done by the
package installer).

2. Automatic timeout handling. I don't know why, but alarm() frequently
returns no residual even when the alarm didn't go off, which defies
the man page but hey, since when was that so unusual? Take out timeouts
but retain the code which temporarily replaces the SIGINT handler in
favor of a more media-specific handler. This way, at least, if it's hanging
you can at least whap it. I think the timeout code would have been losing
over *really slow* links anyway, so it's probably best that it go.

This should fix NFS, tape & CDROM installs again (serves me right for getting
complacent and using just the FTP installs in my testing).

This is a patch that makes some of the "partitions" --> "slice" to be
more consistant in our use of the terms for differentiation between PC
partitions and traditional BSD partitions.

Submitted-By: obrien@cs.ucdavis.edu (David O'Brien)

Argh! Moving the media initialization to before the disk scribbling
section was a good thing, since it made it possible to detect media problems
*before* the installation started, but it also caused various things to
be mounted BEFORE the chroot() call, which definitely messes things up.

Fix this by detecting the pre-chroot() case and mounting into a subdir.

Add extra variables for the configuration of all packages, not just
the lynx browser.

Submitted-By: David O'Brien <obrien@cs.ucdavis.edu>

Correct a real brain-o in my check for when a "fixup" should be run.
Don't recreate parent menus just for submenus - it's irritating.

Fix a variety of problems with my timeout handling, make it more
configurable (you can now set the timeout interval), fix a crash-bug
when no network device was attached.

Whoops! Fix an infinite loop I lovingly introduced into this code
with a previous commit.

Now that I know which parts of the installation really need it (since
there's no menu display bug to work around now), be far more selective
in my use of DITEM_RECREATE (which is slow and involves much screen I/O).

Fix mishandling of extraction return status in commit.

Keep our serial ports distinct so that first device is not found for
all (closes PR#2296).
Print better FTP failure diagnostics
Do better media failure checking in install.

Make the bindist-only checks actually work.
Add code which theoretically should let you get a disk up from
start to finish while running multiuser, using your existing /dev
entries.

Make the FTP installation codepath a lot more defensive. Trap
bogus path and FTP I/O errors much earlier, offer retry possibilities
at steps along the way so you don't have to resume from the very beginning
again on a hard error.

Fix several problems:

1. Bus mouse selection didn't show up properly in mouse menu.
2. U&G management screen didn't respect cancel properly.
3. Novice not prompted to add users or set root password during installation.
4. Username length changes screw up user management form.

Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.

Add more protection when running as init and don't do stupid things.
Fix looping in fixit cdrom selection by adding a missing break.
Move unmount of cdrom down to proper place.

Do a better job of CDROM detection.
Use consistent spelling throughout.
Remove unmount in fixit_common() since that's bogus in the CDROM case and
properly "shut down" the media device instead.

Support the use of the 2nd CDROM as a fixit aid. Also put the EHS
into a submenu in case you need to start it again (or at some other point
in the installation).

Submitted-By: joerg

Fix fixit floppy.

700 now. :)

Don't run routed by default.
Virtually-Demanded-At-Gunpoint-By: joerg

Move configResolv() to *after* the chroot(). This is what was causing
NFS installation to fail the first time. This will go into 2.2.

Provide a symlink for /bin/sh when the fixit floppy is mounted, so
scripts using #!/bin/sh (like /mnt2/dev/MAKEDEV) will work.

Observed by: andreas

"over 600 packages" (geeze, this has been sitting uncommitted in my
source tree for 5 days! :-( ).

Only save userconfig changes if the boot floppy version and the
installed version match.

Pointed-out-by: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)

Several improvements to the `fixit' configuration:

. Don't gzip the crunched binary by now; it just fits, and execution is
a lot faster this way (it's truly demand-paged again).

. Add more(1), ft(8), protocols(5), a stripped down services(5).

. Improve the .profile, and make sysinstall actually use it again.

Still no go for a 4 MB configuration though. :-(

If mounting the fixit floppy fails in the first place, warn the user
but make a second attempt using MNT_FORCE, just in case it has been
unclean from a previous crash. That's dangerous, but far better than
keeping the despaired user standing in the rain...

(Experienced admins can still fsck it then, and remount. Others will
either totally crash, or incidentally succeed, without much further
help possible...)

Btw., mount(2) misses the description of MNT_FORCE for the mount
syscall.

1. Eliminate the sendmail.cw bogon again. Peter fixed it correctly.
2. Preload the ldconfig cache before calling X setup.

Install an evil work-around for /etc/sendmail.cw
[same as from 2.2]

Use macros for package names so it's easier to update them in one
place (sysinstall.h) when packages change rev.

Change the way that the routing daemon is configured entirely, to
placate Joerg. Also auto-load gated if it's specified, while we're at it.

Remove the now-unusable ports configuration code. Swapping CDs is bogus.

Be less draconian about distribution extraction errors - still write
/etc file changes out.

DTRT if ESC is hit in a Yes/No dialog.
Noticed-by: jfieber

Detect the zero-chunks case properly, now that I've reversed the order
of the distribution probes over ftp.

Properly #ifdef the SAVE_USERCONFIG code.

Make the save_userconfig() stuff conditional and turned off by default
(for now - still a few more wrinkles here). Add more debugging code
and some cosmetic tweaks.

Multiple changes stacked as one commit since they all depend on one another.

First, change sysinstall and the Makefile rules to not build the kernel
nlist directly into sysinstall now. Instead, spit it out as an ascii
file in /stand and parse it from sysinstall later. This solves the chicken-n-
egg problem of building sysinstall into the fsimage before BOOTMFS is built
and can have its symbols extracted. Now we generate the symbol file in
release.8.

Second, add Poul-Henning's USERCONFIG_BOOT changes. These have two
effects:

1. Userconfig is always entered, rather than only after a -c
(don't scream yet, it's not as bad as it sounds).

2. Userconfig reads a message string which can optionally be
written just past the boot blocks. This string "preloads"
the userconfig input buffer and is parsed as user input.
If the first command is not "USERCONFIG", userconfig will
treat this as an implied "quit" (which is why you don't need
to scream - you never even know you went through userconfig
and back out again if you don't specifically ask for it),
otherwise it will read and execute the following commands
until a "quit" is seen or the end is reached, in which case
the normal userconfig command prompt will then be presented.

How to create your own startup sequences, using any boot.flp image
from the next snap forward (not yet, but soon):

% dd of=/dev/rfd0 seek=1 bs=512 count=1 conv=sync <<WAKKA_WAKKA_DOO
USERCONFIG
irq ed0 10
iomem ed0 0xcc000
disable ed1
quit
WAKKA_WAKKA_DOO


Third, add an intro screen to UserConfig so that users aren't just thrown
into this strange screen if userconfig is auto-launched. The default
boot.flp startup sequence is now, in fact, this:

USERCONFIG
intro
visual

(Since visual never returns, we don't need a following "quit").

Submitted-By: phk & jkh

Various cosmetic tweaks.

Syncronize my tree so Eric can access the latest code.

Temporarily disable userconfig saving until I figure out why uc_open()
loops internally for BOOTMFS (not being able to run gdb on sysinstall
when it's running as init is a real pain!).

Check return values from uc_open() correctly. Note: This seems to work
really well when running the GENERIC kernel but not with the BOOTMFS kernel.
Further work is needed.

First cut at a "copy userconfig changes from installation kernel to installed
kernel" mechanism. This is just the foundation - more work follows
and will be committed over the next few hours.
Submitted-by: "Eric L. Hernes" <erich@lodgenet.com> & jkh

One small policy tweak to something I like better.

Fixes and a place-holder for future work.

Round 2.5

Saner screen refresh changes, part I.

Correct a minor misspelling.
Noticed-by: der

Try to make screen update more efficient (less flickering) by more
judicious use of dialog_clear_norefresh().

Don't munge keystrokes.

Detect which partitions have already been created with `auto' so as not to create them
twice.

Various cosmetic tweaks.

1. Fix the CD installation bogon for Novice install I mentioned.
2. Add some code for dealing with a ports collection on the second CD now.

Fix a bogon in the Novice mode CD auto-selection.

Fix something I broke with CDROM installation (well, I knew my first
test CD would turn at least one bug up :-).

A number of improvements in the way statistics are printed, add a "chroot"
option for installing distributions and/or packages to somewhere other than /,
say for a case where you're installing to an external disk on some other
machine's behalf. More miscellaneous fixes to various problems I stumbled
across while adding this stuff.

Don't freak out at the lack of root/swap/usr if we're running multiuser
and simply adding another disk.

Fix even more lurking bogons - why do I never find these until the last
possible minute? :-)

Whoops! Now that I'm decompressing docs into /tmp, it's important to
make sure that /tmp is there first! :-) While I'm at it, clean up the
somewhat inexplicably bogus Mkdir() function.

Support compressed doc files again.
Add a few strategic screen clears.
Do a lot less wasted screen I/O in restoring screen contents that don't need
restoring.
Use tar instead of cp to back up /etc in installUpdate.
Don't panic when upgrade shell exits.

Fix some minor reported bogons from the BETA

Document shortcuts.
Fix a bug which prevented variables from working properly

Make it plainer how to exit.

Update the Lynx version number.

Make "Fake" turn off more potentially system-nuking options.

Don't use some of the low-contrast text attributes I was using before - they
apparently look bad on some LCD screens. While I'm in there, tweak and adjust
a number of other minor interface details which have been bothering me for
awhile.

Make the editor work again and we're done.

Fix a truly stupid bug which broke the package installation menu
for everything _but_ the multi-user case now (it was the opposite before :-).
That means adding packages with the 2.2-960511-SNAP boot floppy is busted. Feh.

Change some verbiage slightly.

Sha-ZAM!

The root floppy is now gone. I shall not mourn its passing.
Everything we need is on boot.flp or the bindist.

Fix some long-standing malloc bugs in the package handling code (freeing garbage
in one place, leaking memory in another).

Add a facility to invoke subsystems directly by naming them on
sysinstall's command-line when running post-install. A replacement
for pkg_manage might, for example, be `/stand/sysinstall configPackages'

Fix bogon where upgrade shell was entered with tty modes spammed.

Fix bug with release name checking in ftp_strat. Turned a bunch of
bogus exit()s into proper calls to systemShutdown().

Clear the TCP/IP device configuration screen away after we invoke it.

properly reset SYSTEM_STATE after installCommit runs.

More cosmetic changes before tomorrow's snapshot.

Fix more display weirdnesses that only show up during a real installation.

Reshuffle the installation routines a little for greater clarify.

Add some more debugging statements.

Add a new -fake argument to make sysinstall not actually change things while
I'm testing it.

Fix an ancient index list bug.
Make FTP re-initializion work.
Fix fix fix.

Move some of functions around in order to make this stuff easier
to work on.

Bump snapshot release date - looks like I was off by a couple
of days!

More display fixes to sysinstall and assorted tweaking.

Add a place-holder message for the CDROM fixit feature (which I'm not going
to add in time for the next SNAP).

Quite a few changes:

1. Fix the last display bugs (I hope) by use of dialog rebuilds at stategic
points.
2. Clean up the distributions menus so that everybody (that's reasonable)
has All and Clear options for setting/clearing things en-masse.
3. Various attempts at display optimization.
4. Change the wording of the `Don't use Write!' dialogs to make them more
explicitly define when and when not to use the option.

Bring this into sync.

I still have a _very very annoying_ display bug which occurs when a menu
item causes a submenu to be displayed - the screen repaints for the original
menu (which is restored upon return from the submenu) are off by about 4
characters. I've tried restoring the screen, the cursor position, you name
it - same deal. Grrrr! This commit is my first step in trying to get someone
else to help me look into this one since I'm just tearing my hair out at this
point!

1. Update all the copyrights to delete useless clauses 3 and 4.
2. Change more of the menu code over to new system.
3. Streamline label editor.

Major surgery.

1. Use new dialog menu hacks (no strings, just arrays of dialogMenuItem structs)
so that I can create composite menus with radio/checkbox/... items in them,
removing some long-standing UI bogons in various menus. This work isn't
finished yet, but will be done in two phases. This is phase one.

2. Remove all the script installation stuff. I never got time to document it,
it was arcane and it just complicated much of the code. There are better
ways of doing this if I want to do auto-driven installations later.

3. Remove much dead code and otherwise attempt to remove as much historical
grot as possible so that this code is easier to hack on. This is also
a two-stage process, phase one of which is now complete.

Rename the usage of `private' to `private_data' to cope with the
recent libdisk changes. (sysinstall is guilty of using `private' in
quite more places, but since this ain't in library code, it's not that
important.)

Whenever possible, better not use C++ reserved words...

The name of the lynx package has changed - update it.

Whoops! I create the holographic shell too early now - move it after
the chroot. Nice idea, just didn't work (caused shared execs to fail!).

Make the editor a selectable option. Some people don't care for `ee'!

Lots of fixes:

1. Revamp package installer to use new dependency lists and also
pkg_add's new `read from stdin' mode to prevent a copy of the package
from hitting the disk unnecessarily.

2. More fixes for running "not as init" - don't get upset if CDROM already
mounted, do the right thing instead.

3. If running as init, assume first-time install and _don't show the
(W)rite option in the fdisk screen.

4. Many other little tweaks, some of which will have to wait for fuller testing
until I can create a boot floppy (testing certain system-destroying
features of sysinstall can be a royal pain). Expect some more commits.

Miscellaneous cleanup before big round of menu restructuring (to use new
libdialog features).

Add the -u flag to the cpio's used to install the initial files, just
to make sure they will be overwritten even in cases where the've
bogusly got more recent timestamps.

Don't try to swap to a disk that isn't selected.

Update the -current sources from the 2.1 branch.

Approved (in spirit) by: jkh

This mega-commit brings in Jordan's latest sysinstall version..
This looks like it was developed offline, and is being spammed over the
top of the existing. "That's fine by me! I dont really care how you do
it, just get it in there..." said Jordan in a conversation a short while
ago...

Merge RELENG_2_0_5 into HEAD

Remove trailing whitespace.

Whoops! Fix things so that the root.flp also comes over NFS, not just
the distfiles.

1. Fix a looping bogon in configFstab().
2. Fix the gauge.
3. Don't shut down the media device gratuitously after getting the root
floppy - it saves work later.

Sync up my work for the night. This should implement ALL possible
installation methods and provide a fairly robust set of menu options.
This should also fix a few more bugs on Poul-Henning's latest gripe
list.

Shrink the boot floppy by removing all extraneous stuff. Also increase
number of inodes.

Fix various bugs reported by Poul. Implement VTY switching.

Add various missing seat belts.

Fix bogon I introduced into dist extraction code last night.

Update to Poul's latest gripe list fixes.

Sync up with Poul.

Major cleanup. Mediaroutines now get asked about a file. All the
multi part stuff centralized.
The final check is backwards or something so it always said it failed,
even it it didn't.
Fixed tcpip address check to not be stupid, 10.0.255.1 is legal.

Commit parts of reorg that were diffs. Substantially re-engineer the
extraction and mediaGetFTP() handshaking to solve some unexpected complexities.

Clean up the variable handling code a little.
Write /etc/hosts in the right place.

be nice and tell the user when the installation has completed successfully
so they don't just come back to a menu again 2 hours later with no idea
what happened with the operation(s) they had in progress.

Fix a bug in the /etc populating copy.

Change root.flp from a new format CPIO archive to a tar archive.
Unless we're willing to change the main tarballs from tar format to
"newc" (or, even better, "crc") cpio format, we need to use one common
one for all and that's tar for now. Install will now grab "root floppy"
from an ftp site if that's what you've got set.

Fix even more gripes from Poul's list.

P.S. As soon as I get the distfiles copied over to freefall tomorrow
morning, those of you wishing to test minimal installs over ftp should
be able to do so by grabbing the boot floppy and nothing else. Keep
your eyes open for my announcement.

Tighten up the TCP/IP dialog a little.
Simply install procedure a bit.

Totally revamp the TCP/IP dialog; now network selection makes a bit more sense.

Root floppy (which actually may be able to go completely away at some point
soon!) is now loadable from ftp/nfs/dos as well as CDROM and (of course)
floppy.

Fix more problems on Poul's Gripe List.

Bring in all my fixes to Poul's gripe list as of last night.

Cleanup.

Put back some changes that were smashed in yesterday's release tree
shoot-down.

Bring everybody up to date on my morning's work.

1. Fix a few bugs in the ftp installation code and implement proper
ftp and network shutdown routines.

2. Clean up the menus a fair bit - add a FreeBSD configuration menu.

3. Eliminate the last of the "chaining" - the installation now does
the most obvious thing in the most obvious cases and doesn't present
you with more menus than you were expecting. This makes it necessary to be
a little more explicit in places, but it's still less confusing.

4. Add a few more safety nets for the user. Change a few hard-and-fast
limits to warnings (it now runs as non-root, Bruce).

5. Add descriptions for all the supported ethernet cards.

6. Make the cpio floppy extract put up a menu requesting the drive you wish
to use if you have more than one; don't just always assume drive A.

Sync to latest ftp-capable sysinstall. We're getting there!

Add a final configuration menu and the beginnings of the backing code
for it. The ftp installation method is working well enough to test.
Many more bug fixes, says Gary.

Add my first cut at TCP/IP device configuration. If this works, the
ftp installation method should now function. We'll know as soon as my
make release builds the floppies. I'm just committing this out of my
release tree now so that it doesn't get clobbered again.

1. Bring in the first cut of Poul's ftp routines. We still don't
use them yet, but it's close (we're working on the last wrinkles
in the CD install for now).
2. Complete the CDROM installation strategy code.
3. Simplify the distribtuion loading code.
4. General error message cleanup.
5. Write the /etc/fstab file now and split those routines into config.c
6. Clean up the menus a little more.

Implement most of the CD extract code.
Clean up a few last display bugs.
Add sanity checking that makes sure user creates root and swap partitions.
Add swap partitions with swapon().

1. Start syncing up the network strategy code so that folks like Poul and
Justin can see it.

2. Attempt to fix the redisplay problems in label.c some more. Not clearing
the screen each time is certainly faster, but it's causing all sorts of
problems.

Make newfs options work on rootfs.
Add size argument to new_part, so it can come up with a good default for newfs.
Fix (possibly) a dialog botch after label.c's wizard mode.
Make vsystem even smarter abour crunched binaries (what a speedup!)
(You need to recompile crunchgen !)

Now cpio works for me. (it was Mostly confusion about when the chroot
happened)
Make vsystem crunch aware in an intelligent fashion.
make the boot.flp target more specific (and faster).

1. Add MBR type menu to take it off of Poul's "gripe sheet".
2. Syntax correction from Andrey.

Good night! :-)

Don't clear the screen for every redraw in the disklabel and
partition editors (ugh). Fix an utterly bogus message (no arguments :)
in dist.c. This should all make Poul a little happier and slide in
before the next CTM update window.

Change vsystem to know that the shell is crunched in.
Sanitize a couple of messages.

Fix a few message bogons.

Misc cpio evil. I think I'm going to start working locally and just deal
with the diff/CVS hassles - this represents far too many CVS commit
messages for you folks, and trying to document each and every iteration
of the code is a hassle (and not very useful at that).

Whoops - copy_self() was going to the wrong place!
Use proper floppy device names.

Try again to get cpio_extract() to work. Also fix the bogon
I introduced with msgNotify() again. Sigh. I'll get it looking
correct someday!

Clear the screen on msgNotifys.
Don't notify in vsystem() - it obscures the original message.
Put some debugging code into cpio_extract() so that I can see
why it doesn't work now. :(

Don't call mediaVerify() in quite so many places.

1. Fix a pathological bug I introduced in msgInfo(). Right idea, wrong
implementation.

2. Totally rework device registration. It's about half the size and
more powerful now.

3. Add DOS discovery.

4. Start filling in some of the strategy routines.

5. Another clean-up pass over the menus.

6. Make wizard code use Disk typedef.

If I can get the first strategy routine finished tonite, we should have a working
install (from ftp, at least) this weekend.

Totally re-work cpio_extract.
Erase the annoying "Command output is on debugging screen" message
when it's time to switch back.

This doesn't work - the extract code is half-baked. I commit it only
so that Gary can sync to it before I go to bed.. :)

More assorted verbosity. Also don't log informational messages.

1. Copy the boot floppy into /stand before extracting the CPIO floppy.

2. On Justin's advice, remind the user when they should switch back
from the debugging screen, if they're looking over there.

You want to be in /mnt when extracting the cpio floppy, not in the read
only root filesystem.....

Run bad144 on raw-devs.

A couple of tweaks to make bad144 scan run.

Use raw devices for newfs.
Write and wizard mode only on enabled disks.

I had the arguments to Mount() backwards. Argh.

Add some more debugging information and fix a few missing newlines.

Fix a very embarassing typo. No wonder this thing was looping! :-)

Do more proper bad144 handling. Thanks, Rod.

1. Primitive bad144 support (I believe an additional command is needed, but
won't know until Poul wakes up again).
2. Make vsystem() put its output on the debugging fd.
3. DTRT with root filesystem placement - now I see how this has to work
(thanks, Poul).
4. Many miscellaneous spelling errors fixed and general cleanup.

1. Set a path to /stand by default.
2. Don't clear() when I can dialog_clear().

Commit my latest so that Gary can sync up - this version should also
be the grounds for our first round of testing in the release I'm rolling.
It doesn't load the distributions yet, but it should do everything else.

This will now compile and even scribble helpfully on your disks.
It remains to be seen how successfully. The distribution loading code
is still not here yet, but the partition/newfs/mount/cpio-extract cycle
is as complete as it's ever going to get, modulo possible bug fixes.
The TCP/IP setup screen is also sort of here, albeit in a highly-changing
state due to the fact that per-interface information isn't being kept
right now but is being added (thanks, Gary!).

This does _not yet compile_; I'm simply bringing in my changes from
this weekend in order to more easily sync with my CVS tree at home.
Another commit relative to these changes will follow shortly.

1. Don't check CHUNK_BSD_COMPAT for now; it always returns "no" and is
getting in the way of testing right now.
2. Call system() on commands, not vsystem(). No need for vsystem() here.
3. Add a path for the shell.

Clean this up a bit - add more documentation to the documentation menu.

First round of changes after testing this on actual systems. Clean up
some of the badly displayed menus, use the proper notification box for
messages, make proceed work.

Sync these up so that they'll get into my CVS tree at home, where I'll continue
working on the distribution extract stuff.

Perform a much needed tidying-up pass over this code. Sleep for now,
more tomorrow.

Ok, we should now create all filesystems, mount them and extract the
cpio floppy at this point.

Another sync up for Poul. Added a lot more error checking.

Some fairly serious cleanup. The proper offset should now be used in
creating partitions. Still need to get the mount points displaying carefully,
but I need to get this into my tree on time so that I can work on that.

All the editors are finished. Now if I can just get a problem with libdisk
fixed, we should be able to fully set up the user's disk. Still to come
with next commit: filesystem setup, distribution extraction, final
configuration.

Everything but the partition editor is done. This commit is for MBR testing.

This will now write MBR entries - should be enough for testing.

My latest round of changes - make the "slices" editor work.

Commit my latest changes before having a nap. Still not close to done,
nor is it in sync with my working sources, but it leaves me less CVS hassles
to bring in the new files at this time. Still no documentation to translate
quite yet, but soon. This stuff is actually very close now.

o Add extra menu types (radio implemented, multiple choice shortly).
o Make the framework generally more robust.
o Figured out how to nest the menu descriptions - no more grotty initialization
of menus.
o Fix bug with helpline and helpfile not being reset.
o Add stubs for the media selection code.

Coming next: Fdisk and disklabel screens using Phk's new libdisk stuff.

Latest raft of changes.

Added another couple of menu item types.

Reshuffled the menus and added a few more. Sure wish I could figure out
how to initialize a menu with _one_ initializer rather than two! :(

This commit was generated by cvs2svn to compensate for changes in r8097,
which included commits to RCS files with non-trunk default branches.

Here is my first "framework" commit of the new sysinstall. There is a LOT
more to come in the next 24 hours, this is just the first stable result of
8 hours of hacking so far. The specification format for menus is pretty
much hammered out and the beginnings (very humble) of the doc hierarchy
are present for an example. It should be quite easy to add a lot more
menus quickly to this since I did go somewhat out of my way to make the
framework easy to work with. This is NOT the glorious semi-graphical
sysinstall (or whatever its name will be) that the install-geeks are working
on, this is simply the "son of sysinstall" I've been promising to write in
the interim for 2.0.5 and 2.1R (super install doesn't come until 2.2R).