Date: Wed, 25 Nov 1998 19:35:16 -0800 (PST) From: Jason Evans <jasone@canonware.com> To: freebsd-questions@FreeBSD.ORG Subject: crashdump, dangerously dedicated, hosed system Message-ID: <Pine.BSF.4.05.9811251916280.26945-100000@sturm.canonware.com>
next in thread | raw e-mail | index | archive | help
So, I found a reliable way to crash FreeBSD-stable (cvsup'ed today), and being the good FreeBSDer wannabe that I am, I figured I should trace this down, since it may be exploitable via a remote DoS attack. As the Handbook instructs, I did a "config -g", rebuilt the kernel, and installed a stripped version of it. I also enabled dumpon by specifying my swap partition in /etc/rc.conf: dumpdev="/dev/sd1s1b" (Should this have been a raw device?) I rebooted and crashed the machine. All appeared fine and the core was apparently successfully dumped. When the machine rebooted though, fsck gave nasty errors about two partitions, /dev/rsd1s1e and /dev/rsd1s1f. I tried to run fsck manually, but fsck said the device was not configured. Finally, I commented the two devices out of the /etc/fstab and rebooted successfully. However, I got the following: kern.dumpdev: Device not configured A little more probing has turned up the fact that the disklabel for /dev/sd1 is... not a disklabel anymore. As mentioned in the header, all disks in the system are dangerously dedicated. My question: what did I do wrong? My home directory is on sd1, so I'm a bit reluctant to do this again until I'm confident it won't trash my system. Thanks, Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(415) 808-8742] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811251916280.26945-100000>