Date: Tue, 4 May 1999 10:34:50 -0400 (EDT) From: Simon Karpen <slk@acm.rpi.edu> To: Raymond Wiker <raymond@orion.no> Cc: freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) Message-ID: <Pine.LNX.4.10.9905041031540.27018-100000@delenn.acm.rpi.edu> In-Reply-To: <14126.49715.589157.172436@foobar.orion.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 May 1999, Raymond Wiker wrote: > I have two other machines running 3.1-RELEASE in a slightly > less hostile environment (i.e, no direct connections outwards), and > they have been much more stable. I cannot rule out a hardware problem > on the 486; I'll know for sure as soon as I upgrade it. I have 3.1-STABLE in a fairly hostile network environment. I've found that the following will make the system unstable and reboot. If you avoid all of thses, it's solid as a rock. (otherwise you get the reboots) VESA support VM86 support OSS/Payware sound drivers With any of thses, the system will reboot anywhere from a few minutes to a day or two after being brought up, usually within a few hours. With all of these removed, it's stable. The system is a PII/266 192MB with SCSI disks on a Buslogic, a Tulip (de0) ethernet card, Matrox G200 video, and a Creative Vibra16Xv soundcard. --Simon -- Simon Karpen karpes@rpi.edu slk@acm.rpi.edu #include <std_disclaimer.h> I don't speak for RPI in any way. "Those that give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." --Ben Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.9905041031540.27018-100000>