Date: Tue, 6 Aug 1996 08:27:29 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@freebsd.org (FreeBSD-current users) Cc: eischen@vigrid.com (Daniel Eischen) Subject: Re: CD-R compatiblities Message-ID: <199608060627.IAA08889@uriah.heep.sax.de> In-Reply-To: <9608052037.AA08267@pcnet1.pcnet.com> from Daniel Eischen at "Aug 5, 96 04:37:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Daniel Eischen wrote: > I've got to write a purchase order for a CD-ROM burner (to be used > under FreeBSD). I know that the HP SureStore works with FreeBSD, > but how about any 4x recorders? Anyone get the wormcontrol in > -current to work with the Yamaha line of CD-Rs? Well, it's not ``getting wormcontrol to work''. ;) Wormcontrol is a simple hook to the ioctl's of the driver, 169 lines of C code, including the copyright notice. The mere problem is to convince Yamaha to get you their SCSI documentation. Last time i've checked, they required me to fax them a sheet with figures about ``expected sales next year'' and other crap. Somebody should point them out that all their competitors have realized that providing technical specifications to their users on request is a good thing. Writing the kernel hooks should not be too difficult. If i remember right from the Linux cdwrite command, the Yamaha needs a coupld of MODE SELECTs to prepare it for writing. However, trial&error with a CD-R is like fishing in the dark... > wormcontrol doesn't seem to be available in -stable (from late > June). I have to wait for the 2.1.5R CD to come before trying > that. Has anyone ported the -current wormcontrol back to 2.1.5R > or thereabouts? The worm driver has been backported from 2.2-current to 2.1.5R, and wormcontrol(8) is also there. HOWEVER: if you want to play with an unmodified 2.1.5, get a Plasmon burner, and never boot it with a CD-ROM or fixated CD-R in the drive. Otherwise, it will announce itself as a CD-ROM (the HP 4020i will always do it this way), and be assigned to the `cd' driver. The SCSI code in 2.1.5 lacks the `type override' feature of -current, where a drive that is lying about its device type can be forcibly assigned to a `foreign' driver. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608060627.IAA08889>