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

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

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

Approved by: re (implicit)

Specify 4096 block-size and 512 fragment-size.
This fixes no space error.

Due to some recent-ish work on GEOM/G_PART the c partition (by tradition
the whole disk) isn't available any more since it was redundant. Just
use /dev/md0 instead of /dev/md0c to build the filesystem on.

Consulted-with: marcel

Back out v1.57, the underlying problem that caused a delay between
mdconfig and the device name appearing in /dev seems to be fixed.

Allow MFS images to be built without a disklabel for releases
that don't require one i.e. PPC.

Reviewed by: ru
Submitted by: ssouhlal

I should have marked my previous commit with an XXX to indicate it's a
workaround to a problem that shouldn't exist.

Noticed by: ru

I've had 'make release' problems on a large/fast dual processor machine
with doFS.sh consistently dying here because the device didn't exist
in the namespace fast enough after doing the mdconfig. But the device
did eventually show up. There have been similar complaints on mailing
lists that might boil down to this being the problem too.

This is obviously a hack, if anyone knows what might cause a delay
between mdconfig running and when the name appears in the /dev namespace
(inside a chroot-ed environment if that matters) I'd be happy to back
this out.

- Removed more bitrot (the "while" loops).
- Factored out common parts of dofs_vn() and dofs_md().

GC some old cruft.

Fix this script to produce working bootable floppies on 4.x.

Add support for automatically computing the required file system
size and average inode size.

Reviewed by: jhb

disklabel(8) is spelled bsdlabel(8) or sunlabel(8) these days.
Also make sure bsdlabel(8) (along with the disklabel(8) compat
link) still appear on the fixit floppies of platforms that use
it natively (alpha, i386, and pc98).

Approved by: re (scottl)

Revision 1.49 broke snapshot building on older systems.

Approved by: re (scottl)

The disc1 package set has overfilled the disc. Axe linux-netscape-navigator-4.8
to free up space. linux-netscape-communicator-4.8 remains and is a superset of
the former for those who are stuck are the 1990's =-)

Use UFS1 for the floppies instead of UFS2

Presumably fix sparc64 "make release". (The breakage was due to
sunlabel(8) no longer being linked to disklabel(8).)

Reviewed by: phk

