Op 9-mei-2011, om 12:32 heeft Wayne Blaszczyk het volgende geschreven: > On 09/05/11 05:16, Pol Vangheluwe wrote: >> The script to create the configuration file for sudo-1.7.4p5 (Version >> svn-20110417) contains "&&" at the end of the first line. >> I normally copy/paste the instructions from BLFS when building something on >> my target machine. >> I had to remove this "&&" to create successfully the configuration file. >> >> Same problem with the scripts to create the configuration files for >> xinetd-2.3.14. >> >> pvg >> >> >> > > That is the correct syntax. I did a quick test and it works fine. > Are you sure the cat command was not returning some kind of an error? > Regards, > Wayne.
The bash manual tells me that the structure "command1 && command2" executes command2 if and only if command1 returns the exit status of zero. But here, there is only one command (cat), so I really don't understand why "&&" is needed. When I do this, all goes well: pol [ ~ ]$ cat > oldpoem << "EOF" > Jantje zag eens pruimen hangen > o als eieren zo groot > 't scheen dat Jantje wou gaan plukken > schoon zijn vader 't hem verbood > EOF pol [ ~ ]$ cat oldpoem Jantje zag eens pruimen hangen o als eieren zo groot 't scheen dat Jantje wou gaan plukken schoon zijn vader 't hem verbood When I do the next, the script hangs. Nothings happens when I type <CR>. When I break up with <CTRL>C then no file is created. When I type "EOF"<CR> then the file is created: pol [ ~ ]$ cat > oldpoem << "EOF" && > Jantje zag eens pruimen hangen > o als eieren zo groot > 't scheen dat Jantje wou gaan plukken > schoon zijn vader 't hem verbood > EOF BTW: can you explain why the 'xinetd.conf' script has no "&&" but the 'xinetd.d/<server>' scripts have it on the xinetd-2.3.14 page? The first runs well, the other fail...
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
