From: Joerg Schilling <schilling@fokus.fraunhofer.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6745] New: kernel hangs when trying to read atip wiith cdrecord
Date: Sun, 25 Jun 2006 21:40:47 +0200 [thread overview]
Message-ID: <449EE6BF.nailFJ2SPFY4@burner> (raw)
>Since I have a relatively old glibc I cannot use the newer versions of
>cdrecord-prodvd, but cdrecord-prodvd-2.01b31-i686-pc-linux-gnu sometimes
>works. I did work sometimes, but even when it wors and prints the atip -
>compared to using my dvd-recorder it takes ages to print the results.
Why don't you just compile a recent version by your own?
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
next reply other threads:[~2006-06-25 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 19:40 Joerg Schilling [this message]
2006-06-26 0:01 ` [Bugme-new] [Bug 6745] New: kernel hangs when trying to read atip wiith cdrecord Christian Lohmaier
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 7:29 Joerg Schilling
2006-06-28 11:19 ` Christian Lohmaier
2006-06-28 7:18 Joerg Schilling
2006-06-26 18:49 Christian Lohmaier
2006-06-26 18:21 Joerg Schilling
2006-06-25 10:53 Joerg Schilling
2006-06-25 11:06 ` Andrew Morton
2006-06-25 11:46 ` Joerg Schilling
2006-06-25 19:35 ` Joerg Schilling
[not found] <200606242036.k5OKaSvp031813@fire-2.osdl.org>
2006-06-24 21:47 ` Andrew Morton
2006-06-25 11:05 ` Jan Engelhardt
2006-06-25 11:36 ` Andrew Morton
2006-06-25 19:00 ` Christian Lohmaier
2006-06-25 11:07 ` Arjan van de Ven
2006-06-25 11:37 ` Andrew Morton
2006-06-26 18:59 ` Christian Lohmaier
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=449EE6BF.nailFJ2SPFY4@burner \
--to=schilling@fokus.fraunhofer.de \
--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