the vein of my previous, recent commits.
Updated release notes: Augmented sha(1)/rmd160(1) note, updated pf(4)
pseudo-users, retweaked doscmd note to reinstate a missing word I
deleted by accident [1] and add some more info.
MFCs noted: ppp(8) LQM, ppp(8) set rad_alive.
Pointed out by: "Eagle Eyes" ru [1]
changes, although one release note, about udav(4) promiscuous mode,
was deleted as it was redundant (the driver itself is new and this
fact has its own note).
hasn't been any package build for ia64 for a long time and in this
case it means that the cdrtools package on the FTP sites is one that
doesn't have mkisofs. This breaks the release build. By trying to
build the port first, we protect ourselves a bit more against this.
- Make "die()" more verbose.
- Do not put extra blank lines into the output file.
- Normalize text by using numeric entities because
some characters such as "'" can break the generated SGML.
Reviewed by: simon
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.
to subordinate make(1) invocations through MAKEFLAGS, we cannot add
CFLAGS onto the make(1) command line. This will conflict with the
individual makefiles wanting to append to it, which is not respected
when CFLAGS is given on the command line. Hence build breakage.
So, put CFLAGS in the environment instead.
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
manual pages, to avoid duplicating work between the Hardware Notes and
manual pages.
Each text line in the output from the manual page parser is generated
as a SGML entity, making it possible for translators to only translate
lines which actually contains English text (this neat idea came from
hrs).
To determine which drivers are usable on which architectures the
dev.archlist.txt file is used to explicitly list this. It it an
imperfect solution, but the best I have been able to come up with for
now.
This commit converts most of the devices which has a section 4 manual
page with a HARDWARE section to be the new auto generated format.
Reviewed in principle by: ru, hrs, trhodes
Good ideas for improvements: hrs
No objections: -doc, re
some unknown reason, when LOCAL_PATCHES and LOCAL_SCRIPT were originally
added, they were silently ignored if the actual file did not exist. As a
result, if one mistyped the pathname to a patch or script, then the release
silently succeeded. However, it was not built with the desired changes and
no warning was given to inform the builder either. This commit explicitly
checks to see that all of the defined patches and scripts exist up front
and bails if any of them do not exist. I lost several hours of valuable
sleeping time this evening due to this "feature" so I've finally gone and
ripped out. I've tripped over this in the past several other times as
well.
Glanced at by: scottl
we only pay attention to it during release time and at the moment it's
a -stable release in progress.
This is a MFS I guess, moving rev 1.536.2.113 to HEAD. I ran out of
time to follow through with doing this last night. Sorry for the delay.
Adding a couple of variables to make tweaking the CD-ROM label and .iso
filenames easier.
acpi_asus(4) added,
versrcreach option of ipfw(4), and
Israel Hebrew locale he_IL.UTF-8 added.
Update release note:
The random ephemeral port allocation can be disabled using
the net.inet.ip.portrange.randomized sysctl.
MFC:
ng_hub(4),
vr(4) polling support,
per-interface polling(4) support, and
random ephemeral port allocation.
DA_OLD_QUIRKS removed,
RFC 1948 improvement,
random ephemeral port allocation from OpenBSD,
df(1) -c option added,
rarpd(8) fix when an iface with more than one IP address, and
OpenSSH 3.8p1 -> 3.8.1p1.
acpi_toshiba(4) video switching support,
getvfsent(3) removed,
sx driver added,
pci(4) bus resource and power management updated,
per-interface polling(4) support,
ata(4) early support for Promise SX4/SX4000,
dump(8) and restore(8) -P option,
make(1) .warning directive,
ACPI-CA 20040402 import, and
CVS 1.11.15 import.
Update release note:
Use &man.twa.4;.
VIA C3 Nehemiah's hardware RNG support,
nge(4) VLAN support bugfix,
rl(4) polling support bugfix,
ste(4) and vr(4) polling support,
twa driver,
bsdlabel(8) -f option,
bthidcontrol and bthidd for Bluetooth HID,
doscmd removed,
fdcontrol(8), fdformat(1), and fdread(1) now work on FreeBSD/pc98,
find(1) -acl option,
UTF-8 versions of the supported system locales,
netstat(1) now displays the multicast group memberships,
pgrep(1) and pkill(1),
ps(1) supports more POSIX/SUSv3 compatible options,
Heimdal Kerberos 0.6 -> 0.6.1,
libpcap 0.7.1 -> 0.8.3,
OpenSSL 0.9.7c -> 0.9.7d, and
tcpdump 3.7.1 -> 3.8.3.
Update release note:
Sort ctau(4) entry in the alphabetical order.
isp(4) fix on sparc64,
ipcs(1) -u option,
rmdir(1) -v flag,
rc.d/diskless split,
rc.d/pf.
Update release note:
MFC of umass(4) timeout/ATAPI MMC support,
items related to the rc.d scripts moved into a separate section.
+ declare some shell variables as 'local'
+ add a missing ';;' in a 'case' statement
+ centralize newfs options
+ properly override GID and UID when installing include files and libraries
+ add a missing '-r' in disklabel commands (maybe not necessary, but it
does not harm and it was used in the RELENG_4 version)
+ no more require 'perl' when installing the secondary loader
+ use '-t rsa1' when invoking ssh-keygen
rdp(4), le(4), stl(4), stli(4), ctx(4), spigot(4).
Take a guess that the following devices correspond to removed drivers
and blow their entries away too: "Genius and Mustek hand scanners"
(gsc(4)?) and "GPB and Transputer drivers" (gpib(4)?).
64-bit time_t on FreeBSD/sparc64,
em(4) hiccup during ifconfig em0 alias fixed,
ng_vlan(4) netgraph node type,
umass(4) ATAPI MMC commands support,
rc.d/gbde_swap and gbde_swap_enable in rc.conf,
mountd(8) -p <port> option,
nologin(8) syslog support,
OpenBSD's pf and the related userland utils imported,
SIZE attribute in distinfo enabled by default.
(when you find errors or inappropriate descriptions, please let me know.)
porters-handbook for 5.2.1 docset.
Made this document apply to 5.2.1-RELEASE as well by noting this in
the abstract and noting errata items that were fixed/addressed in
5.2.1.
These files had tags after the copyright notice,
inside the comment block (incorrect, removed),
and outside the comment block (correct).
Approved by: rwatson (mentor)
- Use the regular forth scripts including the stock device.hints file on
the boot floppies.
- gzip all the various text files on the boot floppy that are larger than
one sector to save on space.
- Generate a loader.conf to load the kernel, acpi.ko, and mfsroot making
use of the 'module_before' variables to prompt for a floppy to be entered
when required and use a stock loader.rc. This enables the beastie menu
on i386.
- PC98 has been changed to split the mfsroot for now so that the floppies
fit. When the PC98 bootstrap is updated to work with ELF files (which
needs to happen anyway), then SPLIT_MFSROOT can be turned off for PC98.
all MFS root options together and in the same order on all archs.
- Drop support for using the no longer existing 2.88 floppy image for CD
booting on i386 via the EMUL_BOOT variable.
- Use a stock loader on the boot floppy rather than one without forth.
- Force the gzip of the mfsroot in release.9 to succeed. This is useful
when doing lots of rereleases when testing floppy changes.
- If an acpi kernel module exists, stick it on the boot floppy and for
now always load it after the kernel.
- Fixed spelling of NO_FLOPPIES to unbreak snapshot building on
architectures that don't support them (as installation source).
- Don't rely on CVS setting execution bits on the shell script.
(This is also consistent with the rest of this makefile.)
Reviewed by: jhb
installkernel.debug target (in the kernel build directory) which is
only defined if the kernel was configured for debugging which it is
not the case for GENERIC kernels on release branches.
*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.
requires minimal care and feeding for future releases.
- Consolidate multitude of floppy related constants down to a normal
FLOPPY set for 1.44 floppies and on PC98 a SMALLFLOPPY set for 1.2
floppies. Also, cleanup the i386 arch section by not duplicating
constants that are the same on both machine types (i386 and pc98).
- Update the ZIPNSPLIT macro to generate a file chunks that will actually
fit onto 1.44 floppies formatted with UFS1. Unfortunately, split(1)
seems to be somewhat buggy, so the files generated are slightly larger
than the argument passed to split.
- Split the release.10 target into 3 targers: floppies.1, floppies.2 and
floppies.3 that are added to EXTRAS only if NOFLOPPIES is defined.
floppies.1 builds the install floppies, floppies.2 builds the fixit
floppy, and floppies.3 generates the md5 sums and READMEs for the
floppies/ directory.
- Drop the by now largely obsolete and less useful boot.flp picture. This
was more useful when the mfsroot lived inside the kernel rather than
being loaded from a separate file by the loader.
- Only build a single mfsroot containing no modules that is used for all
installation methods.
- Use split-file.sh to split up a gzipped GENERIC kernel into however many
floppies it takes for the boot kernel. Currently, a stock 5.2 GENERIC
kernel including WITNESS, INVARIANTS, DDB, and other assorted bloat fits
onto 2 additional floppies besides the boot floppy with some room to
spare.
- If SPLIT_MFSROOT is defined, the mfsroot.gz file is similar split into
however many floppies are needed. Currently it is not defined as the
mfsroot.gz fits onto the current boot.flp with room to spare.
- Add a 'makeFloppySet' target which builds a floppy set for a file that
was split using split-file.sh.
- Rename the doMFSKERN target to 'buildBootFloppy' as that more closely
matches what it does now. We no longer build a custom BOOTMFS kernel for
each boot floppy.
- We no longer build a 2.88 boot.flp image to use with emulated CD booting.
The non-emulated cdboot works for almost everyone who boots off of CD and
if it doesn't work on a particular machine, the user can always boot from
the 1.44 floppy images.
- We no longer build a driver floppy or stick kernel modules in the mfsroot
since we now use a stock kernel when booting from floppy.
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.
dc(4) sparc64/OFW fix, sk(4) multicast fix, IPsec bugfix, ata(4)
bugfixes, GEOM fix, NFSv4 panic fix, NSS large groups fix, CVS
security fix.
Most (but not all) of these are 5.2-RELEASE errata items.
It is required to check /etc/rc.d/ldconfig before use, because
${CHROOT} sandbox is sometimes 4.x world. If /etc/rc.d/ldconfig
is not there, run ldconfig(8) directly.
Discussed with: imp, obrien, ru
and rebuilt some bits with crypto but without Kerberos support
(most notably SSH) during "make release", to put them into the
"crypto" distribution.
Now that we don't ship the separate "krb5" distribution anymore
(it's now part of the "crypto" distribuion), don't waste time
recompiling SSH bits without crypto and without Kerberos support
in an attempt to put them in the "base" distribution -- it just
doesn't work as SSH always uses crypto code.
We avoid this by not rebuilding KPROGS from kerberos5/Makefile in
release/Makefile and adding "libpam" to SPROGS in secure/Makefile
to ensure it's still rebuilt without crypto support for the "base"
distribution. (Disabling crypto (NOCRYPT) also disables building
of Kerberos-related PAM modules, and it's OK to depend on this.)
This should be a no-op change saving some "make release" time.
* Long statements with '\' continuation now use <4 spaces>continuation
consistently.
* wraps some long lines
* More consistent on how very simular repeated commands are wrapped.