598 reputation
3717
bio website
location
age
visits member for 3 years, 6 months
seen Aug 24 at 10:46

May
25
awarded  Yearling
May
22
awarded  Popular Question
Mar
26
awarded  Popular Question
Mar
5
awarded  Popular Question
Feb
22
awarded  Popular Question
Jan
11
asked Find out what /dev/cuaU maps to?
Oct
27
asked Ubuntu Server goes to standby mode
Sep
28
asked Manually run a cron job / simulate running cron job?
Sep
25
asked Availability of software during update?
Sep
13
comment Split command output by linebreak?
thank you guys, I tried this solution, but I can't get it working, please see my updated original post, thanks!
Sep
13
revised Split command output by linebreak?
added 637 characters in body
Sep
13
accepted ::1 during exim-config?
Sep
12
asked ::1 during exim-config?
Sep
11
asked Split command output by linebreak?
Sep
10
comment Command substitution: file or command not found
thank you very much, now I understand it!
Sep
10
accepted Command substitution: file or command not found
Sep
10
comment Command substitution: file or command not found
Found the difference between ' and " on linuxcommand.org/wss0060.php. Together with forcefsck's comment I now understand it completely :-)
Sep
10
comment Command substitution: file or command not found
I understand the first part of your reply, but not the one about explaing ${QUERY}, because when one simpley does echo ${QUERY}, therefore without any quotes, it is also expanded. I guess the shell is packaging the parameters into some kind of list and for the query to be one parameter, I need the quotes around it? But then, why do I need double quotes? Why not just single quotes? Thanks :-)
Sep
9
comment Command substitution: file or command not found
Thanks, that works, but I don't really understand way, because echo "${QUERY}" gives the query without the ' and ', so why does it work in the MYROWS line?
Sep
9
asked Command substitution: file or command not found