All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bame <bame@fc.hp.com>
To: Grant Grundler <grundler@dsl2.external.hp.com>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Tue, 22 Jan 2002 12:59:03 -0700	[thread overview]
Message-ID: <E16T74R-0002Ko-00@noam.fc.hp.com> (raw)
In-Reply-To: Your message of "Sun, 06 Jan 2002 20:46:15 MST." <20020107034615.9BFD64839@dsl2.external.hp.com>

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?  I know it's a pain
to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.

	-P

  parent reply	other threads:[~2002-01-22 19:59 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   ` Paul Bame [this message]
2002-01-23  2:13     ` [parisc-linux] vmlinux header for savecrash 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
  -- 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=E16T74R-0002Ko-00@noam.fc.hp.com \
    --to=bame@fc.hp.com \
    --cc=grundler@dsl2.external.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.