07-02-2010
We were not able to make it work and therefore have to rollback the operation.
Thanks for the tips, I'll keep that in mind next time we'll have to work on this.
Regards.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Rebooting with command: boot cdrom -s
Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f File and args: -s
Evaluating: boot cdrom -s
Can't open boot device
If any one knows please advise.
I have changed the CDrom but it did not help. (1 Reply)
Discussion started by: ark
1 Replies
2. Solaris
IS the cluster_patch for Solaris 5.9 free to download from Sun web site, i just can't find it, please help?
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
3. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
4. Solaris
Hi,
One of the pre requirements o upgrade Netbackup 6.5.4 to 7.1 is to apply Patch 119963-21 to all media servers.
My media servers are Oracle Databases ( e-business suite and for other 3rd party app ).
I read the Patch 119963-21's README and there is no Install Requirements for this... (10 Replies)
Discussion started by: HishamN
10 Replies
5. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
6. Solaris
I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here:
Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot
The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies
7. Solaris
Hello
I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC.
Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes.
I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies
8. Solaris
Dear All,
Has Oracle stopped updating Solaris 10 recommended patch cluster ? From suport.oracle.com i could see the last patch bundle was released on 11th july and there has been no updates after that.
Does anyone know about any official announcement from oracle on this ?
Thanks ... (1 Reply)
Discussion started by: abhi_8029
1 Replies
9. Solaris
Hi Guys,
I'm looking to download the latest patche cluster, we install them on a monthly basis.
I have not seen anything released in the last couple months since January.
Did I miss an announcement?
Are they going to start releasing quarterly?
Or is it just so happening there are no... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
10. Solaris
Hi,
I installed Solaris 10 recommended patch cluster (patch bundle of 400+ patches). After reboot global zone is fine, but a lot of services was in uninitialized state. I had to run /lib/svc/bin/restore_repository and then services came online.
Now I can't login to server with NIS account... (1 Reply)
Discussion started by: ron323232
1 Replies
LEARN ABOUT SUSE
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.
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]>
GIT
Part of the git(1) suite
NOTES
1. torvalds@osdl.org
mailto:torvalds@osdl.org
Git 1.7.1 07/05/2010 GIT-PACK-REFS(1)