I found what the problem was, Michael! I used the basic 'kedit' editor when I was at home, but at work I was using the "Advanced Editor" and had the Options set to show BASH script syntax. When I switched back to kedit and save it every thing begin to work again. So, the problem was in using the 'Advanced Editor'. Apparently it was saving invisible control characters in the file and they were barfing the shell parser. Thanks!, Jerry Michael Hasenstein <mha@suse.com> on 09/12/2000 01:33:09 PM To: Jerry Kreps/InfSys/Revenue@Revenue cc: suse-linux-e@suse.com, Jerrykreps@jlkreps.net Subject: Re: [SLE] opportunity to install SuSE at work, but... jkreps@rev.state.ne.us wrote:

bash scripts are not behaving. The following script, which works on my SuSE 6.3 at home, fails on SuSE 6.4 at work with the following messages: ...Line 4: syntax error near unexpected token clearscr(){ ...Line 4: 'clearscr(){

I cut&paste it from your email to my SuSE Linux 7.0 and it runs fine. -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq