While there are some open issues, particulary wrt support of old
NetBSD-specific interfaces, it is better to get the code some public
testing before NetBSD-4 is branched.
${RELEASEDIR}/${MACHINE}. The former is the blessed way as it's
defined as a "subdirectory used below ${RELEASEDIR} when building a
release" and defaults to MACHINE in bsd.own.mk.
Make sure that ${RELEASEDIR}/${RELEASEMACHINEDIR} exists before
installing notes in to it. It only ever worked because ~all ports
build at least one kernel as part of make release, and so the release
directory was created when kernel sets are installed.
XXX: Why don't we create ${RELEASEDIR}/${RELEASEMACHINEDIR} from the
top-level makefile before running make release?
bad output for HTML, and warning for other formats. Fix last line to
have enough empty cells.
XXX: The list of portmasters should be sorted by last name.
gpioow(4), attaching a bit-banging driver via a GPIO pin. Also,
owtemp(4) which supports some of the 1-Wire temperature sensors, including
the DS18b20 and DS1920 - temperatures are returned via the envsys(4)
framework.
Original drivers by Alexander Yurchenko (grange@openbsd), with envsys(4)
support and a fix to the 1-wire search algorithm (for discovering
devices on the bus) by me.
As discussed on tech-kern earlier this week.
1) Add an md_post_extract() function. This function is called after
extracting the sets, and allows the arch to do something at that time.
In the case of prep, it is much easier to install the bootcode after all
the sets are extracted, so we do it in md_post_extract(). Added empty
md_post_extract() functions to all other arches so they compile.
2) Add md_mbr_use_wholedisk() and md_check_mbr(). In edit_mbr() I have
split off the code that uses the whole disk for NetBSD, into the
mbr_use_wholedisk() function. On most ports that use mbr.c, I made
md_mbr_use_wholedisk() just call that and return. On prep we create the
magical prep boot partition here. The md_check_mbr() function allows the
arch to add additional checks after the user had manually edited the MBR
to make sure the choices he made allow NetBSD to function. Added a dummy
routine to all mbr.c using arches.
3) Added code to bsdlabel.c to create a partition of type boot if
PART_BOOT is defined, but BOOT_SIZE is not defined. Also added two more
globals "bootsize" and "bootstart" which must be seeded in order to do
so. This is done on prep in md_check_mbr().
4) Added MBR_PTYPE_PREP to the list of MBR partitions.
5) Made the prep port actually install sanely. It now creates a prep
boot partition, labels it correctly, installs all the sets, and then runs
mkbootimage and dd's the bootimage into the prep partition. The result
is a prep installer that creates a bootable NetBSD installation
automatically.
6) Edited the prep menus and messages files to add new labels. In the
case of the translated files, I just added the words in english for
someone to translate later.
I tried to xcompile a few arches to make sure I didn't break anything,
but I could have missed something. Please let me know if I have broken
your arch in any way. I'll watch the autobuilds for the next few days
too. For all ports other than prep there should be no functional changes
at all.
of digital video recorders popular in Europe and Australia.
These devices have a USB client port which can be used to upload and
download recordings (and other files, such as MIPS binaries for execution
on the DVR's CPU) to/from their internal hard disk, in addition to some
other operations on files and directories.
sun-rbootd package for NetBSD/hp300 and OpenBSD/hp300, which
works on more other OSs including SunOS 4.x, Solaris 2.x, HP-UX 10,
HP-UX 9, NEWS-OS 4.x, FreeBSD, and Linux.
like this, where a user may well want to install one of these but not the
other.
To allow syspkg to be used for its intended purpose here, carefully split
out ipfilter and pf from the main {base,comp,man,misc}-net{,util}-* packages
(something which was partially done for ipf, but not done for pf in the
past).
This way, a user can pkg_delete *-{ipf,pf}-*, and not have utilities,
libraries, man pages, examples, or default /etc files for the packet filter
they don't like.
drochner