version 1.163.4.1, 2007/11/06 23:07:11 |
version 1.180, 2008/11/26 19:00:34 |
Line 16 See also: BUILDING, build.sh, Makefile. |
|
Line 16 See also: BUILDING, build.sh, Makefile. |
|
Recent changes: |
Recent changes: |
^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^ |
|
|
|
|
|
20081122: |
|
On i386 and amd64, various kernel options(4) in GENERIC including |
|
file systems have been disabled and moved into kernel modules. |
|
Before trying a new GENERIC kernel, you have to prepare the |
|
following files as well as a new GENERIC kernel: |
|
|
|
- build and install kernel modules from src/sys/modules |
|
|
|
- install the latest bootloader, which will load a module |
|
for the file system from which the kernel is loaded automatically |
|
|
|
If you have to load your kernel from a file system which is not of |
|
the same type as the root file system, you have to load the necessary |
|
file system module manually on the boot prompt or in the boot.cfg file. |
|
|
|
20080827: |
|
If you built and installed a libc from sources between |
|
2008/08/20 and 2008/08/26 you got a broken strtouq(3) |
|
which results in false errors reported by lint(1). |
|
Since this breaks the libc build itself, manual help is |
|
needed -- lint must be disabled temporarily, e.g.: |
|
$ (cd lib/libc && make MKLINT=no dependall install) |
|
|
|
20080813: |
|
MKDEBUG build was broken because the .depend files did not know |
|
about .go files. You need to remove all .depend files and rebuild. |
|
|
|
20080731: |
|
WAPBL (metadata journaling support) has been added, but at this |
|
time isn't backwards compatible with pre-WAPBL aware kernels |
|
and userland (fsck_ffs in particular). Please make sure you |
|
don't use a journaled filesystem with an older kernel/userland, |
|
especially an uncleanly mounted journaled filesystem. WAPBL |
|
also requires the super block to be in the UFS2 format. You |
|
can use fsck_ffs -c 4 to update the superblock format. |
|
|
|
20080721: |
|
Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR |
|
isn't defined. |
|
|
|
20080531: |
|
The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed |
|
from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) |
|
utility needs to be rebuilt and reinstalled as older binaries |
|
won't work correctly. The following sequence of commands: |
|
|
|
$ (cd sys/sys/ && nbmake-$arch includes) |
|
$ (cd sbin/drvctl/ && nbmake-$arch clean) |
|
$ (cd sbin/drvctl/ && nbmake-$arch all) |
|
|
|
leaves new drvctl utility in sbin/drvctl build directory. |
|
|
|
20080503: |
|
The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. |
|
|
|
20080521: |
|
For a while, unprivileged UPDATE builds would fail to |
|
succeed at the checkflist stage, complaining that |
|
${DESTDIR}/stand/<arch>/ did not exist. A fix for this |
|
problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. |
|
If you already hit this problem, update the .mk file, |
|
remove ${DESTDIR}/stand/<arch>, and re-run the build. |
|
|
|
20080303: |
|
Linker warnings are now fatal if $WARNS>0. |
|
|
|
20080126: |
|
The posix_fadvise system call has been changed from an assembly |
|
stub, to a c file that calls an assembly stub. You need to |
|
'rm -f posix_fadvise.* .depend' in the libc build directory to |
|
avoid using the old assembly stub. |
|
|
|
20071209: |
|
The acpiec(4) driver has been split into two attachments. If you |
|
get ACPI errors before the attachment, please update your kernel |
|
configuration file appropriately or see GENERIC for more details. |
|
|
|
20071115: |
|
The it(4) driver has been renamed to itesio(4) and the old port |
|
argument specified in the kernel configuration file is not valid |
|
anymore. The itesio(4) driver now uses the Super I/O address port |
|
rather than the EC address port. Please update your kernel |
|
configuration file appropriately or see GENERIC for more details. |
|
|
20071028: |
20071028: |
The pccons(4) driver has been removed from the NetBSD/shark port. |
The pccons(4) driver has been removed from the NetBSD/shark port. |
You need to update any custom kernel configuration file you have |
You need to update any custom kernel configuration file you have |
|
|
has been changed. Rather than modify the pathname (and copy back |
has been changed. Rather than modify the pathname (and copy back |
to userspace) namei() and lookup() directly check the emulation |
to userspace) namei() and lookup() directly check the emulation |
root. One side effect is that absolute symlinks inside the emulated |
root. One side effect is that absolute symlinks inside the emulated |
root filesytem will be relative to that filesystem - unless they |
root file system will be relative to that file system - unless they |
start /../ this is useful when the emulated root is a real install |
start /../ this is useful when the emulated root is a real install |
that has such links. |
that has such links. |
This might affect symlinks that have been added to reference outside |
This might affect symlinks that have been added to reference outside |