From: bame@riverrock.org
To: "Phillip D. Beal" <pdbeal@louisville.edu>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] PALO CD Creation
Date: Wed, 10 Jan 2001 13:20:52 -0700 [thread overview]
Message-ID: <m14GRjp-001Vp3C@chalet> (raw)
In-Reply-To: Your message of "Wed, 10 Jan 2001 15:07:02 EST." <20010110150702.A30218@athena.louisville.edu>
= Hey,
=
= I've been building the latest kernel stuff, and I see that its getting
= close to complketiong for the STI console. First off I'd have to say
= great job so far. I would like to create a bootable CD with one of the
= kernels I have built from cvs. The kernel boots on a 755 and 735
= throught the network, but there are other machines I've been asked to
= try this on, and I need a CD. I've read through the README from the
= palo sources
Sometimes the README.html is more up to date -- README is derived from it.
= and followed the steps to create a CD, but I have a
= question about this steps. Are all the steps executed on an HPUX
= machine, a PARISC machine, or a standard linux machine? If they are
= created on a linux machine, where can someone get the palo binary for
= i386 linux.
I master the CD and run palo on x86 Linux. If you're using x86 to
cross-compile your Linux kernels you have the required palo binary
already. Since the CD mastering software is probably not yet compiled
for palinux I think x86 Linux is your best choice.
= Also, the README needs a little bit of an update too I
= think, since we now have to pass console=[tty0|ttyS0] to palo.
The kernel command line is not specific to parisc and so the standard
Linux documentation should be used. Palo's README does not duplicate
this information -- it should only document what's specific to palo
(kernel and ramdisk specifications) though I know it has a couple of
other things in there right now.
-P
prev parent reply other threads:[~2001-01-10 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 20:07 [parisc-linux] PALO CD Creation Phillip D. Beal
2001-01-10 20:20 ` bame [this message]
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=m14GRjp-001Vp3C@chalet \
--to=bame@riverrock.org \
--cc=parisc-linux@thepuffingroup.com \
--cc=pdbeal@louisville.edu \
/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