bashburn-info — BashBurn mailing list

Re: [Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

On Wed, 1 Oct 2008 09:43:32 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 15:09:13 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 14:58:04 +0100
> > Nick Warne <ni...@li...> wrote:
> > 
> > > On Tue, 30 Sep 2008 09:56:36 -0400 (EDT)
> > > "Steven W. Orr" <st...@sy...> wrote:
> > > 
> > > > On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:
> > > > 
> > > > =>
> > > > =>The error message is such after ripping CD to disc:
> > > > =>
> > > > =>...
> > > > =>...
> > > > =>Tracks ripped!
> > > > =>Insert blank CD and then press [ENTER] to go on
> > > > =>
> > > > =>cdrecord: No write mode specified.
> > > > =>cdrecord: Asuming -sao mode.
> > > > =>cdrecord: If your drive does not accept -sao, try -tao.
> > > > =>cdrecord: Future versions of cdrecord may have different drive
> > > > =>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
> > > > =>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC
> > > > Type: 1 =>= CD-ROM scsidev: '/dev/cdrom'
> > > > =>devname: '/dev/cdrom'
> > > > =>scsibus: -2 target: -2 lun: -2
> > > > =>Warning: Open by 'devname' is unintentional and not supported.
> > > > =>Linux sg driver version: 3.5.27
> > > > =>Using libscg version 'schily-0.9'.
> > > > =>SCSI buffer size: 64512
> > > > =>atapi: 1
> > > > =>Device type    : Removable CD-ROM
> > > > =>Version        : 0
> > > > =>Response Format: 2
> > > > =>Capabilities   : 
> > > > =>Vendor_info    : 'Optiarc '
> > > > =>Identifikation : 'DVD RW AD-7200A '
> > > > =>Revision       : '1.06'
> > > > =>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> > > > =>Current: CD-R
> > > > =>Profile: DVD+R/DL 
> > > > =>Profile: DVD+R 
> > > > =>Profile: DVD+RW 
> > > > =>Profile: DVD-R/DL layer jump recording 
> > > > =>Profile: DVD-R/DL sequential recording 
> > > > =>Profile: DVD-RW sequential recording 
> > > > =>Profile: DVD-RW restricted overwrite 
> > > > =>Profile: DVD-RAM 
> > > > =>Profile: DVD-R sequential recording 
> > > > =>Profile: DVD-ROM 
> > > > =>Profile: CD-RW 
> > > > =>Profile: CD-R (current)
> > > > =>Profile: CD-ROM (current)
> > > > =>Profile: Removable Disk 
> > > > =>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 : 866304 = 846 KB
> > > > =>FIFO size      : 4194304 = 4096 KB
> > > > =>cdrecord: No such file or directory. Cannot open
> > > > =>'burnfree:+driveropts=burnfree'.
> > > > =>Error occurred! Could not burn the CD
> > > > =>
> > > > 
> > > > Interesting. You need to run this with tracing turned on so we
> > > > can see what and where
> > > 
> > > BUGGER.  It took ages to rip the *.wavs :-D
> > > 
> > > I will try again...
> > 
> > A quick grep/find:
> > 
> > burning/burning.sh  line 71
> > 
> >     # HACK to get driveroptions to work. FIXME
> >     # FIXME: Also, if you modify the variable then it will only work
> > once. # The second time through, you'll change the value to
> >     # driveropts=driveropts=$BBOPT_ONE
> >     BBOPT_ONE=${BBOPT_ONE:+driveropts="$BBOPT_ONE"}
> > 
> > 
> > I am still running a copy -> copy so will have the trace soon.
>

OK, I have fixed this - Audio CD -> CD now works.  As soon as the SVN
server comes back, I will commit the changes.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 14:56:58 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 13:18:58 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 13:05:09 +0100
> > Nick Warne <ni...@li...> wrote:
> > 
> > > On Tue, 30 Sep 2008 10:37:14 +0100
> > > Nick Warne <ni...@li...> wrote:
> > > 
> > > > On Fri, 12 Sep 2008 00:03:10 +0200
> > > > Anders Lindén <and...@gm...> wrote:
> > > > 
> > > > > lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > > > > > On Sun, 31 Aug 2008 17:37:09 +0100
> > > > > > Nick Warne <ni...@uk...> wrote:
> > > > > > 
> > > > > > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > > > > > Nick Warne <ni...@uk...> wrote:
> > > > > > > 
> > > > > > > > I think we ought to start a thread reporting successful
> > > > > > > > functionality
> > > > > > > > 
> > > > > > > > I just fixed a broken data recording - committed.
> > > > > > > > 
> > > > > > > > So please just reply to this thread as each function is
> > > > > > > > proven to work so we have some sort of visible guide.
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Data recording WORKS
> > > > > > > > 
> > > > > > > 
> > > > > > > Burning ISO works
> > > > > > > 
> > > > > > 
> > > > > > OK, update.  I just burnt a *.ogv file to CD(data
> > > > > > recording).
> > > > > > 
> > > > > > All works perfectly.
> > > > > > 
> > > > > > BTW, worth a watch:
> > > > > > 
> > > > > > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > > > > > 
> > > > > > Nick
> > > > > 
> > > > > Data DVD burning works.
> > > > 
> > > > MP3 to Audio CD works.
> > > 
> > > CD ripping to *.ogg -> hard drive works :-)
> > 
> > CD ripping to *.mp3 -> hard drive works :-))
> 
> CD ripping to *.flac -> hard drive works :-)))
> 
Fix to be committed, but now AudioCD-> CD copy works :-))))

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 15:09:13 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 14:58:04 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 09:56:36 -0400 (EDT)
> > "Steven W. Orr" <st...@sy...> wrote:
> > 
> > > On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:
> > > 
> > > =>
> > > =>The error message is such after ripping CD to disc:
> > > =>
> > > =>...
> > > =>...
> > > =>Tracks ripped!
> > > =>Insert blank CD and then press [ENTER] to go on
> > > =>
> > > =>cdrecord: No write mode specified.
> > > =>cdrecord: Asuming -sao mode.
> > > =>cdrecord: If your drive does not accept -sao, try -tao.
> > > =>cdrecord: Future versions of cdrecord may have different drive
> > > =>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
> > > =>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC
> > > Type: 1 =>= CD-ROM scsidev: '/dev/cdrom'
> > > =>devname: '/dev/cdrom'
> > > =>scsibus: -2 target: -2 lun: -2
> > > =>Warning: Open by 'devname' is unintentional and not supported.
> > > =>Linux sg driver version: 3.5.27
> > > =>Using libscg version 'schily-0.9'.
> > > =>SCSI buffer size: 64512
> > > =>atapi: 1
> > > =>Device type    : Removable CD-ROM
> > > =>Version        : 0
> > > =>Response Format: 2
> > > =>Capabilities   : 
> > > =>Vendor_info    : 'Optiarc '
> > > =>Identifikation : 'DVD RW AD-7200A '
> > > =>Revision       : '1.06'
> > > =>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> > > =>Current: CD-R
> > > =>Profile: DVD+R/DL 
> > > =>Profile: DVD+R 
> > > =>Profile: DVD+RW 
> > > =>Profile: DVD-R/DL layer jump recording 
> > > =>Profile: DVD-R/DL sequential recording 
> > > =>Profile: DVD-RW sequential recording 
> > > =>Profile: DVD-RW restricted overwrite 
> > > =>Profile: DVD-RAM 
> > > =>Profile: DVD-R sequential recording 
> > > =>Profile: DVD-ROM 
> > > =>Profile: CD-RW 
> > > =>Profile: CD-R (current)
> > > =>Profile: CD-ROM (current)
> > > =>Profile: Removable Disk 
> > > =>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 : 866304 = 846 KB
> > > =>FIFO size      : 4194304 = 4096 KB
> > > =>cdrecord: No such file or directory. Cannot open
> > > =>'burnfree:+driveropts=burnfree'.
> > > =>Error occurred! Could not burn the CD
> > > =>
> > > 
> > > Interesting. You need to run this with tracing turned on so we can
> > > see what and where
> > 
> > BUGGER.  It took ages to rip the *.wavs :-D
> > 
> > I will try again...
> 
> A quick grep/find:
> 
> burning/burning.sh  line 71
> 
>     # HACK to get driveroptions to work. FIXME
>     # FIXME: Also, if you modify the variable then it will only work
> once. # The second time through, you'll change the value to
>     # driveropts=driveropts=$BBOPT_ONE
>     BBOPT_ONE=${BBOPT_ONE:+driveropts="$BBOPT_ONE"}
> 
> 
> I am still running a copy -> copy so will have the trace soon.

