> > Meanwhile, shouldn't the 2.0.2 X server run with a -current kernel?
> 
> Als allready noticed in this thread:
> options COMPAT_30

# zcat /netbsd | strings | grep COMPAT_   
_CFG_options \011COMPAT_15\011# compatibility with NetBSD 1.5,
_CFG_options \011COMPAT_16\011# NetBSD 1.6,
_CFG_options \011COMPAT_20\011# NetBSD 2.0,
_CFG_options \011COMPAT_30\011# NetBSD 3.0 compatibility.
_CFG_options \011COMPAT_43\011# and 4.3BSD
_CFG_options \011COMPAT_386BSD_MBRPART # recognize old partition ID
_CFG_options \011COMPAT_NETBSD32
_CFG_options\011\011COMPAT_BSDPTY\011# /dev/[pt]ty?? ptys.
_CFG_options \011WSDISPLAY_COMPAT_PCVT\011\011# emulate some ioctls
_CFG_options \011WSDISPLAY_COMPAT_SYSCONS\011# emulate some ioctls
_CFG_options \011WSDISPLAY_COMPAT_USL\011\011# VT handling
_CFG_options \011WSDISPLAY_COMPAT_RAWKBD\011\011# can get raw scancodes


# zcat /netbsd | ident | head
     $NetBSD: GENERIC,v 1.66 2005/08/19 05:19:49 christos Exp $
     $Revision: 1.66 $
     $NetBSD: std.amd64,v 1.1 2003/04/26 18:39:36 fvdl Exp $
     $NetBSD: GENERIC.local,v 1.1 2003/04/26 18:39:34 fvdl Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $
     $Header: setjmp.h,v 1.1 87/08/18 16:34:11 mdove Exp $