Re: [Bashburn-info] cdrecord OPTIONS dump

[Anders L. <and...@gm...>]

On Tuesday 07 October 2008 18:50:48 Nick Warne wrote:
> On Mon, 06 Oct 2008 22:52:23 +0200
>
> Markus Kollmar <mar...@on...> wrote:
> > Yes you are right, I think also it is much work to grep the output of
> > the burner-option (since it seems not strongly formated and some 
part
> > of output goes not to stdout I think.)
>
> As an aside on this, I too like Markus couldn't work out why some of
> the dump goes to STDOUT and some doesn't seem to go anywhere 
yet still
> gets printed to terminal.
>
> i.e. compare:
>
> cdrecord dev=/dev/<your_drive> driveropts=help -checkdrive
>
> with:
>
> cdrecord dev=/dev/<your_drive> driveropts=help -checkdrive > 
/dev/null
>
> with:
>
> cdrecord dev=/dev/<your_drive> driveropts=help -checkdrive | grep 
-i
> Driver
>
> I dunno how Jörg Schilling has done this.  In the man page quote:
>
> "driveropts=option list
>               Set driver specific options. The options are specified a
> comma separated list.  To get a  list of valid options use
> driveropts=help together with the -checkdrive option.  If you like to
> set driver options without running a typical cdrecord task, you need 
to
> use the -setdropts  option in  addition,  otherwise  the command 
line
> parser in cdrecord will complain."
>
>
> Command line parser?  So he somehow does some magic?
>
> I have never seen this behaviour in any application ever before.
>
> Nick

Jörg is a strange man. I wouldn't be surprised if he uses black magic.

-- 
Anders Lindén
http://bashburn.dose.se