Sponsored Content
Full Discussion: Copying files
Top Forums UNIX for Dummies Questions & Answers Copying files Post 30073 by alpheusm on Wednesday 16th of October 2002 11:05:04 AM
Old 10-16-2002
Question Copying files

I like to know the command structure of copying files/directories from a unix box using telnet session to a windows box.
 

10 More Discussions You Might Find Interesting

1. Solaris

Copying Files and

I am new user to solaris and installed solaris operating system on full Harddisk 120Gb. I am unable to copy music files to desktop and /home directory. One thing happened while registering is- i entered login-root and its password. The message prompted your system is crashed. Is it because of... (1 Reply)
Discussion started by: patilmukundraj
1 Replies

2. Shell Programming and Scripting

copying files

hi I want to copy all files from the current directory and move to .archive file. Moreover,I want to add .bak to each file name, that will be copied. How can I do that? (4 Replies)
Discussion started by: tjay83
4 Replies

3. Solaris

Copying Files

Hi, I understand that to copy files across server, the feasible way will be using scp command. Am I right? What if the two servers are not connected to a network? If by using a cross cable to link up both the server, what will be the best (fastest) way to copy files across? scp as well? ... (3 Replies)
Discussion started by: user50210
3 Replies

4. UNIX for Advanced & Expert Users

copying of files by userB, dir & files owned by userA

I am userB and have a dir /temp1 This dir is owned by me. How do I recursively copy files from another users's dir userA? I need to preserve the original user who created files, original group information, original create date, mod date etc. I tried cp -pr /home/userA/* . ... (2 Replies)
Discussion started by: Hangman2
2 Replies

5. Shell Programming and Scripting

Copying Files

Hi All, I'm trying to list some files from my log directory and files are like this log.20110302_20.gz log.20110302_21.gz log.20110302_22.gz log.20110302_23.gz log.20110303_00.gz log.20110303_01.gz log.20110303_02.gz ............ log.20110311_22.gz log.20110311_23.gz... (2 Replies)
Discussion started by: thelakbe
2 Replies

6. Shell Programming and Scripting

Files copying - [ Listed files alone. ] - Shell script

Hi All, I am doing this for svn patch making. I got the list of files to make the patch. I have the list in a file with path of all the files. To Do From Directory : /myproject/MainDir To Directory : /myproject/data List of files need to copy is in the file: /myproject/filesList.txt ... (4 Replies)
Discussion started by: linuxadmin
4 Replies

7. Shell Programming and Scripting

Copying files after result

Hi, I have a shell script #!/bin/sh date echo 'HI PROD' echo $Please ENTER THE INPUT 1 for old files 2 for new file read i if ; then cd /apps/acetp3_logs/prod3/O* pwd echo $PLEASE ENTER THE STRING TO SEARCH (PLEASE ENTER THE STRING INSIDE QUOTES ' ') read j echo... (6 Replies)
Discussion started by: thelakbe
6 Replies

8. Shell Programming and Scripting

Copying files excluding some files

Hi, I have a folder which contains files in this format. abc-bin.000001 abc-bin.000002 abc-bin.000003 abc-bin.000004 abc-bin.000005 abc-bin.000006 abc-bin.000007 abc-bin.000008 abc-bin.000009 abc-bin.000010 abc-bin.index I want to copy all the files between abc-bin.000004... (6 Replies)
Discussion started by: arijitsaha
6 Replies

9. Shell Programming and Scripting

Copying files

All, I need to grab and rename common files from several unique directory structures. For example, the directory structures looks like: /unique_dir/common/common/common/person_name_dir/common_file.txt There are over 90,000 of these text files that I'd like to put in a single directory as... (5 Replies)
Discussion started by: hburnswell
5 Replies

10. Shell Programming and Scripting

Copying files

I'm trying to do this exact same thing, so far I have created this to move files i've named my script CP.sh #!/bin/bash cd /root/my-documents/NewDir/ for f in *.doc do cp -v $f root/my-documents/NewDir $f{%.doc} done When i go to run this in the console i type, bin/sh/ CP.sh but it... (7 Replies)
Discussion started by: MKTM_93_SIMP
7 Replies
lifcp(1)						      General Commands Manual							  lifcp(1)

