Hi ,
I am new to shell scripting . I have been go through many sites and ready the material for shell scripting. But I am not getting complete examples for practice.
Can any one suggest me any site that contains lots of ready examples for shell scripting ??
Regards (0 Replies)
Hi all,
I tried to understand what this awk and sed does but cudnt understand.
Can any body explain what awk and sed means with one simple example each and complex examples each with explanation.
Thanks in advance. (7 Replies)
Fairly new to RedHat. Can someone tell me what the version that I am working on.
cat /etc/rehdat-release shows
Red Hat Enterprise Linux Server release 5.4 Beta (Tikanga)
I would think that this is RedHat 5 update 4. I don't know how what Beta and (Tikanga) means. Is this truly beta code? (1 Reply)
Hello
I have been asked to provide a security patch analysis of servers in my environment. For HPUX and Solaris there are tools wich can be loaded onto the servers to do this. However I do not know of one for Redhat . At this point I must mentioned that the Redhat servers are behind a firewall... (2 Replies)
Hello,
Please let me know what is meaning of the Tikanga in /etc/redhat-release file?
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
#
Thanks in advance. (1 Reply)
Discussion started by: kuddusrhce
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)