Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!yale!gumby!wupost!emory!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!unidui!rrz.uni-koeln.de!Germany.EU.net!tools!ws From: ws@tools.de (Wolfgang Solfrank) Newsgroups: comp.unix.bsd Subject: Re: CDROM for 386bsd (Re: ftp software inc, their address is...) Date: 14 Nov 92 19:13:29 Organization: TooLs GmbH, Bonn, Germany Lines: 23 Message-ID: <WS.92Nov14191329@kurt.tools.de> References: <AWB.92Nov12101926@otter.uk.ac.ed.aisb> <1992Nov13.073252.9757@ntuix.ntu.ac.sg> NNTP-Posting-Host: kurt.tools.de In-reply-to: eoahmad@ntuix.ntu.ac.sg's message of Fri, 13 Nov 1992 07:32:52 GMT In article <1992Nov13.073252.9757@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes: Given that a 386bsd CDROM is meant for 386bsd, there is little to be gained by using ISO9960(?). However the CDROM driver for 386bsd is only meant for Adaptec 1542 SCSI controller? I will not be able to use it! ISO9660 has nothing whatsoever to do with the CDROM driver. It is just a filesystem just like UFS. You can have an ISO9660 filesystem on any block device, e.g. you can copy a CDROM to a hard disk partition and then mount the partition with the same command you would use to mount the CDROM (I have done this once with an CDROM/XA disk on a SUN). The fact that your CDROM is not supported by 386bsd is something completely different. It means that the system isn't able to read any data from any CDROM, ISO9660 or not. Maybe it is still safest to use ISO9960, at least I can use DOS to transfer files. That would be your only option for using such a CDROM, short of writing your own driver for your CDROM drive. -- ws@tools.de (Wolfgang Solfrank, TooLs GmbH) +49-228-985800