home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.ultrix
- Path: sparky!uunet!caen!batcomputer!theory.TC.Cornell.EDU!riley
- From: riley@theory.TC.Cornell.EDU (Daniel S. Riley)
- Subject: Re: 3 peeves re: Ultrix 4.3
- Message-ID: <1992Nov13.165143.20253@tc.cornell.edu>
- Sender: news@tc.cornell.edu
- Nntp-Posting-Host: theory.tc.cornell.edu
- Organization: Cornell Theory Center
- References: <ggm.720916451@brolga> <AJC.92Nov5075136@thendara.pa.dec.com> <1992Nov6.160317.4836@ucsu.Colorado.EDU>
- Date: Fri, 13 Nov 1992 16:51:43 GMT
- Lines: 23
-
- In article <1992Nov6.160317.4836@ucsu.Colorado.EDU> giltner@pogo.Colorado.EDU (Jon Giltner) writes:
- >Amidst the gushing there are those of who still must ask why DEC is so
- >braindead about their SCSI. Strictly from a user's point of view, I don't
- >see any difference between having to edit the very cryptic /sys/data/cam_data.c
- >to define a new disk or tape device vs. editing /sys/data/scsi_data.c file.
-
- I don't edit cam_data.c for disk drives. I used to edit scsi_data.c
- because the default settings for unknown disks assumed as little as
- possible about the functionality of the attached disk. cam, by
- default, assumes a reasonably functional disk, so I don't need to edit
- it to enable sync transfers, dynamic bad block replacement, and so on.
- Having a reasonable partition table in the kernel is of limited
- utility to me, so I just let cam use the defaults and set the
- partition table with chpt. The only exceptions so far are an entry I
- made for the Seagate Wren VIII with tagged queueing enabled (that
- experiment was *not* a success), and tape drives. Even with tapes you
- can usually get by without adding an entry for the drive--I know we've
- got a few DAT drives that noone has ever given me specs for, so there
- are no entries for them in cam_data.c, and they seem to work...
-
- --
- -Dan Riley Internet: dsr@lns598.tn.cornell.edu
- -Wilson Lab, Cornell University HEPNET/SPAN: lns598::dsr (44630::dsr)
-