On Sat, 2007-08-04 at 06:23 -0500, Randy McMurchy wrote:
> Note that in the first loop using the shell with -e, the rest
> of the loop after failing on the missing 'd' file is *not*
> executed by the parent shell.
Ok, I'd not considered shell constructs like loops - I was thinking more
of individu
Simon Geard wrote these words on 08/03/07 23:25 CST:
> Again, I don't see any merit in using -e in an interactive shell.
Sometimes, a simple 10 second experiment is worth 1000 words:
[EMAIL PROTECTED]: ~/td > ls -l
total 0
-rw-r--r-- 1 randy randy 0 Aug 4 06:14 a
-rw-r--r-- 1 randy randy 0 Aug
Simon Geard wrote:
>
> If the instructions aren't part of a script, what exactly does the "bash
> -e" step contribute? Start a new shell for running commands in, which
> should exit any time one of them fails? The -e might be useful in an
> shell script (i.e the #!/bin/bash case), but what's the
On Fri, 2007-08-03 at 05:01 -0500, Randy McMurchy wrote:
> Simon Geard wrote these words on 08/03/07 04:32 CST:
>
> > If the instructions aren't part of a script, what exactly does the "bash
> > -e" step contribute? Start a new shell for running commands in, which
> > should exit any time one of t
Simon Geard wrote these words on 08/03/07 04:32 CST:
> If the instructions aren't part of a script, what exactly does the "bash
> -e" step contribute? Start a new shell for running commands in, which
> should exit any time one of them fails? The -e might be useful in an
> shell script (i.e the #!/
On Thu, 2007-08-02 at 06:58 -0700, Dan Nicholson wrote:
> This is sort of a compromise area. The last time I worked on it, I
> almost added the shebang in. But, as Randy says, the BLFS intention is
> for you to be pasting the commands into a shell. Here, though, it
> actually says to write a script
Dan Nicholson wrote these words on 08/02/07 08:58 CST:
> This is sort of a compromise area. The last time I worked on it, I
> almost added the shebang in. But, as Randy says, the BLFS intention is
> for you to be pasting the commands into a shell. Here, though, it
> actually says to write a script
On 8/2/07, Nicolas FRANCOIS <[EMAIL PROTECTED]> wrote:
> Le Thu, 02 Aug 2007 08:10:51 -0500 Randy McMurchy
> <[EMAIL PROTECTED]> a écrit :
> >
> > The example shown in the book is meant to be typed (cut/pasted) at the
> > command line, not put in a file and executed. So the answer to the
> > questi
Le Thu, 02 Aug 2007 08:10:51 -0500 Randy McMurchy
<[EMAIL PROTECTED]> a écrit :
> Nicolas FRANCOIS wrote these words on 08/02/07 07:25 CST:
>
> > When you launch such a script, nothing happens, until you type something
> > on the console. Then the script starts.
>
> The BLFS book is not designed
Nicolas FRANCOIS wrote these words on 08/02/07 07:25 CST:
> When you launch such a script, nothing happens, until you type something
> on the console. Then the script starts.
The BLFS book is not designed to read and then create executable scripts
of the instructions. The instructions are meant t
#!/bin/bash -e
is the correct beginning.
It means, use /bin/bash as interpreter for the script, and
exit immediately on any error.
--Luca
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Le Thu, 02 Aug 2007 14:53:15 +0200 Koenraad Lelong
<[EMAIL PROTECTED]> a écrit :
> Nicolas FRANCOIS schreef:
> > Hi.
> >
> > On page xorg7.html of the BLFS book, it is mentionned that the
> > compilation of the different parts of Xorg should be scripted, that I can
> > only agree with. But the sc
Nicolas FRANCOIS schreef:
> Hi.
>
> On page xorg7.html of the BLFS book, it is mentionned that the
> compilation of the different parts of Xorg should be scripted, that I can
> only agree with. But the script behaviour is quite strange :
>
> bash -e #exit on all errors
> section=proto
> version=7
Hi.
On page xorg7.html of the BLFS book, it is mentionned that the
compilation of the different parts of Xorg should be scripted, that I can
only agree with. But the script behaviour is quite strange :
bash -e #exit on all errors
section=proto
version=7.2
mkdir $section
cd $section
...
When you
14 matches
Mail list logo
