All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: rpengelly <rpengelly@ati.stlawrencec.on.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] opening initial console
Date: Fri, 6 Jul 2001 18:08:25 +0100	[thread overview]
Message-ID: <20010706180825.A23509@linuxcare.com> (raw)
In-Reply-To: <001901c1062d$a08091c0$0f809b8e@ati.stlawrencec.on.ca>; from rpengelly@ati.stlawrencec.on.ca on Fri, Jul 06, 2001 at 11:09:17AM -0400

On Fri, Jul 06, 2001 at 11:09:17AM -0400, rpengelly wrote:
> I'm confused about booting from a lifimage. How do we go about this. Note:
> we are unbale to install via CDROM because of harware issues so we are
> relying on a network install.

palo can take a kernel image and wrap stuff round it to make a bootable
image.  That is called a lifimage.  You managed to boot from the
network, so you must have booted a lifimage format file.  You must
have put that lifimage somewhere that bootp/rbootd could find it
when asked by your parisc box.  On the CD is a file called lifimage,
in dists/sid/main/disks-hppa/current/lifimage (or similar).  Simply
copy that file to your bootp server, placing it and naming it as
you did for whatever you booted last time.  Then tell your parisc
box to boot from the network.  Don't interact with the IPL to modify
any kernel boot parameters - it should all "just work".

You should get the installer release notes page displayed, hit return
and you are in to the main installer menu.

Once you have the system installed and using palo to boot from disk,
palo uses plain kernel image files, not lifimages.  Those live in
/boot/vmlinuz or similar, and should be set up for you during the
install.

Hope that helps, ask again if not.

Richard

      reply	other threads:[~2001-07-06 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06 14:19 [parisc-linux] opening initial console rpengelly
2001-07-06 14:39 ` Richard Hirst
2001-07-06 15:09   ` rpengelly
2001-07-06 17:08     ` Richard Hirst [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=20010706180825.A23509@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rpengelly@ati.stlawrencec.on.ca \
    /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.