From: Bill Katz <billk@sr.hp.com>
To: hppa-linux@puffingroup.com
Subject: Re: [hppa-linux] Booting issues.
Date: Mon, 15 Feb 1999 22:06:51 -0800 (PST) [thread overview]
Message-ID: <199902160606.WAA28977@meow.sr.hp.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990215204544.22132E-100000@devserv.devel.redhat.com> from Alex deVries at "Feb 15, 1999 8:48:10 pm"
>
>
> I was hoping someone could explain how booting works on HPs in the
> following ways:
>
> - booting from disk; is it possible to put our boot image onto an existing
> hpux disk, and boot from that image?
It certainly should be. A few notes on the booting process:
The bootROM, known as PDC only knows:
How to move bytes in from the disk (it starts at the beginning), to
look thorugh those first bytes, and find the header for a LIF volume,
and to launch a program. The program usually launched is ISL.
ISL knows more about LIF volumes, and can read an AUTOEXECUTE file
(a text file, call "AUTO" that contains the commands to execute
to boot. In the case of HPUX, it reads typically reads and executes
a file called "HPUX" which is the secondary loader. Note that
with in HP this loader is often called "mongoose".
WHen we want to make a dual boot system, we can include both HPUX
and LILO (for instance) in the LIF volume, and then launch either
operating system.
HPUX know about the hpux file systems, and is able to find /hp-ux,
/stand/vmunix, or /linux-kernel or any other file within the
file system. To use this as a method of booting Linux, Linux
may need to be taught about hte hpux file system. Or at least
somehow know how to find another partition.
>
> - booting over the network: if I understand correctly, my 715 can't do
> bootp, but does some other sort of network protocol. What is it? I'm
> told mklinux had a server hacked that could handle this, what is it, and
> where do we get it?
THe protocol is called RMP, and the requests are normally handled
by rbootd. From the rbootd man page:
+ RMP/BOOTP:
The RMP clients are the older s700 workstations and all DTCs:
workstations: 705, 710, 715, 720, 725, 730, 735, 750, 755
The BOOTP clients are the s712 and future workstations.
I don't know where to get documents on this protocol, but there
must be something around.
-Bill
----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.
next prev parent reply other threads:[~1999-02-16 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 1:48 [hppa-linux] Booting issues Alex deVries
1999-02-16 6:06 ` Bill Katz [this message]
1999-02-16 17:18 ` Alex deVries
1999-02-16 18:23 ` Bill Katz
1999-02-16 18:35 ` Richard J. Rauenzahn
-- strict thread matches above, loose matches on Subject: below --
1999-02-16 16:32 Jason Eckhardt
1999-02-16 18:01 ` Alex deVries
1999-02-16 19:01 ` Bill Katz
1999-02-16 18:12 ` Richard J. Rauenzahn
1999-02-16 18:47 ` Michael Marxmeier
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=199902160606.WAA28977@meow.sr.hp.com \
--to=billk@sr.hp.com \
--cc=hppa-linux@puffingroup.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