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.
*BANG* *BANG* *BANG* *BANG* *BANG* *BANG* *CLICK* *CLICK* *CLICK*
Death to the stripped down BOOTMFS kernel for boot floppies and all the
cruft that goes along with it.
a list file suitable for use with libstand's splitfs filesystem. The first
chunk of the file is 16k and has an extension of '.boot' and is meant to be
placed on the boot floppy. This is required because the current
implementations of gzipfs and bzipfs in libstand want to read in the header
of the file each time it is opened.
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)
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.
package set. More robust than others already in the tree, but a bit
crufty as this was mostly written in the Walnut Creek CDROM days.
Sponsored by: FreeBSD Mall, Inc.
that a) was from this century, b) is not Opera, and c) doesn't require
KDE.
- Don't include the compat22 libraries unless the PKG_ARCH is i386. Same
goes for compat3x and compat4x for i386 and alpha.
- Define PKG_ARCH and make it overridable in the environment.
generates a file which will be installed as DRIVERS.TXT in the
floppies directory so that users know which device drivers are
included on drivers.flp, and whether or not they need to worry about
it.
Reviewed by: ru
Approved by: re
1. On disc1, print/acroread4 for alpha and print/acroread5 for i386
replace print/acroread, which was not compatible with the linux_base
that we ship by default. Remove print/acroread4 from disc3 as
redundant.
2. www/linux-netscape47-* were removed due to security holes;
substitute www/netscape48-* on disc1.
3. Add www/opera to disc1.
Approved by: re (murray)
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.
release/${TARGET}/drivers.conf file which list drivers that have to
go into the third floppy.
Also shuffle i386/drivers.conf so that the floppies don't overflow
anymore. Anybody with real/better usage statistics is welcome to
shuffle it differently.
Reviewed by: ru
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>
very large package is exactly the kind of thing that users buy the
CDs for, so leaving it off of a 4 CD set is very bad.
* Properly quote the last security/sudo entry.
* Add a comment in the CDROM #2 section explaining that packages don't
typically go on this disc.
- 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.
- build_x.sh now does all the steps to build an X dist rather than being
a child script of package_x_dists.sh
- Update the usage information to list the ports you need to install
before running this script as well as needing to set CVSROOT.
- Make sure CVSROOT is set. If not, exit with an error.
- We now take two parameters: a work directory and an output directory.
The work directory is used as scratch space. All of the bindist will
end up in the output directory.
- Only apply XF86.patch to the checked out XFree86 port if it exists.
- Use XFree86's build-bindist tool to package up the dists using their
distfiles rather than using our own packing lists that have to be
manually updated each time the port changes.
Example usage:
env CVSROOT=/home/ncvs ./build_x.sh /usr/xtmp /usr/x11dists
* Rename cvsup-bin to cvsup (cvsup-bin does not exist anymore).
* Add the net/rsync port to the CDROM packages.
* Add the misc/compat* ports.
Approved by: jkh
from the build cluster. These are required to get the dependencies the
same as the parallel builds.
- Add an optional second argument that allows you to specific an alternate
ports directory.
- Remove the temporary file after we are done with it.
- Remove ksh93 because it won't make it on the discs until the license issues
are resolved.
Approved by: jkh
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
Dike out support for DEC3000/300* Pelic* and the DEC3000/[4-9]00
Flamingo/Sandpiper families, SLIP, lance Ethernet (especially since `le'
based Alphas are diked out now too), POSIX P1003_1B real-time extentions,
and last but not least "NOBLOCKRANDOM" since the random device is removed.
This lets us fit [barely!]:
Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted
/dev/vnn0c 1407 1386 21 99% 6 24 20% /mnt
*** Filesystem is 1440 K, 21 left
*** 80000 bytes/inode, 24 left
Created /R/stage/floppies/kern.flp
Remove `pmtimer' from the MFSROOT kernel as `apm' is already removed.
`pmtimer' also removed from the Alpha kernel incase it ever winds up there.
(could it ever?)
SCSI card (should it ever find its way into GENERIC); LPT (we don't need
to print during install time); the parallel 'geek' port; generic USB
driver (thus some attached USB devices will not be detected and thus the
user may wonder what is going on, we couldn't do anything with the device
if only ugen attached to it anyway and we are getting very, very low on
available space; USB "Human Interface Devices" as we don't do anything
with them during installation; and USB printers (same argument as LPT).
