From: "James P. Kinney III" <jkinney@localnetsolutions.com>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: 21 Jan 2002 19:43:05 -0500 [thread overview]
Message-ID: <1011660185.22455.118.camel@archimedes.localnetsolutions.com> (raw)
In-Reply-To: <3C4C53B7.67DA24E@admin.france.hp.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
I think the palo command line is listed in dmesg. That will tell exactly
which kernel was booted.
On Mon, 2002-01-21 at 12:45, Bruno Vidal wrote:
> Hi
> As I said few days ago, I've a dump driver ready.
> Now I'm working on a savecrash command. It works fine
> for the dump, but I need to save with the dump some
> informations like the running kernel at dump time.
> So in the dump I've got this informations:
> utsname_release and utsname_version. Now, how can
> I found the right kernel in /boot ? In other
> word, how can I retrieve utsname informations in a
> binary file (without system.map and gdb) ?
>
> Thanks.
>
> --
> Vidal Bruno, (770-4271)
> SSD-HA Team, HP-UX & LINUX Support
> bruno_vidal@admin.france.hp.com
--
James P. Kinney III \Changing the mobile computing world/
President and COO \ one Linux user /
Local Net Solutions,LLC \ at a time. /
770-493-8244 \.___________________________./
GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney@localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-22 0:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 17:45 [parisc-linux] vmlinux header for savecrash Bruno Vidal
2002-01-21 20:25 ` Grant Grundler
2002-01-22 9:20 ` Bruno Vidal
2002-01-22 9:55 ` Enrik Berkhan
2002-01-22 12:25 ` Bruno Vidal
2002-01-22 15:11 ` Enrik Berkhan
2002-01-22 15:13 ` Matthew Wilcox
2002-01-22 12:05 ` James P. Kinney III
2002-01-22 17:45 ` Grant Grundler
2002-01-22 17:53 ` Randolph Chung
2002-01-22 17:59 ` Bruno Vidal
2002-01-22 17:55 ` Bruno Vidal
2002-01-22 18:11 ` Randolph Chung
2002-01-22 18:34 ` Grant Grundler
2002-01-22 0:43 ` James P. Kinney III [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07 3:46 ` Grant Grundler
2002-01-22 19:59 ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23 2:13 ` Grant Grundler
2002-01-23 10:23 ` Andreas Deresch
2002-01-25 6:30 ` Grant Grundler
2002-01-23 8:57 ` Enrik Berkhan
2002-01-23 9:29 ` phi 4369
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1011660185.22455.118.camel@archimedes.localnetsolutions.com \
--to=jkinney@localnetsolutions.com \
--cc=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox