>From: Duke <[EMAIL PROTECTED]>
>I'm trying to write an audio cd, and I keep getting errors. I'm not
>sure what to do to keep them from happening. Here is the command I
>issue, as well as the output from cdrecord:
># cdrecord -dummy -dao speed=12 dev=0,0,0 -useinfo -audio *.wav
>pregap1: -1
>
>From: P <[EMAIL PROTECTED]>
>> > I'm using RedHat 7.3 with kernel 2.4.18-4. I set up /etc/fstab
>> > with this line:
>> >
>> > /dev/scd0 /mnt/usbcdrom iso9660
>> > noauto,user,ro 0 0
>>
>> For grins try taking the line totally out of fstab. See if the kernel
>> setup is
On Tue, 18 Jun 2002, Joerg Schilling wrote:
{
{ >From: P <[EMAIL PROTECTED]>
{
{ >Thanks again for the suggestion. I should have reported back that I=20
{ >have it running now. I had to upgrade my cdrecord from v1.10-11 to=20
{ >v1.11alpha24. Now everything works great.
{
{
{ Another proof
On Tue, 18 Jun 2002, Joerg Schilling wrote:
[...]
> >Thanks again for the suggestion. I should have reported back that I=20
> >have it running now. I had to upgrade my cdrecord from v1.10-11 to=20
> >v1.11alpha24. Now everything works great.
>
>
> Another proof, that the way most Linux ditri
Hello all,
I installed cdrtools 1.10 in Slackware (kernel 2.4.18) and RedHat (kernel
2.4.7).
The burning process seems ok, but when I check the md5sums of the written
files I find a mismatch very often (before burning the cd I first check the
md5sums in the iso file).
What is wrong here?
Lin
>From: Denis Pelletier <[EMAIL PROTECTED]>
>{ >have it running now. I had to upgrade my cdrecord from v1.10-11 to=3D20
>{ >v1.11alpha24. Now everything works great.
>{=20
>{=20
>{ Another proof, that the way most Linux ditributors act is wrong:
>{=20
>{ =09They distribute cdrecord-1.10 together
On Thu, 13 Jun 2002, Joerg Schilling wrote:
> You missinterpret what happens. The reallity is:
>
> All contributed code is freely available under GPL.
>
> What I am doing is simply a second legal type of use. I am the original Author
> and have the right to make a second publication under
On 12 Jun 2002, gabor wrote:
> any ideas what's wrong with my configuration?
I highly suspect that you are using supermount. Can you use a real mount
program if that's the case?
I have no problems using Slackware and Redhat, and work with folks using
Debian and SuSE, but I have heard from peopl
On Wed, 12 Jun 2002, Joerg Schilling wrote:
> Because the Linux kernel guys are too stupid to understand that this
> should be the default (as it is in nearly all other OS including win32) :-(
This is why people don't want to work with you, you are rude and arrogant.
You assume that anyone who d
>From [EMAIL PROTECTED] Tue Jun 18 15:20:11 2002
>On Wed, 12 Jun 2002, Joerg Schilling wrote:
>> Because the Linux kernel guys are too stupid to understand that this
>> should be the default (as it is in nearly all other OS including win32) :-(
>This is why people don't want to work with you, y
On Thu, 13 Jun 2002, Joerg Schilling wrote:
> Please keep in mind that these drives are available for ~ 6 months now and I am
> very busy. The drive I received short before christmas died a few days later so
> the planned time during the holidays could not be used. The next drive has been
> de
On Thu, 13 Jun 2002, Erik Kunze wrote:
> I'm using RSCSI since about a year now, because the CD burner is built in
> a central file server and the desktop computers do not have CDROM drives.
> Now I'd like to start burning multisession CDs, but mkisofs does NOT
> support RSCSI. Is there any way t
On Tue, 18 Jun 2002, Joerg Schilling wrote:
{ >But then why do you call it v1.11alpha if it's not "alpha quality" code?=20
{ >With this naming scheme one could reasonably assume that v1.10 is the=20
{ >stable version and v1.11alpha is the development/unstable version and=20
{ >so should not be in
On Fri, 14 Jun 2002, Simon Matthews wrote:
> Can anyone suggest what is going wrong here? In order to avoid problems
> with mkisofs not creating and piping the data fast enough, I have created
> an iso9660 file on disk. I know this is good, because I can mount it and
> traverse the hierarchy.
>From: Miguel Figueiredo <[EMAIL PROTECTED]>
>I installed cdrtools 1.10 in Slackware (kernel 2.4.18) and RedHat (kernel
>2.4.7).
>The burning process seems ok, but when I check the md5sums of the written
>files I find a mismatch very often (before burning the cd I first check the
>md5sums in t
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> Another proof, that the way most Linux ditributors act is wrong:
>
> They distribute cdrecord-1.10 together with Linux-2.4
>
> Although they should know that cdrecord -1.10 is sooo old that it cannot
> know about the Linux-2.4 kernel bugs :-(
>From [EMAIL PROTECTED] Tue Jun 18 15:42:51 2002
>> I am currently spending most of my time with star and "true incremental dumps".
>> I hopte that I will be able to convince people to stop using the non-standard
>> GNU tar in favor of my better and even older star.
>I don't think most people
In the old days (linux 2.2.x) I could burn 2 cds at a time without any
trouble and I did hundreds of them. Now that I've upgraded to the 2.4
kernels (redhat 7.2 with first the stock 2.4.7 kernel and now 2.4.18)
the start of the second burn interrupts data streaming on the
first. This fails every
On Jun 18, Joerg Schilling wrote:
> People do not have interest because they don't know and this is because VENDORS
> do not put star on the distributions.
>
> If you only use tar x or tar c, and don't know what else is supported you
> believe that GNU tar is sufficient.
FWIW Debian now include
I'm using Red Hat 7.2 with kernel 2.4.3-12 and have 8
instances of cdrecrod burning all at the same time
with no problem. The only thing I do is sleep for a
couple seconds after starting each copy. Obviously you
need an I/O system capable of handling all the data at
once for each burner. I'm runni
On Tue, Jun 18, 2002 at 11:36:26AM -0400, Don Russell wrote:
>
> In the old days (linux 2.2.x) I could burn 2 cds at a time without any
> trouble and I did hundreds of them. Now that I've upgraded to the 2.4
> kernels (redhat 7.2 with first the stock 2.4.7 kernel and now 2.4.18)
> the start of th
On Tue, Jun 18, 2002 at 04:32:56PM +0200, Joerg Schilling wrote:
> People do not have interest because they don't know and this is because VENDORS
> do not put star on the distributions.
>
> If you only use tar x or tar c, and don't know what else is supported you
> believe that GNU tar is suffi
Changes/problems in the IDE SCSI implementation can also cause problems.
Assuming, as Len said, that you are using an IDE burner.
On Tuesday 18 June 2002 09:50 am, Len Sorensen wrote:
> On Tue, Jun 18, 2002 at 11:36:26AM -0400, Don Russell wrote:
> > In the old days (linux 2.2.x) I could burn 2
On Tue, 18 Jun 2002, Miguel Figueiredo wrote:
> What is wrong here?
No idea, see other message from Jorg on problems.
> Linux kernel 2.4.x ?
No, that has not been a problem, all my working systems (five at the
moment) use 2.4 kernels.
> The md5sums are not a good way to check the written da
Hi Rob,
How often you get errors when you check the data with md5sums?
Today I burned a bunch of Cd's with no errors... The errors that I am getting
maybe normal and/or inevitable. Could a success rate be established for
cdrecord or is more correct to say that the success rate is related to th
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> >From [EMAIL PROTECTED] Tue Jun 18 15:42:51 2002
>
> >> I am currently spending most of my time with star and "true incremental dumps".
> >> I hopte that I will be able to convince people to stop using the non-standard
> >> GNU tar in favor of my be
On Tue, 18 Jun 2002, Don Russell wrote:
>
> In the old days (linux 2.2.x) I could burn 2 cds at a time without any
> trouble and I did hundreds of them. Now that I've upgraded to the 2.4
> kernels (redhat 7.2 with first the stock 2.4.7 kernel and now 2.4.18)
> the start of the second burn interr
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> >But then why do you call it v1.11alpha if it's not "alpha quality" code?=20
> >With this naming scheme one could reasonably assume that v1.10 is the=20
> >stable version and v1.11alpha is the development/unstable version and=20
> >so should not be in
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> >From [EMAIL PROTECTED] Tue Jun 18 15:20:11 2002
> >It has zero to do with kernel developers, it is a **CHOICE** the
> >distribution or user can make. People choose to do it the way which works
> >best for them. Live with it.
>
> Wrong: There are to
On Tue, 18 Jun 2002, Don Russell wrote:
> In the old days (linux 2.2.x) I could burn 2 cds at a time without any
> trouble and I did hundreds of them. Now that I've upgraded to the 2.4
> kernels (redhat 7.2 with first the stock 2.4.7 kernel and now 2.4.18)
> the start of the second burn interrupts
>From: Chris Lawrence <[EMAIL PROTECTED]>
>> If you only use tar x or tar c, and don't know what else is supported you
>> believe that GNU tar is sufficient.
>FWIW Debian now includes star as an optional package for both 3.0 and
>sid (unstable); however, the default is GNU tar because that's wh
On Jun 18, Joerg Schilling wrote:
> >From: Chris Lawrence <[EMAIL PROTECTED]>
>
> >> If you only use tar x or tar c, and don't know what else is supported you
> >> believe that GNU tar is sufficient.
>
> >FWIW Debian now includes star as an optional package for both 3.0 and
> >sid (unstable); h
>From [EMAIL PROTECTED] Tue Jun 18 19:02:12 2002
>> If you only use tar x or tar c, and don't know what else is supported you
>> believe that GNU tar is sufficient.
>Hmm, I almost never have used any more than that. Tar never seems like
>the solution when needing more than that. Perhaps that
On Tue, 18 Jun 2002, E. Robert Bogusta wrote:
> > I am using a Pioneer A04 DVD burner.
> > [root@fuji tmp]# dvdrecord dev=0,0,0 -dao -v -fs=32m -speed=1 -data test.iso
>
> Did you try soa or just nothing? I normally use dao only for audio.
pioneer 104
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> - Star has a lot of features I use every day that are missing in
> GNU tar.
This is the main problem. you wrote star primarily for yourself for
feature you yourself needed, not for other users...
I think a lot of people are turne off of s
>From: Dan Hollis <[EMAIL PROTECTED]>
>On Tue, 18 Jun 2002, E. Robert Bogusta wrote:
>> > I am using a Pioneer A04 DVD burner.
>> > [root@fuji tmp]# dvdrecord dev=0,0,0 -dao -v -fs=32m -speed=1 -data test.iso
>>
>> Did you try soa or just nothing? I no
>From [EMAIL PROTECTED] Tue Jun 18 22:04:58 2002
>On Tue, 18 Jun 2002, Joerg Schilling wrote:
>> -Star has a lot of features I use every day that are missing in
>> GNU tar.
>This is the main problem. you wrote star primarily for yourself for
>feature you yourself needed, not for othe
On Tue, 18 Jun 2002, Joerg Schilling wrote:
> >This is the main problem. you wrote star primarily for yourself for
> >feature you yourself needed, not for other users...
> As I already stated: people who try out star usually never use anything else
> after that.
they won't bother with star unle
No luck...latest cdtools version a24 doesn't fix this issue.
On Mon, 2002-06-17 at 05:39, Thomas Niederreiter wrote:
> On Sun, Jun 16, 2002 at 11:12:31PM -0400, J. Christopher Pereira wrote:
> > Hi:
> >
> > I found a serious bug (Segmentation Fault) in latest xcdroast.
>
> cdda2wav is crashing.
>From [EMAIL PROTECTED] Tue Jun 18 19:54:13 2002
>> People do not have interest because they don't know and this is because VENDORS
>> do not put star on the distributions.
>It's not just Linux and BSD (and HURD?), I don't know of anyone who even
>provides it, much less makes it default.
This
On Jun 18, Dan Hollis wrote:
> for whatever reason, star and gnu tar commandline switches are not 1:1
> compatible. you can rant all you like about how gnu tar sux and star is
> superior but it doesn't matter if you can't drop star into a system and
> have everything "just work".
>
> that's pa
>From [EMAIL PROTECTED] Tue Jun 18 22:27:05 2002
>for whatever reason, star and gnu tar commandline switches are not 1:1
>compatible. you can rant all you like about how gnu tar sux and star is
>superior but it doesn't matter if you can't drop star into a system and
>have everything "just wor
42 matches
Mail list logo
