07-02-2010
Quote:
Originally Posted by
incredible
The only way I have been able to fix the systems
Did they have Tivoli access manager installed ?
Quote:
is to boot in failsafe mode and then apply the new kernel again with patchadd -n -R /a patchid.
I guess you mean "apply the new kernel patch".
Quote:
Look at the README for this patch and see if it gives advice on the workaround.
I don't expect any workaround in the patch documentation as the system as it is is unsupported. Looking at TAM documentation would be a better way to figure out how to handle the situation.
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 OSX
svk::command::patch
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)