Subject: Re: easy ways to crash your NetBSD system
To: Johan Danielsson <firstname.lastname@example.org>
From: Brett Lymn <blymn@bunya3>
Date: 04/07/1996 13:06:22
According to Johan Danielsson:
>This is all a symptom of lazy programming. It is usually easier to
>write one line of panic() than to handle the error.
Aha! Sounds like we have a volunteer here - you don't want the
appellation "lazy" now do you? :-)
Actually, in a lot of the cases panics are about the only thing you
can do. What sort of handling do you want to do when the file system
finds the inode it is trying to free is already free? Just say "gee
I musta lost the plot there someplace, I will just continue on..." to
do more damage to the file system. How do you handle a hard error in
your swap space? Just kill the process and continue on? What if the
process is inetd? or even init?
Brett Lymn, Computer Systems Administrator, AWA Defence Industries
"Upgrading your memory gives you MORE RAM!" - ad in MacWAREHOUSE catalogue.