Command for kernel checking part 1

For Debian User

>> dpkg --list | grep linux-image # To list all kernel.

ex.result
ii linux-image-2.6.38-10-generic 2.6.38-10.46 Linux kernel image for version 2.6.38 on x86/x86_64
ii linux-image-2.6.38-11-generic 2.6.38-11.48 Linux kernel image for version 2.6.38 on x86/x86_64
ii linux-image-2.6.38-8-generic 2.6.38-8.42 Linux kernel image for version 2.6.38 on x86/x86_64
ii linux-image-generic 2.6.38.11.26 Generic Linux kernel image

>> uname -r OR uname -mrs # To display current kernel.

Comments

Post a Comment

Popular posts from this blog

Return Code 127

Exit codes and kill-job signals The exit code from a batch job is a standard Unix termination status, the same sort of number you get in a shell script from checking the " $? " variable after executing a command. Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling  exit()  with a non-zero value to terminate itself and indicate an error. In BaBar we don't make very much use of this. The most common such value you might see is 64, which is the value used by Framework to say that its event loop is being stopped before all the requested data have been read, typically because time ran out. In recent BaBar releases you might also see 125, which we use as a code for a generic "severe error"; the job log should contain a message stating what the error was. Exit codes in the range 129-255 represent jobs terminated by Unix " signals ". Each type of signal has a number, and what's r
Read more