Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Paul Bame <bame@fc.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Tue, 22 Jan 2002 19:13:18 -0700	[thread overview]
Message-ID: <20020123021318.E6C6C482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Paul Bame <bame@fc.hp.com> of "Tue, 22 Jan 2002 12:59:03 MST." <E16T74R-0002Ko-00@noam.fc.hp.com>

Paul Bame wrote:
> 
> palo removes the "3/vmlinux" parameter (and the initrd= one too) before
> passing command line to the kernel which is consistent with x86 I think.
> Would it be helpful to add a kernel parameter like "palo_kernel=3/vmlinux"
> which you could then retrieve from /proc/cmdline?

Sort of. Actually, I was thinking the dump driver could use "palo_kernel"
global to save off the file name of the vmlinux which crashed.
setup_cmdline could parse/squirrel away the palo_kernel parameter.

> I know it's a pain
> to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.

Isn't /vmlinux a symlink to /boot/vmlinux?
ie the file palo loaded is whatever the symlink points to.

BTW, I explicitly specify /boot/vmlinux in my palo.conf files
and see 3/boot/vmlinux in my palo command line.

thanks,
grant

  reply	other threads:[~2002-01-23  2:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07  2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07  3:46 ` Grant Grundler
2002-01-07  5:28   ` Matthias Klose
2002-01-22 19:59   ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23  2:13     ` Grant Grundler [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2002-01-21 17:45 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

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=20020123021318.E6C6C482A@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=bame@fc.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