| 1 |
On Jul 29, 2017 12:27, "Ста Деюс" <sthu.deus@×××××××××××.org> wrote: |
| 2 |
|
| 3 |
Hi, Neil. |
| 4 |
|
| 5 |
|
| 6 |
On Fri, 28 Jul 2017 21:43:53 +0100, you wrote: |
| 7 |
|
| 8 |
> > How do you know that the contents of the script are not relevant |
| 9 |
> > when you |
| 10 |
> don't know what the problem is? It is also useful to know the exact |
| 11 |
|
| 12 |
Mathematics (mother of computers) answers: 1+1=2. -- Meaning: same |
| 13 |
script w/ the same bash gets same execution. |
| 14 |
|
| 15 |
> version of bash in use on each system. There are subtle differences, |
| 16 |
> and bugs, between bash versions. Your script may be tripping up on |
| 17 |
> one of these. |
| 18 |
|
| 19 |
Alright. Here is an example of the problematic line from the point |
| 20 |
of view of "Gentoo's" bash: |
| 21 |
|
| 22 |
read 'Enter device (like /dev/sd(a1,b1,...): ' device |
| 23 |
|
| 24 |
Until i remove the brackets, "Gentoo's" bash keeps error messaging. |
| 25 |
|
| 26 |
|
| 27 |
Thank you for your time, |
| 28 |
Sthu. |
| 29 |
|
| 30 |
The line from your script above doesn't seem to have a matching right hand |
| 31 |
side bracket. |
| 32 |
Try running your script in trace mode like so, bash -x script, to further |
| 33 |
troubleshoot the issue. |
Archives