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)
Hi I am a FreeBSD user
Just want to know is it possible to recompile kernel or any other userland in Solaris 10 or OpenSolaris?
I want check out this UNIX OS which has Flash 9 support :D (2 Replies)
Salamo Alikom after recompilation my kernel does not boot and display msg said : enter full path to bash : /bin/sh i try fsck -r ,fsck -y but the problem is steel . my make.conf : PERL_VER=5.8.8 OVERRIDE_LINUX_BASE_PORT=f8 PERL_VERSION=5.8.8 MODULES_OVERRIDE = linux acpi accf_http pccard msdosfs... (1 Reply)
Hi,
As in the solaris material i know that the patch is added through the command "patchadd <patch no.>".
But i need to know, what are all the steps we have to follow while applying a patch in a production server. My friend says that we have to detach mirror before applying patch and not... (6 Replies)
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Hi, all:
The vmlinuz-3.0.4.old is a kernel previous to the current running kernel vmlinuz-3.0.4 which is compiled the most currently. Could I get the initrd.img-3.0.4.old without recompile under the condition that the config-3.0.4.old, System.map-3.0.4.old and vmlinuz-3.0.4.old exist? if it... (1 Reply)
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Hello everybody, I have downloaded kernel version 3.10.21
and the same version of patch. the question is do I need to apply this patch which is the same version of kernel or is it intended for lower versions of kernel. thanks a lot (1 Reply)
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
LEARN ABOUT XFREE86
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)