linux-mips
[Top] [All Lists]

Re: Partial Success Report

To: ralf@uni-koblenz.de
Subject: Re: Partial Success Report
From: "William J. Earl" <wje@fir.engr.sgi.com>
Date: Sun, 18 Oct 1998 17:13:15 -0700
Cc: Ulf Carlsson <grim@zigzegv.ml.org>, Jeff Coffin <jcoffin@sv.usweb.com>, linux@cthulhu.engr.sgi.com
In-reply-to: <19981017040148.C4768@uni-koblenz.de>
References: <m3ww618s88.fsf@lil.sv.usweb.com> <19981016001717.B2072@zigzegv.ml.org> <m3pvbt8k2y.fsf@lil.sv.usweb.com> <19981016214659.A2754@zigzegv.ml.org> <19981017040148.C4768@uni-koblenz.de>
Sender: owner-linux@cthulhu.engr.sgi.com
ralf@uni-koblenz.de writes:
 > On Fri, Oct 16, 1998 at 09:46:59PM +0200, Ulf Carlsson wrote:
 > 
 > > I thought the bootp command was loaded from the IRIX partition, because it
 > > didn't work when I removed the IRIX harddrive, atleast it didn't with my 
 > > old
 > > PROM.  It claimed that it couldn't find the bootp() command - maybe I'm 
 > > out of
 > > my mind, I'll check next time I remove the cover...
 > 
 > bootp() is just a ARC filename which is either interpreted by the PROM
 > command interpreter or by sash where sash afaik is nothing other than the
 > PROMs compiled with special flags.

       That is, bootp() is part of a path.  There is no bootp command.

       sash, unlike most PROMs, has one or more (read-only) disk file
systems bound into it.  On Indy, older sash versions can read efs volumes,
and newer ones can also read xfs volumes.


<Prev in Thread] Current Thread [Next in Thread>