From: Paul Bame <bame@endor.fc.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] PALO and ramdisk micro-howto
Date: Tue, 21 Mar 2000 10:44:58 -0700 [thread overview]
Message-ID: <E12XSiA-00022u-00@endor.fc.hp.com> (raw)
Grab recent versions of these from CVS:
palo sources
linux-2.3/init/main.c
linux-2.3/arch/parisc/kernel/setup.c
In palo/Makefile, comment out NFSROOT= and uncomment the RAMDISK= line
which assumes your ramdisk is the file ../linux-2.3/ramdisk.bin which
is the way we used to have things. Make sure you have a ramdisk in that
file (or change RAMDISK=).
Next time you 'make palo' in your linux tree, palo inserts the ramdisk
inside lifimage and constructs a default kernel command line to use the
ramdisk.
I tried both the old ramdisk, and I turned willy's nfsroot into a
ramdisk, and both booted and loaded but died with that
'Kernel panic: Attempted to kill init!' message. Looks like sash is
being started with some args it doesn't like and exiting with a usage
message.
-P
next reply other threads:[~2000-03-21 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 17:44 Paul Bame [this message]
2000-03-21 21:40 ` [parisc-linux] PALO and ramdisk micro-howto Paul Bame
2000-03-22 22:33 ` 5116
2000-03-23 3:02 ` willy
2000-03-23 19:05 ` [parisc-linux] Eth0 trouble Thierry SIMONNET
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=E12XSiA-00022u-00@endor.fc.hp.com \
--to=bame@endor.fc.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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