From: ralf@uni-koblenz.de
To: "William J. Earl" <wje@fir.engr.sgi.com>,
"Francis M. J. Hsieh" <mjhsieh@helix.life.nthu.edu.tw>
Cc: Linux <linux%cthulhu.engr.sgi.com@ms21.hinet.net>
Subject: Re: [Q] How to reboot automatically?
Date: Mon, 20 Jul 1998 20:32:00 +0200 [thread overview]
Message-ID: <19980720203200.D440@uni-koblenz.de> (raw)
In-Reply-To: <199807201610.JAA28042@fir.engr.sgi.com>; from William J. Earl on Mon, Jul 20, 1998 at 09:10:34AM -0700
On Mon, Jul 20, 1998 at 09:10:34AM -0700, William J. Earl wrote:
> IRIX looks at the environment when booting. That is, it finds
> argc, argv, and envp in $a0, $a1, and $a2. It copies them to
> private storage before starting up, since they are in memory
> which will be overlaid by dynamic memory allocation. All of the
> NVRAM and temporary environment variables are passed via envp.
> IRIX looks for root= on the command line (in argv) first, and then
> in the environment, before falling back on a default. linux could
> do the same.
That looks like a good idea; it can be implemented easily and nicely
within Linux. And for transparency we should. What will stay different
is the naming convention of Linux partitions.
The environment is allocated in ``Firmware Temporary'' memory, isn't it?
We don't free that yet but we should, for low memory configurations that
should be a significant amount of memory.
Ralf
next prev parent reply other threads:[~1998-07-20 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-18 8:47 [Q] How to reboot automatically? Francis M. J. Hsieh
[not found] ` <19980719041810.G489@uni-koblenz.de>
1998-07-19 20:18 ` Francis M. J. Hsieh
1998-07-19 21:20 ` ralf
1998-07-20 12:25 ` Francis M. J. Hsieh
1998-07-20 16:10 ` William J. Earl
1998-07-20 18:32 ` ralf [this message]
1998-07-20 18:43 ` William J. Earl
1998-07-20 19:11 ` ralf
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=19980720203200.D440@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux%cthulhu.engr.sgi.com@ms21.hinet.net \
--cc=mjhsieh@helix.life.nthu.edu.tw \
--cc=wje@fir.engr.sgi.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