Fixed dofs_vn(): previous revision ran ``rm -f /dev/*vnn*'' too early.

Unmount the file system and detach an underlying memory disk even
if the script fails somewhere in the middle.

Prodded by: phk

Pass the target machine architecture down to disklabel(8).
Do it so that systems without the -m option in disklabel(8),
e.g. 5.0-RELEASE, can still build current snapshots.

While here, drop the -s option from doFS.sh; we have not
been using the .size files for a long time.

Stay consistent with dofs_md().

This took longer to test than expected:

NODEVFS cleanup: don't bother with MAKEDEV.

Look for /boot/boot first, and arrange disklabel arguments accordingly.

Add the necessary tweaks for FreeBSD/ia64 releases. Note that this is
in no way final. A typical ia64 wart is that there are no boot blocks.
Instead, we need to create disks with EFI partitions if we want auto
boot to work. All this functionality is not present yet.

boot2 does not exist on some platforms.

Milestone #1 in cross-arch make releases.

Do not install games and profiled libraries to the ${CHROOTDIR}
with the initial installworld.

Eliminate the need in the second installworld. For that, make sure
_everything_ is built in the "world" environment, using the right
tool chain.

Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the
buildworld process into stages, and skip some stages when
SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5
dists).

Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running
makewhatis(1) at the end of installworld (used when making crypto,
krb4, and krb5 dists).

In release/scripts/doFS.sh, ensure that the correct boot blocks are
used.

Moved the creation of the "crypto" dist from release.5 to
release.2.

In release.3 and doMFSKERN, build kernels in the "world"
environment. KERNELS now means "additional" kernels, GENERIC is
always built.

Ensure we build crunched binaries in the "world" environment.
Obfuscate release/Makefile some more (WMAKEENV) to achieve this.

Inline createBOOTMFS target.

Use already built GENERIC kernel modules to augment mfsfd's
/stand/modules. GC doMODULES as such.

Assorted fixes:

Get rid of the "afterdistribute" target by moving the single use
of it from sys/Makefile to etc/Makefile's "distribute".

Makefile.inc1: apparently "etc" no longer needs to be last for
"distribute" to succeed.

gnu/usr.bin/perl/library/Makefile.inc: do not override the
"install" and "distribute" targets, do it the "canonical" way.

release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and
catpages appear in the right dists. Note that because Perl does
not respect the MANBUILDCAT (and NOMAN), this results in a loss of
/usr/share/perl/man/cat* empty directories. This will be fixed
soon.

Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it
means "make KerberosIV"), as documented in the make.conf(5)
manpage. Most of the userland makefiles did not test it for "YES"
anyway.

XXX Should specialized kerberized libpam versions be included into
the krb4 and krb5 dists? (libpam.a would be incorrect anyway if
both krb4 and krb5 dists were choosen.)

Make sure "games" dist is made before "catpages", otherwise games
catpages settle in the wrong dist.

Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>

Don't print out 0xaa55 at the end of a vnconfig disk and use the
"canonical" disk name when calling disklabel so that disklabel auto works.

- Remove the -T from the 4.x newfs as well.
- Don't write out 0xaa55 to the end of the filesystem as md(4) doesn't
generate that warning and it breaks 'disklabel mdX auto'.
- Use the 'canonical' disk name mdX instead of /dev/mdX to disklabel so
we can use disklabel auto for mfsroot filesizes that aren't a standard
size in /etc/disktab.

The -T argument to newfs is only needed if teh disk isn't already labeled.
Since we run disklabel before newfs, this doesn't apply in this case.

Use the md device not olny a version of the system is 5 but 5 and over.

Requested by: matusita
MFC after: 1 day

Use the vn driver on a stable system.

Add FreeBSD IDs to some files and make the others consistent in style.

Everyone that has commented seems to agree `-m 0' will cause no problems.

Remove tunefs'ing that was OBE by rev 1.30.

Submitted by: bde

Warner gave a nice followup in email, and I thought it would be nice to
get it in the CVS logs. This pertains to rev 1.30 (and the MFC of it):

Space optimization forces the kernel to always use fragments to store
parts of file, rather than using an entire block when less than an
entire block has been written. This forces files to be as small as
they can be at the minor cost of time to do all the fussy stuff. The
cpio image that we put on the disk was so close to filling the disk
exactly that this minor minor difference made a big difference. The
system changed things to time optmization on the first write. When
the end of file was hit, it tried to allocate a full block (4k), but
there was only 3k left on the disk (since you get only 1407 blocks on
a 1.44 floppy) so it failed. So this change nails the space
optmiziation in place for the whole operation.

newfs with `-m 1'

This is needed even with `-o space' as the kernel decides to be "helpful"
and not really do space optimization. Looking at src/sys/ufs/ffs/ffs_alloc.c
we see why: if (fs->fs_minfree <= 5 ||
fs->fs_cstotal.cs_nffree >
(off_t)fs->fs_dsize * fs->fs_minfree / (2 * 100))
break;
log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n"

I have picked `1' vs. `0' just incase some code somewhere has the assumption
the %free can never be `0'.

Helped with understanding why -m 1 made a different: imp

Use mdconfig/md instead of vn.

Using `r'aw device name is out of vogue now.

MFS: comment character and readability fixes.

Moved driver modules for some PCI NICs and PCCARD-only NICs to mfsroot.flp.
http://people.freebsd.org/~hosokawa/driver-floppy/ for details.

Reviewed by: current@FreeBSD.org

We don't do blockdevices any more.

XXX: should use /dev/MAKEDEV

don't mknod stuff without making sure it's not there first.

Make it possible to make release on archaic kernels.

1. Adjust fs sizes to get floppies back under control.

2. Viciously slash all CD support out of boot.flp. It's basically just
a net boot floppy now.

Replace /mnt with ${MNT}

PR: misc/7965
Submitted by: Junji SAKAI sakai@jp.freebsd.org

Hammer on the boot floppy generation bits some more. This is looking
a little better.

Update this to deal with new boot block placement.

Reported by: "John W. DeBoskey" <jwd@unx.sas.com>

Put mfsroot.gz on yet another filesystem so that the boot blocks
can really read it. Hmm. I have no idea *how* this worked in our
earlier tests on the x86. :)

Null commit to commemorate the momentous occasion of the repository
copying of these files from the parent directory. Let us all now
observe a brief moment of silence. OK, that's long enough.

Jordan will adjust the Makefiles appropriately and then "cvs rm" the
originals.

Updates for Alpha.

Whoops, correct brain-o.

Add a tweak for the alpha.

Make the vn device that is being used to build the floppies configurable.
You can now do something like "make release VNDEVICE=vn1". This makes it
possible to do something else with vn0, for instance building another
release.

1. Sync ABOUT.TXT changes.
2. Go back to using a filesystem on the boot floppy; the rawboot boot blocks
were just too non-functional for other things.

Simplify the disklabel trickery, and thus avoid the dreaded
``Operation not supported by device''.

Requested by: jkh

Try to impreve DD mode.
Try to make 4Mb floppies work again.

Purely cosmetic cleanup.

Installation cleanup, round II.

Some release changes I've had to make in dealing with the floppy space
crisis.

Make the reduction algorithm to tune the file system size less
aggressive, in order to avoid /mnt: file system full problems.

Introduce a deadlock counter.

Turn off echoing again, it's cluttering the screen/log.

Gross hack to avoid the `vn0: invalid primary partition table: no magic'
warning.

Seems that doFS.sh is now doing the job...

Remove phk's errr... interesting idea of slicing a floppy into 10
cylinder groups. :)

I belive this works now.

Shrink BOOTMFS kernel further. Make doFS.sh more intelligent.
boot4.flp should work fine as far as I can tell.

Don't make the fs-image in /dev :-)

Moved doFS into shell-script so we can be more smart about it.
make two boot floppies, one without help files for 4MB systems.
Mine's loading one now. :-) -O2 may be needed.