OK, I have fixed this - Audio CD -> CD now works.  As soon as the SVN
server comes back, I will commit the changes.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] NEW bashburn config file determination

[Steven W. O. <st...@sy...>]

On Tuesday, Sep 30th 2008 at 13:26 -0000, quoth Steven W. Orr:

=>On Tuesday, Sep 30th 2008 at 12:26 -0000, quoth Markus Kollmar:
=>
=>=>I was nerved to only get bashburn to work by running "Install.sh"
=>=>which then in turn modifies "BashBurn.sh" to the correct "BBROOTDIR".
=>=>
=>=>This may work but has some disadvantages:
=>=>
=>=>1. Programs modifying other programs code is not always nice and clear. 
=>=>And if someone does not know the
=>=>
=>=>typeset BBROOTDIR='@@BBROOTDIR@@'
=>=>
=>=>construct there could happen ugly things. Also it may become a 
=>=>maintenance nightmare.
=>
=>Think of BashBurn.sh as not being the script that you run unless it has 
=>been installed. What we could do is to rename the file to BashBurn.sh.in 
=>and then the target, derived object, or whatever you want to call it, 
=>would be BashBurn.sh. BBROOTDIR should not be a config parameter. Having 
=>it as a config param implies that it's ok to modify it and it never is. 
=>Also, the value of BBROOTDIR is used for one thing only: to locate where 
=>auxiliary files are kept, for purposes of sourcing them in or locating 
=>language files, etc. 
=>
=>Also, BashBurn is no longer required to be installed by root. In fact, you 
=>can have multiple installations, each with its own BBROOTDIR.
=>
=>=>2. Distributions can not clearly build their own package installer since 
=>=>bashburn does not work unless bashburn "Install.sh" is executed.
=>
=>Markus, sorry, but I don't understand what you're saying. We started with 
=>Install.sh and we're still using it. If we were to also support rpm and 
=>deb packaging then the Install.sh content would probably end up also being 
=>inside the preinst and postinst scripts that accompany the package. But 
=>future packaging is not relevant to whether the BB script is the same as 
=>what we write.
=>
=>Also, we have hard coded the shebang at the top of the script to be 
=>
=>#!/bin/bash
=>
=>That's pretty normal these days, but I remember a time when it was common 
=>for bash to be in /usr/local/bin and when perl scripts got complicated 
=>because some people had perl in /usr/bin and others had it in 
=>/usr/local/bin. In that case the script would start with (something like) 
=>
=>#! @@BASHPATH@@ 
=>
=>and then proper installation would just work correctly for everyone.
=>
=>=>3. The user expects traditionally under unixes following strategies to 
=>=>search for config-file:
=>=> -> search user's $HOME for config.
=>=> -> search system wide config (mostly in "/etc/").
=>=> -> fetch some (hard-coded) default config or ask user interactively for 
=>=>config source or values.
=>
=>I agree. We need to add a -c configfile option and/or a BASHBURNRC 
=>environment variable. But the utility *is* pretty small and I don't see a 
=>real need for individual config params to have to be searched for in a 
=>list of places.
=>
=>=>I have now changed "BashBurn.sh" in my local trunk and added following 
=>=>(note that for this to work in "bashburn.rc" "BBROOTDIR" has to be added 
=>=>and set again):


There's one more thing I'd like to add to what I wrote above. I've 
mentioned some of the things I'd like to shoot for in uncoming revs of BB. 
One of the things I've touched on was the concept of the installation not 
necessarily looking like the src workspace. One example of this concept is 
that we have an installation tree that is overcomplicated. We have a need 
for the (current) installation directory to have a lang subddir but we do 
not have a need for almost all the rest of the subdirectories. Let's get 
rid of burning, config, convert, func, menus and misc. How we program, or 
in other words, the shape of the workspace, is not usually related to how 
a relase should look. When you see projects where the release structure is 
a match of how the sandbox looked then what you're probably seeing is 
another case of where the developer never thought that the release 
structure could be optimized.

I'm just blue-skying here, but let's try this on for size. It may not be 
right, but the example shows the concept. Let's pretend that we have 
abandoned Install.sh  and we're now in rpm and debian package management 
land.

/usr/bin/bashburn	# NOT a symlink. Created by
			# filter < BashBurn.sh > bashburn
