From owner-freebsd-hackers Thu Jan 12 04:01:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA04609 for hackers-outgoing; Thu, 12 Jan 1995 04:01:52 -0800 Received: from trout.nosc.mil (trout.nosc.mil [128.49.16.7]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id EAA04600 for ; Thu, 12 Jan 1995 04:01:47 -0800 Received: by trout.nosc.mil (4.1/SMI-4.1) id AA22313; Thu, 12 Jan 95 04:01:38 PST Received: by pegasus.com (8.6.8/PEGASUS-2.2) id BAA05524; Thu, 12 Jan 1995 01:27:06 -1000 Date: Thu, 12 Jan 1995 01:27:06 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199501121127.BAA05524@pegasus.com> To: freebsd-hackers@freefall.cdrom.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >I've just picked up one of these things sans manual, along with an old 300Mb >ESDI drive that may be on its last legs. The controller has a second board >that looks as if it carries about 2Mb of cache. Does anyone know if these >things just look like an ordinary controller, what jumpers will disable the >floppy drives, is it capable of having its IRQ and i/o ports changed? (yeah, >spare the arguments about how the memory would be better used on the >motherboard, but the fact is the target machine already has all the memory it >can take) It's not just a matter of cost effectiveness. A crash with a full cache can make your disk un-recoverable. A caching controller is a bad thing for Unix, unless the OS knows about it and is designed to cope. -- Richard Foulk richard@pegasus.com