After splitting GENERIC.local/INSTALL.local, I'm going over my configs
and putting what I want (IPSEC, stf(4)) in GENERIC.local.   I found
that I also had disabled DDB_ONPANIC, and think this doesn't belong in
XEN's GENERIC equivalent since it is unsuitable for production.  Any
objections to committing the following?

Index: XEN0
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/conf/XEN0,v
retrieving revision 1.22
diff -u -r1.22 XEN0
--- XEN0	25 Nov 2005 16:41:31 -0000	1.22
+++ XEN0	1 Dec 2005 16:28:06 -0000
@@ -56,7 +56,7 @@
 options 	DEBUG		# expensive debugging checks/support 
 options 	KMEMSTATS	# kernel memory statistics (vmstat -m)
 options 	DDB		# in-kernel debugger
-options 	DDB_ONPANIC=1	# see also sysctl(8): `ddb.onpanic'
+#options 	DDB_ONPANIC=1	# see also sysctl(8): `ddb.onpanic'
 options 	DDB_HISTORY_SIZE=512	# enable history editing in DDB
 #options 	KGDB		# remote debugger
 #options 	KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x2f8,KGDB_DEVRATE=57600
Index: XENU
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/conf/XENU,v
retrieving revision 1.13
diff -u -r1.13 XENU
--- XENU	25 Nov 2005 16:41:31 -0000	1.13
+++ XENU	1 Dec 2005 16:28:06 -0000
@@ -53,7 +53,7 @@
 options 	DEBUG		# expensive debugging checks/support 
 options 	KMEMSTATS	# kernel memory statistics (vmstat -m)
 options 	DDB		# in-kernel debugger
-options 	DDB_ONPANIC=1	# see also sysctl(8): `ddb.onpanic'
+#options 	DDB_ONPANIC=1	# see also sysctl(8): `ddb.onpanic'
 options 	DDB_HISTORY_SIZE=512	# enable history editing in DDB
 #options 	KGDB		# remote debugger
 #options 	KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x2f8,KGDB_DEVRATE=57600