Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: linux@cthulhu.engr.sgi.com (SGI/Linux mailing list)
Subject: Re: bootp on IRIX server
Date: Mon, 21 Dec 1998 13:33:48 -0800 (PST)	[thread overview]
Message-ID: <199812212133.NAA08955@oz.engr.sgi.com> (raw)

[Forwarding bounced message.
 Please subscribe with an explicit general-domain (no machine)
 to avoid anti-spam subscriber-only bounces.
 Majordomo is picky about this -- Ariel]

Date: Mon, 21 Dec 1998 13:23:19 -0800
From: Shrijeet Mukherjee <shm@engr.sgi.com>
To: Al Aumenta <aumenta@albany.sgi.com>
cc: "linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: bootp on IRIX server
In-Reply-To: <367EB96A.AB060206@albany.sgi.com>
Message-ID: <Pine.SGI.4.05.9812211321150.14389-100000@tantrik.engr.sgi.com>


I had the same problem .. and I really do not remember what I did to make
it go away ..

but here are 2 things to try ..

1> run snoop on your SGI box .. and see what exactly is happening ..
2> try and bootp the unix kernel (IRIX) and see if bootp is setup and
running right ..


another thing I gathered is that there is some NFS incompatibility and we
need to serve the bootp of an intel linux box .. and thus I resorted to
that ..

hope this helps ..


On Mon, 21 Dec 1998, Al Aumenta wrote:

->I am attempting to install Linux on an Indy but I am running into a
->problem



-- 
Peace, Ariel

WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: bootp on IRIX server
Date: Mon, 21 Dec 1998 13:33:48 -0800 (PST)	[thread overview]
Message-ID: <199812212133.NAA08955@oz.engr.sgi.com> (raw)
Message-ID: <19981221213348.vuIwETvn71vKt0PXKXGMyLKJ2EtFbNbYEbovjWeHx1I@z> (raw)

[Forwarding bounced message.
 Please subscribe with an explicit general-domain (no machine)
 to avoid anti-spam subscriber-only bounces.
 Majordomo is picky about this -- Ariel]

Date: Mon, 21 Dec 1998 13:23:19 -0800
From: Shrijeet Mukherjee <shm@engr.sgi.com>
To: Al Aumenta <aumenta@albany.sgi.com>
cc: "linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: bootp on IRIX server
In-Reply-To: <367EB96A.AB060206@albany.sgi.com>
Message-ID: <Pine.SGI.4.05.9812211321150.14389-100000@tantrik.engr.sgi.com>


I had the same problem .. and I really do not remember what I did to make
it go away ..

but here are 2 things to try ..

1> run snoop on your SGI box .. and see what exactly is happening ..
2> try and bootp the unix kernel (IRIX) and see if bootp is setup and
running right ..


another thing I gathered is that there is some NFS incompatibility and we
need to serve the bootp of an intel linux box .. and thus I resorted to
that ..

hope this helps ..


On Mon, 21 Dec 1998, Al Aumenta wrote:

->I am attempting to install Linux on an Indy but I am running into a
->problem



-- 
Peace, Ariel

             reply	other threads:[~1998-12-21 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-21 21:33 Ariel Faigon [this message]
1998-12-21 21:33 ` bootp on IRIX server Ariel Faigon
  -- strict thread matches above, loose matches on Subject: below --
1998-12-21 21:11 Al Aumenta

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=199812212133.NAA08955@oz.engr.sgi.com \
    --to=ariel@oz.engr.sgi.com \
    --cc=ariel@cthulhu.engr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox