As the title says, readcd always fails when I try to copy a CDR
prepared by cdrecord and mkisofs. I use both the simple command
"readcd dev=0,0,0 f=cdrom" and the added option "-clone" (sample
output appended below). The files in the CDR, however, are free
from any data error, when I check them a
> Here's a mod for the dvd+rw-tools.spec file included in 5.12.4.7.4 that
> makes it build on Red Hat 9.
Thank you for submission.
> + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
This is basically redundant, because %files section does not cover it
and usr/man/man1/growisofs.1 therefore
> While we're at spec files, man pages go into share, i.e. /usr/share/man.
> I didn't want to bother with a separate patch for this, so put this into
> the spec file:
>
> cp -p Makefile.m4 Makefile.m4.orig
> sed Makefile.m4 \
> -e 's:$(prefix)/man/:$(prefix)/share/man/:g'
/usr/local/share
On Sat, 06 Sep 2003 15:16:21 +0800, you wrote:
>As the title says, readcd always fails when I try to copy a CDR
>prepared by cdrecord and mkisofs. I use both the simple command
>"readcd dev=0,0,0 f=cdrom" and the added option "-clone" (sample
>output appended below). The files in the CDR, howeve
> The drive
> that I have is an 'Optorite DD0203', based on a Sanyo engine,
Just a reminder. For any recording other than DVD+RW, dvd+rw-tools
5.12.x is a requirement for this [and similar] units.
> I have tried two types of media with the unit: KHypermedia DVD+RW and
> now HP DVD+RW media.
>
>
> > + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
>
> This is basically redundant
It's actually wrong. The idea is to build the package into an empty
directory. To make sure, the directory in which the package is created
is cleared out first. To prevent total disaster for idiots^H^H^H^Hu
> > > + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
> >
> > This is basically redundant
>
> It's actually wrong. The idea is to build the package into an empty
> directory.
There is '[ %{buildroot} == / ] || rm -rf %{buildroot}' few lines up,
isn't there? The idea behind the extra rm sug
> I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm using
> kernel 2.4.21 and I've got a NEC 1300 drive.
As the web page mentions, even though DVD+RW is specified to provide for
true random write, not all units actually live up to this promise.
Unfortunately:-( In addition to 2nd gen
On Sat, 06 Sep 2003 20:54:02 +0200
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm
> > using kernel 2.4.21 and I've got a NEC 1300 drive.
>
> As the web page mentions, even though DVD+RW is specified to provide
> for true random write,
> > > I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm
> > > using kernel 2.4.21 and I've got a NEC 1300 drive.
> >
> > As the web page mentions, even though DVD+RW is specified to provide
> > for true random write, not all units actually live up to this promise.
> > Unfortunately:-(
I've got an CDR that has gone bad (no superblock or too many filesystems
mounted, when I try and mount it). I can always try and get a bit copy
with dd, but wonder if there is a fsck.iso9660 about that might be able
to save any files from the cdr. What's most worrying, is this CDR is
only about 1.5
As the title says, readcd always fails when I try to copy a CDR
prepared by cdrecord and mkisofs. I use both the simple command
"readcd dev=0,0,0 f=cdrom" and the added option "-clone" (sample
output appended below). The files in the CDR, however, are free
from any data error, when I check them a
> Here's a mod for the dvd+rw-tools.spec file included in 5.12.4.7.4 that
> makes it build on Red Hat 9.
Thank you for submission.
> + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
This is basically redundant, because %files section does not cover it
and usr/man/man1/growisofs.1 therefore
> While we're at spec files, man pages go into share, i.e. /usr/share/man.
> I didn't want to bother with a separate patch for this, so put this into
> the spec file:
>
> cp -p Makefile.m4 Makefile.m4.orig
> sed Makefile.m4 \
> -e 's:$(prefix)/man/:$(prefix)/share/man/:g'
/usr/local/share
On Sat, 06 Sep 2003 15:16:21 +0800, you wrote:
>As the title says, readcd always fails when I try to copy a CDR
>prepared by cdrecord and mkisofs. I use both the simple command
>"readcd dev=0,0,0 f=cdrom" and the added option "-clone" (sample
>output appended below). The files in the CDR, howeve
> The drive
> that I have is an 'Optorite DD0203', based on a Sanyo engine,
Just a reminder. For any recording other than DVD+RW, dvd+rw-tools
5.12.x is a requirement for this [and similar] units.
> I have tried two types of media with the unit: KHypermedia DVD+RW and
> now HP DVD+RW media.
>
>
> > + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
>
> This is basically redundant
It's actually wrong. The idea is to build the package into an empty
directory. To make sure, the directory in which the package is created
is cleared out first. To prevent total disaster for idiots^H^H^H^Hu
> > > + [ %{buildroot} == / ] || rm -rf %{buildroot}/usr/man
> >
> > This is basically redundant
>
> It's actually wrong. The idea is to build the package into an empty
> directory.
There is '[ %{buildroot} == / ] || rm -rf %{buildroot}' few lines up,
isn't there? The idea behind the extra rm sug
> I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm using
> kernel 2.4.21 and I've got a NEC 1300 drive.
As the web page mentions, even though DVD+RW is specified to provide for
true random write, not all units actually live up to this promise.
Unfortunately:-( In addition to 2nd gen
On Sat, 06 Sep 2003 20:54:02 +0200
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm
> > using kernel 2.4.21 and I've got a NEC 1300 drive.
>
> As the web page mentions, even though DVD+RW is specified to provide
> for true random write,
> > > I've got problems with Andy Polyakov's DVD+RW kernel patch. I'm
> > > using kernel 2.4.21 and I've got a NEC 1300 drive.
> >
> > As the web page mentions, even though DVD+RW is specified to provide
> > for true random write, not all units actually live up to this promise.
> > Unfortunately:-(
I've got an CDR that has gone bad (no superblock or too many filesystems
mounted, when I try and mount it). I can always try and get a bit copy
with dd, but wonder if there is a fsck.iso9660 about that might be able
to save any files from the cdr. What's most worrying, is this CDR is
only about 1.5
22 matches
Mail list logo
