FreeBSD Monitor - Feeds::freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating 2013-06-18T23:59:59Z FreeBSD Monitor freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/ba57c15f689c193b7fd5 2013-06-18T23:59:59Z Fix a bug that allowed a tracing process (e.g. gdb) to write<br />to a memory-mapped file in the traced process's address space<br />even if neither the traced process nor the tracing process had<br />write access to that file. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/5b1fcf40990a5cc237b2 2013-06-15T23:59:59Z CVS has been removed from the base system. An exact copy<br />of the code is available from the devel/cvs port. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/1b33ffb72a6a5a66190b 2013-06-13T23:59:59Z Some people report the following error after the switch to bmake:<br /><br /> make: illegal option -- J<br /> usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]<br /> ...<br /> *** [buildworld] Error code 2<br /><br />this likely due to an old instance of make in<br />${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})<br />which src/Makefile will use that blindly, if it exists, so if<br />you see the above error:<br /><br /> rm -rf `make -V MAKEPATH`<br /><br />should resolve it. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/caad217e309ccdc43aa3 2013-05-16T23:59:59Z Use bmake by default.<br />Whereas before one could choose to build with bmake via<br />-DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old<br />make. The goal is to remove these knobs for 10-RELEASE.<br /><br />It is worth noting that bmake (like gmake) treats the command<br />line as the unit of failure, rather than statements within the<br />command line. Thus '(cd some/where && dosomething)' is safer<br />than 'cd some/where; dosomething'. The '()' allows consistent<br />behavior in parallel build. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/b4ad9a2083c1d657aff3 2013-04-29T23:59:59Z Fix a bug that allows NFS clients to issue READDIR on files. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/a195006ab5547e4b0a8a 2013-04-26T23:59:59Z The sysctl which controls TRIM support under ZFS has been renamed<br />from vfs.zfs.trim_disable -&gt; vfs.zfs.trim.enabled and has been<br />enabled by default. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/ed3e6dc1aed3ffaa6b9a 2013-04-26T23:59:59Z The WITHOUT_IDEA option has been removed because<br />the IDEA patent expired. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/a9504ee78a7364f03fe8 2013-04-25T23:59:59Z The mergemaster command now uses the default MAKEOBJDIRPREFIX<br />rather than creating it's own in the temporary directory in<br />order allow access to bootstrapped versions of tools such as<br />install and mtree. When upgrading from version of FreeBSD where<br />the install command does not support -l, you will need to<br />install a new mergemaster command if mergemaster -p is required.<br />This can be accomplished with the command (cd src/usr.sbin/mergemaster<br />&& make install). freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/ce14f8ced5c272c6e653 2013-04-04T23:59:59Z Legacy ATA stack, disabled and replaced by new CAM-based one since<br />FreeBSD 9.0, completely removed from the sources. Kernel modules<br />atadisk and atapi*, user-level tools atacontrol and burncd are<br />removed. Kernel option `options ATA_CAM` is now permanently enabled<br />and removed. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/8a86e5e0e474cef19985 2013-03-19T23:59:59Z SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)<br />and socketpair(2). Software, in particular Kerberos, may<br />automatically detect and use these during building. The resulting<br />binaries will not work on older kernels. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/9a2d8e8a84ceddd1aa7f 2013-03-08T23:59:59Z CTL_DISABLE has also been added to the sparc64 GENERIC (for further<br />information, see the respective 20130304 entry). freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/5dc5dc95e0ecd63219b8 2013-03-04T23:59:59Z The ctl device has been re-enabled in GENERIC for i386 and amd64,<br />but does not initialize by default (because of the new CTL_DISABLE<br />option) to save memory. To re-enable it, remove the CTL_DISABLE<br />option from the kernel config file or set kern.cam.ctl.disable=0<br />in /boot/loader.conf. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/a72acf8cf7c711410f2c 2013-03-04T23:59:59Z Recent commits to callout(9) changed the size of struct callout,<br />so the KBI is probably heavily disturbed. Also, some functions<br />in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced<br />by macros. Every kernel module using it won't load, so rebuild<br />is requested.<br /><br />The ctl device has been re-enabled in GENERIC for i386 and amd64,<br />but does not initialize by default (because of the new CTL_DISABLE<br />option) to save memory. To re-enable it, remove the CTL_DISABLE<br />option from the kernel config file or set kern.cam.ctl.disable=0<br />in /boot/loader.conf. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/a858fa8835cbcfb6e045 2013-03-01T23:59:59Z The ctl device has been disabled in GENERIC for i386 and amd64.<br />This was done due to the extra memory being allocated at system<br />initialisation time by the ctl driver which was only used if<br />a CAM target device was created. This makes a FreeBSD system<br />unusable on 128MB or less of RAM. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/54d46a5454cec49ebed0 2013-02-08T23:59:59Z A new compression method (lz4) has been merged to -HEAD. Please<br />refer to zpool-features(7) for more information.<br /><br />Please refer to the "ZFS notes" section of this file for information<br />on upgrading boot ZFS pools. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/060beb22b513f09ada5b 2013-01-29T23:59:59Z A BSD-licensed patch(1) variant has been added and is installed<br />as bsdpatch, being the GNU version the default patch.<br />To inverse the logic and use the BSD-licensed one as default,<br />while having the GNU version installed as gnupatch, rebuild<br />ans install world with the WITH_BSD_PATCH knob set. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/9676128662c3e53691f3 2013-01-29T23:59:59Z A BSD-licensed patch(1) variant has been added and is installed<br />as bsdpatch, being the GNU version the default patch.<br />To inverse the logic and use the BSD-licensed one as default,<br />while having the GNU version installed as gnupatch, rebuild<br />and install world with the WITH_BSD_PATCH knob set. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/d6d79c7886913ba698da 2013-01-21T23:59:59Z Due to the use of the new -l option to install(1) during build<br />and install, you must take care not to directly set the INSTALL<br />make variable in your /etc/make.conf, /etc/src.conf, or on the<br />command line. If you with to use the -C flag for all installs<br />you may be able to add INSTALL+=-C to /etc/make.conf or<br />/etc/src.conf. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/cb4b8d3645f408dc7d12 2013-01-21T23:59:59Z Due to the use of the new -l option to install(1) during build<br />and install, you must take care not to directly set the INSTALL<br />make variable in your /etc/make.conf, /etc/src.conf, or on the<br />command line. If you wish to use the -C flag for all installs<br />you may be able to add INSTALL+=-C to /etc/make.conf or<br />/etc/src.conf. freebsd_updating http://www.fbsdmon.org/feed/freebsd_updating/8cb35bca76f007e77938 2013-01-18T23:59:59Z The install(1) option -M has changed meaning and now takes an<br />argument that is a file or path to append logs to. In the<br />unlikely event that -M was the last option on the command line<br />and the command line contained at least two files and a target<br />directory the first file will have logs appended to it. The -M<br />option served little practical purpose in the last decade so its<br />use is expected to be extremely rare.