Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm completely new to writing the shell files to run in batch.
It seemed to be completely straight forward, and I wrote the following file: simpTask.sh
The guess by tredegar was good! The problem arises due to the different line terminators used by windows and unix systems (details here). Try the command
Then you might need to use dos2unix to convert it to the unix format. Or just use a linux text editor to create it, or an editor that can save the files with linux line endings. DOS/Win uses carry return AND line feed to mark a new line, Unix/Linux use just a line feed character.
dos2unix on file didn't change the outcome -- still could not open
downloaded editpad lite, saved as unix file, ./simpTask.sh results in "file not found" but vi simpTask.sh shows file
xwin won't allow me to open nedit -- and before resorting to using vi, or one of those text editors that I find painful, I thought i'd fish around to see if there were any other ideas.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.