From: Bryan Manternach <smash@sgi.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "J. Scott Kasten" <jsk@tetracon-eng.net>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: Kernel boot tips.
Date: Sun, 09 Jul 2000 15:34:17 -0700 [thread overview]
Message-ID: <3968FDE8.3443ED5@sgi.com> (raw)
In-Reply-To: 20000709062927.A5609@bacchus.dhis.org
Ralf Baechle wrote:
> On Fri, Jul 07, 2000 at 10:10:59AM -0300, J. Scott Kasten wrote:
>
> > I learned 3 slick booting tips for booting an Indy from disk without a
> > regular Linux boot loader that might be useful to some of the newbies.
A fourth means is to change the nvram to boot the file you want.
Leave /unix there,and call your linux kernel something like /linux2.2.0
and change the "kernname" nvram.
kernname=pci(0)scsi(0)disk(2)rdisk(0)partition(0)/unix
becomes
kernname=pci(0)scsi(0)disk(2)rdisk(0)partition(0)/linux2.2.0
This should work on the IRIX efs/xfs filesystem on the IRIX
partition. Then you can create a script that resets the NVRAM
variable before reboot.
All we would need to make back and forth boots of IRIX/LINUX
is an "nvram" tool that runs under LInux. (Which would be handy
for other porposes as well.
>
> >--
> THE USE OF EMAIL FOR THE TRANSMISSION OF UNSOLICITED COMMERICAL
> MATERIAL IS PROHIBITED UNDER FEDERAL LAW (47 USC 227). Violations may
> result in civil penalties and claims of $500.00 PER OCCURRENCE
> (47 USC 227[c]). Commercial spam WILL be forwarded to postmasters.
next prev parent reply other threads:[~2000-07-09 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 13:10 Kernel boot tips J. Scott Kasten
2000-07-09 4:29 ` Ralf Baechle
2000-07-09 20:59 ` J. Scott Kasten
2000-07-09 22:34 ` Bryan Manternach [this message]
2000-07-09 22:59 ` Florian Lohoff
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 13:55 Tor Arntsen
2000-07-10 22:53 ` Ralf Baechle
2000-07-11 14:19 Tor Arntsen
2000-07-11 23:57 ` Ralf Baechle
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=3968FDE8.3443ED5@sgi.com \
--to=smash@sgi.com \
--cc=jsk@tetracon-eng.net \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-mips@vger.rutgers.edu \
--cc=ralf@oss.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