/usr/share/man/man1/bashburn.man
/usr/lib/bashburn/lib/*.sh 	# All the sourced files
/usr/lib/bashburn/lib/lang/*	# Assuming we didn't yet get to po files.
/usr/share/doc/bashburn/{README, HOWTO, NOTES, CREDITS, etc}

Markus, is this feeling any better?

=>
=>
=>
=>=>
=>=>
=>=>-------
=>=>
=>=>#!/bin/bash
=>=>
=>=>###############################################################################
=>=># Checks whether given file is readable and a actual config file of 
=>=>bashburn.
=>=># IN[1]: FILENAME.
=>=># OUT[SUCCESS]: <TRUE>
=>=># OUT[FAILURE]: <FALSE>
=>=>function is_valid_configfile {
=>=>    test -r $1  &&  grep -q "VERSION: 3.x" $1
=>=>}
=>=>
=>=>
=>=>## Determine the root directory (BBROOTDIR) of bashburn where all
=>=>## additional programm files for basburn are.
=>=>## CASE1: user config from $HOME:
=>=>if is_valid_configfile "$HOME/.bashburnrc"
=>=>    then
=>=>    typeset BBROOTDIR=$(grep "BBROOTDIR" $HOME/.bashburnrc | cut -d: -f2)
=>=>## CASE2: global config from /etc/
=>=>    elif is_valid_configfile "/etc/.bashburnrc"
=>=>    then
=>=>    typeset BBROOTDIR=$(grep "BBROOTDIR" /etc/.bashburnrc | cut -d: -f2)
=>=>## CASE3: Config from bashburn Install.sh:
=>=>    else
=>=>    # NOTE: BBROOTDIR will be later actualized by bashburn installation 
=>=>script
=>=>    # "Install.sh".
=>=>    typeset BBROOTDIR='@@BBROOTDIR@@'
=>=>fi
=>=>
=>=>
=>=>-----------
=>=>
=>=>Let me know what you think. I have not checked it in yet, since our 
=>=>svn-server seems not online in the moment.
=>=>Like you see I have left the "@@BBROOTDIR@@" as last option, but maybe 
=>=>we should delete it if there is no good reason against it.
=>
=>I'd much rather see something else, which would be to look in a list of 
=>places for a config file. Look first in $HOME, then look in /etc. (BTW, 
=>the filename in /etc should not begin with a dot. Nothing else does.) 
=>
=>That in conjunction with the -c option above is something I see as a 
=>better solution. But look at what we're talking about. The discussion 
=>about the value of BBROOTDIR is getting complicated by the possible 
=>locations of the rc file. :-)
=>
=>What I don't want to be doing is to not have @@BBROOTDIR@@ just so we can 
=>run bb out of the workspace. If that is the real issue then that's a 
=>seperate discussion.
=>
=>-- 
=>Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
=>happened but none stranger than this. Does your driver's license say Organ ..0
=>Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
=>individuals! What if this weren't a hypothetical question?
=>steveo at syslang.net
=>
=>-------------------------------------------------------------------------
=>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
=>Build the coolest Linux based applications with Moblin SDK & win great prizes
=>Grand prize is a trip for two to an Open Source event anywhere in the world
=>http://moblin-contest.org/redirect.php?banner_id=100&url=/
=>_______________________________________________
=>Bashburn-info mailing list
=>Bas...@li...
=>https://lists.sourceforge.net/lists/listinfo/bashburn-info
=>

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] Time to stabilize

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 17:40:39 +0200
Markus Kollmar <mar...@on...> wrote:

> Sounds good. So you would also include the new file
> "TRANSLATION_RULE"? This could confuse someone since we do work with
> this system from bashburn version 3.1 and higher. Version 3.0 still
> has the old translation system.
> 
> Maybe it is useful to make some hints in the file "TRANSLATION_RULE"
> and the man-page that makes this clear?

So far, the man page is only in docs/ directory - it doesn't get
installed yet.  I only put it there as a marker to be developed.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] NEW bashburn config file determination

[Steven W. O. <st...@sy...>]

On Tuesday, Sep 30th 2008 at 12:26 -0000, quoth Markus Kollmar:

=>I was nerved to only get bashburn to work by running "Install.sh"
=>which then in turn modifies "BashBurn.sh" to the correct "BBROOTDIR".
=>
=>This may work but has some disadvantages:
=>
=>1. Programs modifying other programs code is not always nice and clear. 
=>And if someone does not know the
=>
=>typeset BBROOTDIR='@@BBROOTDIR@@'
=>
=>construct there could happen ugly things. Also it may become a 
=>maintenance nightmare.

Think of BashBurn.sh as not being the script that you run unless it has 
been installed. What we could do is to rename the file to BashBurn.sh.in 
and then the target, derived object, or whatever you want to call it, 
would be BashBurn.sh. BBROOTDIR should not be a config parameter. Having 
it as a config param implies that it's ok to modify it and it never is. 
Also, the value of BBROOTDIR is used for one thing only: to locate where 
auxiliary files are kept, for purposes of sourcing them in or locating 
language files, etc. 

Also, BashBurn is no longer required to be installed by root. In fact, you 
can have multiple installations, each with its own BBROOTDIR.

=>2. Distributions can not clearly build their own package installer since 
=>bashburn does not work unless bashburn "Install.sh" is executed.

Markus, sorry, but I don't understand what you're saying. We started with 
Install.sh and we're still using it. If we were to also support rpm and 
deb packaging then the Install.sh content would probably end up also being 
inside the preinst and postinst scripts that accompany the package. But 
future packaging is not relevant to whether the BB script is the same as 
what we write.

Also, we have hard coded the shebang at the top of the script to be 

#!/bin/bash

That's pretty normal these days, but I remember a time when it was common 
for bash to be in /usr/local/bin and when perl scripts got complicated 
because some people had perl in /usr/bin and others had it in 
/usr/local/bin. In that case the script would start with (something like) 

#! @@BASHPATH@@ 

and then proper installation would just work correctly for everyone.

=>3. The user expects traditionally under unixes following strategies to 
=>search for config-file:
=> -> search user's $HOME for config.
=> -> search system wide config (mostly in "/etc/").
=> -> fetch some (hard-coded) default config or ask user interactively for 
=>config source or values.

I agree. We need to add a -c configfile option and/or a BASHBURNRC 
environment variable. But the utility *is* pretty small and I don't see a 
real need for individual config params to have to be searched for in a 
list of places.

=>I have now changed "BashBurn.sh" in my local trunk and added following 
=>(note that for this to work in "bashburn.rc" "BBROOTDIR" has to be added 
=>and set again):



=>
=>
=>-------
=>
=>#!/bin/bash
=>
=>###############################################################################
=># Checks whether given file is readable and a actual config file of 
=>bashburn.
=># IN[1]: FILENAME.
=># OUT[SUCCESS]: <TRUE>
=># OUT[FAILURE]: <FALSE>
=>function is_valid_configfile {
=>    test -r $1  &&  grep -q "VERSION: 3.x" $1
=>}
=>
=>
=>## Determine the root directory (BBROOTDIR) of bashburn where all
=>## additional programm files for basburn are.
=>## CASE1: user config from $HOME:
=>if is_valid_configfile "$HOME/.bashburnrc"
=>    then
=>    typeset BBROOTDIR=$(grep "BBROOTDIR" $HOME/.bashburnrc | cut -d: -f2)
=>## CASE2: global config from /etc/
=>    elif is_valid_configfile "/etc/.bashburnrc"
=>    then
=>    typeset BBROOTDIR=$(grep "BBROOTDIR" /etc/.bashburnrc | cut -d: -f2)
=>## CASE3: Config from bashburn Install.sh:
=>    else
=>    # NOTE: BBROOTDIR will be later actualized by bashburn installation 
=>script
=>    # "Install.sh".
=>    typeset BBROOTDIR='@@BBROOTDIR@@'
=>fi
=>
=>
=>-----------
=>
=>Let me know what you think. I have not checked it in yet, since our 
=>svn-server seems not online in the moment.
=>Like you see I have left the "@@BBROOTDIR@@" as last option, but maybe 
=>we should delete it if there is no good reason against it.

I'd much rather see something else, which would be to look in a list of 
places for a config file. Look first in $HOME, then look in /etc. (BTW, 
the filename in /etc should not begin with a dot. Nothing else does.) 

That in conjunction with the -c option above is something I see as a 
better solution. But look at what we're talking about. The discussion 
about the value of BBROOTDIR is getting complicated by the possible 
locations of the rc file. :-)

What I don't want to be doing is to not have @@BBROOTDIR@@ just so we can 
run bb out of the workspace. If that is the real issue then that's a 
seperate discussion.

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

[Bashburn-info] NEW bashburn config file determination

[Markus K. <mar...@on...>]

I was nerved to only get bashburn to work by running "Install.sh"
which then in turn modifies "BashBurn.sh" to the correct "BBROOTDIR".

This may work but has some disadvantages:

1. Programs modifying other programs code is not always nice and clear. 
And if someone does not know the

typeset BBROOTDIR='@@BBROOTDIR@@'

construct there could happen ugly things. Also it may become a 
maintenance nightmare.

2. Distributions can not clearly build their own package installer since 
bashburn does not work unless bashburn "Install.sh" is executed.

3. The user expects traditionally under unixes following strategies to 
search for config-file:
 -> search user's $HOME for config.
 -> search system wide config (mostly in "/etc/").
 -> fetch some (hard-coded) default config or ask user interactively for 
config source or values.


I have now changed "BashBurn.sh" in my local trunk and added following 
(note that for this to work in "bashburn.rc" "BBROOTDIR" has to be added 
and set again):


-------

#!/bin/bash

###############################################################################
# Checks whether given file is readable and a actual config file of 
bashburn.
# IN[1]: FILENAME.
# OUT[SUCCESS]: <TRUE>
# OUT[FAILURE]: <FALSE>
function is_valid_configfile {
    test -r $1  &&  grep -q "VERSION: 3.x" $1
}


## Determine the root directory (BBROOTDIR) of bashburn where all
## additional programm files for basburn are.
## CASE1: user config from $HOME:
if is_valid_configfile "$HOME/.bashburnrc"
    then
    typeset BBROOTDIR=$(grep "BBROOTDIR" $HOME/.bashburnrc | cut -d: -f2)
## CASE2: global config from /etc/
    elif is_valid_configfile "/etc/.bashburnrc"
    then
    typeset BBROOTDIR=$(grep "BBROOTDIR" /etc/.bashburnrc | cut -d: -f2)
## CASE3: Config from bashburn Install.sh:
    else
    # NOTE: BBROOTDIR will be later actualized by bashburn installation 
script
    # "Install.sh".
    typeset BBROOTDIR='@@BBROOTDIR@@'
fi


-----------

Let me know what you think. I have not checked it in yet, since our 
svn-server seems not online in the moment.
Like you see I have left the "@@BBROOTDIR@@" as last option, but maybe 
we should delete it if there is no good reason against it.


Markus

Re: [Bashburn-info] Time to stabilize

[Markus K. <mar...@on...>]

Anders Lindén wrote:
> It seems like things are calming down now, the interface and functions
> seem to be stable. Things I suggest we do:
>
> * Serious testing of all functionality.
> (I suggest changing the CD recording command to 'cdrecord -dummy' and
> the DVD burning command to 'growisofs -dry-run' to not waste CDs/DVDs)
> * Make sure translations are complete.
> (No further changes that needs .lang-files updated will be accepted)
> * Make sure documentation is updated.
>
> When these steps are done, merge trunk into 3.0 and release it. 
> Do you all agree? Is there anything else you like to add? 
>
> Some restructuring like Steven has suggested and the gettextification
> (And other things anyone can think of) should go into 3.1. 
>
>   

Sounds good. So you would also include the new file "TRANSLATION_RULE"?
This could confuse someone since we do work with this system from 
bashburn version 3.1 and higher. Version 3.0 still has the old 
translation system.

Maybe it is useful to make some hints in the file "TRANSLATION_RULE" and 
the man-page that makes this clear?



Markus

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 14:56:58 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 13:18:58 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 13:05:09 +0100
> > Nick Warne <ni...@li...> wrote:
> > 
> > > On Tue, 30 Sep 2008 10:37:14 +0100
> > > Nick Warne <ni...@li...> wrote:
> > > 
> > > > On Fri, 12 Sep 2008 00:03:10 +0200
> > > > Anders Lindén <and...@gm...> wrote:
> > > > 
> > > > > lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > > > > > On Sun, 31 Aug 2008 17:37:09 +0100
> > > > > > Nick Warne <ni...@uk...> wrote:
> > > > > > 
> > > > > > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > > > > > Nick Warne <ni...@uk...> wrote:
> > > > > > > 
> > > > > > > > I think we ought to start a thread reporting successful
> > > > > > > > functionality
> > > > > > > > 
> > > > > > > > I just fixed a broken data recording - committed.
> > > > > > > > 
> > > > > > > > So please just reply to this thread as each function is
> > > > > > > > proven to work so we have some sort of visible guide.
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Data recording WORKS
> > > > > > > > 
> > > > > > > 
> > > > > > > Burning ISO works
> > > > > > > 
> > > > > > 
> > > > > > OK, update.  I just burnt a *.ogv file to CD(data
> > > > > > recording).
> > > > > > 
> > > > > > All works perfectly.
> > > > > > 
> > > > > > BTW, worth a watch:
> > > > > > 
> > > > > > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > > > > > 
> > > > > > Nick
> > > > > 
> > > > > Data DVD burning works.
> > > > 
> > > > MP3 to Audio CD works.
> > > 
> > > CD ripping to *.ogg -> hard drive works :-)
> > 
> > CD ripping to *.mp3 -> hard drive works :-))
> 
> CD ripping to *.flac -> hard drive works :-)))

Option 9) Define burn data all works perfectly AFAIK.

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 15:09:13 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 14:58:04 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 09:56:36 -0400 (EDT)
> > "Steven W. Orr" <st...@sy...> wrote:
> > 
> > > On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:
> > > 
> > > =>
> > > =>The error message is such after ripping CD to disc:
> > > =>
> > > =>...
> > > =>...
> > > =>Tracks ripped!
> > > =>Insert blank CD and then press [ENTER] to go on
> > > =>
> > > =>cdrecord: No write mode specified.
> > > =>cdrecord: Asuming -sao mode.
> > > =>cdrecord: If your drive does not accept -sao, try -tao.
> > > =>cdrecord: Future versions of cdrecord may have different drive
> > > =>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
> > > =>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC
> > > Type: 1 =>= CD-ROM scsidev: '/dev/cdrom'
> > > =>devname: '/dev/cdrom'
> > > =>scsibus: -2 target: -2 lun: -2
> > > =>Warning: Open by 'devname' is unintentional and not supported.
> > > =>Linux sg driver version: 3.5.27
> > > =>Using libscg version 'schily-0.9'.
> > > =>SCSI buffer size: 64512
> > > =>atapi: 1
> > > =>Device type    : Removable CD-ROM
> > > =>Version        : 0
> > > =>Response Format: 2
> > > =>Capabilities   : 
> > > =>Vendor_info    : 'Optiarc '
> > > =>Identifikation : 'DVD RW AD-7200A '
> > > =>Revision       : '1.06'
> > > =>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> > > =>Current: CD-R
> > > =>Profile: DVD+R/DL 
> > > =>Profile: DVD+R 
> > > =>Profile: DVD+RW 
> > > =>Profile: DVD-R/DL layer jump recording 
> > > =>Profile: DVD-R/DL sequential recording 
> > > =>Profile: DVD-RW sequential recording 
> > > =>Profile: DVD-RW restricted overwrite 
> > > =>Profile: DVD-RAM 
> > > =>Profile: DVD-R sequential recording 
> > > =>Profile: DVD-ROM 
> > > =>Profile: CD-RW 
> > > =>Profile: CD-R (current)
> > > =>Profile: CD-ROM (current)
> > > =>Profile: Removable Disk 
> > > =>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 : 866304 = 846 KB
> > > =>FIFO size      : 4194304 = 4096 KB
> > > =>cdrecord: No such file or directory. Cannot open
> > > =>'burnfree:+driveropts=burnfree'.
> > > =>Error occurred! Could not burn the CD
> > > =>
> > > 
> > > Interesting. You need to run this with tracing turned on so we can
> > > see what and where
> > 
> > BUGGER.  It took ages to rip the *.wavs :-D
> > 
> > I will try again...
> 
> A quick grep/find:
> 
> burning/burning.sh  line 71
> 
>     # HACK to get driveroptions to work. FIXME
>     # FIXME: Also, if you modify the variable then it will only work
> once. # The second time through, you'll change the value to
>     # driveropts=driveropts=$BBOPT_ONE
>     BBOPT_ONE=${BBOPT_ONE:+driveropts="$BBOPT_ONE"}
> 
> 
> I am still running a copy -> copy so will have the trace soon.

Attached the script.  It shows the same.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 14:58:04 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 09:56:36 -0400 (EDT)
> "Steven W. Orr" <st...@sy...> wrote:
> 
> > On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:
> > 
> > =>
> > =>The error message is such after ripping CD to disc:
> > =>
> > =>...
> > =>...
> > =>Tracks ripped!
> > =>Insert blank CD and then press [ENTER] to go on
> > =>
> > =>cdrecord: No write mode specified.
> > =>cdrecord: Asuming -sao mode.
> > =>cdrecord: If your drive does not accept -sao, try -tao.
> > =>cdrecord: Future versions of cdrecord may have different drive
> > =>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
> > =>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC
> > Type: 1 =>= CD-ROM scsidev: '/dev/cdrom'
> > =>devname: '/dev/cdrom'
> > =>scsibus: -2 target: -2 lun: -2
> > =>Warning: Open by 'devname' is unintentional and not supported.
> > =>Linux sg driver version: 3.5.27
> > =>Using libscg version 'schily-0.9'.
> > =>SCSI buffer size: 64512
> > =>atapi: 1
> > =>Device type    : Removable CD-ROM
> > =>Version        : 0
> > =>Response Format: 2
> > =>Capabilities   : 
> > =>Vendor_info    : 'Optiarc '
> > =>Identifikation : 'DVD RW AD-7200A '
> > =>Revision       : '1.06'
> > =>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> > =>Current: CD-R
> > =>Profile: DVD+R/DL 
> > =>Profile: DVD+R 
> > =>Profile: DVD+RW 
> > =>Profile: DVD-R/DL layer jump recording 
> > =>Profile: DVD-R/DL sequential recording 
> > =>Profile: DVD-RW sequential recording 
> > =>Profile: DVD-RW restricted overwrite 
> > =>Profile: DVD-RAM 
> > =>Profile: DVD-R sequential recording 
> > =>Profile: DVD-ROM 
> > =>Profile: CD-RW 
> > =>Profile: CD-R (current)
> > =>Profile: CD-ROM (current)
> > =>Profile: Removable Disk 
> > =>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 : 866304 = 846 KB
> > =>FIFO size      : 4194304 = 4096 KB
> > =>cdrecord: No such file or directory. Cannot open
> > =>'burnfree:+driveropts=burnfree'.
> > =>Error occurred! Could not burn the CD
> > =>
> > 
> > Interesting. You need to run this with tracing turned on so we can
> > see what and where
> 
> BUGGER.  It took ages to rip the *.wavs :-D
> 
> I will try again...

A quick grep/find:

burning/burning.sh  line 71

    # HACK to get driveroptions to work. FIXME
    # FIXME: Also, if you modify the variable then it will only work
once. # The second time through, you'll change the value to
    # driveropts=driveropts=$BBOPT_ONE
    BBOPT_ONE=${BBOPT_ONE:+driveropts="$BBOPT_ONE"}


I am still running a copy -> copy so will have the trace soon.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 09:56:36 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:
> 
> =>
> =>The error message is such after ripping CD to disc:
> =>
> =>...
> =>...
> =>Tracks ripped!
> =>Insert blank CD and then press [ENTER] to go on
> =>
> =>cdrecord: No write mode specified.
> =>cdrecord: Asuming -sao mode.
> =>cdrecord: If your drive does not accept -sao, try -tao.
> =>cdrecord: Future versions of cdrecord may have different drive
> =>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
> =>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC
> Type: 1 =>= CD-ROM scsidev: '/dev/cdrom'
> =>devname: '/dev/cdrom'
> =>scsibus: -2 target: -2 lun: -2
> =>Warning: Open by 'devname' is unintentional and not supported.
> =>Linux sg driver version: 3.5.27
> =>Using libscg version 'schily-0.9'.
> =>SCSI buffer size: 64512
> =>atapi: 1
> =>Device type    : Removable CD-ROM
> =>Version        : 0
> =>Response Format: 2
> =>Capabilities   : 
> =>Vendor_info    : 'Optiarc '
> =>Identifikation : 'DVD RW AD-7200A '
> =>Revision       : '1.06'
> =>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> =>Current: CD-R
> =>Profile: DVD+R/DL 
> =>Profile: DVD+R 
> =>Profile: DVD+RW 
> =>Profile: DVD-R/DL layer jump recording 
> =>Profile: DVD-R/DL sequential recording 
> =>Profile: DVD-RW sequential recording 
> =>Profile: DVD-RW restricted overwrite 
> =>Profile: DVD-RAM 
> =>Profile: DVD-R sequential recording 
> =>Profile: DVD-ROM 
> =>Profile: CD-RW 
> =>Profile: CD-R (current)
> =>Profile: CD-ROM (current)
> =>Profile: Removable Disk 
> =>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 : 866304 = 846 KB
> =>FIFO size      : 4194304 = 4096 KB
> =>cdrecord: No such file or directory. Cannot open
> =>'burnfree:+driveropts=burnfree'.
> =>Error occurred! Could not burn the CD
> =>
> 
> Interesting. You need to run this with tracing turned on so we can
> see what and where

BUGGER.  It took ages to rip the *.wavs :-D

I will try again...

Nick

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 13:18:58 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 13:05:09 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Tue, 30 Sep 2008 10:37:14 +0100
> > Nick Warne <ni...@li...> wrote:
> > 
> > > On Fri, 12 Sep 2008 00:03:10 +0200
> > > Anders Lindén <and...@gm...> wrote:
> > > 
> > > > lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > > > > On Sun, 31 Aug 2008 17:37:09 +0100
> > > > > Nick Warne <ni...@uk...> wrote:
> > > > > 
> > > > > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > > > > Nick Warne <ni...@uk...> wrote:
> > > > > > 
> > > > > > > I think we ought to start a thread reporting successful
> > > > > > > functionality
> > > > > > > 
> > > > > > > I just fixed a broken data recording - committed.
> > > > > > > 
> > > > > > > So please just reply to this thread as each function is
> > > > > > > proven to work so we have some sort of visible guide.
> > > > > > > 
> > > > > > > 
> > > > > > > Data recording WORKS
> > > > > > > 
> > > > > > 
> > > > > > Burning ISO works
> > > > > > 
> > > > > 
> > > > > OK, update.  I just burnt a *.ogv file to CD(data recording).
> > > > > 
> > > > > All works perfectly.
> > > > > 
> > > > > BTW, worth a watch:
> > > > > 
> > > > > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > > > > 
> > > > > Nick
> > > > 
> > > > Data DVD burning works.
> > > 
> > > MP3 to Audio CD works.
> > 
> > CD ripping to *.ogg -> hard drive works :-)
> 
> CD ripping to *.mp3 -> hard drive works :-))

CD ripping to *.flac -> hard drive works :-)))

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] CD to CD copy FAILURE

[Steven W. O. <st...@sy...>]

On Tuesday, Sep 30th 2008 at 09:51 -0000, quoth Nick Warne:

=>
=>The error message is such after ripping CD to disc:
=>
=>...
=>...
=>Tracks ripped!
=>Insert blank CD and then press [ENTER] to go on
=>
=>cdrecord: No write mode specified.
=>cdrecord: Asuming -sao mode.
=>cdrecord: If your drive does not accept -sao, try -tao.
=>cdrecord: Future versions of cdrecord may have different drive
=>dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
=>(i686-pc-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling TOC Type: 1
=>= CD-ROM scsidev: '/dev/cdrom'
=>devname: '/dev/cdrom'
=>scsibus: -2 target: -2 lun: -2
=>Warning: Open by 'devname' is unintentional and not supported.
=>Linux sg driver version: 3.5.27
=>Using libscg version 'schily-0.9'.
=>SCSI buffer size: 64512
=>atapi: 1
=>Device type    : Removable CD-ROM
=>Version        : 0
=>Response Format: 2
=>Capabilities   : 
=>Vendor_info    : 'Optiarc '
=>Identifikation : 'DVD RW AD-7200A '
=>Revision       : '1.06'
=>Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
=>Current: CD-R
=>Profile: DVD+R/DL 
=>Profile: DVD+R 
=>Profile: DVD+RW 
=>Profile: DVD-R/DL layer jump recording 
=>Profile: DVD-R/DL sequential recording 
=>Profile: DVD-RW sequential recording 
=>Profile: DVD-RW restricted overwrite 
=>Profile: DVD-RAM 
=>Profile: DVD-R sequential recording 
=>Profile: DVD-ROM 
=>Profile: CD-RW 
=>Profile: CD-R (current)
=>Profile: CD-ROM (current)
=>Profile: Removable Disk 
=>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 : 866304 = 846 KB
=>FIFO size      : 4194304 = 4096 KB
=>cdrecord: No such file or directory. Cannot open
=>'burnfree:+driveropts=burnfree'.
=>Error occurred! Could not burn the CD
=>

Interesting. You need to run this with tracing turned on so we can see 
what and where

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

[Bashburn-info] CD to CD copy FAILURE

[Nick W. <ni...@li...>]

The error message is such after ripping CD to disc:

...
...
Tracks ripped!
Insert blank CD and then press [ENTER] to go on

cdrecord: No write mode specified.
cdrecord: Asuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive
dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a38
(i686-pc-linux-gnu) Copyright (C) 1995-2008 Jörg Schilling TOC Type: 1
= CD-ROM scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'Optiarc '
Identifikation : 'DVD RW AD-7200A '
Revision       : '1.06'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD+R/DL 
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-R/DL layer jump recording 
Profile: DVD-R/DL sequential recording 
Profile: DVD-RW sequential recording 
Profile: DVD-RW restricted overwrite 
Profile: DVD-RAM 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R (current)
Profile: CD-ROM (current)
Profile: Removable Disk 
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 : 866304 = 846 KB
FIFO size      : 4194304 = 4096 KB
cdrecord: No such file or directory. Cannot open
'burnfree:+driveropts=burnfree'.
Error occurred! Could not burn the CD



Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Fix up misc/check_path.sh

[Steven W. O. <st...@sy...>]

On Tuesday, Sep 30th 2008 at 03:07 -0000, quoth Nick Warne:

=>
=>I noticed this wasn't working right - I was told I had to install
=>missing apps even if I had them all.
=>
=>Looking at this, it was sooooooo convoluted logic the way a missing app
=>was looked at.  Putting echoes in, I was getting 14 apps found and 25
=>nr_apps.
=>
=>Also, I haven't a clue what this line did:
=>
=>nr_apps=$(( ${#BBBURNING} + ${#BBRIPPERS} + ${#BBXCODERS} +
=>${#BBMISC} ))
=>
=>Anyway, it is now fixed - easy to read and will always work, no matter
=>how many apps are added at a later date.
=>
=>The function is already THERE to test if an app exists.  All we need to
=>do is count the MISSING ones.  If after the function,
=>bb_not_found_apps != 0, then we know (but don't care which, the
=>function deals with that) apps are missing, and thus just print the
=>warning.
=>
=>Oh, also the reason I looked at this file was to add a 'clear' so the
=>display is all nice when the paths are printed to stdout.
=>
=>Nick

If you have an array aa, then ${#aa[@]} is equal to the number of 
elements in the array. I screwed up and said ${#aa} instead which only 
returned the length of the first element of the array. Your fix is fine. 
One criticism is that Boolean variables should never be tested to see if 
they are equal to True.

Good form:

if (( var ))
if (( ! var ))
if (( var != 0 ))

Bad form:

if (( var == 1 ))
if (( ( var == 1 ) == 1 ))
if (( ( var != 1 ) == 0 )) 

etc ... :-)

The rest of it looks good.

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steven W. Orr

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 13:05:09 +0100
Nick Warne <ni...@li...> wrote:

> On Tue, 30 Sep 2008 10:37:14 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > On Fri, 12 Sep 2008 00:03:10 +0200
> > Anders Lindén <and...@gm...> wrote:
> > 
> > > lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > > > On Sun, 31 Aug 2008 17:37:09 +0100
> > > > Nick Warne <ni...@uk...> wrote:
> > > > 
> > > > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > > > Nick Warne <ni...@uk...> wrote:
> > > > > 
> > > > > > I think we ought to start a thread reporting successful
> > > > > > functionality
> > > > > > 
> > > > > > I just fixed a broken data recording - committed.
> > > > > > 
> > > > > > So please just reply to this thread as each function is
> > > > > > proven to work so we have some sort of visible guide.
> > > > > > 
> > > > > > 
> > > > > > Data recording WORKS
> > > > > > 
> > > > > 
> > > > > Burning ISO works
> > > > > 
> > > > 
> > > > OK, update.  I just burnt a *.ogv file to CD(data recording).
> > > > 
> > > > All works perfectly.
> > > > 
> > > > BTW, worth a watch:
> > > > 
> > > > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > > > 
> > > > Nick
> > > 
> > > Data DVD burning works.
> > 
> > MP3 to Audio CD works.
> 
> CD ripping to *.ogg -> hard drive works :-)

CD ripping to *.mp3 -> hard drive works :-))


-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 10:37:14 +0100
Nick Warne <ni...@li...> wrote:

> On Fri, 12 Sep 2008 00:03:10 +0200
> Anders Lindén <and...@gm...> wrote:
> 
> > lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > > On Sun, 31 Aug 2008 17:37:09 +0100
> > > Nick Warne <ni...@uk...> wrote:
> > > 
> > > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > > Nick Warne <ni...@uk...> wrote:
> > > > 
> > > > > I think we ought to start a thread reporting successful
> > > > > functionality
> > > > > 
> > > > > I just fixed a broken data recording - committed.
> > > > > 
> > > > > So please just reply to this thread as each function is proven
> > > > > to work so we have some sort of visible guide.
> > > > > 
> > > > > 
> > > > > Data recording WORKS
> > > > > 
> > > > 
> > > > Burning ISO works
> > > > 
> > > 
> > > OK, update.  I just burnt a *.ogv file to CD(data recording).
> > > 
> > > All works perfectly.
> > > 
> > > BTW, worth a watch:
> > > 
> > > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > > 
> > > Nick
> > 
> > Data DVD burning works.
> 
> MP3 to Audio CD works.

CD ripping to *.ogg -> hard drive works :-)


-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@li...>]

On Fri, 12 Sep 2008 00:03:10 +0200
Anders Lindén <and...@gm...> wrote:

> lör 2008-09-06 klockan 14:33 +0100 skrev Nick Warne:
> > On Sun, 31 Aug 2008 17:37:09 +0100
> > Nick Warne <ni...@uk...> wrote:
> > 
> > > On Sun, 31 Aug 2008 17:02:19 +0100
> > > Nick Warne <ni...@uk...> wrote:
> > > 
> > > > I think we ought to start a thread reporting successful
> > > > functionality
> > > > 
> > > > I just fixed a broken data recording - committed.
> > > > 
> > > > So please just reply to this thread as each function is proven
> > > > to work so we have some sort of visible guide.
> > > > 
> > > > 
> > > > Data recording WORKS
> > > > 
> > > 
> > > Burning ISO works
> > > 
> > 
> > OK, update.  I just burnt a *.ogv file to CD(data recording).
> > 
> > All works perfectly.
> > 
> > BTW, worth a watch:
> > 
> > http://www.gnu.org/fry/happy-birthday-to-gnu.html
> > 
> > Nick
> 
> Data DVD burning works.

MP3 to Audio CD works.


-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Fix up misc/check_path.sh

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 08:07:51 +0100
Nick Warne <ni...@li...> wrote:

> 
> I noticed this wasn't working right - I was told I had to install
> missing apps even if I had them all.
> 
> Looking at this, it was sooooooo convoluted logic the way a missing
> app was looked at.  Putting echoes in, I was getting 14 apps found
> and 25 nr_apps.
> 
> Also, I haven't a clue what this line did:
> 
> nr_apps=$(( ${#BBBURNING} + ${#BBRIPPERS} + ${#BBXCODERS} +
> ${#BBMISC} ))
> 
> Anyway, it is now fixed - easy to read and will always work, no matter
> how many apps are added at a later date.
> 
> The function is already THERE to test if an app exists.  All we need
> to do is count the MISSING ones.  If after the function,
> bb_not_found_apps != 0, then we know (but don't care which, the
> function deals with that) apps are missing, and thus just print the
> warning.
> 
> Oh, also the reason I looked at this file was to add a 'clear' so the
> display is all nice when the paths are printed to stdout.

OK, I tweaked this a bit more.  Only a flag is needed if an app is
missing, no counting required.

Works and looks good now.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Fix up misc/check_path.sh

[Nick W. <ni...@li...>]

I noticed this wasn't working right - I was told I had to install
missing apps even if I had them all.

Looking at this, it was sooooooo convoluted logic the way a missing app
was looked at.  Putting echoes in, I was getting 14 apps found and 25
nr_apps.

Also, I haven't a clue what this line did:

nr_apps=$(( ${#BBBURNING} + ${#BBRIPPERS} + ${#BBXCODERS} +
${#BBMISC} ))

Anyway, it is now fixed - easy to read and will always work, no matter
how many apps are added at a later date.

The function is already THERE to test if an app exists.  All we need to
do is count the MISSING ones.  If after the function,
bb_not_found_apps != 0, then we know (but don't care which, the
function deals with that) apps are missing, and thus just print the
warning.

Oh, also the reason I looked at this file was to add a 'clear' so the
display is all nice when the paths are printed to stdout.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Time to stabilize

[Nick W. <ni...@li...>]

On Tue, 30 Sep 2008 03:30:58 +0200
Anders Lindén <and...@gm...> wrote:

> It seems like things are calming down now, the interface and functions
> seem to be stable. Things I suggest we do:
> 
> * Serious testing of all functionality.
> (I suggest changing the CD recording command to 'cdrecord -dummy' and
> the DVD burning command to 'growisofs -dry-run' to not waste CDs/DVDs)
> * Make sure translations are complete.
> (No further changes that needs .lang-files updated will be accepted)
> * Make sure documentation is updated.
> 
> When these steps are done, merge trunk into 3.0 and release it. 
> Do you all agree? Is there anything else you like to add? 
> 
> Some restructuring like Steven has suggested and the gettextification
> (And other things anyone can think of) should go into 3.1. 
> 

Yep, I agree too.

One thing Anders.  I noticed in the Changelog the version had been
bumped up to 3.1, so I did likewise in BashBurn.sh and made the
version $VAR 3.1 too.

So are we at version 3.0, or 3.1? 

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Time to stabilize

[Steven W. O. <st...@sy...>]

On Monday, Sep 29th 2008 at 21:30 -0000, quoth Anders Lind?n:

=>It seems like things are calming down now, the interface and functions
=>seem to be stable. Things I suggest we do:
=>
=>* Serious testing of all functionality.
=>(I suggest changing the CD recording command to 'cdrecord -dummy' and
=>the DVD burning command to 'growisofs -dry-run' to not waste CDs/DVDs)
=>* Make sure translations are complete.
=>(No further changes that needs .lang-files updated will be accepted)
=>* Make sure documentation is updated.
=>
=>When these steps are done, merge trunk into 3.0 and release it. 
=>Do you all agree? Is there anything else you like to add? 
=>
=>Some restructuring like Steven has suggested and the gettextification
=>(And other things anyone can think of) should go into 3.1. 

Anders, that sounds good to me.

Just so you understand, I just made a change, yet again. I had created a 
function in BB.sh called source_non_language_modules. I eliminated that 
whole function in favor of just putting that code inline. I believe the 
problem we had today was related to the fact that that function had caused 
all the typedefs to become local variables inside 
source_non_language_modules, instead of being the globals we wanted them 
to be.

We really should be ok now.

As for testing, if possible, we need to beat on audiofunc. There really is 
some hairy code there and I'm concerned that no one noticed that it was 
broken before.

I'm actually building up a collection of tricks in bash that I had never 
developed before. In particular, there's an interesting concept that turns 
out to be useful, not from an algorithm perspective, but more from a 
patterns view. It goes something like this:

funcA()
{
    typeset stbe="$1"		# Something To Be Eval'd.

    while something_is_true
    do
	var=something
	eval $stbe
    done
}

But note that stbe might refer to var. Then we call funcA


xxx='I love a parade. Especially on a $var' # Notice the single quotes.
funcA "$xxx"

Note that xxx is just an uninterpolated string, and no one outside of 
funcA knows anything about var. This is used *all* over the place.

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] Nick, I'm reverting the change you made to configfunc.sh

[Steven W. O. <st...@sy...>]

On Monday, Sep 29th 2008 at 18:05 -0000, quoth Nick Warne:

=>On Mon, 29 Sep 2008 16:15:54 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> On Monday, Sep 29th 2008 at 15:50 -0000, quoth Nick Warne:
=>> 
=>> =>On Mon, 29 Sep 2008 15:25:29 -0400 (EDT)
=>> =>"Steven W. Orr" <st...@sy...> wrote:
=>> =>
=>> =>> On Monday, Sep 29th 2008 at 14:00 -0000, quoth Nick Warne:
=>> =>> 
=>> =>> =>On Mon, 29 Sep 2008 13:53:12 -0400 (EDT)
=>> =>> =>"Steven W. Orr" <st...@sy...> wrote:
=>> =>> =>
=>> =>> =>> On Monday, Sep 29th 2008 at 13:41 -0000, quoth Nick Warne:
=>> =>> =>> 
=>> =>> =>> =>On Mon, 29 Sep 2008 13:38:13 -0400 (EDT)
=>> =>> =>> =>"Steven W. Orr" <st...@sy...> wrote:
=>> =>> =>> =>
=>> =>> =>> =>> On Monday, Sep 29th 2008 at 13:29 -0000, quoth Nick Warne:
=>> =>> =>> =>> 
=>> =>> =>> =>> =>On Mon, 29 Sep 2008 18:25:56 +0100
=>> =>> =>> =>> =>Nick Warne <ni...@li...> wrote:
=>> =>> =>> =>> =>
=>> =>> =>> =>> =>> On Mon, 29 Sep 2008 13:21:47 -0400 (EDT)
=>> =>> =>> =>> =>> "Steven W. Orr" <st...@sy...> wrote:
=>> =>> =>> =>> =>>  
=>> =>> =>> =>> =>> > Just so you know what's happening, 
=>> =>> =>> =>> =>> > 
=>> =>> =>> =>> =>> >     (( ${!BB_CONFIG_VAR} == 0 )) && return 1
=>> =>> =>> =>> =>> > 
=>> =>> =>> =>> =>> > says, "Indirect through BB_CONFIG_VAR and see if
=>> it's =>> value =>> is =>> 0. =>> > BB_CONFIG_VAR is only ever equal
=>> to either =>> =>> =>> BB_CONFIG_MODIFIED or =>> >
=>> BB_ADVANCED_CONFIG_MODIFIED. =>> Both of =>> =>> those variables are
=>> declared =>> > to be of type =>> integer using =>> =>> typeset -i =>>
=>> > =>> =>> =>> =>> > typeset -i BB_CONFIG_MODIFIED=0
=>> =>> =>> =>> =>> > typeset -i BB_ADVANCED_CONFIG_MODIFIED=0
=>> =>> =>> =>> =>> > 
=>> =>> =>> =>> =>> > So, if you test (( ${BB_CONFIG_VAR} == 0 )) it will
=>> =>> always =>> be =>> =>> > false. And if you test to see if it's
=>> equal =>> to 'true' =>> then =>> that's a =>> > problem also because
=>> you're =>> testing it inside =>> an =>> arithmetic test, =>> > i.e.
=>> (( )) =>> instead of [[ ]]. Because =>> bash does =>> not require
=>> integer =>> > =>> variables to be preceeded by =>> a dollarsign =>>
=>> in an arithmetic =>> context, =>> > it should complain =>> that there
=>> is no =>> variable =>> called true but =>> > instead it just =>>
=>> converts the true to a =>> =>> 1 because it's not equal to =>> > 0.
=>> =>> =>> =>> > =>> =>> =>> =>> > Something is going on where you might
=>> have (for some =>> reason =>> I =>> don't =>> > know about) a value
=>> for BB_CONFIG_VAR of =>> null (""). =>> =>> =>> > 
=>> =>> =>> =>> =>> > I need to see more about why you're getting a syntax
=>> =>> =>> problem. =>> =>> > 
=>> =>> =>> =>> =>> > 
=>> =>> =>> =>> =>> 
=>> =>> =>> =>> =>> Attached in script output.
=>> =>> =>> =>> =>
=>> =>> =>> =>> =>Ummm.  WTF.  Bloody thing got stripped of the mail -
=>> let me =>> =>> gzip it. =>> 
=>> =>> =>> =>> I just checked in a change. Tell me if it fixes it for
=>> you. =>> =>> =>> 
=>> =>> =>> =>> Also, what rev of bash are you running?
=>> =>> =>> =>> 
=>> =>> =>> =>Nope, same issue.
=>> =>> =>> =>
=>> =>> =>> =>GNU bash, version 3.1.17(2)-release
=>> (i486-slackware-linux-gnu) =>> =>> =>Copyright (C) 2005 Free Software
=>> Foundation, Inc. =>> =>> 
=>> =>> =>> Don't know what to say. Can you start putting print
=>> statements in? =>> =>> When you go into bbconfmenu, BB_CONFIG_VAR
=>> *has* to be one or the =>> =>> other.
=>> =>> =>> 
=>> =>> =>> You can see it being set in configure and advanced.
=>> =>> =>> 
=>> =>> =>Well, you could be onto something here.  Glad I am not going mad
=>> =>> =>again...
=>> =>> =>
=>> =>> =>My changes marked <---HERE:
=>> =>> =>
=>> =>> =># Confirmation routine on leaving configuration.
=>> =>> =>get_confirm()
=>> =>> =>{
=>> =>> =>echo "$BB_CONFIG_VAR" <---------------------------------  HERE
=>> =>> =>(( ${!BB_CONFIG_VAR} == 0 )) && return 1
=>> =>> =>
=>> =>> =>
=>> =>> =>And the output running BB:
=>> =>> =>
=>> =>> =>|-(Actions)
=>> =>> =>|- 19) Apply changes
=>> =>> =>|- 20) Apply defaults
=>> =>> =>|- 21) Revert changes
=>> =>> =>|- 22) Back
=>> =>> =>Your Choice? |>  22
=>> =>> =>
=>> =>> =>BB_CONFIG_MODIFIED  <--------------- HERE
=>> =>> =>/usr/lib/Bashburn/lib/func/configfunc.sh: line 33: ((: == 0 :
=>> syntax =>> =>error: operand expected (error token is "== 0 ") It
=>> appears you =>> changed =>an option but did not apply it.
=>> =>> =>
=>> =>> =>Here you can select 'n' to go back and do so;
=>> =>> =>If you wish to ignore the change, select 'y'.
=>> =>> 
=>> =>> This kinda sucks having to do this long distance like this.
=>> =>> 
=>> =>> Next step might be, after your echo, to add something like
=>> =>> 
=>> =>> echo "!BB_CONFIG_VAR = ${!BB_CONFIG_VAR}"
=>> =>
=>> =>Your Choice? |>  22
=>> =>
=>> =>!BB_CONFIG_VAR = 
=>> =>/usr/lib/Bashburn/lib/func/configfunc.sh: line 33: ((: == 0 : syntax
=>> =>error: operand expected (error token is "== 0 ") It appears you
=>> changed =>an option but did not apply it.
=>> =>
=>> =>${!BB_CONFIG_VAR}  returns sweet nothing.
=>> =>
=>> =>Nick
=>> 
=>> Ok. Try now. This should do it, though I'm not sure why it failed
=>> before.
=>> 
=>> Like they say in the funny papers, this time fer sher.
=>
=>It works!
=>
=>What gets me is why you do not see these issues, yet everybody does,
=>Steve?
=>
=>Do you set up some sort of test environment of sorts that could hide
=>all this sort of stuff (i.e. make it work OK)?

No. I always do it the same way.
(as root) ./Install.sh 

bashburn

and if I need to make sure I see any funny stuff,

script
bashburn
exit
vi typescript

I'm making a couple of changes to make it even better. :-(

Hold onto your hats.

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steven W. Orr

[Bashburn-info] Time to stabilize

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

It seems like things are calming down now, the interface and functions
seem to be stable. Things I suggest we do:

* Serious testing of all functionality.
(I suggest changing the CD recording command to 'cdrecord -dummy' and
the DVD burning command to 'growisofs -dry-run' to not waste CDs/DVDs)
* Make sure translations are complete.
(No further changes that needs .lang-files updated will be accepted)
* Make sure documentation is updated.

When these steps are done, merge trunk into 3.0 and release it. 
Do you all agree? Is there anything else you like to add? 

Some restructuring like Steven has suggested and the gettextification
(And other things anyone can think of) should go into 3.1. 

-- 
Anders Lindén
http://bashburn.sf.net