diff options
author | jb <jb@FreeBSD.org> | 2006-11-04 23:50:12 +0000 |
---|---|---|
committer | jb <jb@FreeBSD.org> | 2006-11-04 23:50:12 +0000 |
commit | 0ba5da19a5a4bc0b3cd94514f7f139723b4b3764 (patch) | |
tree | 88959728f4d2d466cd8949f02dd7327cda3a7285 /sys/pc98/conf | |
parent | ca30d69fda30d846074cf41aba30e036b5e06f78 (diff) | |
download | FreeBSD-src-0ba5da19a5a4bc0b3cd94514f7f139723b4b3764.zip FreeBSD-src-0ba5da19a5a4bc0b3cd94514f7f139723b4b3764.tar.gz |
Remove the KDTRACE option again because of the complaints about having
it as a default.
For the record, the KDTRACE option caused _no_ additional source files
to be compiled in; certainly no CDDL source files. All it did was to
allow existing BSD licensed kernel files to include one or more CDDL
header files.
By removing this from DEFAULTS, the onus is on a kernel builder to add
the option to the kernel config, possibly by including GENERIC and
customising from there. It means that DTrace won't be a feature
available in FreeBSD by default, which is the way I intended it to be.
Without this option, you can't load the dtrace module (which contains
the dtrace device and the DTrace framework). This is equivalent to
requiring an option in a kernel config before you can load the linux
emulation module, for example.
I think it is a mistake to have DTrace ported to FreeBSD, but not
to have it available to everyone, all the time. The only exception
to this is the companies which distribute systems with FreeBSD embedded.
Those companies will customise their systems anyway. The KDTRACE
option was intended for them, and only them.
Diffstat (limited to 'sys/pc98/conf')
-rw-r--r-- | sys/pc98/conf/DEFAULTS | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/pc98/conf/DEFAULTS b/sys/pc98/conf/DEFAULTS index 6b480b7..7fd3dba 100644 --- a/sys/pc98/conf/DEFAULTS +++ b/sys/pc98/conf/DEFAULTS @@ -23,6 +23,3 @@ device uart_ns8250 # KSE support went from being default to a kernel option options KSE - -# Kernel support for loading DTrace modules -options KDTRACE |