Sponsored Content
Top Forums Shell Programming and Scripting UNIX file system to Linux file system migration Post 302805821 by jlliagre on Saturday 11th of May 2013 10:56:30 AM
Old 05-11-2013
It would help if you tell what file systems are used on the source and destination machines, what Unix OS is used, and what method you plan to use to perform the copy.

In any case, "du" is the wrong tool to check the proper copy.

If you really want to make sure all the files are copied without any corruption, create a hash/checksum of every file on the source side and use it to check it is correct on the destination one for each file.

You would also need to make sure all (empty) directories are created and possibly decide what to do with files taht are neither plain files nor directories.

Finally, you might also want to check the permissions, owner/group, extended attributes and ACLs if any.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I send a file as an attachment (gzip file) on a Unix system

Hi, How do I send a file as an attachment (gzip file) on a Unix system ? Using sendmail. Please help me. :confused: (3 Replies)
Discussion started by: lacca
3 Replies

2. UNIX for Dummies Questions & Answers

how to mount a file system of a remote machine to local file system

Hi friends, In my case, there are serveral PCs running Linux in a LAN. I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory. I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies

3. Programming

compare XML/flat file with UNIX file system structure

Before i start doing something, I wanted to know whether the approach to compare XML file with UNIX file system structure. I have a pre-configured file(contains a list of paths to executables) and i need to check against the UNIX directory structure. what are the various approches should i use ? I... (6 Replies)
Discussion started by: shafi2all
6 Replies

4. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

5. Programming

Linux file system insight

I have a basic knowledge of the various structures like file, dentry, inode, superblocks of linux virtual file systems. I want to get a more deep insight as to how these structures are utilized in reality. I mean I want to get an understanding of how and where these structure come up in picture... (4 Replies)
Discussion started by: rupeshkp728
4 Replies

6. Infrastructure Monitoring

Nagios: How to read the Linux system file?

hi 2 all i installed nagios in my linux srvr . check_ftp file is in format of system format . i wants to see the syntax for that script how can i read that file .. ??? please help me ! (4 Replies)
Discussion started by: ponmuthu
4 Replies

7. Shell Programming and Scripting

File name on linux system

Hi, One of the customer wants to receive the file with name //CEC821.K003GUK.DOMD(+1) on their linux system. I am using Java application to send the file to remote system, but I am not able to send the file with that name ane even i am not able to create the file with that name on linux system. ... (6 Replies)
Discussion started by: Satyak
6 Replies

8. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies
INSTALL(1)						      General Commands Manual							INSTALL(1)

NAME
install - install files SYNOPSIS
install [-lcszN] [-o owner] [-g group] [-m mode] [-S stack] [file1] file2 install [-lcszN] [-o owner] [-g group] [-m mode] [-S stack] file ... dir install -d [-o owner] [-g group] [-m mode] directory DESCRIPTION
Install puts executables, manual pages, and library files in their proper place in the bin, man, and lib directories. The first two forms of the command are like cp(1) copying either one file to another or copying several files to a directory. The "-d" form is like mkdir(1) with the -p flag. File1 may be omitted if neither -l nor -c is given to change the attributes of file2. Attributes are always copied from the source file, use the options to change. Note that the source file's attributes are changed with the destination file if they are linked. So copy the file if you change it in a way that makes it read-only. You would otherwise not be able to compile a command again. OPTIONS
-l Link the destination to the source file instead of copying it. This is done to either save space on a file system with both the source and the bin directories on it, or to install synonyms to a command. -c Copy the source file to its proper place. This option is the default if -l is not given. With -l, the file is copied if the link fails. -s Strip the destination file of its symbol table, if it is an executable, and if it is actually copied. It has no effect on a link or a non-executable. -z Compress the executable using compress(1) and prepend a header line that calls zexec(1) to decompress and execute the binary. This will on average save 40% disk space at the expense of a slower startup time. Like -s the file must be actually copied for the flag to have effect. -N Use gzip -N to compress the binary. You may see up to 60% space savings, but it will take much longer. N is a digit from 1 to 9 telling the compression effort, see gzip(1). -d Make a directory, usually to install files in a separate directory in a library. Intermediate directories in the path are created with the same attributes as the final directory. Only the attributes of the final directory are set if the directory exists. -o owner Set the owner of the target. This only works if the invoker is the super-user, or if install is run setuid root and the invoker is a member of group zero. If -o is omitted then the ownership is copied from the source file, or set to the id of the invoker if a directory is made. -g group Like -o, but for the group ownership of the target. -m mode Mode is an octal number that specifies the mode the target should get. The default is the source file's mode with a chmod a+rX applied to it, or 755 for a new directory. Implies -o 0, or -g 0 if a file is to be set-uid or set-gid and the invoker has permis- sion to change ownership. This trick allows a group 0 member to install third party software, even though it expects to be installed by root. -S stack Sets the maximum amount of heap + stack that an executable may have when running. The argument is a C-style decimal, octal or hexa- decimal number, optionally followed by the multipliers m, k, w, and b for mega (1024*1024), kilo (1024), "word" (2 or 4), and byte (1). Uppercase M is also accepted for those who know what S.I. means. The compilers use -S 32kw by default, that translates to 64kb for an 8086, and 128kb for other architectures. This option is ignored on a non-executable. SEE ALSO
ln(1), cp(1), strip(1), compress(1), gzip(1), zexec(1), chown(8), chgrp(8), chmod(1), chmem(1), mkdir(1). BUGS
Uppercase K, W, and B are also accepted for those who don't know what S.I. means. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) INSTALL(1)
All times are GMT -4. The time now is 02:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy