10-30-2003
Upgrading AIX Unix
Hi all,
I've got a question about an OS upgrade.
I'm planning to do a upgrade from AIX UNIX 4.3.2 to 4.3.3 in a few weeks.
I haven't got that much information.
Could someone give me some general tips or hints, things I should think of before? Things I should know, or general errors.
I know this question is a bit weird maybe,
But any tips or hints are welcome,
Thanks in advance!
Erik
10 More Discussions You Might Find Interesting
1. HP-UX
Right now we are using HP-UX 11i
We are thinking of upgrading to 11i v3..
Questions:
Why would we want to upgrade? Benefits?
Do we need to install v2 and then v3 or can we just go straight to v3?
I see we can get the following:
HP-UX 11i v3 Operating Environment and applications... (10 Replies)
Discussion started by: nixie21
10 Replies
2. AIX
Hi All,
We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment...
how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies
3. AIX
Hi,
I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup.
Please suggest
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. Programming
Hi, I have got java 1.4.1 in my unix server, i wish to upgrade it to 1.4.2 version. I know how to do that in Windows, but it is the first time i am doing it in UNIX. Please tell me how to do it from command line?
Are there any environment variable to be set in unix as in windows?
Thanks in... (0 Replies)
Discussion started by: macmohanin
0 Replies
5. AIX
We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC.
Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers.
My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies
6. Hardware
I have an old Unisys U6000/65 server I obtained as surplus about 12 years ago. For its day (1993) this server line was capable of insane ability, up to 4 gig of memory using dozens of 30-pin SIMMs and up to six processors, including mixed processor speeds and types (486/Pentium) in the same... (2 Replies)
Discussion started by: DMahalko
2 Replies
7. AIX
Hey guys,
since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap.
Any experience on upgrading directly to 7.1, with sap/db2/oracle?
could do fresh installs and import my sap/db vgs, but this would be a lot of work
cheers Funksen (4 Replies)
Discussion started by: funksen
4 Replies
8. AIX
Hello,
I am trying to update Samba on my AIX 7.1 system as there is an issues with it, the smbd process coredumps and I have had no luck figuring it out why.
My approach is to try to re-install a newer samba and I have found the latest 3.x package for samba in ppc.rpm format at perlz.org
... (6 Replies)
Discussion started by: c3rb3rus
6 Replies
9. AIX
Hi Folks,
Currently we are having the below configuration in one of our AIX 6.1 server.
RAM:- 8 GB
Paging space :- 19 GB
CPU processor:- 1
CPU type: 64 bit
But we would like to upgrade the configuration to below to improve the system performance and resolve some memory issues.
... (11 Replies)
Discussion started by: sumanmca2006
11 Replies
10. AIX
Hi all,
I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies
LEARN ABOUT LINUX
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 in a (sub)directory 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 storing the refs in a single file, $GIT_DIR/packed-refs. When a ref is
missing from the traditional $GIT_DIR/refs directory hierarchy, it is looked up in this file and used if found.
Subsequent updates to branches always create new files under $GIT_DIR/refs directory hierarchy.
A recommended practice to deal with a repository with too many refs is to pack its refs with --all once, and occasionally run git
pack-refs. 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.
BUGS
Older documentation written before the packed-refs mechanism was introduced may still say things like ".git/refs/heads/<branch> file
exists" when it means "branch <branch> exists".
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-PACK-REFS(1)