- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: kernel
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 05:34 AM
тАО03-09-2009 05:34 AM
kernel
In server there are three for vmunix file in /stand file system.
How can we check which current kernel the server is using it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 05:41 AM
тАО03-09-2009 05:41 AM
Re: kernel
Using adb(1) :
o echo boot_string/S | adb /stand/vmunix /dev/kmem
Using dmesg(1M) :
If dmesg(1M) works, booting was performed from /stand/vmunix .
If dmesg(1M) does not work, run it against each kernel in /stand , until dmesg works.
When dmesg works, the kernel from which booting was performed is found. For example:
# dmesg
May 17 08:16
Magic number wrong (namelist mismatch?)
The previously mentioned example is the equivalent of:
# dmesg /dev/kmem /stand/vmunix
May 17 08:19
Magic number wrong (namelist mismatch?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 05:41 AM
тАО03-09-2009 05:41 AM
Re: kernel
GSP> CL
Sample output:
ISL booting hpux -lqtest STATUS: 0
CALLER SUBACTIVITY: 1F = implementation dependent
BootRTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
: disk(0/0/1/1.2.0.0.0.0.0;0)/stand/vmunix
10317824 + 10788864 + 421038032 start 0x201068 Data Field Unused
0x58000800800011F0 00006D01 0E100914 type 11 = Timestamp 02/14/2009 16:09:20
Type CR for next entry, - CR for previous entry, Q CR to quit.
rgs,
rariasn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 05:51 AM
тАО03-09-2009 05:51 AM
Re: kernel
Please assign points to your thread
http://forums11.itrc.hp.com/service/forums/helptips.do?#33
This is a way of saying thanks to the right answers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 07:24 AM
тАО03-09-2009 07:24 AM
Re: kernel
It is much easier.
The following is a list of directories and their meanings that now exist with B.11.23:
Currently running kernel: /stand/current/
Copy of the current config prior to changes: /stand/backup/
Kernel config originally installed with OS /stand/last_install/
Link to the config to be used at the next boot: /stand/nextboot/
Automatically created after any crash dump: /stand/crashconfig/
There are also two special files in /stand:
/stand/vmunix is a hard link to /stand/current/vmunix
/stand/system is a soft link to /stand/nextboot/system
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2009 10:48 PM
тАО03-15-2009 10:48 PM
Re: kernel
But still i am not able to get it,
I am not able to decide from which current kernel the server is running.
# cd /stand
# ls -lrt
total 227712
-r-xr-xr-x 1 bin bin 58204072 Jan 25 2006 vpmon
drwxr-xr-x 2 root root 65536 Aug 1 2006 lost+found
dr-xr-xr-x 3 bin bin 1024 Aug 1 2006 boot.sys
-r--r--r-- 1 root sys 2434 Aug 1 2006 system.import
-r--r--r-- 1 root sys 82 Aug 1 2006 kernrel
drwxr-xr-x 5 root sys 1024 Aug 1 2006 last_install
-rw-r--r-- 1 root sys 42 Aug 3 2006 bootconf
-rw-r--r-- 1 root sys 3759 Aug 16 2008 system.prev
-rwxr-xr-x 2 root sys 57994304 Aug 16 2008 vmunix
drwxr-xr-x 5 root sys 1024 Aug 16 2008 backup
drwxr-xr-x 5 root sys 1024 Aug 16 2008 current
-rw------- 1 root root 12 Aug 16 2008 rootconf
lrwxr-xr-x 1 root root 15 Aug 16 2008 system -> nextboot/system
lrwxr-xr-x 1 root root 14 Aug 16 2008 bootfs -> current/bootfs
lrwxr-xr-x 1 root root 7 Aug 16 2008 nextboot -> current
drwxr-xr-x 2 root sys 1024 Aug 16 2008 krs
-rw------- 1 root root 16464 Aug 17 2008 vpdb
-rw-r--r-- 1 root sys 24136 Oct 14 19:30 ioconfig
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2009 11:10 PM
тАО03-15-2009 11:10 PM
Re: kernel
You can use the below command to know the result
dmesg | grep boot
or
dmesg | grep -i vmunix
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2009 11:29 PM
тАО03-15-2009 11:29 PM
Re: kernel
You can use kconfig with -S parameter.
See the man kconfig
-S
kconfig will display all settings of the currently running configuration that are not at their default value. In other words, it will execute
kcmodule -S
kctune -S
(If any additional kernel configuration data become available in future HP-UX releases, settings of them will be included as well.) Not valid in combination with any other flags.
hope this help.
Whiteknight
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2009 11:44 PM
тАО03-15-2009 11:44 PM
Re: kernel
do
echo "\n$a"; echo $a|sed -e s/./=/g
echo "linkstamp/s\nlinkstamp?s"| \
adb -o $a /dev/kmem
done >/tmp/res 2>&1
/stand/nextboot/vmunix
======================
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
/stand/current/vmunix
=====================
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
/stand/vmunix
=============
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
linkstamp:
linkstamp:
Thu Sep 11 18:01:06 METDST 2008
/stand/last_install/vmunix
==========================
adb: warning: Object file and memory file versions do not match ...
adb: warning: Symbol lookups may fail.
linkstamp:
linkstamp:
7├Г ?├В┬бS├Г >├Г┬б├Г┬л├Г┬м├В┬в
7├Г ?├В┬бS├Г >├Г┬бSW^A├Г ^W ^RS_^A
linkstamp:
linkstamp:
Fri Sep 10 13:59:09 EDT 2004
When the 2 linkstamp lines are matching, then it is the booted kernel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 12:03 AM
тАО03-16-2009 12:03 AM
Re: kernel
I got the exact command,
It can be find out using the following command:
#kcpath -x
Thanks for all your support.