Hello
Can I write script file(batch) same as window batch file on linux

regards
RKB

Yes you can write the script that will do what you want but with linux commands ofcourse!!!
If you want some thing to do oftenly, you may want to look at cron.

How !
I am new for Linux
Can u give me some examples

The "Advanced Bash Scripting Guide" book in the www.tldp.org website has hundreds of examples. The entire book consists of well commented examples making it easier to learn than from a reference guide. Don't let the word Advanced scare you off. Thorough would be a better description.

assuming that you do know basic bash commands.
try this
open a text editor.enter the following
assuming that you have saved it as test.sh
then make it an executable by command

then type in bash

then you will understand everything

Linux shell scripts are the equivalent of windows batch scripts, they are really no more than a series of commands in a text file. In particular, they have a call to the shell they are supposed to use (linux has a number of different shells available, with different functionalities and syntaxes), which will look like

#!/bin/bash

The #! tells the system that what follows is the path to the shell that should run the commands contained in the script. /bin/bash is the location of the bash shell, the linux standard. Take for example the series of commmands:

ls
pwd
whoami

The first command, ls, gives a listing of files in the current directory. The pwd command prints the path of the directory you are currently located in. The whoami command returns your username. A shell script to execute those commands would look like this:

So far it's just a text file; it needs to have execute permission added to it. The command

Where 'shellfile' is the name of the script, the file containing the series of commands. The script can now be executed by passing the command
from the directory where the script resides. You can also pass the absolute path, for example /home/bob/shellfile. The results and output of the commands in the script will be displayed on your screen.

Now, I kind of lied when I said that it needs execute permission to be run; an alternative to adding execute permission to a file can be to use the source command, as in

source shellfile

or

. shellfile

(the . is short for 'source'). You may also forego the inclusion of the #!/bin/bash call on the first line and invoke your script with

bash shellfile

Keep in mind too that ANYONE, including root, attempting to execute a file that does not have execute permission set (either by ./shellfile or /home/bob/shellfile) will get a "permission denied" error. Many shell script files will also be named with a .sh extension, or one that corresponds to the shell that handles them, such as .ksh, .bash, .zsh, etc, although this is not strictly necessary.

Google for Unix Shell Scripting. It totally rocks. Makes Windows Batch Scripting look like a cheap gimmick!


Debian Kernel

This book is a must read if you are serious about learning shell scripting. Despite of it's title, it's suitable for beginners as well as advanced users. However, note that linux shells (any of them) are far far more feature rich than command.com, also, linux (and unix like OSes in general) have a very big set of tools that have been programmed in ways that they can be often connected to operate with the output of each other tools. That adds a lot of possibilities, the set of available tools is much bigger than those available under DOS or Windows command line as well.

So, be prepared to learn.

Here you go - just what you need
http://tldp.org/LDP/abs/html/dosbatch.html#VIEWDAT
has conversion tables for dos batch commands to Baxh shell commands
and an example of converting viewdata.bat to viewdata.sh
Good luck

You may also find this useful: http://rute.2038bug.com/index.html.gz

Note that sourcing a script and running it are not the same thing. I don't want to disrupt the thread so I will not enumerate the differences here, but this has many implications that can misguide the OP. Enough to say that the environment will be different, and that the script can change your working environment, producing lots of funky effects once the script is terminated.

Neither of these ways is more or less correct. Just be aware that they are not the same, and they might be better or worse depending on the concrete case. I just wanted to say: don't assume that they all are equivalent ways to launch a script. They aren't.