06-11-2008
Solaris migration
Hi ,
There is going to be a server migration from Solaris 8.0 to Solaris10.0.
Could anyone give me some tips and documents regarding the steps to be remembered,tips to be followed etc.
like
syntax differences
any new changes to the existing commands and tools we use
whatever the document which is helpful in this scenario
cheers
mohan
10 More Discussions You Might Find Interesting
1. Solaris
Hi, it is necessary to make the migration of Solaris 5.8 for Solaris 10, would like to know which the best form to execute this task, if to be able to say me where I can arrange some manual that helps me to make this task. Thanks :o (2 Replies)
Discussion started by: bruno_a_correia
2 Replies
2. HP-UX
Hi eveyone
Ours is an application hosted on HP-UX 11 and we are trying to migrate the server to different flavour of UNIX. We are actually looking at the option of migrating it to Sun Solaris or Linux.
We are trying to evaulate the pros and cons of migrating our application to Solaris/Linux.... (6 Replies)
Discussion started by: turaga.krishna
6 Replies
3. Solaris
Hello,
We have upgraded our system from SunOS 5.8 to Solaris 10.
I would like to know if the applications (written in c, c++, pro*c, java,..) running on the 5.8 can run on the Solaris 10 without code modification or the need to be recompiled ?
thanks you for your help. (4 Replies)
Discussion started by: Jidma
4 Replies
4. Solaris
Hello folks,
I'm currently working on migration of printing system from one server to another (namely from Sol 9 to Sol 10).
I would like ask if is possible to manage migration via simple copying /etc/printers.conf file and folder /etc/lp to the new server??? I'm not sure if printers... (2 Replies)
Discussion started by: brusell
2 Replies
5. Solaris
HI,
let me explain you the current situation.
We have three server with OS Solaris and oracle products. Following is the somewhat detail,
1st Server= oracle DB
2nd Server= Oracle Warehouse builder
3rd Server= Oracle Business Intelligence Enterprise Manager
Question: these three... (0 Replies)
Discussion started by: malikshahid85
0 Replies
6. Solaris
Hi All,
We are planing to do a migration of our server from AIX 5.3 to Solaris (Linux). But we are not aware about the gap between the both and also impact of that gap. We want to migrate following things,
- Common directories setup (like control-M, emer,sysout, and others)
- Inbound &... (1 Reply)
Discussion started by: vinod369
1 Replies
7. Linux
Hi,
Currently I can able to access php script from solaris. I want to access from Linux
I have done the following things:
1) I have copied all the scripts from solaris to linux.
2) I have installed php,mysql,apache.
I tried with http://Hostname/username/test.php . This is not working .... (6 Replies)
Discussion started by: Mani_apr08
6 Replies
8. Solaris
Hello Admins...
How can we migrate a solaris 10 zone which is clustered...??
We have sun cluster 3.2 in our environment. And this is 2 -node cluster
Let me know guys...
Thanks. (0 Replies)
Discussion started by: snchaudhari2
0 Replies
9. Solaris
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Discussion started by: amity
2 Replies
10. Solaris
We are going to work on a project which aims at migrating set of applications from AIX to Solaris. The major portion of the source code involves C, C++, Shell/PERL scripts and Oracle database. We are grateful hear about any commercial tools available for porting AIX to Solaris. Another... (2 Replies)
Discussion started by: Namitap
2 Replies
LEARN ABOUT DEBIAN
git-pack-refs
GIT-PACK-REFS(1) Git Manual GIT-PACK-REFS(1)
NAME
git-pack-refs - Pack heads and tags for efficient repository access
SYNOPSIS
git pack-refs [--all] [--no-prune]
DESCRIPTION
Traditionally, tips of branches and tags (collectively known as refs) were stored one file per ref under $GIT_DIR/refs directory. While
many branch tips tend to be updated often, most tags and some branch tips are never updated. When a repository has hundreds or thousands of
tags, this one-file-per-ref format both wastes storage and hurts performance.
This command is used to solve the storage and performance problem by stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref
is missing from the traditional $GIT_DIR/refs hierarchy, it is looked up in this file and used if found.
Subsequent updates to branches always create new files under $GIT_DIR/refs hierarchy.
A recommended practice to deal with a repository with too many refs is to pack its refs with --all --prune once, and occasionally run git
pack-refs --prune. Tags are by definition stationary and are not expected to change. Branch heads will be packed with the initial pack-refs
--all, but only the currently active branch heads will become unpacked, and the next pack-refs (without --all) will leave them unpacked.
OPTIONS
--all
The command by default packs all tags and refs that are already packed, and leaves other refs alone. This is because branches are
expected to be actively developed and packing their tips does not help performance. This option causes branch tips to be packed as
well. Useful for a repository with many branches of historical interests.
--no-prune
The command usually removes loose refs under $GIT_DIR/refs hierarchy after packing them. This option tells it not to.
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-PACK-REFS(1)