From owner-freebsd-stable Thu Jun 10 8: 9:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 3812A1504F for ; Thu, 10 Jun 1999 08:09:54 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id KAA28380; Thu, 10 Jun 1999 10:10:02 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id KAA28376; Thu, 10 Jun 1999 10:10:02 -0500 (CDT) Message-ID: <00cc01beb353$651a4330$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Jason L. Schwab" Cc: "FreeBSD-Stable" Subject: Re: burning a cd Date: Thu, 10 Jun 1999 10:10:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG right. But acdx and racdx have been removed from CURRENT. They went back to wcdx and rwcdx. That is what I tried to use and it failed. acdx does not exist in CURRENT, unless you built the world from a 3.x system and never updated your dev directory. Perhaps there is a bug in the way the wcd device is created in CURRENT. Tom Veldhouse veldy@visi.com -----Original Message----- From: Jason L. Schwab To: Thomas Veldhouse Date: Thursday, June 10, 1999 10:04 AM Subject: Re: burning a cd >Thomas, > > in the burndata script, it puts an 'r' in front of what ever you tell it >on the command like ... so I was indeed using >/dev/racd1c works fine under 3.2-stable and 4.0-current for me. > >At 09:48 AM 6/10/99 -0500, you wrote: >>I have no problem with 3.2-STABLE, but I have yet to get it to work under >>4.0-CURRENT. What device did you use? I know that they moved /dev/acd0 >>back to /dev/wcd0 in CURRENT, but I can't get it to work. Even after >>./MAKEDEV wcd0. My CD-Burner is /dev/acd0c under STABLE. Under CURRENT >>my PC locks up solid, although it does it slowly, the burn starts and then >>it just locks. You can "feel" it coming but there is nothing that can be >>done about it. That was current as of one week ago (approx). >> >>Tom Veldhouse >>veldy@visi.com >> >>On Thu, 10 Jun 1999, Alexander Langer wrote: >> >>> Thus spake Richard Kiss (richard@homemail.com): >>> >>> > last time I was able to build a CD-ROM was in 2.2.8. It almost seems >(this >>> > is very unscientific) that it never actually writes, but just goes into >>> > test mode. Blanking a CD-RW doesn't seem to work. Writing just plain >don't >>> > work. >>> > Please let me know if you can get it to work. I've been very frustrated >>> > with this for quite some time. >>> >>> Works perfectly for me on 4.0-CURRENT from yesterday. Thanks for the >>> info :) >>> It returns an input/output error when finishing writing, but the CD is >>> ok. I just copied a 2.2.7 CD with it for testing-purposes and it also >boots from it. >>> >>> Thnx >>> >>> Alex >>> -- >>> ************** I doubt, therefore I might be. ************** >>> *** Send email to to get PGP-Key *** >>> >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-stable" in the body of the message >>> >> >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message >> > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message