man, misc, and text sets (i.e. all non-X11 sets).
This support currently allows two make(1) targets to be executed from
src/distrib/syspkg/sets:
a.) `make register' will register the existing system as packages.
This willl allow the version of software on the current system
to be queried with
PKG_DBDIR=/var/db/syspkg pkg_info
and individual packages to be deleted with
PKG_DBDIR=/var/db/syspkg pkg_delete <pkgname>
b.) `make package' will create binary packages from the existing
system (or from the contents of ${DESTDIR}, if ${DESTDIR} is
set). These packages can be taken to another system, and
installed with
PKG_DBDIR=/var/db/syspkg pkg_add <pkgname>
to update or install specific packages.
The need to explicitly specify the syspkg PKG_DBDIR will be replaced with a
flag for the various pkg tools in the next few days.
unconditionally.
Avoid running the crunchgen command multiple times for each dependent
target by marking only one target (instbin.mk) for unconditional re-make.
This is the latest version of <bsd.syspkg.mk>, and forms the basis of
NetBSD System Packages (syspkg). Further development of this codebase
will occur within TNF's cvs repository, and copyright will be assigned
to TNF when the relevant paperwork is complete.
macppc/hardware
Forgot to put PowerComputing PowerCenter in list of models that can't use
on-board video
macppc/prep
Reword four-key-combo c-o-O-F to imply you need to hold all four down
until the 0 > prompt appears, also a better description of the keys
shuffle System Disk instructions around a little to make more sense
Fix BootVars instruction to "uncheck auto-boot?"
Change '.Dl 0 \*> Ic "..."' to '.No 0 \*> Ic "..."' surrounded by .(disp
Link to new FAQ entries (such as how to use the Open Firmware environment
and instruction for people unfamiliar with MacOS)
Describe how to prepare an MS-DOS filesystem for booting
Be more consistent about "ISO9660"
The NetBSD/macppc boot CD-R image has "partition zero" bootloader and
XCOFF bootloader to work on all models -- this is described better now
Better info on how to netboot OF 1.0.5 systems
Mention that UFS is not currently supported by NetBSD and MacOS < 10
Detab the dhcpd.conf example
Add .To 2 tags for preparation of bootable media subsections
macppc/install
Change '.Dl 0 \*> Ic "..."' to '.No 0 \*> Ic "..."' surrounded by .(disp
Added new and very very useful "Open Firmware boot syntax" section
describing how to determine the OF boot-device and boot-file
Clean up examples of boot commands
Update descriptions of booting problems (some were incorrect)
Add .To 2 tags for OF boot command subsections and common problems
tweaks to the "Quick install for the impatient", particularly changing the
recommendation to MS-DOS floppy with bootloader and kernel instead of
boot floppy image
common/sysinst
add .To 2 tags for macppc-specific sections
common/postinstall
change tlp0 to de0 in description of typical ethernet interface
listpkgs -- a utility script for syspkg maintainers. Given a pkgset name,
list all packages in that pkgset by parsing the src/distrib
set list files. Imported at draga.com revision 1.2.
Usage: ./listpkgs [-a arch] [-m machine] [-s setsdir] [-p prefix] setname
-a arch set arch (e.g, m68k, mips, powerpc)
-m machine set machine (e.g, amiga, i386, macppc)
-s setsdir directory to find sets
setname set to list packages for
makeplist -- a script called by <bsd.syspkg.mk>. Given a pkgset name
and a pkg name, output a valid PLIST for that package by
parsing the src/distrib set list files. Imported at
draga.com revision 1.2.
Usage: ./makeplist [-a arch] [-m machine] [-s setsdir] [-p prefix] setname pkgname
-a arch set arch (e.g, m68k, mips, powerpc)
-m machine set machine (e.g, amiga, i386, macppc)
-s setsdir directory to find sets
-p prefix prefix for created plist
setname pkgname set and package to build plist for
* Regen files with proper OS names and version numbers.
* Clean up toolchain2netbsd somewhat, to get it ready to be cross-host
compatible (more work to be done here, but it's getting closer).
* Add framework for gdbreplay and gdbserver, but hold off on enabling these
by default until low-nbsd.c is verified to work everywhere.
address parts of PR toolchain/14896. This header file is nonstandard
(and doesn't even exist in gcc 3.0); an out-of-the-box gcc build also
doesn't provide the missing functions. So just drop the .h completely.
Don't error out if DESTDIR exists.
Use "find -s" instead of "find | sort"
While here: Drop syssrc/usr.sbin/dbsym from syssrc.tgz, since it has been
replaced by gnusrc/gnu/usr.sbin/dbsym.
XXX: Add gnusrc/gnu/usr.sbin/dbsym (and libbfd)?
When doing a UDP NFS mount, ask if "small transfers" (i.e.,
-r 1024 -w 1024) should be used; this is necessary when
the client and/or server has a feeble network card.
1. Replace all "groff"'s with $GROFF so the right binary is picked up depending
on new or old toolchain setups and USETOOLS
2. Remove the DESTDIR check where it adds -M. This is pointless as some of the
file in share/tmac have hard coded references to /usr/share/tmac so using the
new ones in $DESTDIR will just point you back into /usr/share anyways...
(the new toolchain has no issue here as it's tmac files all point into
$TOOLDIR. Any old setups should just depend on the local setup instead of
some mix of DESTDIR and old files the -M would have produced).
- Use new boot system. Bootfloppies now use ustarfs.
- Split instkernel.* directory from bootfloppy.*.
- Adjust ramdisk size.
- others.
2-floppy installation system cannot be compiled due to size bloat.
Disabled temporarily (?).
release notes (and thus missed updating the NetBSD/evbarm notes):
Based on feedback (various), remove the .toc files from CVS,
and instead generate them each and every time (twice!).
Mention how to manually create /dev entries, since the suggested "Re-install
sets" option doesn't automatically do this (leaving the user without
/dev/console)
fleshing-out (and general "how to set up diskless environment"
instructions in the ../common directory).
Supported hardware and setup for the Intel IQ80310 board is written.
I've filled in the supported-hardware bits for the ARM Integrator
board, but someone (HI RICHARD! :-) will need to provide info about
setting up the firmware for booting and typical run-time environments
for this board.
and instead generate them each and every time (twice!).
Based on a suggestion from Alan Barrett, allow setting MAKETOC=no
to permit rebuilding the install notes without regenerating the
.toc files, to allow more speedy debugging of markup changes.
mrg