- 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
