public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Glendon Gross <gross@clones.net>
To: Jan Dittmer <jdittmer@ppp0.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Burning CD's and 2.6.9
Date: Fri, 10 Dec 2004 07:47:30 -0800	[thread overview]
Message-ID: <41B9C512.1010908@clones.net> (raw)
In-Reply-To: <41B98054.8080002@ppp0.net>

I just successfully made a data DVD using 2.6.9 and growisofs.   So I 
know that the lockups I had experienced were either a fluke or due
to problems with cdrecord. 

I think you are right, that growisofs calls mkosifs which cannot make 
audio CD's.  So at least I know this is not a driver issue.  Most likely 
the
problems I have been having were due to cdrecord. 

Regards,

Glendon Gross


Jan Dittmer wrote:

> Glendon Gross schrieb:
>
>> I've been using growisofs for quite some time now, but I haven't yet 
>> tested it under 2.6.9. Is it possible to make audio CD's with 
>> growisofs?  If it is, then I really don't need cdrecord at all.
>
>
> Sorry didn't test it. But I think the answer is no, as it just
> calls mkisofs to get an iso which in turn is not capable of creating
> audio cds?
>
> Jan
>
>>
>> Thanks  for your input.
>>
>> Regards,
>>
>> Glendon Gross
>>
>>
>> Jan Dittmer wrote:
>>
>>> Glendon Gross wrote:
>>>  
>>>
>>>> When I initially posted the problem, I had no /dev/hdc device but 
>>>> now I have cleared that up by commenting out
>>>> the "append hdc=ide-scsi" line in /etc/lilo.conf.   I still need to 
>>>> do more testing to determine the cause of the lockups
>>>> I have been getting when trying to burn CD's under 2.6.9 with 
>>>> cdrecord.  I may be using the wrong version of
>>>> cdrecord, but I noticed that the syntax   "cdrecord dev=/dev/hdc" 
>>>> does work, and is able to talk to the DVD writer.
>>>>   
>>>
>>>
>>>
>>> You should also try growisofs from the dvd+rw-tools package. It works
>>> great for me burning dvds.
>>>
>>> Jan
>>>
>>>
>>>  
>>>
>
>
>
>


  parent reply	other threads:[~2004-12-10 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 16:21 Burning CD's and 2.6.9 Glendon Gross
2004-12-09 16:40 ` Jan Dittmer
2004-12-10  3:52   ` Glendon Gross
     [not found]     ` <41B950E5.3080806@ppp0.net>
     [not found]       ` <41B97A81.50606@clones.net>
     [not found]         ` <41B98054.8080002@ppp0.net>
2004-12-10 15:47           ` Glendon Gross [this message]
     [not found] ` <41B87EB4.1080604@dif.dk>
2004-12-10  3:46   ` Glendon Gross
     [not found] <5b64f7f04120908343c407f99@mail.gmail.com>
     [not found] ` <Pine.NEB.4.44.0412090839210.29667-100000@bsd.clones.net>
     [not found]   ` <5b64f7f04120909005059fbb2@mail.gmail.com>
2004-12-10  4:06     ` Glendon Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41B9C512.1010908@clones.net \
    --to=gross@clones.net \
    --cc=jdittmer@ppp0.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox