Re: Wodim: How to read from stdin?

[Greg Wooledge]

On Sun, Jan 03, 2010 at 08:39:37AM +0100, Til Schubbe wrote:
> Computer A has the burner inside, but not enough free diskspace to
> cache the image, which is on computer B... But meanwhile I think
> about putting the burner into A.

Or you could mount the filesystem from B onto A, using NFS or Samba
or sshfs or any other protocol that allows A to see the contents of B
as files.


-- 
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org

Re: ide-scsi -> write_g1: scsi sendcmd: fatal error

[Greg Wooledge]

On Thu, May 28, 2009 at 11:49:13AM +0200, Thomas Schmitt wrote:
> Something appears wrong, indeed.
> The /proc tree seems truncated.

My guess is he built his own custom kernel and left out a lot of
drivers that he needs.


-- 
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org

Re: cdrecord floating point exception

[Greg Wooledge]

> > Perhaps before the name was used, but there was a fork with DVD 
> > capability before cdrecord got the ProDVD code. I used it because I had 
> > too many problems with the licensing of ProDVD and couldn't get 
> > permission to install it.

> Well, please try to find a proof that someone different did add DVD support 
> to cdrecord before February/March 1998.

You're playing with words.  This is the timeline as I remember it:

 1) cdrecord writes to CDs.

 2) cdrecord gets DVD writing code added and becomes cdrecord-ProDVD
which is not free software.  The free version of cdrecord continues
to exist, without DVD writing capability.

 3) dvdrecord (dvdrtools) forks the free cdrecord and adds DVD writing
code that only works for a few drives under a few situations.

 4) growisofs (dvd+rwtools) comes along, adds DVD writing that works
pretty well.

 5) cdrecord's DVD writing code is merged into the free version of cdrecord.
License is changed to a different free license.

 6) Debian forks "wodim" from an older cdrecord because they're uncertain
of the new license.

Nobody claims their DVD writing code is better than yours or older than
yours.  They just claim (correctly) that other code was FREE during a
time when yours was not.

> You will not be able to do this because the official cdrecord DVD support 
> has been introduced at a time, when only two other DVD recording programs
> have been available at all, one of them was from Pioneer. At the time
> cdrecord introduced DVD support, only 35 DVD recorders existed in the whole 
> world.

All well and good, but the resulting program was non-free and therefore
many people could not use it, or chose not to use it.  It is free NOW,
and thank you for that, but we're discussing the state of affairs during
the time cdrecord-ProDVD was non-free.


-- 
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org

Re: Question regarding correct linux cdrecord device and buffer issues.

[Greg Wooledge]

On Sun, Jan 18, 2009 at 11:05:28PM +0200, Khelben Blackstaff wrote:
> 1)
> The device choice was always a gray area in linux but in older times
> it was more clear. With 2.4 linux kernel there was ide-scsi support.
> With early 2.6 there was dev=ATAPI:x,y,z.
> 
> Nowadays with recent kernels (for example 2.6.28) i can use two namings.
> The /dev/sr0 and the usual x,y,z naming.

Joerg has given some advice, but I just wanted to add this:

When using dev=FOO:x,y,z on recent 2.6 Linux kernels, FOO should be
ATA and not ATAPI.


-- 
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org

Re: cdrecord: compiling failure on RHEL3 due to MKLINKS

[Greg Wooledge]

On Tue, Jan 13, 2009 at 01:58:15PM +0100, Giulio Orsero wrote:
>  System data
> OS: Linux 2.4.33 (RHEL3)
> cdrecord:  2.01.01a55
>   
>  Problem
> compiling with
>   $ make
> fails due to, I think, the way/order in which make (3.79.1) processes
> missing files.

If you're using GNU make (which you appear to be, based on that version
string), here's the easiest way to do it:

$ sudo ln -s /usr/bin/make /usr/local/bin/gmake
$ gmake

Joerg also shipped a wrapper script called "Gmake" in the top level
directory of the cdrtools source tree, so I suppose you could try
running

$ ./Gmake

instead, but having the gmake symlink in /usr/local/bin will help you
in the long run with other programs that expect "gmake" to exist.


-- 
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org

Re: Issues with cdrsin and USB devices on RHEL5

[Greg Wooledge]

On Mon, Jul 14, 2008 at 10:45:25PM +0200, Giulio Orsero wrote:
>  /lib/udev/check-cdrom.sh
> #!/bin/bash
...
> pos=$[$pos+1]

Dear gods.  Didn't anyone tell them that $[ is deprecated?

pos=$(($pos+1))

... is the preferred syntax, and is POSIX/ksh compatible.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrecord -scanbus problem

[Greg Wooledge]

On Mon, Jun 23, 2008 at 03:00:17PM -0400, Bill Davidsen wrote:
> Did you read what he wrote? He clearly says "as root" in the very 
> paragraph you quoted.
> This can be done by reading ALL of what he wrote and understanding what 
> it says.
> You did not do that...

And yet... it turned out that Joerg was correct.  The cdrecord process
was indeed running without UID 0 privileges.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrecord -scanbus problem

[Greg Wooledge]

On Mon, Jun 23, 2008 at 01:41:00PM +0200, [EMAIL PROTECTED] wrote:
> This is strange. I certainly ran it as root, like I always do.
> It is installed as: -rwsr-xr-x 1 bin bin
> Now, when I changed the owner to root:root, it ran.
> I changed the owner back to bin:bin and it still runs...
> I'm confused now!

It probably lost its setuid bit during the chowns, which fixed the issue.
Since having it installed setuid bin is clearly not useful, I'm rather
confused why it was done that way in the first place.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Help: Burning multisession DVD+R with cdrecord 2.01.01a37

[Greg Wooledge]

On Wed, Feb 13, 2008 at 10:21:48AM -0600, Eric Wanchic wrote:
> Slight install issue :( I tried a simple command: cdrskin and recieved 
> this error:
> 
> cdrskin: error while loading shared libraries: libburn.so.4: cannot open 
> shared object file: No such file or directory

If this is on Linux, check the /etc/ld.so.conf file, and make sure
the location of the shared libraries is in there.  Then, if you change
that file, run ldconfig.  (See "man ld.so" and "man ldconfig".)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Doesn't wodim close disk ?

[Greg Wooledge]

On Tue, Jan 01, 2008 at 01:54:43PM +0100, Gregoire Favre wrote:
> #!/bin/bash
[...]
> UNLOCK='cdrdao unlock --device 0,1,0 --driver generic-mmc && sleep 1'
[...]
> #$UNLOCK

Good thing this is commented out, because that would not have worked.

Try using a function instead:

unlock() {
  cdrdao unlock ... && sleep 1
}
...
unlock

You can't stick a complex command (foo && bar) in a variable and execute
it with a simple parameter expansion -- you would have to use eval for
that, and you really don't want to do that.  Just use a function.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrecord problems

[Greg Wooledge]

On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote:
> Perhaps I am talking out of turn here, but isn't this mailing list
> restricted to covering the Debian fork (reference
> )?

No, this mailing list predates 2006 by quite some time.  It's a general
list for discussion of all CD and DVD writing software, although in
practice, it's just for Unix-type systems.

It just happens to be hosted by Debian.

Don't let the flame wars get to you... wodim is just as much on-topic
here as cdrecord is, and each one has its place.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem with Samsung CDRW/DVD SM-308B

[Greg Wooledge]

On Fri, May 04, 2007 at 06:21:06PM +0200, Joerg Schilling wrote:
> Greg Wooledge <[EMAIL PROTECTED]> wrote:
> >
> > This is a valid point, and very frustrating -- especially when the stable
> > versions also seem to expire after a couple years.  (But in his defense,
> > after this happened, I was able to build a cdrecord alpha on my HP-UX 10.20
> > box and replace the now-defunct "stable" one.  It works.  Until this one
> > expires, anyway.)
> 
> If you were able to read sources, you would know that your claims from above 
> are lies..

Does this sentence mean, "You should have dug through the source code,
found the place where it expires, and changed it yourself."?

I could probably do that, but it was easier to download an alpha source
tarball instead.  Maybe that's your intention: to convince people to
upgrade to newer versions.  If so, fine, but I do wish the error messages
were clearer.

Also, the expired stable releases to which I refered in the first sentence
were NOT accompanied by source code.  They were your pre-compiled
binary-only cdrecord-ProDVD releases for the HP-UX 10.20 platform,
before you freed the source for the ProDVD part.  So, modifying the
source code actually wouldn't have been an option for me with those.

I certainly don't intend to spread any lies here.  If I've misunderstood
something (such as the cryptic "Alarm call" error message that I get),
then I may be guilty of unintentionally spreading misinformation, but
that's a bit different from outright lying.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem with Samsung CDRW/DVD SM-308B

[Greg Wooledge]

On Fri, May 04, 2007 at 09:21:17AM -0400, Bill Davidsen wrote:
> Greg Wooledge wrote:
> >http://kerneltrap.org/node/view/3513

> Jo"erg constantly complains about bugs in derived versions of 
> cdrecord, and old versions of his software, and hasn't released a stable 
> version in years and tells people to use alpha quality releases.

This is a valid point, and very frustrating -- especially when the stable
versions also seem to expire after a couple years.  (But in his defense,
after this happened, I was able to build a cdrecord alpha on my HP-UX 10.20
box and replace the now-defunct "stable" one.  It works.  Until this one
expires, anyway.)

(Hmm... y'know what would be handy?  A command line switch to show when
cdrecord expires.  So I could PLAN for this sort of thing, rather than
getting called by users saying that they can't burn CDs.)

(Also, a better error message than "Alarm call".)

> To 
> discourage people from trying a released stable kernel before claiming a 
> Linux bug seems pretty hypocritical to me.

There hasn't been a stable Linux kernel release since 2.4.*.  Linux 2.6.*
is a development series.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem with Samsung CDRW/DVD SM-308B

[Greg Wooledge]

On Sun, Apr 29, 2007 at 08:43:49PM -0400, Bill Davidsen wrote:
> Joerg Schilling wrote:
> >Note that the Linux kernel folks do not like that these sources are used 
> >and claim that they are not useful for running a stable system. They 
> >rather point
> >you to a distribution..

> I am very surprised to hear this from you! You have complained many time 
> over the years that people were finding problems in modified versions of 
> cdrecord and blaming errors on your source. [...]

Joerg is correct here.

http://kerneltrap.org/node/view/3513

 "Andrew's vision, as expressed at the summit, is that the mainline
 kernel will be the fastest and most feature-rich kernel around, but
 not, necessarily, the most stable. Final stabilization is to be
 done by distributors (as happens now, really), but the distributors
 are expected to merge their patches quickly."

This quote basically applies to all 2.6.* kernels.  I stopped building
my own Linux kernels from source a couple years ago.  It's just not
worth the pain.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: autotools

[Greg Wooledge]

On Wed, Apr 25, 2007 at 01:13:14AM +1200, Volker Kuhlmann wrote:
> I have no old "authoritative" sh at hand, but a Solaris 2.7 /bin/sh
> spits a dummy on an empty item list. I view that as a dumb design (one
> would have to enclose for loops in a check for empty item lists), since
> corrected.

I don't have a copy of POSIX.2 (the shell stuff), so I have to refer to
the Single Unix Specification:

http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_009_004_002

for name [ in word ... ]
do
compound-list
done

First, the list of words following in will be expanded to generate a list
of items. Then, the variable name will be set to each item, in turn,
and the compound-list executed each time. If no items result from the
expansion, the compound-list will not be executed.


You don't have to perform a separate check for an "empty item list".  This
is perfectly valid, and will do nothing:

  words=""
  for i in $words; do echo hello, world; done

If Solaris's shell is giving any output or errors from the commands above,
then it's crap.  (Which means autoconf would have to work around it.)

For Joerg: the fact that Solaris does NOT put its POSIX-compliant shell
in /bin/sh is a source of unending pain.  Since you can't use

  #!PATH=`getconf PATH`; sh

in a script, it's useless in real life.  Real scripts have to put SOMETHING
on the shebang line, and the only thing we can use is

  #!/bin/sh

Gods, how I wish POSIX had mandated something like "posix-shell"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: problems writing a large file to DVD+R Double Layer disk

[Greg Wooledge]

On Mon, Apr 23, 2007 at 04:31:53PM +0200, Thomas Schmitt wrote:
> I got an antiquity online (some SuSE 6.x):
>   $ uname -a
>   Linux * 2.2.13 #1 Mon Nov 8 15:51:29 CET 1999 i686 unknown
>   $ for i in ; do echo $i ; done
>   bash: syntax error near unexpected token `;'
>   $ for i in
>   bash: syntax error near unexpected token `in'
>   $ for i in 1
>   > do echo $i
>   > done
>   1
>   $

Which version of bash is that?  I can't reproduce that result at all.

svr1:~$ cat /etc/redhat-release 
Red Hat Linux release 5.2 (Apollo)
svr1:~$ echo $BASH_VERSION
1.14.7(1)
svr1:~$ for x in
> do
> echo
> done
svr1:~$ for i in ; do echo $i ; done
svr1:~$ 

I'm not saying that the syntax is valid -- just that I can't find ANY
system that can reproduce this error.  I understand all about writing
portable scripts with autoconf, but without a way to TEST various things,
writing portable code becomes a whole lot harder.  My oldest bash (1.14.7)
and dash (0.5.2) both accept it as valid.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: problems writing a large file to DVD+R Double Layer disk

[Greg Wooledge]

On Sun, Apr 22, 2007 at 12:17:57PM +0200, Thomas Schmitt wrote:
> I'll have to correct that via sed.
>test -z 1 && for ac_header in dummy
> should be a single line repair of
>for ac_header in

I don't understand this "repair".  test -z 1 will always return "false",
because "1" is not a zero-length string.  So you might as well just comment
out the "for ac_header in dummy" line altogether.

As far as the original code goes, I'd have to see the entire "for"
loop to know what the actual problem is.  Since I don't have access to
a Solaris system (with its ancient pre-POSIX /bin/sh), and since dash
gives me no errors when I run

  for ac_header in
  do
  echo
  done

that means I don't have any systems that are prehistoric enough to
duplicate the bug -- assuming this "for" loop really is the bug at all.

It seems more likely that there's really some sort of mistake *before*
the "for" loop, which would mean tracking backward through 2 lines
of ./configure code to try to find it... good luck with that.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Need help

[Greg Wooledge]

On Thu, Jan 11, 2007 at 02:57:15PM +0100, Joerg Schilling wrote:
> cdrecord works without real problems on Linux-2.6 if you install it correctly
> suid root.
> 
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
> http://cdrecord.berlios.de/old/private/problems.html

I looked at the HTTP link above.  It does not contain any of the words
"setuid", "suid" or "root".  It doesn't even contain the word "install",
except as part of "installation", and that's only in the paragraph that
says ATAPI is supported.

So I don't really see why you gave us that URL.

> Some old versions do not [...]

Where "old" means "anything not in my alpha/ subdirectory"?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Need help

[Greg Wooledge]

On Wed, Jan 10, 2007 at 01:41:21PM -0800, Shim, JaiX K wrote:
> I tried "cdrecord -scanbus". But I got the following error message.
> 
>  
> 
> "cdrecord: No such file or directory. Cannot open SCSI driver."

Sounds like you run Linux 2.6.

If you want any help, you're going to have to tell us a lot more detail --
which version of cdrecord, which operating system, etc.  (Although if
your platform is Linux 2.6, all the help you'll get is "don't try to run
cdrecord -scanbus on Linux 2.6", or possibly "we've attempted a workaround
for Linux 2.6 in cdrecord version xx.yy.zz, and you can try that".)

Also, your Subject: line is abysmal.  Some people filter which messages
they'll read based on that, and yours screams "unhelpable" or "spammer".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrecord-2.01.01a21 refuses work on Linux 2.4 if non-ide-scsi DVD-ROM is present

[Greg Wooledge]

On Wed, Nov 29, 2006 at 01:00:35AM +0100, [EMAIL PROTECTED] wrote:
> > ./configure: line 19396: syntax error near unexpected token `in'
> > ./configure: line 19396: `for ac_header in'
> 
> That looks much like an icculus.org/burn libburn-0.2 tarball
> or CVS version prior to about march 2006. (Newer bash versions
> accept an empty "for" list. I noticed that problem only on
> a SuSE 7.2 system. Meanwhile our ./configure is fat but legal.) 

Is there a version of bash that *doesn't*?  My testing indicates that
the following command

  for x in $nothing_here; do echo "$x"; done

works just fine (does nothing, and produces no errors) in bash 1.14 (the
oldest I have available) and in HP-UX's /sbin/sh (the oldest traditional
Bourne shell I have available), as well as dash 0.5.2.  I couldn't find
any shell where it failed.

The syntax error quoted above probably indicates a problem earlier in the
script, which simply didn't show up until line 19396.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Excluding paths with mkisofs

[Greg Wooledge]

On Sat, Nov 11, 2006 at 08:56:56PM +0100, Joerg Schilling wrote:
> I thought people should know the find(1) program...so it should be obvious to 
> call
> 
>   mkisofs -o some-file -find . ! -path 'pattern'

You'd be amazed at how poorly understood find is.  I've been doing Unix
stuff for over 15 years now, and I still have to re-read the documentation
every time someone asks how to use find -prune.  (! -path will still
descend into every subdirectory, even the ones that will be thrown away;
-prune causes find to skip over subdirectories entirely, saving a lot
of time.  But it's hard to use because of awkward syntax and a lack of
useful examples in the man pages -- in particular, the GNU man pages.)

find . -path 'pattern' -prune -o -print


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: "Wrong medium type" from growisofs...

[Greg Wooledge]

On Tue, Oct 17, 2006 at 08:37:30PM +0200, Christian Henz wrote:
> The command used was "cdrecord -v -atip dev=ATAPI:/dev/hdc".

The ATAPI: kernel interface is different from the ATA: interface.
You might wish to try the ATA: one instead -- that often produces
better results.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Cdrtools-2.01.01a13 ready with libfind

[Greg Wooledge]

On Fri, Sep 08, 2006 at 10:37:30AM -0400, [EMAIL PROTECTED] wrote:
> Yes, -uid is sorta global, so you will have all files owned by root. But then 
> again you won't be able to have two -find statements in one
> invocation, while processing stdin is allowing you to enumerate files with
> multiple find statements or anything else you can think of.

I'm surprised Jörg didn't simply use \; in his -find syntax, so that you
could put additional mkisofs arguments after the -find ... \; (including
a second -find).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: HP cd-writer 8200 and cdrecord

[Greg Wooledge]

On Mon, Jul 24, 2006 at 11:42:25AM +0200, Dominique Dumont wrote:
> Are you running kernel 2.4 or 2.6 ?

Based on the fact that "cdrecord -scanbus" actually succeeded, I'd
guess 2.4.x.

The original poster might want to look into ide-scsi documentation and
tutorials; for example,
.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Unidentified subject!

[Greg Wooledge]

On Sat, Feb 18, 2006 at 08:56:12PM -0800, charles robison wrote:
> when i burn a cd with my burner an play it in cd player it goes in revirce. 
> what is wrong?

http://www.catb.org/~esr/faqs/smart-questions.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: dvd+rw-tools update [6.1, O_EXCL]

[Greg Wooledge]

On Mon, Feb 13, 2006 at 10:27:52PM +0100, Matthias Andree wrote:
> [ -f rpl8 ] && whatever
> 
> fails if rpl8 is missing, and does not only skip "whatever" (here:
> install), but also exits the whole compound command with code 1, which
> aborts the make target.
> 
> "[ CONDITION ] && whatever" is therefore a Makefile pitfall.

Try this:

[ -f rpl8 ] && whatever || true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrtools cdrecord/cdrecord.c

[Greg Wooledge]

On Tue, Jan 24, 2006 at 07:47:00AM -0500, Bill Davidsen wrote:
> Joerg Schilling wrote:
> >For this reason, I cannot try out problems with Linux versions ewer than 
> >2.6.8.1
> >unless people give access to machines where newer versions are installed.
> >
> Did you ever wonder why no one provides access?

... because none of the REST of us have time to play "chase the latest
unstable Linux 2.6 kernel" games either.  Well, except for the Gentoo
users -- obviously *they* have time, since that seems to be what they
devote their entire lives to.

HP-UX imadev B.10.20 A 9000/785 2008xx two-user license
OpenBSD pegasus 3.8 GENERIC#0 i386
Linux griffon 2.4.32 #7 Mon Dec 5 19:58:55 EST 2005 i686 GNU/Linux


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrtools cdrecord/cdrecord.c

[Greg Wooledge]

On Mon, Jan 23, 2006 at 12:00:59AM +0100, Joerg Schilling wrote:
> Maybe the problem is that Debian accepts bug reports for things that are not 
> broken (at least not inside cdrecord).

Debian is not a monolithic entity.  It's a large group of individual
developers, each of whom works in complete isolation, and has almost
total authority over his or her assigned packages.

Getting a Debian developer to accept a patch (or bug, or whatever) can
be easy or it can be impossible.  It depends on the developer.

This can be rather frustrating, if the package you're dealing with happens
to have one of the obtuse developers.  (I can name one such package and
developer, but it's off topic here, as it's not related to CD writing.)

Now, clearly Steve and Joerg aren't seeing eye to eye on some issues.  I
don't know enough about the issues in question to know which one of them
is right.  As an end user, I have choices -- I can use the Debian version
of a program, or I can use the upstream author's version.  Most of the time,
the Debian version of a package works fine.  In a few cases, the upstream
version works better.

So, end users like me should just try both versions and use whichever one
works better.  Continuing to flame Joerg or Steve is not productive.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: What to do if...

[Greg Wooledge]

On Tue, Jan 03, 2006 at 04:39:41PM -0500, Mangan, Cate A (N-Superior Technical 
Resources) wrote:
> Hello O Great and Powerful Guru,

> What would you say if I told you that I put in a r-w DVD and the
> software thinks that there is too much data. - Sees the DVD as though
> it's a CD-ROM when trying to burn to the DVD? Any hints on Linux
> 2.4.20-31_9?

The Guru isn't in, but I'd say you need to tell us what drive you're
using, what media you're using, and what software you're using to do the
burning.

The free cdrecord program (i.e., not cdrecord-ProDVD, which is non-free)
can't handle arbitrary DVD writing.  It's only for CDs.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: License issue?

[Greg Wooledge]

On Thu, Aug 18, 2005 at 02:41:20PM +0200, Joerg Schilling wrote:
> Once you put some code under a OSI compliant license, you cannot
> give someone else exclusive rights anymore.

That is not correct.

The copyright holder can give the code to Microsoft and say, "Here, use
this in the next version of Windows any way you like."  Microsoft will
*not* be under the obligations of the GPL.

However, if Microsoft takes the GPL-licensed version of the software
and incorporates it into Windows, then they *would* have to comply with
the terms of the GPL.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: License issue?

[Greg Wooledge]

On Thu, Aug 18, 2005 at 07:43:59PM +0100, Alvaro Lopez Ortega wrote:
> ===
> Version 5.6 adds support for Solaris 2.x [commercial licensing terms
> for distribution on Solaris are to be settled with Inserve
> Technology].
> ===
> 
>   I am wondering how is it possible to this be compatible with the GPL
>   license (which is the only license I have found on
>   dvd+rw-tools-5.21.4.10.8/LICENSE file).

The person who writes the software holds the copyright on it.
The copyright holder may release the software to various people or
organizations under as many licenses as he likes.

So you might get it under the GPL, but Sun gets to use it under a
different license.

Nothing that Sun does with their licensed copy of the software will affect
your rights under the GPL in any way.  Likewise, none of the rights that
you received under the GPL can be applied to the version that Sun has.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mkisofs aborts but exit value is 0

[Greg Wooledge]

On Mon, Aug 08, 2005 at 05:56:02PM +0200, Joerg Schilling wrote:
> P.S.: which recent OS does not come with star?

Microsoft Windows.  But it *can* read ISO 9660 CDs... which makes
backups using mkisofs + cdrecord quite handy for many situations.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: expired cdrecord-ProDVD builds for HP-UX

[Greg Wooledge]

On Fri, May 13, 2005 at 04:17:35PM +0200, [EMAIL PROTECTED] wrote:
> i resolved my "alarm clock" by downloading only
> the current wrapper script 
>  ftp://ftp.berlios.de/pub/cdrecord/ProDVD/cdrecord-wrapper.sh
> which obviously contains the new license key.
> (Saying: "Key Expires ---> 2005 Oct 22 18:53:20")

It's not a license key issue.  I checked that first, and we've got the
key from February 2005.

The alpha releases have built-in expiration dates, and they will simply
stop working after a time regardless of how recent the key is.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

expired cdrecord-ProDVD builds for HP-UX

[Greg Wooledge]

One of my coworkers recently noticed the infamous "Alarm clock" error
from cdrecord-ProDVD on our HP-UX workstations.  She's been using
cdrecord-ProDVD 2.01a27 which is the newest version available on the
berlios FTP site for HP-UX.  Apparently, this alpha release is expired,
and there is no 2.01 release to take its place for HP-UX yet.  I advised
her to change the symbolic link to point to the 2.0 version instead.

Is Joerg planning to release newer versions of cdrecord-ProDVD for
HP-UX 10.20, or are we stuck with 2.0 forever?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mount question

[Greg Wooledge]

On Mon, May 02, 2005 at 05:44:52PM +0200, Joerg Schilling wrote:
> Suid shell scripts work since approx. 25 years.

Only on *some* operating systems.  On others, the setuid/setgid bits
are ignored when the kernel handles the shebang.

Example 1:
imadev:~$ uname -a
HP-UX imadev B.10.20 A 9000/785 2008897791 two-user license
imadev:~$ id
uid=563(wooledg) gid=22(pgmr) groups=1002(webauth),208(opgmr)
imadev:~$ ls -l foo.sh
-rwsr-xr-x   1 root   sys 22 May  3 08:04 foo.sh
imadev:~$ cat foo.sh
#!/bin/sh
/usr/bin/id
imadev:~$ ./foo.sh
uid=563(wooledg) gid=22(pgmr) euid=0(root) groups=1002(webauth),208(opgmr)

Example 2:
svr1a:~$ uname -a
Linux svr1a 2.2.26 #2 Wed Feb 25 12:48:36 EST 2004 i686 unknown
svr1a:~$ id
uid=563(wooledg) gid=22(voice) 
groups=22(voice),97(vsifax),1002(webauth),208(opgmr)
svr1a:~$ ls -l foo.sh
-rwsr-xr-x1 root sys22 May  3 08:04 foo.sh
svr1a:~$ cat foo.sh
#!/bin/sh
/usr/bin/id
svr1a:~$ ./foo.sh
uid=563(wooledg) gid=22(voice) 
groups=22(voice),97(vsifax),1002(webauth),208(opgmr)

That is, in fact, precisely the same file.  My home dir is shared over NFS.
Just to alleviate any questions of mount options, here's what the Linux box
actually shows for the file system in question:

imadev:/home/wooledg on /net/home/wooledg type nfs 
(rw,hard,intr,addr=10.76.142.103)

I could repeat the test on /var/tmp if you wish.  That's a local ext2
file system with no options other than "rw".

> The problem if course is security...
> 
> Since 1990, /bin/sh will revert to euid==uid in case euid!=uid
> except when you use:
> 
> #!/bin/sh -p

svr1a:~$ ls -l foo.sh 
-rwsr-xr-x1 root sys25 May  3 08:07 foo.sh
svr1a:~$ cat foo.sh
#!/bin/sh -p
/usr/bin/id
svr1a:~$ ./foo.sh
uid=563(wooledg) gid=22(voice) 
groups=22(voice),97(vsifax),1002(webauth),208(opgmr)

The "-p" has nothing to do with it on this system.  Perhaps on Solaris it
might have some effect, but on Linux, there is none.  It's the *kernel*
that ignores the setuid bit on a shebang-driven script.  Nothing that
/bin/sh does can elevate its own privileges beyond those with which it
was spawned.  (If Solaris can do it, then it's because /bin/sh is setuid,
or has a setuid helper/consort program that it can invoke, a la suidperl.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DVD+RW-tools for HP-UX

[Greg Wooledge]

On Thu, Mar 31, 2005 at 07:33:31PM +0300, Ismail Donmez wrote:
> On Thursday 31 March 2005 18:37, Daulerio, Michael N wrote:
> > Can the DVD+RW-tools package be compiled for HP-UX 10.20 systems or is
> > it meant only for Linux systems.
> 
> http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXDVDWRITE

No, it does not work on HP-UX 10.20, and probably never will.  It's only
been ported to HP-UX 11.

For DVD writing on HP-UX 10.20, cdrecord-ProDVD is the only choice.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Errors with 8x media, works in other OS

[Greg Wooledge]

On Wed, Mar 02, 2005 at 08:58:38AM +0100, Alexander Noe' wrote:
> How stupid can one single person actually benot long ago, a certain
> "takeshima" broke the record one sourceforge (read about that
> here: http://linuxfr.org/~zeb/17243.html ), but you are some serious
> competition for that guy. Your email address suggests that english
> is your native language, so you should actually know what "buy" or
> "pay" means...
> 
> ftp://ftp.berlios.de/pub/schily/cdrecord/ProDVD/README

Could you please quote the relevant parts of the message to which you're
responding?  I can't figure out whom you're addressing with your insults.

I'm one of the people who tried to get a response from Joerg about
obtaining a license for cdrecord-ProDVD for our HP-UX 10 systems here
at the Cleveland Clinic.  I never received a reply.

If you've ever managed to obtain a license for cdrecord-ProDVD, there
are many of us who'd love to know how you did it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DVD+, buffer underrun, write speed and verification issues

[Greg Wooledge]

On Fri, Jan 28, 2005 at 03:18:10AM -0500, Michael Shell wrote:
> Another way to verify
> is to use md5sum. However, md5sum does not seem to have an -n which implies
> that dd must first be used to get the first N bytes of /dev/dvd where N is
> the file length of the image - and doing so can take up a lot of HD space.

You could just use a pipe:

  dd if=/dev/dvd bs=N count=1 | md5sum


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: "LUN appears to be stuck writing LBA=10h, retry in 0ms" kills my DVD+R...

[Greg Wooledge]

On Tue, Jan 04, 2005 at 11:58:10PM +0100, Alessandro Suardi wrote:
> FC3 adds in fstab entries for CD/DVD drives with a syntax
>  I don't know but that quite clearly hints to automounting:
> 
> #/dev/hdd/media/cdrecorder   auto
> pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
> #/dev/hdc/media/cdrecorder1  auto
> pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0

The first "auto" (field three) is the file system type; so it attempts
to detect the type of file system automatically.  The "noauto" in the
long string of options (field four) means it does *not* mount this file
system at system boot time; you'd have to ask for it specifically.

If either of these systems is to be automounted, then there would have
to be entries for them in a different file, usually /etc/auto.master
or something that's read in after that.  /etc/fstab doesn't control
automounting at all.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DVD-R readback error on SONY DRU510A

[Greg Wooledge]

On Tue, Nov 02, 2004 at 12:50:30PM +1300, Volker Kuhlmann wrote:
> >   Vendor: SONY  Model: DVD RW DRU-510A   Rev: 1.0d
> 
> I think the burner doesn't handle that media properly. AFAICT the Sony
> 510 isn't so hot when it comes to compatibility with a lot of different
> media.

The SONY DRU-530A is quite bad as well.  We had much better luck with
the SONY DRU-500A.  Too bad we can't buy those any more.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sony DRU-700A gets errors writing ordinary CD.

[Greg Wooledge]

On Mon, Oct 25, 2004 at 12:48:35PM +0800, Clare Johnstone wrote:
> Linux version 2.6.7, Distribution Crux (i.e. no frills).

> [EMAIL PROTECTED]:/home/clare# cdrecord -v -dao speed=16 fs=16m dev=ATAPI:0,0,0
> 041001.iso
> Cdrecord 2.00.3 (i586-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling

> Writing pregap for track 1 at -150
> Starting new track at sector: 0
> Track 01:6 of  275 MB written (fifo  83%) [buf   5%]  12.4x.cdrecord:
> Input/output erro
> r. write_g1: scsi sendcmd: no error
> CDB:  2A 00 00 00 0C 5A 00 00 1F 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 0C 09 00 00 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.003s timeout 200s

Looks like a buffer underrun to me.  Try turning on the "burnfree" option,
maybe.  Failing that, I'd at least remove the speed=16 parameter, since
your output above shows 12.4x.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: blank=all only works in isolation

[Greg Wooledge]

On Mon, Oct 18, 2004 at 01:58:17PM -0700, none none wrote:
> cdrecord -vv dev=1,0 blank=all /path/to/some.iso
> 
> NEVER works. I typically get something like:

Hah.  We've got Sony DRU-530A drives that are completely incapable
of blanking a DVD-RW or CD-RW.  At all.  We have to use a different
drive (e.g. the Sony DRU-500A).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrecord-ProDVD key expired?

[Greg Wooledge]

On Mon, May 03, 2004 at 09:23:23AM -0600, Ashish Rangole wrote:
> I wonder if anybody has ever had any success in getting 
> one from Joerg. Please let me know if anybody has. 

A colleague of mine has also attempted to get permanent keys from Joerg,
without success.  He's with a commercial entity (a business associate
of ours), though, and not a non-profit.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

cdrecord-ProDVD key expired?

[Greg Wooledge]

I'm getting the infamous "Alarm clock" error during the countdown
when trying to burn with cdrecord-ProDVD.  I've got the key from
the README file (ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README)
which was updated on 2004-01-26... and it's only May.  Is this key
expired already?

Once again, what's the procedure for getting a *real* (non-expiring)
key?  We'd be willing to buy one for our organization if necessary.
We're a deparment within a large but non-profit hospital.  We burn
data CDs and occasionally DVDs for both doctors and patients.

Details:  This is an HP-UX 10.20 system.  I've burned using this software
on this computer with the same hardware many, many time.  This looks
precisely like the error I get when a cdrecord-ProDVD key expires.

# prodvd -v dev=1,0,0 sarge-hppa-netinst.iso
Cdrecord-ProDVD-Clone 2.01a11 (hppa1.1-hp-hpux10.20) Copyright (C) 1995-2003 Jörg 
Schilling
Unlocked features: ProDVD Clone 
Limited  features: 
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
Using libscg version 'schily-0.7'
atapi: 0
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities   : SYNC 
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision   : '2.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-RW sequential overwrite 
Profile: DVD-RW restricted overwrite 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R (current)
Profile: CD-ROM 
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8112896 = 7922 KB
FIFO size  : 4194304 = 4096 KB
Track 01: data97 MB
Total size:  112 MB (11:07.12) = 50034 sectors
Lout start:  112 MB (11:09/09) = 50034 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 3
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type B, low Beta category (B-) (4)
  ATIP start of lead in:  -11580 (97:27/45)
  ATIP start of lead out: 359849 (79:59/74)
Disk type:Short strategy type (Phthalocyanine or similar)
Manuf. index: 9
Manufacturer: Kodak Japan Limited
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 309815
Starting to write CD/DVD at speed 4 in real TAO mode for single session.
Last chance to quit, starting real write7 seconds.Alarm clock


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Best way to write DVD+R? growisofs ?

[Greg Wooledge]

On Sun, Apr 25, 2004 at 04:02:26PM +0200, Gregoire Favre wrote:
> I think I already got the latest firmware from Sony...

The word "latest" is a big red flag for me.  If you just want to say
that you don't know what version of the firmware you have, then say
that.  Don't ever say "I have the latest..." because then we'll assume
that you don't know what version you have *and* that you don't know
which version is the newest at the time of your writing.

This applies to all the different forms of end-user support that I'm
involved in, not just CD/DVD writer firmware.  If you come into #debian
and say you "have the latest kernel", and it turns out you're actually
running 2.2.20-idepci because you just hit Enter on the Debian 3.0
installer's boot prompt, expect to be ridiculed. ;-)

Re: Best way to write DVD+R? growisofs ?

[Greg Wooledge]

On Sun, Apr 25, 2004 at 04:02:26PM +0200, Gregoire Favre wrote:
> I think I already got the latest firmware from Sony...

The word "latest" is a big red flag for me.  If you just want to say
that you don't know what version of the firmware you have, then say
that.  Don't ever say "I have the latest..." because then we'll assume
that you don't know what version you have *and* that you don't know
which version is the newest at the time of your writing.

This applies to all the different forms of end-user support that I'm
involved in, not just CD/DVD writer firmware.  If you come into #debian
and say you "have the latest kernel", and it turns out you're actually
running 2.2.20-idepci because you just hit Enter on the Debian 3.0
installer's boot prompt, expect to be ridiculed. ;-)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrtools-2.01a28 ready

[Greg Wooledge]

On Wed, Apr 21, 2004 at 09:24:01AM +0200, Helmut Jarausch wrote:
> > ftp://ftp.berlios.de/pub/cdrecord/alpha ...
> 
> Am I the only one having problems to access this site?
> I get "421 Service not available, remote server has closed connection"
> most of the time.

Any time I attempt to reach it through a web browser, using squid as
a proxy, I can't do it.  Apparently it doesn't like squid's anonymous
logins, or default password, or something.  But then it works fine if
I use a "normal" FTP client.  In fact, it's working right now.

Also, if you don't have a PTR record for your visible IP address, many
FTP servers will reject you.  I don't know whether ftp.berlios.de is one
of these, but on several occasions in the past, I've had better results
by ssh'ing from work to my DSL box at home, obtaining files on the
DSL box, and then sending them back to myself at work.  (The NAT setup
at work doesn't have a valid PTR record for its external IP address!)

I personally look forward to the death of FTP.  I hate that protocol
with a passion.  But that's a rant for a different mailing list :)

Re: cdrtools-2.01a28 ready

[Greg Wooledge]

On Wed, Apr 21, 2004 at 09:24:01AM +0200, Helmut Jarausch wrote:
> > ftp://ftp.berlios.de/pub/cdrecord/alpha ...
> 
> Am I the only one having problems to access this site?
> I get "421 Service not available, remote server has closed connection"
> most of the time.

Any time I attempt to reach it through a web browser, using squid as
a proxy, I can't do it.  Apparently it doesn't like squid's anonymous
logins, or default password, or something.  But then it works fine if
I use a "normal" FTP client.  In fact, it's working right now.

Also, if you don't have a PTR record for your visible IP address, many
FTP servers will reject you.  I don't know whether ftp.berlios.de is one
of these, but on several occasions in the past, I've had better results
by ssh'ing from work to my DSL box at home, obtaining files on the
DSL box, and then sending them back to myself at work.  (The NAT setup
at work doesn't have a valid PTR record for its external IP address!)

I personally look forward to the death of FTP.  I hate that protocol
with a passion.  But that's a rant for a different mailing list :)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: writing speed issue with dvd+rw-tools

[Greg Wooledge]

On Tue, Mar 02, 2004 at 07:57:35PM +0100, Lourens Veen wrote:
> - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key
> - cdrecord-ProDVD will burn more than 1 GB of data, but only with a 
> key
> - the key must be obtained from you
> - the key is time limited
> - the key restricts usage (burning speed for CDs)
> - it is your right to licence cdrecord-ProDVD like this
  - all attempts to buy a license key go unanswered

Re: writing speed issue with dvd+rw-tools

[Greg Wooledge]

On Tue, Mar 02, 2004 at 07:57:35PM +0100, Lourens Veen wrote:
> - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key
> - cdrecord-ProDVD will burn more than 1 GB of data, but only with a 
> key
> - the key must be obtained from you
> - the key is time limited
> - the key restricts usage (burning speed for CDs)
> - it is your right to licence cdrecord-ProDVD like this
  - all attempts to buy a license key go unanswered


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: plextor px-708uf: cannot get disk type

[Greg Wooledge]

On Thu, Jan 29, 2004 at 05:43:46PM +0100, Joerg Schilling wrote:
> Note that I always
> install Linux in an extedned partition because Linux likes to call a Solaris
> Partition a "Linux Swap" partition. Fortunately, it does not swap on it
> immediately if there is no Linux swap signature on it.

That's somewhat misleading.  Linux doesn't automatically start swapping
on any partition with label "82" in the partition table.  You have to
explicitly issue the swapon command, or have the partition listed in
/etc/fstab, to use it for swap space.

And, as mentioned above, there must also be a valid swap signature,
created with mkswap.

If your distribution's installation tool automatically puts all partitions
it doesn't recognize into /etc/fstab as swap, then that's a problem with
your distribution's installation tool, not with Linux.  Try Debian instead.

Re: plextor px-708uf: cannot get disk type

[Greg Wooledge]

On Thu, Jan 29, 2004 at 05:43:46PM +0100, Joerg Schilling wrote:
> Note that I always
> install Linux in an extedned partition because Linux likes to call a Solaris
> Partition a "Linux Swap" partition. Fortunately, it does not swap on it
> immediately if there is no Linux swap signature on it.

That's somewhat misleading.  Linux doesn't automatically start swapping
on any partition with label "82" in the partition table.  You have to
explicitly issue the swapon command, or have the partition listed in
/etc/fstab, to use it for swap space.

And, as mentioned above, there must also be a valid swap signature,
created with mkswap.

If your distribution's installation tool automatically puts all partitions
it doesn't recognize into /etc/fstab as swap, then that's a problem with
your distribution's installation tool, not with Linux.  Try Debian instead.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [Cdrecord-developers] Cdrtools-2.01a25: Patch to make cdrtools 2.01a25 Linux compatible

[Greg Wooledge]

On Tue, Jan 27, 2004 at 09:01:56AM -0500, Ambrose Li wrote:
> Back "in the former times" (I started using GNU/Linux back
> when the only distros were SLS and Slackware), apps assumed
> that the kernel header files are in a "linux" directory in the
> system include path (the /usr/include/linux symlink, unless the
> user has a very strange setup). They need not assume there is
> anything in /usr/src/linux, though /usr/include/linux is likely
> a symlink to /usr/src/linux/include/linux.

True -- *but*, it must be pointed out that this is historic!  In a
modern GNU/Linux distribution, /usr/include/linux should *not* be
a symlink to anything at all.  It should be a plain directory containing
the kernel header files with which the GNU libc was built.

Every once in a while, someone comes along with a seriously broken
Debian system because they followed the advice in some old Slackware
HOWTO document from 1997, and made /usr/include/{linux,asm} symlinks
to some kernel source tree they happened to find somewhere.  The
only fix for it is to remove the symlinks they made by hand, and
reinstall the libc6-dev package.  (And in unstable now, the
linux-kernel-headers package.)

> And I have never
> heard of anyone hard-coding /usr/src/sys (nor have I heard of
> such a directory at all) in their makefiles.

That's where BSD keeps its kernel source tree.  BSD is dramatically
more consistent than GNU/Linux.

> I have never encountered any app that has such an elaborate
> setup to detect where the kernel include files are; I would tend
> to say that such elaborate setup is unnecessary.

Not quite true.  As has already been pointed out in this discussion,
there are different kinds of applications, and they need to use
different kinds of header files.

Most applications (like "hello, world") just use #include 
and so on.  These headers come from the libc development package.  This
case is easy.

Kernel modules need kernel headers -- specifically, they need the exact
kernel headers for the kernel that the module is going to be loaded into.
But there's no way of knowing exactly *where* the correct set of kernel
headers can be found, unless the sysadmin takes action when compiling
the module.  With Linux 2.4.x, there's a "build" symlink under the
/lib/modules tree which (theoretically) points back to /usr/src/linux-2.4.x
or wherever the kernel source tree was configured.  Failing that, the
kernel headers may be in a package (e.g. kernel-headers-2.4.18-bf2.4 in
Debian), which when installed will put them in a directory such as
/usr/src/kernel-headers-2.4.18-bf2.4/.  Or they may be in /usr/src/linux/.
Or they may be in /home/fred/kernels/.  There's no way to be sure,
so in the worst case the sysadmin who's building the module *WILL*
have to supply a -I flag to gcc.

Then there's a funky kind of application which seems to be in both user
space (like "hello, world") *and* kernel space at the same time.  It
uses normal libc headers, but it also uses kernel headers.  cdrecord
seems to be one of these kinds of applications.  I don't know *what*
the right way to build these kinds of applications is -- and I don't
think there's any concensus among the various developers either.

Re: [Cdrecord-developers] Cdrtools-2.01a25: Patch to make cdrtools 2.01a25 Linux compatible

[Greg Wooledge]

On Tue, Jan 27, 2004 at 09:01:56AM -0500, Ambrose Li wrote:
> Back "in the former times" (I started using GNU/Linux back
> when the only distros were SLS and Slackware), apps assumed
> that the kernel header files are in a "linux" directory in the
> system include path (the /usr/include/linux symlink, unless the
> user has a very strange setup). They need not assume there is
> anything in /usr/src/linux, though /usr/include/linux is likely
> a symlink to /usr/src/linux/include/linux.

True -- *but*, it must be pointed out that this is historic!  In a
modern GNU/Linux distribution, /usr/include/linux should *not* be
a symlink to anything at all.  It should be a plain directory containing
the kernel header files with which the GNU libc was built.

Every once in a while, someone comes along with a seriously broken
Debian system because they followed the advice in some old Slackware
HOWTO document from 1997, and made /usr/include/{linux,asm} symlinks
to some kernel source tree they happened to find somewhere.  The
only fix for it is to remove the symlinks they made by hand, and
reinstall the libc6-dev package.  (And in unstable now, the
linux-kernel-headers package.)

> And I have never
> heard of anyone hard-coding /usr/src/sys (nor have I heard of
> such a directory at all) in their makefiles.

That's where BSD keeps its kernel source tree.  BSD is dramatically
more consistent than GNU/Linux.

> I have never encountered any app that has such an elaborate
> setup to detect where the kernel include files are; I would tend
> to say that such elaborate setup is unnecessary.

Not quite true.  As has already been pointed out in this discussion,
there are different kinds of applications, and they need to use
different kinds of header files.

Most applications (like "hello, world") just use #include 
and so on.  These headers come from the libc development package.  This
case is easy.

Kernel modules need kernel headers -- specifically, they need the exact
kernel headers for the kernel that the module is going to be loaded into.
But there's no way of knowing exactly *where* the correct set of kernel
headers can be found, unless the sysadmin takes action when compiling
the module.  With Linux 2.4.x, there's a "build" symlink under the
/lib/modules tree which (theoretically) points back to /usr/src/linux-2.4.x
or wherever the kernel source tree was configured.  Failing that, the
kernel headers may be in a package (e.g. kernel-headers-2.4.18-bf2.4 in
Debian), which when installed will put them in a directory such as
/usr/src/kernel-headers-2.4.18-bf2.4/.  Or they may be in /usr/src/linux/.
Or they may be in /home/fred/kernels/.  There's no way to be sure,
so in the worst case the sysadmin who's building the module *WILL*
have to supply a -I flag to gcc.

Then there's a funky kind of application which seems to be in both user
space (like "hello, world") *and* kernel space at the same time.  It
uses normal libc headers, but it also uses kernel headers.  cdrecord
seems to be one of these kinds of applications.  I don't know *what*
the right way to build these kinds of applications is -- and I don't
think there's any concensus among the various developers either.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cdrtools-2.01a22 ready

[Greg Wooledge]

On Thu, Jan 08, 2004 at 11:10:54AM -0800, Scott Bronson wrote:
> Any chance this thread can be put to rest here?

You could try invoking Godwin's Law

Re: cdrtools-2.01a22 ready

[Greg Wooledge]

On Thu, Jan 08, 2004 at 11:10:54AM -0800, Scott Bronson wrote:
> Any chance this thread can be put to rest here?

You could try invoking Godwin's Law


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compilation problem on HPUX11

[Greg Wooledge]

On Tue, Dec 09, 2003 at 11:24:24AM +0100, Gansser, Martin wrote:
> dvd+rw-tools-5.14.4.7.4 # gmake
> gmake[1]: Entering directory `/users/mgansser/GNU/dvd+rw-tools-5.14.4.7.4'
> gcc  -O2 -c  -o growisofs.o growisofs.c
> g++  -O2 -fno-exceptions -c  growisofs_mmc.o growisofs_mmc.cpp
> g++: growisofs_mmc.o: No such file or directory

Clearly this g++ command is malformed.  Looking at Makefile.m4, I see
this:

.c.o:
$(CC) $(CFLAGS) -c  -o $@ $<
.cpp.o:
$(CXX) $(CXXFLAGS) -c  $@ $<

The "-c" on the last line above should be "-c -o", just like on the
second line.

Re: compilation problem on HPUX11

[Greg Wooledge]

On Tue, Dec 09, 2003 at 11:24:24AM +0100, Gansser, Martin wrote:
> dvd+rw-tools-5.14.4.7.4 # gmake
> gmake[1]: Entering directory `/users/mgansser/GNU/dvd+rw-tools-5.14.4.7.4'
> gcc  -O2 -c  -o growisofs.o growisofs.c
> g++  -O2 -fno-exceptions -c  growisofs_mmc.o growisofs_mmc.cpp
> g++: growisofs_mmc.o: No such file or directory

Clearly this g++ command is malformed.  Looking at Makefile.m4, I see
this:

.c.o:
$(CC) $(CFLAGS) -c  -o $@ $<
.cpp.o:
$(CXX) $(CXXFLAGS) -c  $@ $<

The "-c" on the last line above should be "-c -o", just like on the
second line.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: DVD recording adventures continued

[Greg Wooledge]

On Mon, Nov 24, 2003 at 11:48:20AM +0100, Joerg Schilling wrote:
> Note that unlike most software, my programs are higly portable and you may not
> notice that I e.g. put a lot of effort into the OS/2 port or a new upcoming
> vanilla DOS port.

As someone who's using cdrecord-ProDVD on HP-UX, I'd like to thank you
for that.

Re: Re: DVD recording adventures continued

[Greg Wooledge]

On Mon, Nov 24, 2003 at 11:48:20AM +0100, Joerg Schilling wrote:
> Note that unlike most software, my programs are higly portable and you may not
> notice that I e.g. put a lot of effort into the OS/2 port or a new upcoming
> vanilla DOS port.

As someone who's using cdrecord-ProDVD on HP-UX, I'd like to thank you
for that.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: trouble with DVD+R

[Greg Wooledge]

On Fri, Nov 07, 2003 at 08:05:02AM -0500, Steven Legowik wrote:
> I took a look at my copy of "Sphere" on both DVD drives and am somewhat 
> confused.  On both drives I get the IO errors when I cat the files to null, 
> yet both systems seem to be able to play the movie using ogle.

Make sure you're mounting the DVD as a UDF file system, and not as an
ISO 9660 file system.  Mounting a UDF file system as ISO 9660 gives
strange results (rather than a complete failure, which would have been
more useful).  I think I've seen that specific symptom before, but I
might be mis-remembering.

Re: trouble with DVD+R

[Greg Wooledge]

On Fri, Nov 07, 2003 at 08:05:02AM -0500, Steven Legowik wrote:
> I took a look at my copy of "Sphere" on both DVD drives and am somewhat 
> confused.  On both drives I get the IO errors when I cat the files to null, 
> yet both systems seem to be able to play the movie using ogle.

Make sure you're mounting the DVD as a UDF file system, and not as an
ISO 9660 file system.  Mounting a UDF file system as ISO 9660 gives
strange results (rather than a complete failure, which would have been
more useful).  I think I've seen that specific symptom before, but I
might be mis-remembering.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Incorrect Mail set up please correct!

[Greg Wooledge]

On Tue, Nov 04, 2003 at 05:33:40PM +1300, Volker Kuhlmann wrote:
> I *had* asked not to be cc'ed for list
> postings, if you ignore that, you'll have to put up with the bounce.

If that's so important to you, then you should configure your mail
software to add the Mail-Followup-To: header pointing to the mailing
list.

Re: Incorrect Mail set up please correct!

[Greg Wooledge]

On Tue, Nov 04, 2003 at 05:33:40PM +1300, Volker Kuhlmann wrote:
> I *had* asked not to be cc'ed for list
> postings, if you ignore that, you'll have to put up with the bounce.

If that's so important to you, then you should configure your mail
software to add the Mail-Followup-To: header pointing to the mailing
list.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: unable to burn DVD +RW/+R on a new drive

[Greg Wooledge]

On Thu, Jul 31, 2003 at 05:14:28PM +0200, Dominique Rousset wrote:
> By the way, I can't manage to sucscribe to the liste
> any help is welcome
> [...]
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Do the reverse of what it says above.  Send a message with the body
"subscribe" to <[EMAIL PROTECTED]>.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How do I subscribe to this mailing list?

[Greg Wooledge]

On Wed, Jul 23, 2003 at 11:42:25AM +0200, Craig Main wrote:
> See subject

Sent a message containing the word 'subscribe' (and nothing else!)
in the body to the address <[EMAIL PROTECTED]>.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: two questions concerning fast burning and burn-free

[Greg Wooledge]

On Wed, Jul 16, 2003 at 11:49:32PM +0200, Lourens Veen wrote:
> I think I know why too. UNIX has traditionally been used on large 
> machines, servers and mainframes, not on consumer-grade PCs. Those 
> big machines don't have IDE. The low end has SCSI, and maybe the 
> high end too I don't know, but at least it's not IDE.

Older HP workstations are pure SCSI.  Newer ones (e.g. B2000 and B2600)
have SCSI hard drives, but IDE/ATAPI CD-ROM drives.  But the CD-ROM
is still presented as if it were SCSI:

# uname -a
HP-UX imadev B.10.20 A 9000/785 2008xx two-user license
# ioscan -fn -C disk
Class I  H/W Path   Driver S/W State   H/W Type Description
===
disk  0  10/0/14/0.0.0  sdisk CLAIMED DEVICE   MITSUMI CD-ROM FX4830T!B
   /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0
disk  1  10/0/15/0.6.0  sdisk CLAIMED DEVICE   QUANTUM ATLAS5-9LVD
   /dev/dsk/c2t6d0   /dev/rdsk/c2t6d0

That Mitsumi drive is really IDE, but the kernel is presenting it as
SCSI disk (0,0,0).  (c0t0d0 = controller 0 target 0 LUN 0.)

Now, keep in mind that HP-UX 10.20 is so old that HP isn't even
supporting it any more (yet it's still in widespread use).  (According to
http://www.software.hp.com/RELEASES-MEDIA/history/slide2.html , it was
introduced in 8/96 and became "obsolete" 6/30/03.)  IDE-SCSI emulation has
been the standard way to handle newer CD-ROM drives on Unix for a *very*
long time.

I'm no kernel hacker, so I won't criticize what the Linux team is doing.
I just want things to work as well and as easily as possible.  It seems
that IDE-SCSI emulation is the way most Unix systems achieve that.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Dvdrecord problem

[Greg Wooledge]

On Thu, Jun 19, 2003 at 01:14:34PM +0200, Joerg Schilling wrote:
> 
> >From [EMAIL PROTECTED] Wed Jun 18 16:03:00 2003
> 
> >> Well, cdrecord-ProDVD definitely is free for private and research/educational
> >> use.
> 
> >s/free/libre/
> 
> Do you really belive that the context changes if you only translate from 
> english to french?

More important is the fact that he used the wrong translation.
cdrecord-ProDVD is gratis ("free as in beer"), not libre ("free as
in speech").


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ProDVD 2.0 HP-UX Medium Error

[Greg Wooledge]

On Fri, Jan 31, 2003 at 11:35:56PM +0100, Joerg Schilling wrote:
> The Sony is known to be very picky about medium quality
> You did neither mention the media manufacturer nor include a cdrecord -atip
> outout.

It was a Memorex DVD-R, as I mentioned in the previous message.  Anyway,
I got it to work with the same media type on the second try by adding
"speed=1" to the options.

Since this experiment was successful, our next step will be licensing.
We are one department in a non-profit hospital and we plan to use DVD for
data backups.  Does this fall under the "private/educational/research"
license for cdrecord-ProDVD?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ProDVD 2.0 HP-UX Medium Error

[Greg Wooledge]

Hello.  This is partially a request for help, and partially a test
to see if I'm actually subscribed to this list.  (I haven't gotten any
sort of confirmation message yet, and couldn't find a direct subscription
address -- just one of these silly web things.)  Replying to me directly
might be necessary. :(

I'm using cdrecord-ProDVD 2.0 on HP-UX 10.20.  I'm trying to burn my
very first DVD ever.  I've got a Sony DRU-500A drive and a Memorex DVD-R
disc.  I used the following commands as root:

 # mkisofs -split-output -R -J -o ../tempfile .
 # cd ..
 # prodvd -v dev=1,0,0 tempfile*

(prodvd is a script in /usr/local/bin that sets the CDR_SECURITY
variable and runs cdrecord-prodvd.)  It seemed to be going pretty
well for the first several minutes, then aborted with a Medium Error,
and the resulting disc cannot be mounted.

My first thought, of course, is that the DVD-R disc itself was
defective.  But I only have 3 of them (oops!  make that 2 now), and
I can't get hold of any DVD-RWs at the moment, since our supplier is
out of both brands that they sell.  So I'm reluctatant to throw
another DVD-R in and try again without understanding exactly what
went wrong the first time.

Has anyone else (in the world?) written a DVD under HP-UX yet?  Have
I done something wrong, or is this just a bad disc?  Is there something
I should do differently to improve my chances of success?  Should I
go shopping for a DVD-RW in a local retail store and hope to be
reimbursed for it by the local bureaucracy eventually? :-/

Here is the full output:

scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
Cdrecord-ProDVD-Clone 2.0 (hppa1.1-hp-hpux10.20) Copyright (C) 1995-2002 JM-vrg 
Schilling
Unlocked features: ProDVD Clone 
Limited  features: speed 
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.7'
atapi: 0
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities   : SYNC 
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision   : '1.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd).
Driver flags   : DVD SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8126464 = 7936 KB
FIFO size  : 4194304 = 4096 KB
Track 01: data  1024 MB
Track 02: data  1024 MB
Track 03: data  1024 MB
Track 04: data  1024 MB
Track 05: data   310 MB
Total size: 4406 MB = 2256048 sectors
Current Secsize: 2048
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 42448
Starting to write CD/DVD at speed 2 in real TAO mode for single session.
Last chance to quit [...]
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Compiling virtual track list ...
Vtrack:  1 size: 1073764352 bytes 1073764352 rounded (524299 sectors)
Vtrack:  2 size: 1073762304 bytes 1073762304 rounded (524298 sectors)
Vtrack:  3 size: 1073762304 bytes 1073762304 rounded (524298 sectors)
Vtrack:  4 size: 1073762304 bytes 1073762304 rounded (524298 sectors)
Vtrack:  5 size: 325335040 bytes 325335040 rounded (158855 sectors)
Vtracks: 5 size: 4620386304 bytes 4620386304 rounded (2256048 sectors) total
Starting new track at sector: 0
Track 01:0 of 1024 MB written. [...]
Track 02:  980 of 1024 MB written (fifo  98%)   2.1x.cdrecord-prodvd: I/O error. 
write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 0F A9 A4 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F1 00 03 00 0F A0 CB 12 00 00 00 00 0C 08 00 00 00 00 00 00 8C 03 00 00 
00 00 DF FF 00 00 00 00
Sense Key: 0x3 Medium Error, deferred error, Segment 0
Sense Code: 0x0C Qual 0x08 (write error - recovery failed) Fru 0x0
Sense flags: Blk 1024203 (valid) 
resid: 63488
cmd finished after 0.027s timeout 100s
Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00

write track data: error after 1028442112 bytes
Writing  time:  827.486s
Average write speed   4.0x.
Fixating...
Fixating time:0.001s
cdrecord-prodvd: fifo had 33176 puts and 33113 gets.
cdrecord-prodvd: fifo was 0 times empty and 18601 times full, min fill was 92%.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]