Sponsored Content
Operating Systems Linux Red Hat Command to know the Patch Version Post 302344050 by fpmurphy on Friday 14th of August 2009 12:20:13 PM
Old 08-14-2009
This will list all the installed packages by date of installation.
Code:
rpm -q -a --list

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

command to get the AIX version.

and by the is there any command to get the OS currently running regardless of the constructor (HP, IBM...)? thanks! (3 Replies)
Discussion started by: jericho
3 Replies

2. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

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)
Discussion started by: Rakesh Ranjan
0 Replies

3. Solaris

How to disply the patch version ?!

Hi , I need to collect all information about the patches in my server , I want to know what is the required patch and how to apply it. Regards (2 Replies)
Discussion started by: ArabOracle.com
2 Replies

4. Solaris

command to know ssh version

Hi, I want to know the command to know ssh version on solaris (1 Reply)
Discussion started by: manoj.solaris
1 Replies

5. Solaris

How can i see kernel patch version?

Hello experts. How can i see kernel patch version? what are advantages applying that patch? Thanx in advance (5 Replies)
Discussion started by: younus_syed
5 Replies

6. Linux

OS Patch level command

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

7. Shell Programming and Scripting

Patch command help

Hello All, I have a patch file which contains following types of lines - @@ -617,14 +617,8 @@ What does they signify ? (1 Reply)
Discussion started by: paragkalra
1 Replies

8. UNIX for Dummies Questions & Answers

Unix command help version 2.0

Having trouble doing the following things, I know it has something to do with using metacharacters but I'm not able to get it working correctly. I need a command to get a long directory listing of all the files that have: exactly two characters following the letters zot. all files that... (1 Reply)
Discussion started by: lakers34kb
1 Replies

9. Debian

Applying patch for Samba version 4.1.17

The version of Samba in our billing server is 4.1.17-Debian. I have been reminded by our management to implement the patch for Samba on this server. However, I am not sure how to implement the patch. I have browsed some websites for the correct patch to implement for Samba 4.1.17, and the patch... (11 Replies)
Discussion started by: anaigini45
11 Replies
SHAPE_PATCH(1)						      General Commands Manual						    SHAPE_PATCH(1)

NAME
shape_patch - shapeTools RMS generate patch file SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>] DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape patch from the top node of the central source repository creates a patch file for the whole system. The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH- FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output. Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure will leave an equally named patch file for each visited subsystem. The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1). INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit. SEE ALSO
shape_releas(1), vdiff(1), patch(1) FILES
<name1>+2+<name2>.pat 20.7.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 10:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy