From: Tom Woelfel <eedthwo@eede.ericsson.se>
To: "Dag Bakke" <dagb@oslo.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: IRIX Partations with HardHat Linux
Date: Wed, 30 Jun 1999 16:49:55 +0200 [thread overview]
Message-ID: <199906301449.QAA14683@sun168.eu> (raw)
In-Reply-To: <9906301627.ZM14888@dagb.oslo.sgi.com>
Dag Bakke writes:
> As I understand it, you only need to partition the disk with the SGI tools
> (fx).
> (If this is wrong, please feel free to correct me.)
> Thus, you only need bootp and tftp to boot fx.
Yep.
> To boot fx on the Indy from the prom monitor (command monitor) enter:
> setenv -p netaddr 123.456.789.123
> boot -f bootp()remotemachine:/path/to/stand/fx.ARCS
After endeavouring with the bootp/tftp options for a couple of hours I
finally managed to get sash or fx loaded. But I've seen lot of
rejected requests during this session from the i386 server. But what's
the next step ? Do I have to change the bootfile-entry in bootptab to
point to the next requested file ? (Ooops, I'm at work - so I don't
have access to my Indy, but after partitioning the disk the Indy
requested something like sash(NN).)
I will try it once again and write down my experiences.
//Tom
next prev parent reply other threads:[~1999-06-30 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-29 15:19 IRIX Partations with HardHat Linux Shane W.
1999-06-30 8:43 ` Roald Lygre
1999-06-30 9:20 ` Shane W.
1999-06-30 15:25 ` Dag Bakke
1999-06-30 13:48 ` Tom Woelfel
1999-06-30 14:06 ` Vince Weaver
[not found] ` <weave@eng.umd.edu>
1999-06-30 16:27 ` Dag Bakke
1999-06-30 14:49 ` Tom Woelfel [this message]
1999-06-30 16:48 ` Ulf Carlsson
-- strict thread matches above, loose matches on Subject: below --
1999-06-30 13:24 Tor Arntsen
1999-06-30 15:32 ` Roald Lygre
1999-06-30 15:32 ` Roald Lygre
1999-06-30 13:35 Tor Arntsen
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=199906301449.QAA14683@sun168.eu \
--to=eedthwo@eede.ericsson.se \
--cc=dagb@oslo.sgi.com \
--cc=linux@cthulhu.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 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.