Re: odd error in bioscall.s
On Tue, 6 Jun 2000, R Joseph Wright wrote:
I have this problem while building a kernel from sources cvsup'ed
today:
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../..
-I../../../include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s
{standard input}: Assembler messages:
{standard input}:774: Error: operands given don't match any known 386 instruction
{standard input}:839: Error: operands given don't match any known 386 instruction
*** Error code 1
Stop in /usr/src/sys/compile/MANATEE.
The file bioscall.s has only 163 lines. Where is it getting 774 and
839?
Preprocessor.
Kris
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: odd error in bioscall.s
On Wed, 7 Jun 2000, Kris Kennaway wrote:
On Tue, 6 Jun 2000, R Joseph Wright wrote:
I have this problem while building a kernel from sources cvsup'ed
today:
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../..
-I../../../include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s
{standard input}: Assembler messages:
{standard input}:774: Error: operands given don't match any known 386 instruction
{standard input}:839: Error: operands given don't match any known 386 instruction
*** Error code 1
Stop in /usr/src/sys/compile/MANATEE.
The file bioscall.s has only 163 lines. Where is it getting 774 and
839?
Preprocessor.
Preprocessor + broken assembler. Error messages about files in pipelines
are even less useful than error messages about temporary files. The
preprocessor puts line numbers in its output, but gas apparently doesn't
understand them.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
'make world' broken
while making usr.sbin/kdump or usr.bin/truss: - In file included from ioctl.c:80: /usr/obj/ext/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/ext/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition ioctl.c: In function `ioctlname': ioctl.c:363: sizeof applied to an incomplete type *** Error code 1 Stop in /ext/src/usr.bin/truss. *** Error code 1 - Any ideas ? -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
In [EMAIL PROTECTED], Martin Cracauer wrote: In [EMAIL PROTECTED], David O'Brien wrote: On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: I don't have a -current machine I want to delete all ports from, but I have a -current from yesterday, I compiled xaos on it and libpng, which is the only dependency of xaos. That leave XFree as the only non-recompiled thing in the chain. Works fine. OK, now I am pissed. I also recompiled and restarted X11 to trace this down, only to find that some stupid error in Xwrapper breaks xinit and I had to roll my own xinit. Anyway, now I am running everything in the pipe compiled within the last 24 hours on a fresh -current and xaos work just fine. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. xoas and png themself do not have assembler files. Xfree servers have some, but not in floating point related things. Where is the information that this is a floating-point problem from? Matthew, do you possibly use a custom gcc from /usr/local/bin and the native assembler or vice versa? Also, what level of optimization do you use? Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP + APM = panic - fixed!
Hi, On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: We're having this problem for long time (from the old 4.0-CURRENT days), but Mr. SUMITANI discovered a bug and fixed it. The problem was that we got worng gdt pointer for the current cpu, then panic... The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' OK, I think many people will be happy with poweroff on SMP system, so I'd like to commit this first. Then I'll track it down and try to fix later in order to support suspend/resume SMP system. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Check for ports updates
On Tue, Jun 06, 2000 at 10:25:02PM +0200, Thomas Schuerger wrote: Is there already a tool that checks the installed ports for available updates in /usr/ports? I've written such a tool, which seems to work fine already. Anyone interested? pkg_version(1) Ah, haven't seen that before. The output of pkg_version is very canonical, but not very readable for humans. pkg_version -v pkg_version -c N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mesa segfaults
It would be nice if you let us know what programs your trying to run and what kind of video card you have :) -cosmic-665 From: Thomas Schuerger [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mesa segfaults Date: Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) MIME-Version: 1.0 Received: from [204.216.27.18] by hotmail.com (3.2) with ESMTP id MHotMailBB06B47000B1D820F3DACCD81B1255920; Tue Jun 06 14:13:23 2000 Received: by hub.freebsd.org (Postfix, from userid 538)id 85C9A37BAAD; Tue, 6 Jun 2000 14:12:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org (Postfix) with SMTPid 719342E8168; Tue, 6 Jun 2000 14:12:44 -0700 (PDT)(envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.12); Tue, 6 Jun 2000 14:12:44 -0700 Received: from uni-sb.de (uni-sb.de [134.96.252.33])by hub.freebsd.org (Postfix) with ESMTP id 5C31D37BC10for [EMAIL PROTECTED]; Tue, 6 Jun 2000 14:12:41 -0700 (PDT)(envelope-from [EMAIL PROTECTED]) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])by uni-sb.de (8.10.1/240900) with ESMTP id XAA02619for [EMAIL PROTECTED]; Tue, 6 Jun 2000 23:12:37 +0200 (CEST) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42])by cs.uni-sb.de (8.10.1/240900) with ESMTP id XAA10407for [EMAIL PROTECTED]; Tue, 6 Jun 2000 23:12:36 +0200 (CEST) Received: (from schuerge@localhost)by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id XAA12640for [EMAIL PROTECTED]; Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) From [EMAIL PROTECTED] Tue Jun 06 14:17:00 2000 Delivered-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] X-Mailer: ELM [version 2.4ME+ PL57 (25)] Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.ORG Precedence: bulk Hi! I'm having problems with Mesa 3.2. Some OpenGL programs don't work at all (they quit with a segmentation fault on initialization), some other programs work a short time and then crash the same way. I installed 4.0-Release some days ago (I had 4.0-Current before that), but that didn't solve the problem, neither did remaking the Mesa port. Is anyone else experiencing this? Any ideas of what to do? Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What happens with SECURELVL? (init complains)
At bde's request, I moved kern.suser_permitted to kern_prot.c and accidentally also trimmed kern.securelevel. I just committed it back into kern_mib.c. Please let me know if there are further problems. That said, I'm a little puzzled as to where securelevel is being defined -- a bunch of stuff depends on the variable and yet my test build succeeded without it in there. And you go that far also -- far enough to boot rather than have the linking fail. Robert On Tue, 6 Jun 2000, Andrey A. Chernov wrote: Now init always complains: init: cannot get kernel security level: No such file or directory It is because KERN_SECURELVL define still present in /sys/sysctl.h but gone from kern_mib.c Moreover, even define is gone from kern_mib.c, sysctl_kern_securelvl() function is still there! Please clean up the mess. -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What happens with SECURELVL? (init complains)
On Wed, 7 Jun 2000, Robert Watson wrote: That said, I'm a little puzzled as to where securelevel is being defined -- a bunch of stuff depends on the variable and yet my test build succeeded without it in there. And you go that far also -- far enough to boot rather than have the linking fail. Nevermind -- I just trimmed the SYSCTL, not the variable declaration. Sorry for inconvenience to all. Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mesa segfaults
It would be nice if you let us know what programs your trying to run and what kind of video card you have :) Oops, sorry. I have a Matrox G200 (8 Meg SGRAM) and a Voodoo 2 card (12 Meg) running on a dual P II/400 (512 Megs) with 4.0-Release and XFree86 3.3.6 (XF86_SVGA) installed... Before Mesa 3.2, everything worked fine). Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release broken on Alpha
make release is breaking in the crunch gen'ing:
gzip -cn /usr/src/release/sysinstall/sysinstall.8 sysinstall.8.gz
install -c -s -o root -g wheel -m 555 sysinstall /stand
install -c -o root -g wheel -m 444 sysinstall.8.gz /usr/share/man/man8
rm -rf /R/stage/crunch
mkdir -p /R/stage/crunch
export RELEASE_BUILD_FIXIT=noway ; for j in boot fixit ; do sed -e "s:MACHINE:
alpha:" /usr/src/release/${j}_crunch.conf /usr/obj/usr/src/release/${j}_crun
ch.conf rm -rf ${j}_crunch mkdir ${j}_crunch ( cd ${j}_crunch cr
unchgen /usr/obj/usr/src/release/${j}_crunch.conf make -DRELEASE_CRUNCH -f $
{j}_crunch.mk subclean all NOCRYPT=yes "CFLAGS=-O -pipe -DCRUNCHED_BINARY")
mv ${j}_crunch/${j}_crunch /R/stage/crunch/${j} true || { rm -rf ${j}_cru
nch ; false ; } ; done
[reading /usr/obj/usr/src/release/boot_crunch.conf] ^Mcrunchgen: /usr/obj/usr/s
rc/release/boot_crunch.conf:4: `/usr/src/sbin/alpha' is not a directory, skippin
g it
[filling in parms for sh] ^M [filling in parms for fin
d] ^M [filling in parms for sed] ^M [filling in parms for test] ^M [filling in p
arms for rm] ^M [filling in parms for pwd] ^M [filling in parms for ppp] ^M [fi
lling in parms for sysinstall] ^M [filling in parms for newfs] ^M [filling i
n parms for minigzip] ^M [filling in parms for cpio]^M [filling in parms for
fsck] ^M [filling in parms for ifconfig] ^M [filling in parms for route] ^M [
filling in parms for slattach] ^M [filling in parms for mount_nfs] ^M [filling i
n parms for dhclient] ^M [filling in parms for arp] ^M [filling in parms for
hostname] ^M [filling in parms for pccardc] ^M [filling in parms for pccardd]
[filling in parms for usbd] ^M [filling in parms for usbdevs] ^M [generating
boot_crunch.cache] ^M [generating boot_crunch.c]^M [generating boot_crunch.m
k] ^M [] ^MRun "make -f boot_crunch.mk objs exe" to buil
d crunched binary.
*** Error code 1
Stop in /usr/src/release.
*** Error code 1
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mktemp() patch
This patch was developed by Peter Jeremy and myself and increases the
number of possible temporary filenames which can be generated by the
mktemp() family, by more densely encoding the PID and using a larger set
of characters to randomly pad with.
Instead of using only alphabetic characters, the patch uses the following
character set:
0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~
which is not believed to cause any problems with shells. The PID is also
base-64 encoded into 3 characters (instead of the usual 5 for a base-10
representation) with an extra bit of randomness added in to fill the
space. All up, for the usual case of a program calling mktemp() with 6 X's
in the argument, this patch gives 74^3*2=810448 possibilities instead of
52 (assuming the PID is known), and the number increases exponentially
thereafter with additional X's.
It's not a solution to mktemp() since there's still a race condition, and
for applications which only use 6 X's there's still only a relatively
small number of possible filenames, but it does incrementally improve the
situation by making it less likely for an attacker to guess the correct
name (i.e. harder to win the race).
Unless anyone has comments, I'd like to commit this to -current. Peter, I
hope I've got the right version of the patch - any remaining bugs are
likely to be my fault (although I've been running this here for a long
time without problems).
Kris
Index: mktemp.c
===
RCS file: /home/ncvs/src/lib/libc/stdio/mktemp.c,v
retrieving revision 1.19
diff -u -r1.19 mktemp.c
--- mktemp.c2000/01/27 23:06:46 1.19
+++ mktemp.c2000/06/08 00:57:17
@@ -52,6 +52,11 @@
static int _gettemp __P((char *, int *, int, int));
+static unsigned char base64[] =
+ ".#0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz";
+static unsigned char padchar[] =
+"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~";
+
int
mkstemps(path, slen)
char *path;
@@ -103,8 +108,10 @@
int slen;
{
register char *start, *trv, *suffp;
+ char *pad;
struct stat sbuf;
- int pid, rval;
+ int rval, n;
+ uint32_t pid;
if (doopen domkdir) {
errno = EINVAL;
@@ -120,20 +127,22 @@
errno = EINVAL;
return (0);
}
- pid = getpid();
- while (*trv == 'X' pid != 0) {
- *trv-- = (pid % 10) + '0';
- pid /= 10;
+
+ /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */
+ pid = getpid() | (arc4random() 0x0002);
+ for (n = 0; *trv == 'X' n 3; n++) {
+ *trv-- = base64[pid 0x3f];
+ pid = 6;
}
- while (*trv == 'X') {
- char c;
+ if (n 3) {/* Not enough characters to encode PID */
+ errno = EINVAL;
+ return(0);
+ }
- pid = (arc4random() 0x) % (26+26);
- if (pid 26)
- c = pid + 'A';
- else
- c = (pid - 26) + 'a';
- *trv-- = c;
+ /* Fill remaining space with random characters */
+ while (*trv == 'X') {
+ pid = arc4random() % (sizeof(padchar) - 1);
+ *trv-- = padchar[pid];
}
start = trv + 1;
@@ -179,15 +188,11 @@
for (trv = start;;) {
if (*trv == '\0' || trv == suffp)
return(0);
- if (*trv == 'Z')
- *trv++ = 'a';
+ pad = strchr(padchar, *trv);
+ if (pad == NULL || !*++pad)
+ *trv++ = padchar[0];
else {
- if (isdigit((unsigned char)*trv))
- *trv = 'a';
- else if (*trv == 'z') /* inc from z to A */
- *trv = 'A';
- else
- ++*trv;
+ *trv++ = *pad;
break;
}
}
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
heimdal/kerberosV pam module?
there doesn't appear to be recent mail in the searchable archives discussing the status of Heimdal, Kerberos V or pam. can somebody clueful give me some pointers please? cheers -George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Wed, 7 Jun 2000, Kris Kennaway wrote: This patch was developed by Peter Jeremy and myself and increases the number of possible temporary filenames which can be generated by the mktemp() family, by more densely encoding the PID and using a larger set of characters to randomly pad with. Instead of using only alphabetic characters, the patch uses the following character set: 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ Symbols '=' and '+' are prohibited in some other filesystems. It is possible to avoid using them ? -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Thu, 8 Jun 2000, Boris Popov wrote: Instead of using only alphabetic characters, the patch uses the following character set: 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ Symbols '=' and '+' are prohibited in some other filesystems. It is possible to avoid using them ? Yes, but at the expense of weakening the number of possible random filenames :-( Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On 08-Jun-00 Kris Kennaway wrote: On Thu, 8 Jun 2000, Boris Popov wrote: Instead of using only alphabetic characters, the patch uses the following character set: 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ Symbols '=' and '+' are prohibited in some other filesystems. It is possible to avoid using them ? Yes, but at the expense of weakening the number of possible random filenames :-( IMHO the loss of 2 characters doesn't greatly reduce the number of possibilities, but it DOES greatly reduce the chance of an obscure error message appearing when you try and make a temp file on a brain dead FS. BTW.. For 5 character long temp names with + and = the number of possibile names is 2073071593, without it is 1804229351. (13% less) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
"-O -pipe" is all I use for kernel and world builds. The kernel config file from my work box is attached. I have never built gcc from ports. I always use "config -r" when building kernels. I dont use modules as I have everything I need in my kernel including COMPAT_LINUX. And as I said before I removed all ports so that my testing is with XFree86, xaos and any supporting libraries all compiled after my world and kernel build. Did you do something similar ? I am using XFree86 3.3.6 on both machines. If it comes down to particular video cards, My work machine has: VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c09da (c9da) VESA: S3 Incorporated. Trio64V+ My home machine has a "3dfx Velocity 100 AGP with 8MB SGRAM" which is detected as a Voodoo 3 by the VESA code. Martin Cracauer wrote: In [EMAIL PROTECTED], Martin Cracauer wrote: In [EMAIL PROTECTED], David O'Brien wrote: On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: I don't have a -current machine I want to delete all ports from, but I have a -current from yesterday, I compiled xaos on it and libpng, which is the only dependency of xaos. That leave XFree as the only non-recompiled thing in the chain. Works fine. OK, now I am pissed. I also recompiled and restarted X11 to trace this down, only to find that some stupid error in Xwrapper breaks xinit and I had to roll my own xinit. Anyway, now I am running everything in the pipe compiled within the last 24 hours on a fresh -current and xaos work just fine. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. xoas and png themself do not have assembler files. Xfree servers have some, but not in floating point related things. Where is the information that this is a floating-point problem from? Matthew, do you possibly use a custom gcc from /usr/local/bin and the native assembler or vice versa? Also, what level of optimization do you use? Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 # $FreeBSD: FUZZ,v 5.5 2000/05/30 10:59:00 +09:30 thyerm Exp $ # based on $FreeBSD: src/sys/i386/conf/LINT,v 1.775 2000/05/22 15:00:40 dan Exp $ machine i386 ident "FUZZ" maxusers64 options INCLUDE_CONFIG_FILE # Include this file in kernel cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT# Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options SHM_PHYS_BACKED options SHMALL=16384 options SHMMAXPGS=4096 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMSEG=50 options SHMMNI=64 options SEMMNI=32 options SEMMNS=128 # DEBUGGING OPTIONS #optionsDDB # Enable the kernel debugger options KTRACE # kernel tracing (SVR4 emul needs this) options UCONSOLE# Allow users to grab the console options USERCONFIG # boot -c editor options VISUAL_USERCONFIG # visual boot -c editor # NETWORKING OPTIONS options INET# Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop# Network loopback device #pseudo-device tun # Tunnel driver (user ppp requirement) # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT# FFS usable as root device options NFS # Network Filesystem options MFS # Memory Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process Filesystem options MSDOSFS # MSDOS Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # Allow FFS to use Softupdates tech options NCP # NetWare Core protocol
