Sponsored Content
Full Discussion: Package Installation HELP!
Top Forums UNIX for Advanced & Expert Users Package Installation HELP! Post 302173703 by odys on Friday 7th of March 2008 02:40:39 PM
Old 03-07-2008
Hi,
Not easy situation, seems you need to copy files from B to A.
You can choose 2 ways:
1. remove all files you know about for the package from A and then copy all the files you know about from B to A.
2. try to overwrite the files on A with related old files from B.

I'd say, backup everything and start with 1) and then try 2).

Good luck,
 

10 More Discussions You Might Find Interesting

1. HP-UX

Silent package installation swinstall swask

Hi, I have a question and hoping that someone might already know. I'm trying to do a silent installation on a packages. I generate a set of response files manually. # swask -s /package.depot -c response_files \* I'm able to install the package silently without any issues if I install... (0 Replies)
Discussion started by: mendocino
0 Replies

2. Solaris

Solaris Package Installation

Hi Friends,, I got a doubt about installing packages after the installation of Solaris 10. Suppose if we want to get smc tool by installing some packages from cd-3,, then how can we know the packages that has to be installed to get the smc tool. Can anyone help to solve this small... (1 Reply)
Discussion started by: sdspawankumar
1 Replies

3. Solaris

Problem with solaris 10 installation package

Hi, I want to install man pages package from solaris 10. Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (12 Replies)
Discussion started by: MasterapocA
12 Replies

4. Red Hat

RPM package installation

Hi, can someone help me with this? How do we apply a new version of s/w package without disrupting the processes & daemons running with the old version? Thanks (1 Reply)
Discussion started by: naan
1 Replies

5. Red Hat

Custom package installation using kickstart

Hi there, I've started playing around with Linux a few days back, as part of my intenship. I was wondering if there is anyway I can install custom packages (non RPM packages...say like Oracle) as a part of Kickstart. My machines are running RHEL 4. Thanks a lot :) (1 Reply)
Discussion started by: iman453
1 Replies

6. Red Hat

Remote installation of rpm package (Using YUM)

Hi, I have configured YUM repository on a server and we have 10 linux machine (clients). Is there any way we can install a package on all the 10 machines from YUM repository server? Please help me. (7 Replies)
Discussion started by: uday123
7 Replies

7. Solaris

Package installation dates

Hi All, I have a solaris machine, in which I wanted to find the Oracle Installation date and Solaris Installation date.Any ways of finding out the package installation dates. Kindly let me know Thanks Rj (1 Reply)
Discussion started by: jegaraman
1 Replies

8. Solaris

php package installation problem

can u tell me the procedure to install php 5 using package .. i downloaded php-5.2.1-sol10-x86-local.gz from sunfreeware i have added package using pkgadd -d php-5.2.1-sol10-x86-local then i have added these two lines in httpd.conf LoadModule php5_module modules/libphp5.so... (7 Replies)
Discussion started by: senkerth
7 Replies

9. Fedora

Install RPM package after OS Installation

Hi Guys I want to know whether is it possible to automatically Install a RPM package after installing OS. Basically we have have one rpm package which we want to install as part of OS installation . Please Suggest (3 Replies)
Discussion started by: mr_deb
3 Replies

10. Solaris

Package installation in Solaris 11

I have Solaris-11 and installed few non global zones inside it. I saw many of the packages are not installed in non global zone after installing it. root@pos_ddr01 # pkg list | wc -l 479 root@pos_ddr01 # root@pos_ddr01-zkmq01:~# pkg list | wc -l 206 root@pos_ddr01-zkmq01:~# I can... (1 Reply)
Discussion started by: solaris_1977
1 Replies
CP(1)								   User Commands							     CP(1)

NAME
cp - copy files and directories SYNOPSIS
cp [OPTION]... [-T] SOURCE DEST cp [OPTION]... SOURCE... DIRECTORY cp [OPTION]... -t DIRECTORY SOURCE... DESCRIPTION
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY. Mandatory arguments to long options are mandatory for short options too. -a, --archive same as -dR --preserve=all --attributes-only don't copy the file data, just the attributes --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument --copy-contents copy contents of special files when recursive -d same as --no-dereference --preserve=links -f, --force if an existing destination file cannot be opened, remove it and try again (this option is ignored when the -n option is also used) -i, --interactive prompt before overwrite (overrides a previous -n option) -H follow command-line symbolic links in SOURCE -l, --link hard link files instead of copying -L, --dereference always follow symbolic links in SOURCE -n, --no-clobber do not overwrite an existing file (overrides a previous -i option) -P, --no-dereference never follow symbolic links in SOURCE -p same as --preserve=mode,ownership,timestamps --preserve[=ATTR_LIST] preserve the specified attributes (default: mode,ownership,timestamps), if possible additional attributes: context, links, xattr, all --no-preserve=ATTR_LIST don't preserve the specified attributes --parents use full source file name under DIRECTORY -R, -r, --recursive copy directories recursively --reflink[=WHEN] control clone/CoW copies. See below --remove-destination remove each existing destination file before attempting to open it (contrast with --force) --sparse=WHEN control creation of sparse files. See below --strip-trailing-slashes remove any trailing slashes from each SOURCE argument -s, --symbolic-link make symbolic links instead of copying -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY copy all SOURCE arguments into DIRECTORY -T, --no-target-directory treat DEST as a normal file -u, --update copy only when the SOURCE file is newer than the destination file or when the destination file is missing -v, --verbose explain what is being done -x, --one-file-system stay on this file system -Z set SELinux security context of destination file to default type --context[=CTX] like -Z, or if CTX is specified then set the SELinux or SMACK security context to CTX --help display this help and exit --version output version information and exit By default, sparse SOURCE files are detected by a crude heuristic and the corresponding DEST file is made sparse as well. That is the behavior selected by --sparse=auto. Specify --sparse=always to create a sparse DEST file whenever the SOURCE file contains a long enough sequence of zero bytes. Use --sparse=never to inhibit creation of sparse files. When --reflink[=always] is specified, perform a lightweight copy, where the data blocks are copied only when modified. If this is not pos- sible the copy fails, or if --reflink=auto is specified, fall back to a standard copy. The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the values: none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups As a special case, cp makes a backup of SOURCE when the force and backup options are given and SOURCE and DEST are the same name for an existing, regular file. AUTHOR
Written by Torbjorn Granlund, David MacKenzie, and Jim Meyering. REPORTING BUGS
GNU coreutils online help: <http://www.gnu.org/software/coreutils/> Report cp translation bugs to <http://translationproject.org/team/> COPYRIGHT
Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
Full documentation at: <http://www.gnu.org/software/coreutils/cp> or available locally via: info '(coreutils) cp invocation' GNU coreutils 8.28 January 2018 CP(1)
All times are GMT -4. The time now is 02:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy