08-30-2010
backing out of patch which was not installed properly due to H/W failure
Hi All
If suppose I am installing the normal patch or kernal patch and during that time hardware failure occur . Please let me know how can we backup out of patch which was not installed properly. As such I haven't gone through this situation but definately like to know what should be done in this situation
Few inputs from gurus are definately increase our knowledge on this issue.
Regards
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Simple question:
After applying a cluster patch to a sun solaris box I am left with a root volume 81% full. I could run through the hassle of resizing the slices which is way too much work for a Ultra 5 running DNS only.
Is there a way to clean up the /var/sadm/pkg area, aka dump the save info. (5 Replies)
Discussion started by: edkung
5 Replies
2. Solaris
"Solaris 10 is here and so are the latest patches. For a limited time SunSolve will provide access to all Solaris 10 patches. Download the latest Solaris 10 patches using Patchfinder and find updated support content using the SunSolve Knowledgebase. After this promotion ends, Solaris 10 security... (2 Replies)
Discussion started by: busta
2 Replies
3. Solaris
Is there any way to show the patches that have been installed in what order, or by date?
For example, we have servers, we run the sun patch cluster on them every so often. but then we have some 1zee 2zee's which id like to identify.
do i ahve to go into each directory and look at time stamps?... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
4. Solaris
I am seeking help to add patches to Solaris 10 on 64 bit Sparc server. This is to prepare the server for the installation of Oracle 10g. Please list command and specific directory that patches should be added to. Thanks (4 Replies)
Discussion started by: duke0001
4 Replies
5. UNIX for Dummies Questions & Answers
I am seeking help to add patches to Sloris 10 on 64 bit Sparc server. This is to prepare the server for the installation of oracle 10g. Please list command and the directory (If needed). Thanks. (7 Replies)
Discussion started by: duke0001
7 Replies
6. Solaris
Does anyone get the following error message below when trying to download solaris 10 recommended patch?
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and... (8 Replies)
Discussion started by: Sarccastik Dude
8 Replies
7. Solaris
Has anyone ever seen the patch cluster just hang and do nothing?
When I run in debug mode, here is where it hangs...
I tried clearing out my profile, running in different shells, I have no idea whats going on, any help is appreciated...
export/home/unixadm/10_Recommended>ksh -x... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
8. Solaris
Hello all,
I wanted to check in Solaris 10 machine whether it has got all the required patches .
Is there any way to find out.
Rgds
Rj (6 Replies)
Discussion started by: jegaraman
6 Replies
9. Solaris
Can anyone link me to where I can get solaris 10 patches, since now sunsolve.sun.com redirects to some useless oracle support page? (1 Reply)
Discussion started by: goodvikings
1 Replies
10. Solaris
Hi,
From security guy, I was told to install below three patches on Solaris-10 (Sparc) server
120272-31
124393-12
125731-11
Here is output from server -
# showrev -p | grep 120272-31
# showrev -p | grep 120272
Patch: 120011-14 Obsoletes: 116781-02, 117447-01, 117463-05, 118371-10,... (3 Replies)
Discussion started by: solaris_1977
3 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)