and without Kerberos 4 & 5 (MKKERBEROS=no). Previously checkflist
complained of missing files.
* move kerberos- and kerberos 4-only files into new flists,
distrib/sets/lists/*/krb.*
* make the flist generators grok MKKERBEROS{,4} variables
* fix Makefiles which treat MKKERBEROS=no as MKKERBEROS5=no.
9 out of 10 experts agree that it is ludicrous to build w/
KERBEROS4 and w/o KERBEROS5.
* fix header files, also, which treat MKKERBEROS=no as MKKERBEROS5=no.
* omit some Kerberos-only subdirectories from the build as
MKKERBEROS{,4} indicate
(I acknowledge the sentiment that flists are the wrong way to go,
and that the makefiles should produce the metalog directly. That
sounds to me like the right way to go, but I am not prepared to do
revamp all the makefiles. While my approach is expedient, it fits
painlessly within the current build architecture until we are
delivered from flist purgatory, and it does not postpone our
delivery. Fair enough?)
Uses a hook in spec_strategy() to save data written from a mounted
file system to its block device and a hook in dounmount().
Not enabled by default in any kernel config.
Approved by: Frank van der Linden <fvdl@netbsd.org>
print a summary rather than the full (and not usually desired) output
of netstat -inv. The old behavior can be returned by simply setting
full_netstat to YES in daily.conf.
Original idea by me, cleaner and more correct execution via small awk
script from Greg Woods.
add some example country codes, and use disjoint CNAMES by default, as
discussed in PR misc/23283 (by Adrian 'Dagurashibanipal' von Bidder),
the pool.ntp.org mastermind and maintainer).
- use ttyC[0123] for DCA and APCI with MI com(4)
- use ttyM[0-f] for DCM instead of tty0[0-f] to avoid confusion with MI com(4)
- create the foloowing symlnks to compatibility:
tty0 -> ttyC0 (for DCA)
ttya0 -> ttyC1 (for APCI)
ttya1 -> ttyC2 (for APCI)
ttya2 -> ttyC3 (for APCI)
tty0? -> ttyM? (for DCM)
- note the above symlinks should be removed after the next release
As per discussion on recent port-hp300 (ok'ed by thorpej).
When /dev is an fdesc, and /dev/tty is stat()ed without a controlling tty,
a "Device not configured" error is returned.
Filter mtree's stderr to ignore this error.
If fdesc is fixed to not behave in this fashion, this workaround can
be removed; bin/12900 should remain open until that time.
Make ls -A explicit, to help n debugging when not run as root
(-A is implied when ls is run as root)
Ignore dotfiles, as they are not mailboxes (e.g. .jhawk.pop)
* Restore previous functionality which supported running postinstall
with an extracted etc.tgz set as the "source" directory (i.e,
/usr/src isn't available). We do this by generating the MAKEDEV
to ${SCRATCHDIR} if the real source is available, and leverage off
the compare_dir() code that the rest of postinstall uses to support
this functionality.
* Don't special case MACHINE_ARCH==arm; the MAKEDEV.awk should
be doing that since etc/Makefile doesn't have similar special
case code. In any case, AFAICT the only MACHINE_ARCHs are
"arm" and "armeb"; there is no "armel" in NetBSD.
to generate the MAKEDEV to scratch dir and compare that with the currently
installed /dev/MAKEDEV; also add -a MACHINE_ARCH option to explicitly
set machine architecture for non-native builds
problem with postinstall pointed out by Patrick Welche and Hubert Feyrer
in private e-mails
add some more necessary device entries
introduce makedisk_minimal() and use it to create the CD-ROM & md entries;
this procedure only creates 'a' and RAW_PART device entries
remove pf from 'all' target - it's not part of tree, so shouldn't be
created by default
at MAXPARTITIONS/OLDMAXPARTITIONS in kernel sources, so that it wouldn't
need to be specified separately in MAKEDEV.conf
change platform MAKEDEV.conf to contain only MD targets and nothing else;
simplify the parsing in MAKEDEV.awk accordingly
for tty0[0-9]
as pointed out by David Laight
remove spaces between makedisk_p*() functions, so the output script looks
neater once some of them are filtered out
when filtering the template, leave only the wanted makedisk_p*() routine
in the output
as pointed out by David Laight
also make it mandatory for MACHINE and MACHINE_ARCH to be set in
environment; it would be possible to use use uname -p/-m, but better
to catch possible cross-build mistakes sooner than later
