How to detect OS is SLES 10 or not Post: 302256575

10 More Discussions You Might Find Interesting

1. Linux

How to take OS Backup of SLES 10 on DVD....???

Dear All, I have two intel xeon servers running with SLES 10 on a cluster environment (Veritas Cluster 4.1 - 2 Node Cluster - Active Passive). Both the systems are having hardware RAID 1 for OS disk. Both the systems are having DVD writer. I would like to take the OS backup on DVD which can...

2. SuSE

YaST no longer works on SLES 10

YaST no longer works on one of our SUSE Linux Enterprise Server 10, When I issue �Yast� I get the following error messages "warning: the ncurses frontend is installed but does not work" "You need to install yast2-ncurses to use the YaST2 text mode interface" Can you help? please

3. SuSE

configure vnc sles 11

Is there any doc/procedure to set up VNC on SLES 11 to connect from windows clients??

4. SuSE

errors after upgrading from SLES10Sp2 to SLES 11

I just upgraded sles 10 sp2 to sles 11. Apache is running on the server. apache needs to contact the backend server which is weblogic. But once I upgrade to sles 11 i cant able to telnet or ping to the backend (weblogic)server. I checked firewall and is disabled. Any ideas. Thanks.

5. Shell Programming and Scripting

shell scripts for linux SLES 10

Hi, could someone help me to create the following scripts Need to create couple of shell scripts on LINUX SLES 10 Using my id --------------- First script – this script should contain su and should take input <process name> 1 -login using my id and then sudo to...

6. SuSE

user simple password SLES

Hello, I would like to change a password of a user to a simple one but when i try to add an only lowercase pass i get the error: Weak password: too short. Try again. You can now choose the new password. A valid password should be a mix of upper and lower case letters, digits, and...

7. SuSE

SLES 9 vs SLES 11 hard drive cache read timings are diffrent

Can anyone give me a little clue on why the hard drive cache read timings on sles 9 is better then sles 11? The same hardware was used in both test. I even deleted the ata_generic module from initrd. The speed difference is 10MB vs 5 MB Thanks

8. UNIX for Advanced & Expert Users

YUM GROUPLIST not working on SLES 11

I have a SLES 11 install with yum also installed. yum works when I try to install single packages. However, when i try the yum command: "yum grouplist" yum can not detect any groups. Is there some way to "enable" or install a grouplist feature in SLES 11 ? ==== details ==== SUSE Linux...

9. SuSE

Linux SLES Gui Not coming up

I had sles 11 sp2 installed on my system some days back and it was running fine. Today after I restarted my system the gui is not coming up and system starts in command terminal. sax2 command returns error: sax: gui is missing, starting command line interface sax: no x-server...

10. SuSE

'createrepo' not found on SLES 10.3

Hello All, I'm trying to configure a SLES 10.3 machine as our Zypper server. I created the zypper directories with all the RPMs, made the directory structure accessible over HTTP but I'm stuck at the final stage: createrepo. Looks like 'createrepo' is not present on this version :confused: ...

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)