From: Stan Sieler <sieler@allegro.com>
To: bame@debian.fc.hp.com (Paul Bame)
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] boot loader
Date: Thu, 21 Oct 1999 18:39:36 -0700 (PDT) [thread overview]
Message-ID: <199910220139.SAA29964@bart.allegro.com> (raw)
In-Reply-To: <199910220055.SAA20611@debian.fc.hp.com> from "Paul Bame" at Oct 21, 99 06:55:38 pm
Hi,
> My proposal is to have a LIF volume on the beginning of any disk
> from which one might boot. Make that LIF volume at least 2Mb, and
> maybe 10Mb if you want to store several kernels and ramdisk images.
> Here are the files it would hold:
>
> IPL Pretty much the boot loader we're using today
> with some LIF intelligence added
> vmlinuz The kernel image, put there with the 'lifcp'
> command. Could have several kernels
> on the LIF volume and boot any of them.
> cmdline The default, or the last?, command line used
> to boot Linux. Could possibly have several
> different command lines in one or several files
> but the UI for this needs thought.
> ramdisk One or more files containing ramdisk images
> ptable Partition table -- see below
As long as you don't want to use LIF utilities to access those files,
lowercase should be okay.
The LIF tools won't accept lowercase filenames.
Why care? Because you could possibly boot HP-UX and use the LIF tools
to manipulate the vmlinuz file, for example.
Example:
Oz(su) /: lifcp test /dev/dsk/c0t0d0:vmlinuz
lifcp: Cannot create vmlinuz ; improperly formatted LIF name
Oz(su) /:
(BTW, the lifcp "-t" option won't help)
I'd suggest using uppercase, and making the IPL smart enough
to allow user-entry of lowercase (which gets mapped to uppercase)
> After building a new kernel, you'd have to
> 'lifcp <the-kernel-image> /dev/sda:vmlinuz' instead of
> doing 'mkImage' like we do today. It's also cool that the ramdisk
> isn't linked into the kernel.
Note: my lifcp test was on 10.20
> lifinit and lifcp should already be able to handle the LIF stuff, so
> no new C code required to build the LIF volumes. We can probably
> talk HP into open sourcing the LIF commands, and if not can grab
> the ones from OpenBSD. For now we can use the ones on HP-UX.
> [I suspect the HP ones are not byte-order safe (yet).]
If that happens, we could support lowercase.
> The Name
>
> BTW the current contender for the name, instead of hilo, is palo
> for PArisc LOader. It is also a reminder of of Palo Alto
> which is where HP began.
Great name!
--
Stan Sieler sieler@allegro.com
http://www.allegro.com/sieler/
next prev parent reply other threads:[~1999-10-22 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 23:55 [parisc-linux] boot loader Paul Bame
1999-10-22 1:39 ` Stan Sieler [this message]
1999-10-22 18:03 ` Stan Sieler
1999-10-22 2:10 ` Jason Eckhardt
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=199910220139.SAA29964@bart.allegro.com \
--to=sieler@allegro.com \
--cc=bame@debian.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