IEEE 802.3 Annex 28B.3 specifies the following relative
priorities of the technologies supported by
802.3 Selector Field value:
1000BASE-T full duplex
1000BASE-T
100BASE-T2 full duplex
100BASE-TX full duplex
100BASE-T2
100BASE-T4
100BASE-TX
10BASE-T full duplex
10BAST-T
Our drivers give 100BASE-T4 a higher priority than
100BASE-TX full duplex.
Fix this. This patch is based on changes in FreeBSD and OpenBSD.
Patch presented on tech-kern and tech-net:
http://mail-index.netbsd.org/tech-kern/2009/02/15/msg004397.htmlhttp://mail-index.netbsd.org/tech-net/2009/02/15/msg001064.html
got no comments, no objections.
- build mesa_dri.so, saving ~1.8MB per module (yay, the size of the
xsetrver set goes down massively now)
- use the right includes so that dri * mesa use the same headers
- correct LIBDPLIBS for libdri
tested by jmcneill, and builds fine for me.
(ours is patched to not do this) leave in utmp. PR 26168.
I'm doing this by testing for ^:[0-9] in the line field of utmp(x),
rather than by attempting to stat the device name corresponding to the
entry as in Martin's patch, because (1) no valid tty should ever have
a name beginning with a colon, and (2) this way we don't silently skip
over real ttys that should be there but for some reason have disappeared.
(I suppose this might conceivably fail to catch entries for displays
connected via XDCMP; however, ~nobody does that any more and XDCMP is
a security hole anyhow. If anyone's really concerned about this, let
me know.)
In the long run we should look into ways of getting "tty" messages to
users logged in with an X session and no terminal windows open, as
that's probably fairly common for the desktop.
option MODULAR to using %MODULAR%. While it is now possible to only
request the new version in the affected Makefiles, it is made mandatory for
everybody because I just fixed a bug in config(1) that would not make it
fail in the case of a syntax error in the Makefile template.
