[owc] Weekly src changes ending 2008-01-13
OWC
auto at squish.net
Mon Jan 14 07:00:01 GMT 2008
OpenBSD src changes summary for 2008-01-06 to 2008-01-13 inclusive
==================================================================
bin/csh bin/ksh
bin/pwd distrib
distrib/alpha distrib/amd64
distrib/hp300 distrib/hppa
distrib/i386 distrib/landisk
distrib/luna88k distrib/mac68k
distrib/macppc distrib/miniroot
distrib/mvme68k distrib/mvme88k
distrib/mvmeppc distrib/ramdisk
distrib/sets distrib/sgi
distrib/sparc64 distrib/vax
etc/etc.alpha/ttys etc/etc.amd64/ttys
etc/etc.armish/ttys etc/etc.aviion/ttys
etc/etc.hp300/ttys etc/etc.hppa/ttys
etc/etc.hppa64/ttys etc/etc.i386/ttys
etc/etc.landisk/ttys etc/etc.luna88k/ttys
etc/etc.mac68k/ttys etc/etc.mvme68k/ttys
etc/etc.mvme88k/ttys etc/etc.mvmeppc/ttys
etc/etc.sgi/fbtab etc/etc.sgi/ttys
etc/etc.sparc/ttys etc/etc.sparc64/ttys
etc/etc.vax/ttys etc/etc.zaurus/ttys
etc/netstart etc/rc
lib/libc libexec/spamd
regress/usr.bin sbin/disklabel
sbin/dump sbin/newfs
sbin/scsi share/man
share/zoneinfo sys/arch/alpha/alpha
sys/arch/alpha/pci sys/arch/arm/arm
sys/arch/aviion/aviion sys/arch/hppa/conf
sys/arch/i386/i386 sys/arch/i386/include
sys/arch/luna88k/luna88k sys/arch/m88k/include
sys/arch/mvme88k/include sys/arch/mvme88k/mvme88k
sys/arch/sgi/conf sys/arch/sparc/conf
sys/arch/sparc/sparc sys/arch/sparc64/dev
sys/arch/sparc64/include sys/arch/sparc64/sparc64
sys/dev/acpi sys/dev/ic
sys/dev/pci sys/kern
sys/lib/libsa sys/msdosfs
sys/net sys/nfs
sys/uvm usr.bin/cvs
usr.bin/lndir usr.bin/make
usr.bin/man usr.bin/mg
usr.bin/mixerctl usr.bin/patch
usr.bin/pcc usr.bin/ranlib
usr.bin/rcs usr.bin/ssh
usr.bin/sudo usr.sbin/httpd
usr.sbin/inetd usr.sbin/pkg_add
usr.sbin/sliplogin usr.sbin/slstats
usr.sbin/snmpd
== bin =============================================================== 01/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/bin
csh
~ Makefile
> providing MLINKS for shell builtins makes little sense: what we had was out
> of date for ever (no ksh builtins), and since we have two shells, pointing
> to one page or the other is never going to work; so remove MLINKS for
> csh(1); the cd(1) and wait(1) pages (also builtins); and update any
> trailing
> Xr's;
> please, there are tools like whence, man, and locate for finding this
> stuff;
> ok deraadt miod (jmc@)
ksh
~ Makefile
> Remove ulimit MLINK, it is a shell built-in. (miod@)
pwd
~ pwd.1
> providing MLINKS for shell builtins makes little sense: what we had was out
> of date for ever (no ksh builtins), and since we have two shells, pointing
> to one page or the other is never going to work; so remove MLINKS for
> csh(1); the cd(1) and wait(1) pages (also builtins); and update any
> trailing
> Xr's;
> please, there are tools like whence, man, and locate for finding this
> stuff;
> ok deraadt miod (jmc@)
== distrib =========================================================== 02/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/distrib
distrib
~ Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
alpha
~ bsd.rd/Makefile ~ common/Makefile.inc
~ inst-common/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
amd64
~ common/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
hp300
~ ramdisk/install.md
> No need to disklabel -W before disklabel -B, -W will do it for us. (miod@)
~ ramdisk/Makefile ~ ramdisk/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
hppa
~ ramdisk/Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
i386
~ common/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
landisk
~ ramdisk/install.md
> No need to disklabel -W before disklabel -B, -W will do it for us. (miod@)
luna88k
~ ramdisk/Makefile ~ ramdisk/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
mac68k
~ ramdisk/Makefile ~ ramdisk/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
macppc
~ ramdisk/Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
miniroot
~ Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
mvme68k
~ ramdisk/Makefile ~ ramdisk/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
mvme88k
~ ramdisk/Makefile ~ ramdisk/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
mvmeppc
~ ramdisk/Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
ramdisk
~ Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
sets
~ lists/man/mi
> Sync (miod@)
sgi
~ ramdisk/list
> kbd(8) on the ramdisks. (miod@)
~ ramdisk/Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
sparc64
~ bsd.rd/Makefile ~ common/Makefile.inc
~ ramdisk/Makefile ~ ramdiskB/Makefile
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
vax
~ common/Makefile.inc
> cleanup: make -> ${MAKE} consistenly.
> zap extra subshells.
> okay miod@ (espie@)
== etc =============================================================== 03/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/etc
etc.alpha/ttys
~ etc.alpha/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.amd64/ttys
~ etc.amd64/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.armish/ttys
~ etc.armish/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.aviion/ttys
~ etc.aviion/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.hp300/ttys
~ etc.hp300/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.hppa/ttys
~ etc.hppa/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.hppa64/ttys
~ etc.hppa64/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.i386/ttys
~ etc.i386/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.landisk/ttys
~ etc.landisk/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.luna88k/ttys
~ etc.luna88k/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.mac68k/ttys
~ etc.mac68k/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.mvme68k/ttys
~ etc.mvme68k/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.mvme88k/ttys
~ etc.mvme88k/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.mvmeppc/ttys
~ etc.mvmeppc/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.sgi/fbtab
~ etc.sgi/fbtab
> Update fbtab with the glass console devices. (miod@)
etc.sgi/ttys
~ etc.sgi/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.sparc/ttys
~ etc.sparc/ttys
> switch console to std.9600 (suncons is the same); ok miod (deraadt@)
etc.sparc64/ttys
~ etc.sparc64/ttys
> switch console to std.9600 (suncons is the same); ok miod (deraadt@)
~ etc.sparc64/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.vax/ttys
~ etc.vax/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
etc.zaurus/ttys
~ etc.zaurus/ttys
> Try to make /etc/ttys more consistent accross platforms, which will also
> make the installation media's life easier:
> - stop using ``Pc'' as a getty terminal type, use std.9600 instead.
> - on platforms with multiple virtual consoles (alpha, amd64, i386,
> zaurus), console is disabled, various ttyC* are enabled.
> - on other platforms, console is enabled, all other devices are
> disabled. This only changes armish, mac68k, sgi.
> - default terminal for console is unknown on serial-only machines, vt220
> on glass-capable machines (questionable, but done for consistency).
> - minor whitespace changes.
> - glass console forgotten on a couple platforms (luna88k, sparc64, vax).
> eyeballed by deraadt@, ok krw@ (miod@)
netstart
~ netstart
> Do not bring up pfsync(4) before the working ruleset
> has been loaded. Otherwise, states that are received during the
> initial bulk update mismatch the correct pf-checksum and
> do not attach to the rules.
> Problem identified by david at . Fix done in collaboration.
> OK henning@ (mpf@)
rc
~ rc
> Do not bring up pfsync(4) before the working ruleset
> has been loaded. Otherwise, states that are received during the
> initial bulk update mismatch the correct pf-checksum and
> do not attach to the rules.
> Problem identified by david at . Fix done in collaboration.
> OK henning@ (mpf@)
== lib =============================================================== 04/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/lib
libc
~ time/ctime.3 ~ time/private.h
~ time/tz-art.htm ~ time/tz-link.htm
~ time/tzfile.5 ~ time/zic.c
> update to tzcode2007k from elsie.nci.nih.gov (millert@)
== libexec =========================================================== 05/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/libexec
spamd
~ spamd.8
> simplify the suggested pf ruleset; ok beck (jmc@)
== regress =========================================================== 06/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/regress
usr.bin
~ cvs/Makefile
> Branches are separated with \n\t in GNU rcs/cvs.
> This makes regress tests easier to check with OpenCVS and GNU cvs.
> OK xsa@ (tobias@)
~ cvs/Makefile
> Slap in -b support for tag command. It was missing for a full regress test
> as of now. (tobias@)
~ cvs/Makefile
> Adjust value to proper GNU cvs output (and OpenCVS now, too) (tobias@)
~ cvs/Makefile
> extend already available regress tests (tobias@)
~ cvs/Makefile
> Make it easier to test local and remote setups by adding a Makefile var
> called MYCVSROOT (just to make sure noone thinks it is 'CVSROOT', -d is
> still needed). (tobias@)
~ cvs/Makefile
> more tests (tobias@)
== sbin ============================================================== 07/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin
disklabel
~ editor.c
> There is no point in having cpg manipulated in -E. newfs does all the
> work anyway and ignores this value. So just set it to 1 and nuke
> get_cpg(), shrinking and simplifying.
> ok otto@ millert@ (krw@)
~ editor.c
> Calculate amount of free space by adding up space in free chunks, rather
> than hand rolling another partition walking loop. No functional change.
> (krw@)
~ editor.c
> Move check for overlap inside get_size() as it was always called after
> get_size() anyway. Allows elimination of make_contiguous() since we
> no longer allow overlaps to develop. (krw@)
~ editor.c
> Kill some now-dead code/variables. (krw@)
~ editor.c
> Shrink & simplify some more -E code. Remove some chances for user
> error.
> 1) Don't accept a partition offset in used space.
> 2) Make the default size the space available from the offset
> to the end of the free chunk the offset is in.
> 3) Make (m)odify ask the questions in the same order as
> the (a)dd command. i.e. filesystem type after offset/size.
> 4) Make it more obvious new partitions default into the largest
> chunk of free space.
> 5) Nuke another now pointless function - next_offset().
> "Looks reasonable" millert@ (krw@)
~ editor.c
> When increasing d_npartitions as a result of (a)dd'ing a partition in
> -E, zero intervening partitions as well as the specified partition so
> no partitions are inadvertantly activated. (krw@)
~ editor.c
> Oops. Need to ensure we zero selected partition too. (krw@)
~ editor.c
> Do initial free space count *after* resolving overlapping partitions.
> This removes the last need for has_overlap() to touch the free space
> counter. So eliminate that parameter. (krw@)
~ editor.c
> Ensure that the initial free space chunk can't have a length <= 0. (krw@)
~ editor.c ~ disklabel.8
> Beef up the (r)ecalculate command in -E mode by having it display the
> details of the free space it calculates. Gives an easy way to see all
> the chunks of free sectors on the disk.
> ok beck@ (krw@)
~ editor.c
> Minor aligning of code and comments between editor_add() and
> editor_modify(). No functional change. (krw@)
~ editor.c
> Don't allow (a)dd or (m)odify to create 0 length partitions. Don't
> allow editing the fsize/bsize FFS values for FS_UNUSED partitions.
> ok (for at least the first bit) miod@ weingart@ beck@ (krw@)
~ editor.c
> Remove one level of epicycles by not looping in get_size() or
> get_offset() when the user enters an invalid value. Just abort the
> partition operation and return to the main prompt. Prevents users
> getting trapped because they don't know about ^D. Requested by
> deraadt at .
> Tweak an error message to remove ambiguity about what 'between x and
> y' means. (krw@)
~ editor.c
> Introduce the function max_partition_size() to calculate the max size
> a partition can be without causing overlap. Use it to eliminate the
> need to check overlap in get_size() and to make the (c)hange command
> message more meaningful, i.e. mention max size allowed not the amount
> of total free space. (krw@)
~ editor.c
> Parameter 'new' to get_size() no longer used. (krw@)
~ editor.c
> Change editor_countfree() to return the count rather than recording it
> in a semi-global. Call it whenever the count is needed rather than
> trying to make sure it is called anytime the value might change.
> Eliminates a bunch of now unnecessary *freep parameters and calls to
> editor_countfree(). (krw@)
~ editor.c
> Tweak get_offset() so it does it's own free chunks to check the
> new offset being in a free area. (krw@)
~ editor.c
> has_overlap() now always tries to resolve overlaps because it is only
> called during -E initialization. Thus it no longer needs the
> 'resolve' parameter. (krw@)
~ editor.c
> Check for expert mode/FFS inside get_fsize() and get_bsize() and
> reduce meat of editor_add() && editor_modify() to single if statements
> checking for != 0 from all get_* functions. No functional change. (krw@)
dump
~ tape.c
> compute transfer rate using 64-bit arithmetic, ok sthen@ millert@ (otto@)
newfs
~ newfs.8
> document the max size of FFS and FFS2 file systems plus some rewording;
> with and ok jmc@ (otto@)
scsi
~ libscsi.c ~ libscsi.h
> remove unused functions
> from tobias@
> ok miod@ tobias@ (chl@)
== share ============================================================= 08/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/share
man
~ man4/nmea.4 ~ man4/sl.4
~ man4/strip.4
> Don't reference {sl|nmea}attach(8) in the SEE ALSO section but ldattach(8)
> Discussed with and ok jmc@ (mbalmer@)
~ man4/trunk.4
> make the descriptions of roundrobin and loadbalance more consistent,
> and better explain what they do;
> help/ok sthen (jmc@)
~ man4/trunk.4
> add a CAVEATS section documenting some issues when using roundrobin
> and loadbalance protocols;
> brad, claudio, and sthen all helped explain this to me,
> and sthen helped me put the diff together; (jmc@)
~ man4/strip.4
> two more slattach -> ldattach; (jmc@)
~ man4/cmpci.4
> - add support for 4, 6, and 8 channel playback
> - print chip version in `audioctl version'
> - advertise some features of supported hardware in the man page
> - CMI8768 now working properly
> yes! ratchov@ (jakemsr@)
~ man4/cmpci.4 ~ man4/pci.4
> tweak cmpci's Nd, and update its entry in pci.4; (jmc@)
~ man4/bnx.4 ~ man4/brgphy.4
~ man4/re.4 ~ man4/vge.4
> 1000baseTX -> 1000baseT
> ok dlg@ (brad@)
~ man4/re.4
> gigE -> GigE
> ok dlg@ (brad@)
~ man4/pciide.4
> mention the ATI SB700 chipset.
> ok dlg@ (brad@)
~ man4/azalia.4 ~ man4/nfe.4
> mention the NVIDIA MCP77/79 chipsets.
> ok dlg@ (brad@)
~ man4/tty.4
> List the MSTSDISC line discipline. (mbalmer@)
~ man4/tty.4
> punctuation fix; (jmc@)
- man1/cd.1 - man1/wait.1
~ man1/Makefile
> providing MLINKS for shell builtins makes little sense: what we had was out
> of date for ever (no ksh builtins), and since we have two shells, pointing
> to one page or the other is never going to work; so remove MLINKS for
> csh(1); the cd(1) and wait(1) pages (also builtins); and update any
> trailing
> Xr's;
> please, there are tools like whence, man, and locate for finding this
> stuff;
> ok deraadt miod (jmc@)
~ man7/ports.7
> document manual locking: how it works, why it's there. (espie@)
~ man5/bsd.port.mk.5
> finish documenting ALL_REGRESS_FLAGS
> Document lock/unlock (espie@)
~ man5/bsd.port.mk.5
> tweak previous; (jmc@)
zoneinfo
~ datfiles/backward ~ datfiles/europe
~ datfiles/southamerica ~ datfiles/zone.tab
> update to tzdata2007k from elsie.nci.nih.gov (millert@)
== sys =============================================================== 09/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sys
arch/alpha/alpha
~ debug.s ~ locore.s
~ multiproc.s ~ pal.s
~ prom_disp.s
> Replace STABS debug info (which causes problems with truncated relocations)
> with some limited DWARF2 generating .file and .line symbols. Makes it
> possible
> to build kernels with debug information again.
> ok miod@ (kettenis@)
arch/alpha/pci
~ pci_1000.c ~ pci_1000a.c
> Make dec_xxx_intr_map() fail silently; caller will print a message if
> appropriate. Removes unwanted messages that got printed when mapping pins
> on PCI-PCI bridges that don't matter.
> ok miod@ (kettenis@)
arch/arm/arm
~ pmap.c
> Nuke avail_start and avail_end, they are not used by ps(1) since ten years,
> and nothing in the MI kernel code (and in the MD arm code) uses these
> values. (miod@)
arch/aviion/aviion
~ machdep.c
> Add a machdep.cputype sysctl, which returns the processor type (0 for
> 88100,
> 1 for 88110), for userland to have an easy way to figure out. (miod@)
arch/hppa/conf
~ GENERIC
> Move a couple of tested USB devices out of the 'untested' block,
> add urlphy.
> ok deraadt kettenis (sthen@)
~ GENERIC
> uark -> uark*, allow multiple devices to attach (jsg@)
~ RAMDISK
> add urlphy for RAMDISK, move tested devices up.
> req by kettenis (sthen@)
arch/i386/i386
~ machdep.c
> Fix build with DEBUG defined.
> ok kettenis (mikeb@)
~ pmap.c
> Don't reserve space for msgbuf and bootargs in pmap_bootstrap(), since we
> do those reservations again (and now for real) in init386().
> ok weingart@ (kettenis@)
~ mainbus.c
> Kill <machine/mp.h>.
> ok marco@ (kettenis@)
arch/i386/include
- mp.h
> Kill <machine/mp.h>.
> ok marco@ (kettenis@)
arch/luna88k/luna88k
~ machdep.c
> Add a machdep.cputype sysctl, which returns the processor type (0 for
> 88100,
> 1 for 88110), for userland to have an easy way to figure out. (miod@)
arch/m88k/include
~ cpu.h
> Add a machdep.cputype sysctl, which returns the processor type (0 for
> 88100,
> 1 for 88110), for userland to have an easy way to figure out. (miod@)
arch/mvme88k/include
~ param.h
> Remove unused cpumod variable. (miod@)
arch/mvme88k/mvme88k
~ machdep.c
> Remove unused cpumod variable. (miod@)
~ machdep.c
> Add a machdep.cputype sysctl, which returns the processor type (0 for
> 88100,
> 1 for 88110), for userland to have an easy way to figure out. (miod@)
arch/sgi/conf
~ GENERIC
> Enable raw keyboard for wscons - prompted by matthieu at . Whilst we're here
> remove entries that are irrelevant and clean up comments/indentation.
> ok miod@ (jsing@)
~ RAMDISK
> Sync console devices with GENERIC. (miod@)
arch/sparc/conf
~ SUN4C
> Add lebuffer. (miod@)
arch/sparc/sparc
~ trap.c
> Enclose some SUN4-specific code within preprocessor directives, this lets
> SUN4C
> kernel compile again. (miod@)
arch/sparc64/dev
~ com_ebus.c
> the rsc-console on the v880 operates at 115200, not the 9600 we think we
> have to force all console devices to. this change passes the right speed
> to the com code, and continues to use it when the device is opened as the
> console device.
> figured out by kettenis@
> ok kettenis@ miod@ (dlg@)
~ sab.c
> sab.c (deraadt@)
arch/sparc64/include
~ ctlreg.h
> Add STICK_INT. (kettenis@)
arch/sparc64/sparc64
~ pmap.c
> Fix spello
> ok kettenis (marco@)
~ ofw_machdep.c
> Fix {}
> ok kettenis (marco@)
~ ofw_machdep.c
> instead of showing { love }, fix the macro do use the do { ... } while (0)
> construct; ok kettenis marco (deraadt@)
~ locore.s
> Don't steal a register window in ipi_save_fpstate; it could have bad
> consequences if it forces a register window to be spilled into the pcb.
> (kettenis@)
dev/acpi
~ acpicpu.c
> re-add _PPC.
> ok gwk@ (marco@)
~ acpitz.c
> Add a more robust gettempreading that debounces the value (idea from
> FreeBSD)
> Add a macro to convert from K to C
> Redo notify and sprinkle some debug
> Tested on D810 T60 & Q2010 and tested by several others. (marco@)
~ acpitz.c
> Don't free res twice.
> ok jordan (marco@)
dev/ic
~ com.c
> the rsc-console on the v880 operates at 115200, not the 9600 we think we
> have to force all console devices to. this change passes the right speed
> to the com code, and continues to use it when the device is opened as the
> console device.
> figured out by kettenis@
> ok kettenis@ miod@ (dlg@)
~ gem.c
> Fall back on using SERDES if MDI0/MDI1 bits aren't set too. Fix PCS
> handling.
> Makes the onboard fiber gem(4) in the Sun Fire V880 work.
> tested by many; ok dlg@ (kettenis@)
~ com.c
> Make comconsrate initialized to TTYDEF_SPEED at compile-time, for ports
> which need to setup the chip before comcnattach() is invoked. (miod@)
~ ac97.c
> Check for a negative devinfo index, which could get here through
> mixer_ioctl.
> ok jakemsr@ (deanna@)
dev/pci
~ cmpci.c ~ cmpcireg.h
~ cmpcivar.h
> - add support for 4, 6, and 8 channel playback
> - print chip version in `audioctl version'
> - advertise some features of supported hardware in the man page
> - CMI8768 now working properly
> yes! ratchov@ (jakemsr@)
~ pcidevs.h ~ pcidevs_data.h
> regen (thib@)
~ pcidevs
> Add some more Intel 10G PCIe entries.
> From Intel's ixgbe driver.
> ok dlg@ (thib@)
~ pcidevs
> Add the Broadcom 10Gb controller PCI id, BCM57710.
> From the Linux -mm kernel tree.
> ok dlg@ (brad@)
~ pcidevs.h ~ pcidevs_data.h
> regen (brad@)
~ pcidevs.h ~ pcidevs_data.h
> regen (jsg@)
~ pcidevs
> Some additional Intel devices from submitted dmesgs. (jsg@)
~ pcidevs ~ pciide.c
> Turns out the id I thought was both CX700/VX700 IDE was only for VX700,
> so rename it and add a CX700 id.
> Tweaked version of a diff from dtrombley at dslindiana.com who tested
> with a board with the new id. (jsg@)
~ pcidevs.h ~ pcidevs_data.h
> regen (jsg@)
kern
~ tty_msts.c
> Degrade the sensor state from OK to WARNING and CRITICAL after periods of
> ten minutes (same behaviour as nmea(4)). If the cable is pulled, the
> sensor
> no longer keeps the OK status forever. Tested with a PEX511 as MSTS
> sender. (mbalmer@)
lib/libsa
~ ufs.c
> repair build of boot code where it uses an undefind __ashldi3 on some archs
> boot code uses 32-bit blknos anyway (otto@)
msdosfs
~ msdosfs_denode.c
> Return pcbmap() errors from deget() rather than ignoring them. EIO at
> least has been seen from ian@'s new iPod, causing inappropriate
> mounting.
> ok miod@ (krw@)
net
~ if_trunk.c
> return with ENOTTY instead of EINVAL for unknown ioctl requests to trunk
> ports.
> ok reyk@ dlg@ (brad@)
~ if.c ~ route.c
TAGGED OPENBSD_4_2
> MFC, initial fix by Chris Cappucino, more complete fix by me:
> make sure users of rtlabel_id2name() can deal with no label present,
> by not calling it when the label id is 0 (initial fix) and also checking
> for rtlabel_id2name() returning NULL (complete fix). original rtlabel code
> had that all right, the newer rtlabel bound to an interface code not.
> impact: local users can cause a kernel panic by using the SIOCGIFRTLABEL
> ioctl on interfaces with no route label assigned. (henning@)
~ if_pfsync.c
TAGGED OPENBSD_4_2
> Kill all timeouts and undo carp demotion on pfsync_clone_destroy.
> Panic reported by deraadt.
> OK henning@ (mpf@)
nfs
~ nfs_serv.c ~ nfs_socket.c
~ nfs_subs.c ~ nfs_var.h
~ nfs_vnops.c ~ nfsm_subs.h
> More NFS-related kernel shrinkage...
> When you use a macro ~200 times, it tends to bloat your code, so make a
> function out of it.
> Shaves ~8.5 kB from my kernel.
> ok thib@, "looks good" krw@
> In snaps for 1+ week with no negative reports. (blambert@)
~ nfs_vfsops.c
> diff missed in previous commit:
> More NFS-related kernel shrinkage...
> When you use a macro ~200 times, it tends to bloat your code, so make a
> function out of it.
> Shaves ~8.5 kB from my kernel.
> ok thib@, "looks good" krw@
> In snaps for 1+ week with no negative reports. (deraadt@)
uvm
~ uvm_page_i.h
> Make uvm_page_lookup_freelist() simpler and faster if VM_PHYSSEG_MAX is 1.
> Has been in snapshots for a short while. (miod@)
== usr.bin =========================================================== 10/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin
cvs
~ rcs.c
> Branches are separated with \n\t in GNU rcs/cvs.
> This makes regress tests easier to check with OpenCVS and GNU cvs.
> OK xsa@ (tobias@)
~ rcs.c
> Added support for keyword $Log$. In order to support $Log$, new lines have
> to be added which mustn't be expanded again (this log message for example
> would loop forever due to $Log$ keywords in it). (tobias@)
~ add.c ~ client.c
> Properly handle "cvs add" on a client/server setup with GNU cvs as a
> client. (tobias@)
~ add.c
> Handle the addition of directories right, especially in remote setups with
> GNU cvs as a server. (tobias@)
~ rcs.c
> An empty -k option is invalid (tobias@)
~ client.c
> Properly free entry
> > Patch from Igor Zinovik (tobias@)
~ client.c
> Ignore CVS directories during import in remote setups. assert()ed GNU
> cvs server and was unwanted behaviour anyway. (tobias@)
~ rcs.h ~ rcsnum.c
~ tag.c
> Slap in -b support for tag command. It was missing for a full regress test
> as of now. (tobias@)
~ add.c ~ commit.c
~ file.c ~ import.c
~ rcs.c ~ status.c
> RCS files without head keyword mustn't segfault our implementation. Only
> command that supports such files is "cvs status", therefore properly handle
> them in all other commands, too. (tobias@)
~ server.c
> Got cvs_server_rlog back into shape. (tobias@)
~ repository.c
> Don't ignore files and directories due to patterns on repository-side,
> these patterns should only be applied on working directories.
> This finally enables a fully working "cvs checkout src" (but don't expect
> all checkout options to work, too). (tobias@)
~ checkout.c ~ commit.c
~ import.c ~ rcs.h
> Our keyword expansion had a big flaw, due to this construction:
> if (!(mode & RCS_KWEXP_NONE))
> RCS_KWEXP_NONE is defined to 0, so expansion happened always.
> Left shifted all RCS_KWEXP defines and looked carefully at hard-coded
> values
> throughout the code. (tobias@)
~ util.c
> cvs_mkpath missed to add all "yet to be added" directories into
> CVS/Entries,
> thus making further access to these subdirectories rather difficult.
> (tobias@)
~ file.c
> Make cvs_file_classify more readable.
> "Be especially careful with this one" joris@ (tobias@)
~ rcs.c
> Damnit, I should avoid this nasty Log word in a comment ... (tobias@)
~ entries.c ~ file.c
~ util.c
> xmalloc + memset -> xcalloc (tobias@)
~ add.c ~ checkout.c
~ client.c ~ edit.c
~ remove.c ~ update.c
~ util.c
> another strcspn() round (tobias@)
~ rcs.h
> rcs_getrev is gone: zap prototype, too. (tobias@)
~ client.c ~ cmd.c
~ cvs.c ~ cvs.h
~ log.c ~ release.c
> Simply the use of cmdp and cvs_command by zapping cvs_command and working
> solely with cmdp. This remedies some reliability issues with invalid
> commands supplied and also fixes a GNU cvs style incompatibility with
> release command.
> > Based on patch from Igor Zinovik (tobias@)
~ rcs.c
> just for the record: I HATE Log (tobias@)
~ client.c ~ cmd.c
~ remote.h ~ server.c
~ tag.c
> Added support for rtag in local and remote setups (with interoperability
> with GNU cvs). Basically we already had rtag in place as tag is supposed
> to work with revisions in working directory, but our implementation was
> wrong. Fixed that on the fly as well. (tobias@)
~ file.c
> various fixes for remote commands (right now we support rlog and rtag)
> (tobias@)
~ getlog.c ~ tag.c
> Synced rlog's usage checks and with rtag. Also unbreaks rtag and rlog with
> GNU cvs on server-side. (tobias@)
~ getlog.c ~ watch.c
> Added missing break statements.
> OK xsa@
> > Diff from Igor Zinovik <zinovik at cs dot karelia dot ru> (tobias@)
~ commit.c ~ rcs.c
> Typos fixed.
> OK xsa@
> > Diff from Igor Zinovik. (tobias@)
~ commit.c
> Revision buffers are supposed to be of size CVS_REV_BUFSZ (32) instead
> of 24.
> OK xsa@
> > Diff from Igor Zinovik. (tobias@)
lndir
~ lndir.1
> providing MLINKS for shell builtins makes little sense: what we had was out
> of date for ever (no ksh builtins), and since we have two shells, pointing
> to one page or the other is never going to work; so remove MLINKS for
> csh(1); the cd(1) and wait(1) pages (also builtins); and update any
> trailing
> Xr's;
> please, there are tools like whence, man, and locate for finding this
> stuff;
> ok deraadt miod (jmc@)
make
~ main.c
> fix stupid typo in grouping, make PWD work correctly again.
> Found out by Christian Ehrhardt. (espie@)
~ error.c ~ job.c
~ job.h ~ lst.h
~ make.c
> better error reporting/job handling error:
> - systematically reorder jobs based on who did output last, so that the
> last job to output is *first* to output again.
> - better reaction to errors: any job that outputs is checked for
> termination
> directly, and the Error message is printed right afterwards.
> - better error messages, giving more useful information in -j mode.
> (espie@)
~ Makefile + lst.lib/lstRequeue.c
> new function: lstRequeue, to be used by the job handler (espie@)
man
~ help.1
> add a note about shell built-ins; (jmc@)
mg
~ mg.1
> Greatly improve this man page. ok jmc@ (kjell@)
~ mg.1
> This file is in the public domain. ok deraadt@ (kjell@)
~ mg.1
> kill trailing whitespace; (jmc@)
mixerctl
~ mixerctl.c
> the mixer_devinfo structure contains next and prev pointers; they are used
> to create doubly linked "chains" of mixer devices. Currently mixerctl(1)
> supposes that the 'next' index is never smaller than the index of the
> device; so it fails to handle such mixers. The fix, allows 'next' indexes
> to
> be smaller than the index of the device.
> ok jakemsr@ (ratchov@)
patch
~ patch.1
> providing MLINKS for shell builtins makes little sense: what we had was out
> of date for ever (no ksh builtins), and since we have two shells, pointing
> to one page or the other is never going to work; so remove MLINKS for
> csh(1); the cd(1) and wait(1) pages (also builtins); and update any
> trailing
> Xr's;
> please, there are tools like whence, man, and locate for finding this
> stuff;
> ok deraadt miod (jmc@)
pcc
~ ccom/pass1.h ~ ccom/symtabs.c
> Pull from master repo:
> Use proper type for ix, code and match in lookup(). ok ragge@ (stefan@)
~ mip/manifest.h ~ mip/match.c
~ mip/mkext.c ~ mip/optim2.c
~ mip/protos.h ~ mip/reader.c
~ mip/regs.c
> Update from master repo:
> > Convert TEMPs to use rval for numbers. (ragge@)
~ vax/code.c ~ vax/local.c
> Updates from master repo. (ragge@)
~ i386/code.c ~ i386/local.c
~ i386/local2.c
> Updates from master repo:
> > Change to new initializer handling.
> > Make prtdcon() target dependent to allow for float constants in code.
> (ragge@)
~ ccom/cgram.y ~ ccom/gcc_compat.c
~ ccom/init.c ~ ccom/inline.c
~ ccom/pass1.h ~ ccom/pftn.c
~ ccom/scan.l ~ ccom/stabs.c
~ ccom/trees.c
> Large update from master repo:
> > Pragma not position dependent
> > Accept declarations anywhere in the C code.
> > Just typing "a;" is not allowed anymore when declaring variables.
> > Change to new initializer handling.
> > Use symtab entry, not name to identify inline functions.
> > Remove "suse" symtab element and replace it with output name.
> > Print out strings directly, do not store them until end.
> > Make prtdcon() target dependent to allow for float constants in code.
> (ragge@)
~ cpp/cpp.1 ~ cpp/cpp.c
~ cpp/scanner.l
> Updates from master repo:
> > Fix whitespace bug.
> > Define __STDC_VERSION__ to 199901L. (ragge@)
ranlib
~ extern.h
> revert 1.4, a.out toolchain needs this not-so-unused-after-all function.
> ok miod@ (chl@)
rcs
~ rcs.c
> gnu cvs added a new keyword 'commitid', this diff adds just enough code
> to parse the commitid so that cvsweb (using rcs) continues to work on
> those files
> ok niallo@, xsa@ (sturm@)
~ rcs.c
> Branches are separated with \n\t in GNU rcs/cvs.
> This makes regress tests easier to check with OpenCVS and GNU cvs.
> OK xsa@ (tobias@)
ssh
~ sftp-client.c ~ sftp-client.h
> disable unused functions
> initially from tobias@, but disabled them by placing them in "#ifdef
> notyet" which was asked by djm@
> ok djm@ tobias@ (chl@)
sudo
~ CHANGES ~ Makefile.in
~ README.LDAP ~ check.c
~ config.h.in ~ configure
~ configure.in ~ ldap.c
~ sudo.pod ~ sudoers.pod
~ version.h
> Update to sudo 1.6.9p11 (millert@)
== usr.sbin ========================================================== 11/11 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin
httpd
~ Makefile.bsd-wrapper
> sync patches in messages with reality
> Matthew Mulrooney <openbsd-2008.01.07 at fm.beyonddata.net> (henning@)
~ src/modules/standard/mod_imap.c ~ src/modules/standard/mod_status.c
> Fix mod_status XSS CVE-2007-6388:
> A flaw was found in the mod_status module. On sites where mod_status
> is enabled and the status pages were publicly accessible, a cross-site
> scripting attack is possible. Note that the server-status page is
> not enabled by default and it is best practice to not make this
> publicly available.
> Fix mod_imap XSS CVE-2007-5000:
> A flaw was found in the mod_imap module. On sites where mod_imap
> is enabled and an imagemap file is publicly available, a cross-site
> scripting attack is possible.
> ok miod@ (martynas@)
inetd
~ inetd.8
> - document what happens when a service exceeds its max spawn rate. this is
> based on a diff from reed at netbsd, but i chose a different fix
> - whilst here, make the descriptions of -R and .max more consistent
> ok sthen sobrado(in part, at least) (jmc@)
~ inetd.8
> remove out of date/irrelevant section of BUGS dealing with ip6;
> ok deraadt (jmc@)
pkg_add
~ OpenBSD/PackageInfo.pm
> better ui for locking messages.
> Instead of just saying we await the release, we say when it's done.
> (practically, a lot of package operation take `some time', it's good
> for the user to know whether the command is still waiting for an held lock,
> or actually doing some work) (espie@)
sliplogin
~ sliplogin.8
> Don't reference {sl|nmea}attach(8) in the SEE ALSO section but ldattach(8)
> Discussed with and ok jmc@ (mbalmer@)
~ sliplogin.8
> Remove HISTORY section that states that sliplogin "is currently in beta
> test"
> per jmc's request. (mbalmer@)
slstats
~ slstats.8
> Don't reference {sl|nmea}attach(8) in the SEE ALSO section but ldattach(8)
> Discussed with and ok jmc@ (mbalmer@)
~ slstats.8
> sort SEE ALSO; (jmc@)
snmpd
~ README
> sync (reyk@)
~ mps.c
> big endian fixes (tested on sparc64) (reyk@)
~ snmp.h ~ snmpe.c
> rename snmp context type enum elements (reyk@)
~ snmpe.c
> unbreak DEBUG code (reyk@)
===============================================================================
More information about the owc
mailing list