Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!daver!genco!rag From: rag@genco.bungi.com (Art Gentry) Newsgroups: comp.sys.att Subject: Re: SCSI disk on a 3B2 Keywords: 3B2, SCSI Disk, System V Message-ID: <564@genco.bungi.com> Date: 14 Mar 91 04:58:34 GMT References: <1991Mar11.210006.15458@pslu1.psl.wisc.edu> Reply-To: rag@genco.bungi.com (Art Gentry (SysOp)) Organization: Gentry & Assoc. Excelsior Springs, MO Lines: 45 In article <1991Mar11.210006.15458@pslu1.psl.wisc.edu> dhoyman@fammed.wisc.edu writes: >We would like to accquire a 3rd party SCSI disk, such as a Fuji, for our 3B2. >In order to use this, the System V device drivers must recognize this "foreign" >disk. Without buying the driver from AT&T, how can we do this configuration >ourselves? You need to create a vtoc file for the drive. Below is a copy of the file I have for my HP SCSI drive on my 3b2/400. ===================cut here====================== * /dev/rdsk/c4t1d0s8 partition map * * Dimensions: * 512 bytes/sector * 32 sectors/track * 12 tracks/cylinder * 384 sectors/cylinder * 1642 cylinders * 1640 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 6 0 01 0 629760 629759 7 0 01 0 384 383 8 0 00 384 315264 315647 /usr2 9 0 00 315648 314112 629759 /usr3 ==================cut here====================== See the command fmthard(1M) for detailed info on creating this file. >Of course, this would not be a problem if AT&T System V would just go out and >"see" who's on the bus, like a Sun does. But, no-o-o, the kernel must know >about each disk drive. Wouldn't it be nice if AT&T did alot of things like the rest of the world does? | R. Arthur Gentry -- Gentry & Associates -- Excelsior Springs, MO | | gentry@genco.bungi.com uunet!daver!genco!gentry 816-637-2443 | |Computer Consultants specializing in UNIX system admin, mgmt and security| | I am the boss - so my opinions DO count! |