07-02-2008
you can check the current patch level by doing uname -a
See if your kernel level is lower of that is shown from
Sun Microsystems
Solaris 8, 9 and 10 have diff latest kernel patch levels.
7 More Discussions You Might Find Interesting
1. Solaris
Hi,
how do you check that the latest service packs/patches are installed on the server, When i look at the OS Modules file, all i see is these numbers like 117176-02 etc, what is currently the latest patch level for sunOS 5.9?
thnaks (1 Reply)
Discussion started by: narik007
1 Replies
2. Solaris
required Solaris 5.10 Kernel patch 137111-03
required Solaris 5.10 Fibre Channel Device Driver patch 125184-08
I want to know about the descriptions and what the patches will do. I searched www.sun.com (patches/updates) but don't see I am looking for. (1 Reply)
Discussion started by: Y4Net
1 Replies
3. Linux
Hi
Do let me know how to find OS Patch 's installed on Linux server ?
Thanks
~ SPai (3 Replies)
Discussion started by: sbanala
3 Replies
4. AIX
Hi,
How to find out patch level in AIX and what patches are installed on AIX box?
As per my knowledge oslevel -s will give service and maintanance level description , but regarding patch level any command is there?
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
5. Solaris
I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies
6. Solaris
how can i know the patch level in solaris 10?
is there a command to know what patchs installed in my solaris?
i mean is there any tool i can run to know that other than pkginfo | more?
i need to make an inventory of all my SUN servers.
i can run explorer in all the machines but unfortunately i... (3 Replies)
Discussion started by: q8devilish
3 Replies
7. Solaris
Hi,
Anyone able to advise on how to find the kernel patch level of an ABE?
showrev and uname -a will provide kernel patch details of the running environment, but how can I run these commands against the ABE or where do these commands get their information from i.e. is the kernel patch level... (3 Replies)
Discussion started by: CiCa
3 Replies
LEARN ABOUT OSX
git-patch-id
GIT-PATCH-ID(1) Git Manual GIT-PATCH-ID(1)
NAME
git-patch-id - Compute unique ID for a patch
SYNOPSIS
git patch-id [--stable | --unstable]
DESCRIPTION
Read a patch from the standard input and compute the patch ID for it.
A "patch ID" is nothing but a sum of SHA-1 of the file diffs associated with a patch, with whitespace and line numbers ignored. As such,
it's "reasonably stable", but at the same time also reasonably unique, i.e., two patches that have the same "patch ID" are almost
guaranteed to be the same thing.
IOW, you can use this thing to look for likely duplicate commits.
When dealing with git diff-tree output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and
outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. This can be used to make
a mapping from patch ID to commit ID.
OPTIONS
--stable
Use a "stable" sum of hashes as the patch ID. With this option:
o Reordering file diffs that make up a patch does not affect the ID. In particular, two patches produced by comparing the same two
trees with two different settings for "-O<orderfile>" result in the same patch ID signature, thereby allowing the computed result
to be used as a key to index some meta-information about the change between the two trees;
o Result is different from the value produced by git 1.9 and older or produced when an "unstable" hash (see --unstable below) is
configured - even when used on a diff output taken without any use of "-O<orderfile>", thereby making existing databases storing
such "unstable" or historical patch-ids unusable.
This is the default if patchid.stable is set to true.
--unstable
Use an "unstable" hash as the patch ID. With this option, the result produced is compatible with the patch-id value produced by git 1.9
and older. Users with pre-existing databases storing patch-ids produced by git 1.9 and older (who do not deal with reordered patches)
may want to use this option.
This is the default.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-PATCH-ID(1)