[odc] Daily src changes for 2007-05-30
ODC
auto at squish.net
Thu May 31 07:00:01 BST 2007
OpenBSD src changes summary for 2007-05-30
==========================================
bin/md5 distrib/sets
etc/sensorsd.conf lib/libc
sbin/mknod sbin/route
share/man sys/arch/amd64/include
sys/arch/amd64/stand/boot sys/arch/amd64/stand/cdboot
sys/arch/amd64/stand/libsa sys/arch/amd64/stand/pxeboot
sys/arch/arm/arm sys/arch/hp300/include
sys/arch/i386/stand/boot sys/arch/i386/stand/cdboot
sys/arch/i386/stand/libsa sys/arch/i386/stand/pxeboot
sys/arch/mac68k/include sys/arch/macppc/dev
sys/arch/mips64/mips64 sys/arch/mvme68k/include
sys/conf sys/dev
sys/dev/pci sys/dev/usb
sys/kern sys/lib/libsa
sys/netbt sys/netinet
sys/sys sys/xfs
usr.bin/asa usr.bin/at
usr.bin/awk usr.bin/basename
usr.bin/bc usr.bin/cal
usr.bin/cmp usr.bin/comm
usr.bin/compress usr.bin/csplit
usr.bin/ctags usr.bin/cut
usr.bin/cvs usr.bin/diff
usr.bin/dirname usr.bin/du
usr.bin/env usr.bin/expand
usr.bin/false usr.bin/find
usr.bin/fold usr.bin/getconf
usr.bin/grep usr.bin/head
usr.bin/hexdump usr.bin/id
usr.bin/join usr.bin/less
usr.bin/lex usr.bin/logger
usr.bin/logname usr.bin/m4
usr.bin/make usr.bin/man
usr.bin/mesg usr.bin/nice
usr.bin/nohup usr.bin/paste
usr.bin/pr usr.bin/printf
usr.bin/rcs usr.bin/sed
usr.bin/sort usr.bin/split
usr.bin/ssh usr.bin/strings
usr.bin/systat usr.bin/tail
usr.bin/tee usr.bin/time
usr.bin/touch usr.bin/tr
usr.bin/true usr.bin/tty
usr.bin/uname usr.bin/uniq
usr.bin/uuencode usr.bin/vi
usr.bin/wc usr.bin/what
usr.bin/who usr.bin/xargs
usr.bin/yacc usr.sbin/bgpctl
usr.sbin/bgpd usr.sbin/cron
usr.sbin/dvmrpctl usr.sbin/hoststated
usr.sbin/ospfctl usr.sbin/pkg_add
usr.sbin/ripctl usr.sbin/sensorsd
== bin =============================================================== 01/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/bin
md5
~ cksum.1
> some i missed...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
== distrib =========================================================== 02/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/distrib
sets
~ lists/base/md.alpha ~ lists/base/md.amd64
~ lists/base/md.armish ~ lists/base/md.aviion
~ lists/base/md.cats ~ lists/base/md.hp300
~ lists/base/md.hppa ~ lists/base/md.hppa64
~ lists/base/md.i386 ~ lists/base/md.landisk
~ lists/base/md.luna88k ~ lists/base/md.mac68k
~ lists/base/md.macppc ~ lists/base/md.mvme68k
~ lists/base/md.mvme88k ~ lists/base/md.mvmeppc
~ lists/base/md.sgi ~ lists/base/md.sparc
~ lists/base/md.sparc64 ~ lists/base/md.vax
~ lists/base/md.zaurus ~ lists/comp/mi
> sync (deraadt@)
~ lists/base/md.alpha ~ lists/base/md.amd64
~ lists/base/md.armish ~ lists/base/md.aviion
~ lists/base/md.cats ~ lists/base/md.hp300
~ lists/base/md.hppa ~ lists/base/md.hppa64
~ lists/base/md.i386 ~ lists/base/md.landisk
~ lists/base/md.luna88k ~ lists/base/md.mac68k
~ lists/base/md.macppc ~ lists/base/md.mvme68k
~ lists/base/md.mvme88k ~ lists/base/md.mvmeppc
~ lists/base/md.sgi ~ lists/base/md.sparc
~ lists/base/md.sparc64 ~ lists/base/md.vax
~ lists/base/md.zaurus ~ lists/comp/mi
> sync (deraadt@)
== etc =============================================================== 03/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/etc
sensorsd.conf
~ sensorsd.conf
> Major update to sensorsd.
> Improves support for both 'smart' (those providing sensor status) and
> 'old-style' sensors.
> Due to re-design, the following improvements are now present and many
> flaws are now gone:
> == for smart sensors ==
> * automatically monitor all sensors that provide status by themselves,
> with the possibility to ignore certain individual sensors or sensors
> of certain type (appropriate template for sensorsd.conf is included)
> * report actual sensor status as provided by the driver. Previously,
> WARN, CRITICAL and UNKNOWN statuses were considered the same, but
> now they are different and will be reported separately. This also
> improves readability of the log-files and consistency with sysctl
> output.
> * ability to ignore status provided by the driver with the 'istatus'
> keyword ("ignore automatic status" or "I set the status"), with the
> possibility to set your own settings for acceptable limits.
> Previously, it was not possible to set any kind of user limits for
> those sensors that had their own status facilities.
> == for old-style sensors ==
> * previously, lm(4)-style fans that were flagged SENSOR_FINVALID during
> sensorsd startup were completely ignored, but now their invalid status
> is appropriately reported, and they are monitored again when they come
> out of their invalid mode
> * previously, a sensor that had an empty entry in the configuration file
> was reported to be "within limits", but now it will not be monitored
> at all (unless, of cause, it provides its own status)
> As a bonus, sensorsd syslog entries should now be shorter, and the
> majority of them will fit on one line on 80-column terminals.
> ok beck@, henning@, deraadt@ (cnst@)
== lib =============================================================== 04/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/lib
libc
~ sys/kqueue.2
> add a new kevent filter type for timers. this allows processes to create
> a series of oneshot or periodic timers. capped to a global limit.
> from freebsd via brad.
> ok art pedro (tedu@)
== sbin ============================================================== 05/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin
mknod
~ mkfifo.1
> some i missed...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
route
~ route.c
> Unbreak route.c after TOKEN removal by henning (bad henning, no cookie)
> looks ok otto@ (mcbride@)
== share ============================================================= 06/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/share
man
~ man4/options.4
> It's 'SCSIDEBUG_LEVEL', not 'SCSI_DEBUG_LEVEL'. (krw@)
== sys =============================================================== 07/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sys
arch/amd64/include
~ loadfile_machdep.h
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/amd64/stand/boot
~ Makefile ~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/amd64/stand/cdboot
~ Makefile ~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/amd64/stand/libsa
+ elf32.c + elf64.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/amd64/stand/pxeboot
~ Makefile ~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/arm/arm
~ arm32_machdep.c
> Missed one minaddr initialization before invoking uvm_km_suballoc().
> (miod@)
arch/hp300/include
~ cpu.h
> More cpuinfo vs _KERNEL fallback. (miod@)
arch/i386/stand/boot
~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/i386/stand/cdboot
~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/i386/stand/libsa
~ Makefile + elf32.c
+ elf64.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/i386/stand/pxeboot
~ conf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
arch/mac68k/include
~ cpu.h
> More cpuinfo vs _KERNEL fallback. (miod@)
arch/macppc/dev
~ xlights.c
> Make xlights(4) probe correctly on the Xserve G5, still does not correct
> the i2s timeout.
> ok drahn (gwk@)
~ tpms.c
> Add support for iBook G4. -moj (maja@)
arch/mips64/mips64
~ busdma.c
> Q: How did _dmamap_sync() work before?
> A: It didn't. (miod@)
arch/mvme68k/include
~ cpu.h
> More cpuinfo vs _KERNEL fallback. (miod@)
conf
~ files
> Import parts of the NetBSD bluetooth stack; ok gwk, and grange on removal
> of the existing code (uwe@)
~ files
> Unbreak the tree - forgot a needs-flag; discovered by gwk (uwe@)
~ files
> Unbreak the tree for gwk (uwe@)
dev
~ softraid.c ~ softraidvar.h
> add basic support for a crypto(9) backed raid C discipline
> ok marco (tedu@)
~ softraid.c ~ softraidvar.h
> Sync after the metadata is saved. (marco@)
~ softraid.c
> Remove ugly print and don't panic when doing a partial bringup. (marco@)
~ softraid.c
> Make sure that if there are staggered syncs that they complete successfully
> before detaching the scsi bus.
> ok dlg (marco@)
dev/pci
~ ahci.c
> my (dlg says crappy) laptop requires some more delays in port_reset or
> things go really crazy.
> ok/help toby tom. dlg unhappy but ok. (tedu@)
~ if_che.c
> fix the ether_aton-like function to print the correct lladdr (swap bytes)
> ok claudio@ (reyk@)
~ if_em.c ~ if_em.h
> Move the knob for the interrupt throttling register next to the knobs for
> the other interrupt moderation schemes.
> ok beck drahn (ckuethe@)
dev/usb
- if_ubt.c - if_ubtreg.h
+ ubt.c
> Drop if_ubt.c originally from freebsd and replace with ubt.c from
> netbsd that will work with the new netbt code.
> ok uwe (gwk@)
~ files.usb
> fix this for ubt.c (gwk@)
kern
~ kern_event.c
> add a new kevent filter type for timers. this allows processes to create
> a series of oneshot or periodic timers. capped to a global limit.
> from freebsd via brad.
> ok art pedro (tedu@)
~ kern_event.c
> openbsd has timeouts, not callouts so rename the variables. i applied an
> older
> diff from brad. from brad. (tedu@)
~ vfs_cache.c ~ vfs_getcwd.c
~ vfs_subr.c
> back out vfs change - todd fries has seen afs issues, and I'm suspicious
> this can cause other problems. (beck@)
~ subr_autoconf.c
> the (root) stuff is ugly, so print "at root", so it looks more like
> regular things. everyone here buys it, and i'm 90% sure miod will be
> ok with it (deraadt@)
~ kern_sig.c
> Adjust filename buffer for the new /var/crash prefix to prevent
> truncation and add an additional truncation check.
> ok deraadt@ tedu@ (moritz@)
lib/libsa
~ loadfile.c + loadfile_elf.c
> Pull out the ELF loadfile pieces from the standalone libraries, so that
> both 32- and 64-bit versions can be created (previously only one or the
> other could be built for a given boot loader).
> Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
> ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
> vice versa). Obviously the system must support LONG mode in order to
> successfully run the amd64 kernel once it is loaded.
> Advice and discussions from/with dale@ (going back three years). Much
> testing nick@ and todd@; thanks. (tom@)
netbt
- bt.h - h4.h
- hci_raw.c - hci_var.h
- l2cap_var.h - rfcomm_var.h
~ bluetooth.h ~ hci.h
~ l2cap.h + hci_event.c
+ hci_link.c + hci_misc.c
+ hci_socket.c + hci_unit.c
+ l2cap_lower.c + l2cap_misc.c
+ l2cap_signal.c + sco.h
> Import parts of the NetBSD bluetooth stack; ok gwk, and grange on removal
> of the existing code (uwe@)
~ bt_input.c ~ bt_proto.c
> Unbreak the tree for gwk (uwe@)
netinet
~ ip_output.c ~ ip_input.c
> no need to declare extern ipsec_in_use, we get it via ip_ipsp.h
> found by itojun (henning@)
sys
~ event.h
> add a new kevent filter type for timers. this allows processes to create
> a series of oneshot or periodic timers. capped to a global limit.
> from freebsd via brad.
> ok art pedro (tedu@)
~ namei.h ~ vnode.h
> back out vfs change - todd fries has seen afs issues, and I'm suspicious
> this can cause other problems. (beck@)
xfs
~ xfs_node-bsd.c
> back out vfs change - todd fries has seen afs issues, and I'm suspicious
> this can cause other problems. (beck@)
== usr.bin =========================================================== 08/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin
asa
~ asa.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
at
~ at.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
awk
~ awk.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
basename
~ basename.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
bc
~ bc.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
cal
~ cal.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
cmp
~ cmp.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
comm
~ comm.1
> some i missed...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
compress
~ compress.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
csplit
~ csplit.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
ctags
~ ctags.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
cut
~ cut.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
cvs
~ diff_internals.c
> Sync rcsdiff -> cvs diff
> Surprisingly, rcsdiff has nicer code than cvs diff. Changes:
> 1. Include sys/param.h because we are using MIN/MAX... not sure why
> it hasn't complained in the past.
> 2. Use fstat instead of stat.
> 3. Remove useless casts and __inline.
> 4. Plug a memory leak.
> OK niallo@ (ray@)
~ diff_internals.c
> Remove unused struct diff_arg. (ray@)
~ diff_internals.c
> Remove cand structure (but not its definition). (ray@)
diff
~ diff.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
dirname
~ dirname.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
du
~ du.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
env
~ env.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
expand
~ expand.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
false
~ false.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
find
~ find.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
fold
~ fold.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
getconf
~ getconf.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
grep
~ grep.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
head
~ head.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
hexdump
~ od.1
> some i missed...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
id
~ id.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
join
~ join.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
less
~ less.1
> some i missed...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
lex
~ flex.1
> rearrange the start of this page to appease man -h; (jmc@)
logger
~ logger.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
logname
~ logname.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
m4
~ m4.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
make
~ make.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
man
~ man.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
mesg
~ mesg.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
nice
~ nice.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
nohup
~ nohup.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
paste
~ paste.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
pr
~ pr.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
printf
~ printf.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
rcs
~ diff.c
> Remove unused struct diff_arg. (ray@)
~ diff.c
> Remove cand structure (but not its definition). (ray@)
~ rcs.1
> document \&$Mdocdate$; prodded by xsa (jmc@)
sed
~ sed.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
sort
~ sort.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
split
~ split.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
ssh
~ kex.c
> tidy: KNF, ARGSUSED and u_int (djm@)
strings
~ strings.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
systat
~ iostat.c ~ systat.1
> rename msec to the less confusing sec and improve the description in
> the man page. ok dlg@ and jmc@ (otto@)
tail
~ tail.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
tee
~ tee.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
time
~ time.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
touch
~ touch.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
tr
~ tr.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
true
~ true.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
tty
~ tty.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
uname
~ uname.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
uniq
~ uniq.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
uuencode
~ uuencode.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
vi
~ docs/USD.doc/vi.man/vi.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
wc
~ wc.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
what
~ what.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
who
~ who.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
xargs
~ xargs.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
yacc
~ yacc.1
> - use a consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
== usr.sbin ========================================================== 09/09 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin
bgpctl
~ bgpctl.c
> bad henning (otto@)
bgpd
~ mrt.h
> mrtd.net is no longer, prune
> ok claudio@ (msf@)
cron
~ crontab.1
> usr.sbin is kinder...
> - consistent text for STANDARDS
> - note which options are extensions to POSIX (jmc@)
dvmrpctl
~ dvmrpctl.c
> yuck, no cookie for me (henning@)
hoststated
~ hoststated.c
> backout last diff which introduces problems and use the global
> environment instead. (pyr@)
~ hoststated.c
> backout more code that shouldn't have gone in. (pyr@)
~ hoststated.c
> give ibuf to event_set (pyr@)
ospfctl
~ ospfctl.c
> yuck, no cookie for me (henning@)
pkg_add
~ OpenBSD/PackageRepository.pm
~ OpenBSD/PackageRepository/Installed.pm
> move close methods so that error paths can proceed on
> Repository::Installed. (espie@)
~ OpenBSD/Delete.pm
> redo keep_old_files as a visitor. Copy more stuff over. (espie@)
~ OpenBSD/Add.pm ~ OpenBSD/PackingList.pm
> separate the creation of the borked package and the Fatal. (espie@)
~ pkg_add ~ OpenBSD/Add.pm
> slightly better control over partial installations (still preparing for
> bigger sets) (espie@)
~ OpenBSD/CollisionReport.pm
> allow for removing colliding files... very dangerous. (espie@)
~ OpenBSD/Delete.pm
> don't bother not copying the pkgname, we're going to overwrite it anyways.
> (espie@)
~ OpenBSD/PackingElement.pm ~ OpenBSD/PackingList.pm
> new functionality: copy elements of packing-lists to a new plist if they
> are registered in a hash. This will be used to create borked packages in
> a much simpler way.
> Also, set_pkgname, so that I don't have to remember whether this
> packing-list already has a name. Useful when copying stuff over. (espie@)
~ pkg_create
> use set_pkgname (espie@)
~ pkg_add ~ OpenBSD/Add.pm
~ OpenBSD/PackingElement.pm ~ OpenBSD/Replace.pm
> simplify the way partial installations get recorded: store elements
> already installed in a hash, and do a shallow copy of the list when
> necessary, using make_copy.
> This removes a lot of action-at-a-distance in packing-list elements.
> (espie@)
~ OpenBSD/Add.pm ~ OpenBSD/Replace.pm
> avoid setting partial directly when we can, use inheritance instead.
> (espie@)
~ pkg_add ~ OpenBSD/Add.pm
~ OpenBSD/Delete.pm ~ OpenBSD/Replace.pm
~ OpenBSD/Vstat.pm
> simplify really_add to use real visitors for extraction and installation.
> Just do one single try {} catchall {} per-method, as this is enough.
> New methods: extract_and_progress, install_and_progress, that catch
> interrupts (die) deal with fake, and handle the progress meter.
> One single method: mark_progress, can be used for extraction, installation
> and deletion. (espie@)
~ pkg_add
> fold even more stuff under the same control loop. (espie@)
~ pkg_delete
> fix verbosity. (espie@)
~ pkg_add ~ OpenBSD/Add.pm
~ OpenBSD/Delete.pm ~ OpenBSD/PackageInfo.pm
~ OpenBSD/PackingList.pm
> simplify script handling a bit (they're going to disappear probably
> anyways).
> Remove two passes visitors, we don't use them. (espie@)
ripctl
~ ripctl.c
> token fallout.. bad henning (henning@)
sensorsd
~ sensorsd.8 ~ sensorsd.c
~ sensorsd.conf.5
> Major update to sensorsd.
> Improves support for both 'smart' (those providing sensor status) and
> 'old-style' sensors.
> Due to re-design, the following improvements are now present and many
> flaws are now gone:
> == for smart sensors ==
> * automatically monitor all sensors that provide status by themselves,
> with the possibility to ignore certain individual sensors or sensors
> of certain type (appropriate template for sensorsd.conf is included)
> * report actual sensor status as provided by the driver. Previously,
> WARN, CRITICAL and UNKNOWN statuses were considered the same, but
> now they are different and will be reported separately. This also
> improves readability of the log-files and consistency with sysctl
> output.
> * ability to ignore status provided by the driver with the 'istatus'
> keyword ("ignore automatic status" or "I set the status"), with the
> possibility to set your own settings for acceptable limits.
> Previously, it was not possible to set any kind of user limits for
> those sensors that had their own status facilities.
> == for old-style sensors ==
> * previously, lm(4)-style fans that were flagged SENSOR_FINVALID during
> sensorsd startup were completely ignored, but now their invalid status
> is appropriately reported, and they are monitored again when they come
> out of their invalid mode
> * previously, a sensor that had an empty entry in the configuration file
> was reported to be "within limits", but now it will not be monitored
> at all (unless, of cause, it provides its own status)
> As a bonus, sensorsd syslog entries should now be shorter, and the
> majority of them will fit on one line on 80-column terminals.
> ok beck@, henning@, deraadt@ (cnst@)
===============================================================================
More information about the odc
mailing list