Hi all
I wanted to know does solaris 11 have any place to download patch cross-reference file like solaris 10 (h t t p s://getupdates.oracle.com/reports/patchdiag.xref)? I wanted to use this file to filter out those security patches and use it to check if any of my solaris 11 systems are... (0 Replies)
Hi All,
I have a requirement, where i have to pool file A data to file B continuously and need to process the data in the file B.
Since the data need to be processed only once so i have to truncate the data in file A after every pool. So that on the next pooling i can get the fresh data and... (3 Replies)
I just wanted to understand the timer patch in timer.c.
It has already been merged in linux mainline kernel
It says that
I did not understand how it calcuates expires_limit as 0x20000000e from given value of expires=0xffffe6f5 and slack=25.
Any help will be apreciable.
... (0 Replies)
Hi,
We have a filesystem whose usage has gone above 81%, i tried to zip some files in the sub directories but the space is not released in the main file system.
> df -h
Filesystem size used avail capacity Mounted on
/u01/app 5.8G 4.6G 1.2G 81% ... (2 Replies)
sorry for being a noob, i am trying to find which user accessed the server at what time and there ip address at first i used who command but the output didn't contain the ip address then i used the last command which provided me with the ip of the users but when i searched i searched and found that... (1 Reply)
Hi All,
I have an AIX executable (/usr/bin/shell) in my system.
I want to know if this file was updated by any of the installed fixes/apars on my system.
What is the AIX way of finding this information?
Greetings,
Peter (1 Reply)
Hi there,
files are being transferred via ftp to a folder in my machine which runs solaris 8. I would like to know if is possible to find out from my side if a file is completely transferred or not.
Is there a way to control this?
Thanks! (6 Replies)
I just downloaded a updating make file to build Ethereal to .dll file, but I don't know how to update the old make file with this new one. Please help.. thnx a lot. (1 Reply)
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)
FILTERDIFF(1)FILTERDIFF(1)NAME
filterdiff - extract or exclude diffs from a diff file
SYNOPSIS
filterdiff [-i PATTERN] [-p n] [--strip=n] [--addprefix=PREFIX]
[-x PATTERN] [--verbose] [-v] [-z] [-# RANGE | --hunks=RANGE]
[--lines=RANGE] [--annotate] [--format=FORMAT] [--as-numbered-lines=WHEN]
[file...]
filterdiff {--help | --version | --list | --grep ...}
DESCRIPTION
You can use filterdiff to obtain a patch that applies to files matching the shell wildcard PATTERN from a larger collection of patches. For
example, to see the patches in patch-2.4.3.gz that apply to all files called lp.c:
filterdiff -z -i '*/lp.c' patch-2.4.3.gz
If neither -i nor -x options are given, -i '*' is assumed. To remove lines from a file that are not part of a patch, you might do this:
filterdiff message > patch
Note that the interpretation of the shell wildcard pattern does not count slash characters or periods as special (in other words, no flags
are given to fnmatch). This is so that ``*/basename''-type patterns can be given without limiting the number of pathname components.
You can use both unified and context format diffs with this program.
OPTIONS -i PATTERN
Include only files matching PATTERN. All other lines in the input are suppressed.
-x PATTERN
Exclude files matching PATTERN. All other lines in the input are displayed.
-p n When matching, ignore the first n components of the pathname.
-# RANGE | --hunks=RANGE
Only include hunks within the specified RANGE. Hunks are numbered from 1, and the range is a comma-separated list of numbers or
``first-last'' spans; either the first or the last in the span may be omitted to indicate no limit in that direction.
--lines=RANGE
Only include hunks that contain lines from the original file that lie within the specified RANGE. Lines are numbered from 1, and the
range is a comma-separated list of numbers or ``first-last'' spans; either the first or the last in the span may be omitted to indi-
cate no limit in that direction.
--annotate
Annotate each hunk with the filename and hunk number.
--format=unified|context
Use specified output format.
--strip=n
Remove the first n components of pathnames in the output.
--addprefix=PREFIX
Prefix pathnames in the output by PREFIX.
--as-numbered-lines=before|after
Instead of a patch fragment, display the lines of the selected hunks with the line number of the file before (or after) the patch is
applied, followed by a TAB character and a colon, at the beginning of each line. Each hunk except the first will have a line con-
sisting of ``...'' before it.
-v, --verbose
Always show non-diff lines in the output. By default, non-diff lines are only shown when excluding a filename pattern.
-z Decompress files with extensions .gz and .bz2.
--help Display a short usage message.
--version
Display the version number of filterdiff.
--list Behave like lsdiff(1) instead.
--grep Behave like grepdiff(1) instead.
EXAMPLES
To see all patch hunks that affect the first five lines of a C file:
filterdiff -i '*.c' --lines=-5 < patch
To see the first hunk of each file patch, use:
filterdiff -#1 patchfile
To see patches modifying a ChangeLog file in a subdirectory, use:
filterdiff -p1 Changelog
To see the complete patches for each patch that modifies line 1 of the original file, use:
filterdiff --lines=1 patchfile | lsdiff |
xargs -rn1 filterdiff patchfile -i
To see all but the first hunk of a particular patch, you might use:
filterdiff -p1 -i file.c -#2- foo-patch
If you have a very specific list of hunks in a patch that you want to see, list them:
filterdiff -#1,2,5-8,10,12,27-
To see the lines of the files that would be patched as they will appear after the patch is applied, use:
filterdiff --as-numbered-lines=after patch.file
You can see the same context before the patch is applied with:
filterdiff --as-numbered-lines=before
patch.file
Filterdiff can also be used to convert between unified and context format diffs:
filterdiff -v --format=unified context.diff
SEE ALSO lsdiff(1), grepdiff(1)AUTHOR
Tim Waugh <twaugh@redhat.com>.
patchutils 23 Aug 2002 FILTERDIFF(1)