Sponsored Content
Operating Systems Solaris 10 Recommended Patch Not Working Post 302414527 by incredible on Tuesday 20th of April 2010 10:23:20 AM
Old 04-20-2010
A quick question.. are the majority of the patches succeeded including the kernel patch?
If yes, then ignore it. You may just try to copy the patch to a temp dir, and manually do a patchadd. Provide us the output
 

8 More Discussions You Might Find Interesting

1. Solaris

after patch, telnet not working

The problem: I installed the Solaris 8 recommended patch cluster 117350-11 over 108528-15 before the Christmas break. The server is a SunFire V100. Here is the situation: Before the patch install, there was a working cron job that did daily, weekly, and monthly backups of the V100 filesystems... (3 Replies)
Discussion started by: antalexi
3 Replies

2. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

3. Solaris

Issue while installing: Solaris 10 SPARC Recommended Patch Cluster (2009.10.23)

Hello, As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23). Actually, patch no 120011-14 stops with the following error: ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed file type <f>... (6 Replies)
Discussion started by: a.mauger
6 Replies

4. Solaris

Applying Recommended Patch Cluster to Whole Root Zone

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

5. Solaris

Jumpstart and Applying Recommended Patch Cluster

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

Recommended Patch Cluster Using ZFS Snapshots

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

Recommended patchset for Solaris and the patch bundle

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

Oracle stopped updating Solaris 10 recommended patch cluster ?

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
STG-UNCOMMIT(1) 						   StGit Manual 						   STG-UNCOMMIT(1)

NAME
stg-uncommit - Turn regular git commits into StGit patches SYNOPSIS
stg uncommit <patch-name-1> [<patch-name-2> ...] stg uncommit -n NUM [<prefix>] stg uncommit -t <committish> [-x] DESCRIPTION
Take one or more git commits at the base of the current stack and turn them into StGIT patches. The new patches are created as applied patches at the bottom of the stack. This is the opposite of stg commit. By default, the number of patches to uncommit is determined by the number of patch names provided on the command line. First name is used for the first patch to uncommit, i.e. for the newest patch. The -n/--number option specifies the number of patches to uncommit. In this case, at most one patch name may be specified. It is used as prefix to which the patch number is appended. If no patch names are provided on the command line, StGIT automatically generates them based on the first line of the patch description. The -t/--to option specifies that all commits up to and including the given commit should be uncommitted. Only commits with exactly one parent can be uncommitted; in other words, you can't uncommit a merge. OPTIONS
-n NUMBER, --number NUMBER Uncommit the specified number of commits. -t TO, --to TO Uncommit to the specified commit. -x, --exclusive Exclude the commit specified by the --to option. STGIT
Part of the StGit suite - see linkman:stg[1] StGit 03/13/2012 STG-UNCOMMIT(1)
All times are GMT -4. The time now is 07:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy