Use of cp in a script


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Use of cp in a script
Prev   Next
# 3  
Old 12-14-2011
Thanks

I think that was it, thanks for the help, it is the little things like that, that trip me up. Stuff you would not realize was wrong just by looking at the man page.Smilie
 
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to block first bash script until second bash script script launches web server/site?

I'm new to utilities like socat and netcat and I'm not clear if they will do what I need. I have a "compileDeployStartWebServer.sh" script and a "StartBrowser.sh" script that are started by emacs/elisp at the same time in two different processes. I'm using Cygwin bash on Windows 10. My... (3 Replies)
Discussion started by: siegfried
3 Replies

2. Shell Programming and Scripting

Shell script works fine as a standalone script but not as part of a bigger script

Hello all, I am facing a weird issue while executing a code below - #!/bin/bash cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset sh UKBA_publish.sh UKBA 28082015 3 if then echo "Param file conversion for all the areas are completed, please check in your home directory"... (2 Replies)
Discussion started by: ektubbe
2 Replies

3. UNIX for Dummies Questions & Answers

Calling a script from master script to get value from called script

I am trying to call a script(callingscript.sh) from a master script(masterscript.sh) to get string type value from calling script to master script. I have used scripts mentioned below. #masterscript.sh ./callingscript.sh echo $fileExist #callingscript.sh echo "The script is called"... (2 Replies)
Discussion started by: Raj Roy
2 Replies

4. Shell Programming and Scripting

Script will keep checking running status of another script and also restart called script at night

I am using blow script :-- #!/bin/bash FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not if then # echo "process found" exit 0; else echo "process not found" exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Discussion started by: ketanraut
1 Replies

5. Shell Programming and Scripting

create a shell script that calls another script and and an awk script

Hi guys I have a shell script that executes sql statemets and sends the output to a file.the script takes in parameters executes sql and sends the result to an output file. #!/bin/sh echo " $2 $3 $4 $5 $6 $7 isql -w400 -U$2 -S$5 -P$3 << xxx use $4 go print"**Changes to the table... (0 Replies)
Discussion started by: magikminox
0 Replies
Login or Register to Ask a Question
makefloppies(8) 					      System Manager's Manual						   makefloppies(8)

Name
       MAKEFLOPPIES - Creates the default floppy device nodes.

Note
       This  manpage has been automatically generated from fdutils's texinfo documentation.  However, this process is only approximative, and some
       items, such as cross-references, footnotes and indices are lost in this translation process.  Indeed, these items have no appropriate  rep-
       resentation  in	the  manpage  format.  Moreover, only the items specific to each command have been translated, and the general information
       about fdutils has been dropped in the manpage version.  Thus I strongly advise you to use the original texinfo doc.

       *      To generate a printable copy from the texinfo doc, run the following commands:

		     ./configure; make dvi; dvips fdutils.dvi

       *      To generate a HTML copy,	run:

		     ./configure; make html

	      A pre-made HTML can be found at: `http://www.tux.org/pub/knaff/fdutils'

       *      To generate an info copy (browsable using emacs' info mode), run:

		     ./configure; make info

       The texinfo doc looks most pretty when printed or as HTML.  Indeed, in the info version certain examples are difficult to read due  to  the
       quoting conventions used in info.

Description
	  MAKEFLOPPIES [-tlvng] [drives]

       The  MAKEFLOPPIES  shell  script creates the new floppy block device node.  It uses the floppycontrol program to translate the minor device
       numbers into meaningful names. It also uses these names to decide whether to create a given block device file or not, depending on the type
       of the physical drive (for instance, for a 3 1/2 drive, the formats corresponding to a 5 1/4 drive are not created).

       If  you	have  more  than  two  floppy  drives,	you  need  to  tell  the  kernel  the  CMOS  types  of	those  additional drives using the
       floppy=drive,type,cmos lilo option.

       If the drives  parameter is given, only the device nodes for the listed drives are made. By default, all only  the  two	first  drives  are
       tried.

       MAKEFLOPPIES does not work if you redefine your default formats.

       Caution: MAKEFLOPPIES removes already existing floppy device nodes.

Options
       -t     Use the old naming convention for 3 1/2 devices (e.g. `fd0H720' instead of `fd0u720').

       -m     Base the name for the created devices on the type of the media (e.g. `fd0h720' instead of `fd0u720').

       -l     Local. Creates device nodes in the local directory, not /dev

       -v     Verbose

       -n     Dry run. (just report what would be done, do not do anything)

       -g     Group.  Allow read/write access to floppy devices only for group `floppy'

Bugs
       The MAKEFLOPPIES script does not work on redefined "default" formats, If you redefine default formats, you need to create the needed device
       nodes manually.

See Also
       Fdutils' texinfo doc

fdutils-5.5							      03Mar05							   makefloppies(8)