NAME
lifcp - copy to or from LIF files SYNOPSIS
xxx] xxx] xxx] xxx] file1 file2 xxx] xxx] xxx] xxx] [file1 file2 ...] directory DESCRIPTION
copies a LIF file to an HP-UX file, an HP-UX file to a LIF file, or a LIF file to another LIF file. It also copies a list of (HP-UX/LIF) files to a (LIF/HP-UX) directory. The last name on the argument list is the destination file or directory. Options The space between option and argument is optional. Used only when copying files to a LIF volume. This option forces the file type of the LIF directory entry to be set to the argument given. The argument can be decimal, octal or hex, using standard C notation. Used only when copying files to a LIF volume. This option will set the "last volume flag" to xxx (0 or 1). The default "last volume flag" is Used only when copying files to a LIF volume. This option sets the "volume number" to xxx. The default "volume number" is one. This option forces a ASCII mode of copying regardless of the file type. When copying in ASCII mode from HP-UX to LIF the default file type is BINARY (1). (For details on available modes of copying refer to lif(4)). This option has no effect when copying from LIF to LIF. This option forces a BINARY mode of copying regardless of the file type. When copying in BINARY mode from HP-UX to LIF the default file type is BINARY (-2). (For details on available modes of copying refer to lif(4)). This option has no effect when copying from LIF to LIF. Used only when copying files to a LIF volume. This option sets the "implementation" field of the LIF directory entry to the argument given. The argument value can be decimal, octal or hex, using standard C notation. The "implementation" field can only be set for file types -2001 to -100000 (octal). The "implementation" field is set to zero for all interchange file types and for file types -2 to -200 (octal). Note that the "implementation" value controls the attributes of the LIF file with regard to protection and record sizes. or can be used to determine the "implementation" value of a file. Forces RAW mode copying regardless of file type. When copying in RAW mode from HP-UX to LIF the default file type is BIN (-23951). option overrides the default file type. (various modes of copying are explained in lif(4).) The option has no effect in LIF to LIF copy operations. causes HP-UX file names to be translated to a name acceptable by a LIF utility; that is, all lowercase letters are converted to uppercase and all other characters except numerics are changed to an underscore If the HP-UX file name starts with a nonletter, the file name is preceded by the capital letter Thus, for example, if two files named colon and semicolon were copied, both of them would be translated to File names are truncated to a maximum of 10 characters. When copying a LIF file to an HP-UX or LIF file, has no effect. Omitting causes an error to be generated if an improper name is used. The default copying modes when copying from LIF to HP-UX are summarized in the following table: | File Type | Default Copying Mode ----------+---------------------- ASCII | ASCII BINARY | BINARY BIN | RAW other | RAW When copying from HP-UX to LIF, the default copying mode is ASCII and an ASCII file is created. When copying from LIF to LIF, if no options are specified, then all the LIF directory fields and file contents are duplicated from source to destination. A LIF file name is recognized by the embedded colon delimiter (see lif(4) for LIF file naming conventions). A LIF directory is recognized by a trailing colon. If an HP-UX file name containing a colon is used, the colon must be escaped with two backslash characters (the shell removes one of them). The file name (dash) is interpreted to mean standard input or standard output, depending on its position in the argument list. This is particularly useful if the data requires nonstandard translation. When copying from standard input, if no other name can be found, the name "STDIN" is used. LIF file naming conventions are known only to the LIF utilities. Since file name expansion is done by the shell, this mechanism cannot be used for expanding LIF file names. Do not mount the special file while using DIAGNOSTICS
returns exit code 0 if the file is copied successfully. Otherwise it prints a diagnostic and returns nonzero. EXAMPLES
Copy HP-UX file to LIF file on LIF volume which is actually an HP-UX file initialized to be a LIF volume: Copy all the HP-UX files in the current directory to the LIF volume which is present in the parent directory. File names are translated to appropriate LIF file names. Copy all the HP-UX object files in the current directory to the LIF volume lifvol. Copying mode is RAW and LIF file types are set to -5555. Copy all the object files in the current directory to the LIF volume Copying mode is BINARY and LIF BINARY files are created. Copy a BDAT file, without a password, from a BASIC WorkStation to an HP-UX LIF volume Note that controls protection and record size attributes. The file type for a BDAT file is -5791 (or 0xffffe961) and its record size is 256 bytes per record. Copy all files in the current directory to the LIF volume in the directory. Copying mode is RAW and LIF file types are set to BIN. Copy file to LIF file in Copy files and to LIF files and within Copy LIF file within to file within current directory. Copy standard input to LIF file on LIF volume Copy LIF file in to LIF file on Copy the output of pr to the LIF file Copy the output of pr to the LIF volume LIF file is created since no file names are specified. Copy LIF file in to standard output. Copy all files in current directory to LIF files of the same name on LIF volume (may cause errors if file names in the current directory do not obey LIF naming conventions!). DEPENDENCIES
Series 700/800 The following option is also supported: forces each file copied in to begin on an nnn x 1024-byte boundary from the beginning of the volume. This is useful when files are used for Series 700/800 boot media. This option has no effect when copying from a LIF volume. AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
lifinit(1), lifls(1), lifrename(1), lifrm(1), lif(4). lifcp(1)
All times are GMT -4. The time now is 03:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy