From owner-freebsd-current  Wed May 20 05:44:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA29951
          for freebsd-current-outgoing; Wed, 20 May 1998 05:44:55 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mexcom.net (ver2-117.uninet.net.mx [200.38.135.117])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29943
          for <FreeBSD-Current@FreeBSD.ORG>; Wed, 20 May 1998 05:44:50 -0700 (PDT)
          (envelope-from eculp@ver1.telmex.net.mx)
Received: from mc.mexcom.net (telmex@ppp-7.mexcom.net [206.103.65.199])
	by ns.mexcom.net (8.8.8/8.8.7) with SMTP id HAA25209;
	Wed, 20 May 1998 07:41:07 -0500 (CDT)
Message-ID: <3562D0EC.68C780B5@ver1.telmex.net.mx>
Date: Wed, 20 May 1998 07:47:40 -0500
From: Edwin Culp <eculp@ver1.telmex.net.mx>
Organization: Mexico Communicates, S.A. de C.V.
X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.18 i586)
MIME-Version: 1.0
To: Andy Sparrow <spadger@best.com>
CC: FreeBSD-Current@FreeBSD.ORG
Subject: Re: cdrecord
References: <3561A45E.61FC7DB9@ver1.telmex.net.mx> <35624F27.132CA586@best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks a lot, I'll give it a try as soon as I get to work.

ed


Andy Sparrow wrote:
> 
> Edwin Culp wrote:
> 
> > cdrecord has been working fine with current until Monday.  I cvsuped and
> > made
> > world on sunday as usual.  Everything looks good.  I tried to run a
> > weekly
> > backup that I do every monday on cd and it appears that cdrecord can't
> > find
> > 0,3,0 because I can mount cd0c and read it with no problem.  I must have
> > done
> > something stupid that doesn't let cdrecord find 0,3,0.  Maybe a new
> > library?
> >
> > Suggestions would be appreciated.  I've also tried cdrecord 1.6 release
> > no luck.
> 
> Looks like it can't open the control device(s).cdrecord tries to open the
> 'su' device that corresponds to the bus, target, lunyou specify, e.g.
> /dev/su0-3-0 in your case.
> 
> If this fails (and it will, because the 'su' device shouldn't  be used and
> the minor
> numbers are incorrect in the "standard" cdrecord dist), it'll try to open
> /dev/scgx
> instead. This should be linked to the control device for the CDR, either
> /dev/wormX.ctl or /dev/cdX.ctl.
> 
> I think that's your problem.
> 
> See my web page for more hints (the author of cdrecord even links to it
> from
> the cdrecord page, so it must be useful :=):
> 
>     http://www.best.com/~spadger/CDR-cdrecord.html
> 
> HTH.
> 
> Regards,
> 
> AS
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message