From owner-freebsd-questions Sun Nov 5 11:19: 2 2000 Delivered-To: freebsd-questions@freebsd.org Received: from aeon.conundrum.com (aeon.conundrum.com [216.191.71.202]) by hub.freebsd.org (Postfix) with ESMTP id 2904237B479 for ; Sun, 5 Nov 2000 11:18:58 -0800 (PST) Received: from smtp.conundrum.com (smtp.conundrum.com [216.191.71.197]) by aeon.conundrum.com (8.9.3/8.9.2) with ESMTP id OAA82251; Sun, 5 Nov 2000 14:18:47 -0500 (EST) (envelope-from mattp@conundrum.com) Date: Sun, 5 Nov 2000 14:18:47 -0500 (EST) From: Matt of the Long Red Hair To: cjclark@alum.mit.edu Cc: "Kenneth D. Merry" , freebsd-questions@FreeBSD.ORG Subject: Re: Building cd devices In-Reply-To: <20001105015626.Y75251@149.211.6.64.reflexcom.com> Message-ID: X-URL: http://www.conundrum.com/~mattp/ X-PGP-Fingerprint: 40 E8 24 BC C1 98 00 F2 56 2F F6 7B 36 34 58 01 X-NIC-Handle: MP1229 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Nov 2000, Crist J . Clark wrote: > > In fact, it looks like cd1c wasn't even being created. Just to see if it > > would make a difference, I tried removing cd1c before doing a `./MAKEDEV cd1` > > and nothing was created at all. > > > > flux# rm cd1c > > flux# ./MAKEDEV cd1 > > flux# ls -l cd1* > > ls: No match. > > What version is your MAKEDEV? Actually, doing 'cd0' _or_ 'cd1' should > create both the cd0 and cd1 devices. Try a, > > sh -x MAKEDEV cd1 Hrm.. okay, this gave me a thought. It looks like the last world I built didn't update MAKEDEV. I was running this, whis is probably from 4.0-R: # $FreeBSD: src/etc/MAKEDEV,v 1.243 2000/03/08 18:13:43 jlemon Exp $ And here's what it did: flux# sh -x ./MAKEDEV cd1 + [ -n ] + PATH=/sbin:/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + expr cd1 : ..\(.*\) + units=1 + name=cd + chr=15 + [ -z 1 -o 1 -le 0 ] + [ 1 -le 31 ] + i=0 + [ 0 -lt 1 ] + dname=cd0 + rm -rf cd0a cd0c rcd0a rcd0c + mknod cd0a c 15 0 root:operator + rm -f cd0a + /sbin/mknod cd0a c 15 0 root:operator + mknod cd0c c 15 2 root:operator + rm -f cd0c + /sbin/mknod cd0c c 15 2 root:operator + mknod rcd0a c 15 0 root:operator + rm -f rcd0a + /sbin/mknod rcd0a c 15 0 root:operator + mknod rcd0c c 15 2 root:operator + rm -f rcd0c + /sbin/mknod rcd0c c 15 2 root:operator + i=1 + [ 1 -lt 1 ] + umask 77 I'm now running this: # $FreeBSD: src/etc/MAKEDEV,v 1.243.2.11 2000/10/25 06:51:50 sos Exp $ And it appears to do more: flux# sh -x ./MAKEDEV cd1 + [ -n ] + PATH=/sbin:/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + expr cd1 : ..\(.*\) + units=1 + name=cd + chr=15 + [ -z 1 -o 1 -le 0 ] + [ 1 -le 31 ] + i=0 + [ 0 -le 1 ] + dname=cd0 + rm -rf cd0a cd0c rcd0a rcd0c + mknod cd0a c 15 0 root:operator + rm -f cd0a + /sbin/mknod cd0a c 15 0 root:operator + mknod cd0c c 15 2 root:operator + rm -f cd0c + /sbin/mknod cd0c c 15 2 root:operator + ln -f cd0a rcd0a + ln -f cd0c rcd0c + i=1 + [ 1 -le 1 ] + dname=cd1 + rm -rf cd1a cd1c rcd1a rcd1c + mknod cd1a c 15 8 root:operator + rm -f cd1a + /sbin/mknod cd1a c 15 8 root:operator + mknod cd1c c 15 10 root:operator + rm -f cd1c + /sbin/mknod cd1c c 15 10 root:operator + ln -f cd1a rcd1a + ln -f cd1c rcd1c + i=2 + [ 2 -le 1 ] + umask 77 However, I'm still having the original problem that led me to all of this... that my CD-R doesn't seem to be accessible to my burn software. Here's my current dmesg info for the CDs: cd0 at sym0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at sym0 bus 0 target 6 lun 0 cd1: Removable Worm SCSI-2 device cd1: 3.300MB/s transfers cd1: cd present [314413 x 2048 byte records] Now, my CDR102 works great if it's cd0 (I've put it there by disabling scanning of target 5 in my SCSI BIOS). However, running as cd1 it can't be detected by my burn software (cdrecord). This leads me to believe that there are still some devices missing. Maybe this is getting away from a FreeBSD issue now and into more of an application issue, but I can't really tell where the line is, here... whether the software can't detect the drive because of some bug, or because some device it's looking for isn't present. Thanks for all your help, Matt ---------------------------------------------------------------------- ``I ask the minister whether, no pun intended, it's appropriate in this case for a woman's body parts to be inserted into a sheep when that's normally been the domain of Tory males?'' --New Zealand MP Grant Gillon, regarding transgenic sheep containing human female DNA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message