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)
We are getting one error when we execute the binary file below mentioned, and ownership goes to root:nobody, how to resolve this problem.
sh /home/pub/bin/awk: cannot execute binary file
:confused:
Pls help me out . (2 Replies)
HI,
i am trying to execute one .bin file which is a pre-installed (not compiled by me). But I am getting the error "cannot execute binary file".I checked the permissions and everything is ok.
also I checked ldd <bin-filename> andit showed a msg "not a dynamic executable"
Can anyone help in... (4 Replies)
When I am trying to execute a script created by Perl2exe in Linux SLES 8.1 running with virtual machine on mainframe s/390 ....I am getting
"cannot execute binary file"....
In the linux server which are not in mainframe the scripts are fine.....
Thanks for help (1 Reply)
As root, I receive the error message, "cannot execute binary file" when running some commands such as /usr/bin/clear or /usr/sbin/brctl or /usr/sbin/lsof. The system is running RHEL5.5. File permissions are 755. noexec is NOT set on the partitions where these files live.
I've spent a... (6 Replies)
I'm trying to install JasperReports Server 4.1 on Linux Ubuntu (release 11.04) as root and have following message:
-bash: ./jasperreports-server-cp-4.1.0-linux-x64-installer.run: cannot execute binary file
Is any idea what should I do in order to install Jasper?
Previously, I installed... (6 Replies)
Grettings,
Hi and thanks for taking a look at this. I'm going to attempt to explain this the best I possible can but due to my limited knowledge of linux this may prove difficult. I have attempted to install xcrysden on cygwin following the instruction on xcrysden webpage (I attempted to link the... (2 Replies)
Hey all,
I am using Cygwin on a machine running windows 7 64bits. I am about to use the following command:
$ faToTwoBit in.fa out.2bit
In the manual on sourceforge it mentioned:
"Download blat and faToTwoBit and set the blat_bin and fatotwobit_bin entries in config.txt to the fully... (4 Replies)
Hi all,
Probably somewhat of an obvous problem here but i'm no pro.
I just bought a PengPod1000 at pengpod.com
On it I have an image of Fedora 18.
I am trying to run an application I wrote for Fedora 14 32 bit desktop on this tablet. With all permissions setup using chmod but I get... (7 Replies)
Discussion started by: fedora18
7 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)