Sponsored Content
Full Discussion: Migrating from HP to Solaris
Top Forums UNIX for Dummies Questions & Answers Migrating from HP to Solaris Post 89869 by jkuchar747 on Wednesday 16th of November 2005 01:01:46 PM
Old 11-16-2005
Migrating from HP to Solaris

My company is considering migrating from HP unix to Solaris just to get two more years of support for a particular software product. My question is just how much of an effort is it to do this migration? Are you aware of any migration tools to assist us in this migration? Thanks
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Migrating Solaris 9 to different hardware

Hi, I am new to this forum and hope someone can help. Does anyone know how to restore a Solaris 9 backup tape from server A to a completely different server B hardware. Both boxes are sun 64bit. Your help is much appreciated. Thank you Jan. (5 Replies)
Discussion started by: snerta
5 Replies

2. AIX

migrating solaris DB servers to AIX - resources ?

Hi Guys, I have a new project where I have to migrate about 150+ database environments from various solaris systems running Solaris 8 / 10 and residing on very different sun boxes (from 25k down to ancient/unsupported hardware) to AIX (power6). As special bonus for me, about half of these DBs... (1 Reply)
Discussion started by: zxmaus
1 Replies

3. HP-UX

Migrating from HP UX to LINUX/SOLARIS- which one is more preferable?

Hi all, We have an application that is running on HP-UX operating system (11i). the application is built using C, C++, ProC and ProC++ codes. we have been given two choices for migration: LINUX and SOLARIS. I would like to know the differences between the three OS and which OS to prefer... (3 Replies)
Discussion started by: pb0069950
3 Replies

4. Solaris

Migrating Solaris 8, 9 to Guest Domains (LDOMs)

Hi Everyone, one question is it possible to migrate a physical standalone Solaris 8 or 9 OS to Guest Domain (LDOMs). If yes, can someone please provide steps to migrate these OS to LDOMs. Thanks, Kartheek. (1 Reply)
Discussion started by: bobby320
1 Replies

5. Shell Programming and Scripting

Migrating Oracle on Solaris Sparc to Linux RHEL 7 VM

Hi Gurus, We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux. we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris.. Could you please help me here by proving any info... (1 Reply)
Discussion started by: mssprince
1 Replies

6. Red Hat

Migrating Oracle on Solaris Sparc to Linux RHEL 7 VM

Hi Gurus, We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux. we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris.. Could you please help me here by proving any info ... (4 Replies)
Discussion started by: mssprince
4 Replies
DH_STRIP(1)							     Debhelper							       DH_STRIP(1)

NAME
dh_strip - strip executables, shared libraries, and some static libraries SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug] DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for debugging. This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a, debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good guesses, and will do the right thing in almost all cases. Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not currently deal with stripping binary modules such as .o files. OPTIONS
-Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a list of things to exclude. --dbg-package=package This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the specified debugging package. For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip --dbg-package=foo-dbg. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym or --dbgsym-migration. -k, --keep-debug This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is easier to use than this option, but this option is more flexible. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym. --dbgsym-migration=package-relation This option is used to migrate from a manual "-dbg" package (created with --dbg-package) to an automatic generated debug symbol package. This option should describe a valid Replaces- and Breaks-relation, which will be added to the debug symbol package to avoid file conflicts with the (now obsolete) -dbg package. This option implies --automatic-dbgsym and cannot be used with --keep-debug, --dbg-package or --no-automatic-dbgsym. Examples: dh_strip --dbgsym-migration='libfoo-dbg (<< 2.1-3~)' dh_strip --dbgsym-migration='libfoo-tools-dbg (<< 2.1-3~), libfoo2-dbg (<< 2.1-3~)' --automatic-dbgsym, --no-automatic-dbgsym Control whether dh_strip should be creating debug symbol packages when possible. The default is to create debug symbol packages. --ddebs, --no-ddebs Historical name for --automatic-dbgsym and --no-automatic-dbgsym. --ddeb-migration=package-relation Historical name for --dbgsym-migration. NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1 "Binaries"). This will also inhibit the automatic creation of debug symbol packages. The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible). CONFORMS TO
Debian policy, version 3.0.1 SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_STRIP(1)
All times are GMT -4. The time now is 09:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy