you can check the dependancy libraries which can distinguish the binaries
If their versions match that of the current version of the libs.
apparently you can check out the external libs they are using another way too.
The binary file alone cannot give you the information about which version of gcc was used to build it.
If there is a difference b/w the kernel version they are using then you can check the binaries that are made for 2.4 or 2.6 . I suppose redhat-6.2 uses 2.4 while rhel uses 2.6.18.
example :
So it lists 2.6 on mine
So in order to distinguish you can rename all lthe binaries depending on the kernel version to later distinguish them
Apparently you can rename the files with the kernel version to find out which OS it was built.
Hope this helps,
Regards,
gaurav.
Last edited by gaurav1086; 04-18-2010 at 02:34 AM..
Reason: correct variable names
Hi,
I have two Solaris machines.
1. SunOS X 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1500
2. SunOS Y 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-60
I am trying to buiild a project on both these machines. The Binary output file compiled on machine 2 runs on both the machines. Where... (0 Replies)
dears i working in solaris and when i type make for report it gives me the error kindly can you help me what is the reason
-bash-3.00$ make BPSEXT130
make: Warning: File `BPSEXT130.rc' has modification time 12 s in the future
make BPSEXT130.c
make: Entering directory... (3 Replies)
Hi,
When i'm compiling my C files, I'm getting an error saying that the file name i've defined is undeclared. Could someone tell me how to solve this error. I've defined the file name as
#define _FILE_CODE_ _XYZ_C_
The error is "_XYZ_C undeclared".
Thanks in advance (1 Reply)
I am planning carving out dual VIO servers on a P750 based and would like to know how to allocate internal disks to the VIOS. This has 4 internal disks and I would to assign 2 disks to each VIO.
This is what I was thinking of assigning . Any advise?
vio1
U5802.001.9K8H757-P1-C1 PCI-E x8... (17 Replies)
Hi,
Generally we will run to install, configure apache 2.x on Solaris machine, but dont want to follow these on the remaining machines.
I want to build the apache binary centrally, so that i can untar the tar file on remaining machines. Please suggest on how to prepare this file and when i... (12 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
I have a tree structure as follows:
/vik/build/sc/botoh.sc
/vik/lib/endian.f
/vik/utils/botoh.f
Then I run the build script as
cd vik/build/sc
scons -f botoh.sc
The above shows that the SConstruct botoh.sc is down a few levels, and it
may be easiest to have the main... (6 Replies)
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
LEARN ABOUT CENTOS
ksc
KSC(1) User Commands KSC(1)NAME
ksc - Linux kernel module source checker
SYNOPSIS
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
-h, --help
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
/etc/ksc.conf
-d DIRECTORY, --directory=DIRECTORY
path to the directory
-i, --internal
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
-s, --submit
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
-v, --version
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)