07-04-2008
03 is newer then 01. so if you've problems that can be fixed with a newer version of the patch you have to add the new one...
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Does anyone know how can I verify if the DST update on a SCO Unixware system has been installed successfully? UNIXWARE 7.1.4 MP3
Looking forward to some help, please....
Thanks (8 Replies)
Discussion started by: Yorgy
8 Replies
2. Solaris
Hi All,
I need to update my solaris with a particular patch. When reading the instruction on the sun web site, I got this:
Installation Requirements:
Reboot immediately after installing this patch on an active boot environment to bring the system to a consistent state. An alternative may... (8 Replies)
Discussion started by: itik
8 Replies
3. Solaris
Hi All,
How do you know if you need to break the mirror on solaris 8 patch update?
Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical.
Is breaking a mirror a best practice only or really a requirement to some patch?
Thanks,
itik (1 Reply)
Discussion started by: itik
1 Replies
4. Solaris
Hi All,
How do I execute patch update on a single user mode?
Please give me the steps by step procedures?
Is single user mode the same as run level 1?
Thanks. (2 Replies)
Discussion started by: itik
2 Replies
5. Linux
Hi All,
I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm.
When I run this
# rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm
warning: user brewbuilder does not exist - using root
warning: group brewbuilder does not exist - using root
warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
2 Replies
6. High Performance Computing
hi all,
can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic.
it doesn't need to be detail, just give me the steps like:
login to the backup node and update the... (0 Replies)
Discussion started by: itik
0 Replies
7. Solaris
Hi, I was troubleshooting H/W issue on a Ultra 5 workstation, whereby the system kept rebooting. In the course of isolating the issue, I patched the system with the latest Recommended cluster patch for solaris 7. SInce then, sendmail is not working and am getting the following errors. Kindly check... (6 Replies)
Discussion started by: incredible
6 Replies
8. Solaris
Hi All
I had update the solaris version, and now wish to update the patch.
but when i check my patch version, i cant find any version for that.
any idea?
root@leo # showrev
Hostname: leo
Hostid: 839b58a3
Release: 5.10
Kernel architecture: sun4u
Application architecture: sparc... (8 Replies)
Discussion started by: SmartAntz
8 Replies
9. Solaris
Solaris 10 10/09 (Update 8) Patch upgrade can be done in single user mode? any suggestions.. thanks (2 Replies)
Discussion started by: chandravadrevu
2 Replies
LEARN ABOUT DEBIAN
stg-push
STG-PUSH(1) StGit Manual STG-PUSH(1)
NAME
stg-push - Push one or more patches onto the stack
SYNOPSIS
stg push [options] [<patch1>] [<patch2>] [<patch3>..<patch4>]
DESCRIPTION
Push one or more patches (defaulting to the first unapplied one) onto the stack. The push operation allows patch reordering by commuting
them with the three-way merge algorithm. If there are conflicts while pushing a patch, those conflicts are written to the work tree, and
the command halts. Conflicts raised during the push operation have to be fixed and the git add --update command run (alternatively, you may
undo the conflicting push with stg undo).
The command also notifies when the patch becomes empty (fully merged upstream) or is modified (three-way merged) by the push operation.
OPTIONS
-a, --all
Push all the unapplied patches.
-n NUMBER, --number NUMBER
Push the specified number of patches.
--reverse
Push the patches in reverse order.
--set-tree
Push the patches, but don't perform a merge. Instead, the resulting tree will be identical to the tree that the patch previously
created.
This can be useful when splitting a patch by first popping the patch and creating a new patch with some of the changes. Pushing the
original patch with --set-tree will avoid conflicts and only the remaining changes will be in the patch.
-k, --keep
Keep the local changes.
-m, --merged
Check for patches merged upstream.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-PUSH(1)