Patch Clusters and Patch Bundles are popular collections of patches providing specific functionality. They contain an install script for ease of installation. Patch Clusters and Patch Bundles are provided for the Solaris OS; Solaris, shared component, and middleware patches for Java Enterprise System; and Solaris patches recommended for J2SE.
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)
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)
I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
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)
Hi Admins,
I came across an error while installing patch cluster on solaris.
# ./installcluster --s10cluster
ERROR: Another instance of an install script is already running for target
boot
environment '/'.
I did killed the related processes. Now there is no any process running from ps... (1 Reply)
:mad: :mad: Hello,
Could some help me to resolve why i am geting the below errors... :(
Just tried installing patch bundle on solairs 10.
many patches are been failed. wen i am trying to install it manualy i am geting the below errors..
... (8 Replies)
What if ,all of my patches in solaris10 05/08 there are not find following:
118731-01 122660-10 119254-59 138217-01 .... about 30
How i can fill up 30 patches? Do command patchadd separetely for everyone? Or make all patch cluster in S mode? Do it in global? I must stop zones befor patchadd... (0 Replies)
Does anyone have an alternate site to download J2SE Solaris Recommended Patch Cluster for Solaris 8. Sun does not let me download the patches unless I have a support contract. I do not. Our software is legal, but our support contract wore out. I need this patchset to avoid downloading 30... (6 Replies)
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)
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)
