All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Lott <milos@insync.net>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: New Indy kernel uploaded
Date: Mon, 05 Apr 1999 08:36:33 -0500	[thread overview]
Message-ID: <3708BC61.AF904C06@insync.net> (raw)
In-Reply-To: 19990330235135.A2991@alpha.franken.de

This is working for me, too - to a point.  I get stuck
just past the package selection and the message that a log
will be created.  It looks as if it is hanging trying to
mount the linux partition.  So, stupid question.  The 
install instructions say to begin by running fx and setting
up a root partition on the second disk from within IRIX.
So, am I supposed to format ext2 from within the Hardhat setup
program?  Or, rather, at what point is the partition formatted
suitably for the Hardhat install to begin unpacking files on it?
TIA

Thomas Bogendoerfer wrote:
> 
> On Tue, Mar 30, 1999 at 09:43:16AM +0200, Tom Woelfel wrote:
> > Yep, done. Works without problems - Linux is up and running. How do
> > you solve the problems with the ECOFF/ELF thing ? Is there some kind
> > of backwards-compatibility ?
> 
> yes, every newer PROM is also able to boot ECOFF kernels. So I just
> uploaded an ECOFF kernel, which should work with every PROM.
> 
> Thomas.
> 
> --
>    This device has completely bogus header. Compaq scores again :-|
> It's a host bridge, but it should be called ghost bridge instead ;^)
>                                         [Martin `MJ' Mares on linux-kernel]

  reply	other threads:[~1999-04-05 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-28 23:26 New Indy kernel uploaded Thomas Bogendoerfer
1999-03-30  7:43 ` Tom Woelfel
1999-03-30 21:51   ` Thomas Bogendoerfer
1999-04-05 13:36     ` Miles Lott [this message]
1999-04-05 14:08       ` Alex deVries
     [not found] <8F94EAC86EE3D011BBCB08003667410229A436@aries.kprc.net>
1999-04-05 22:43 ` Thomas Bogendoerfer

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=3708BC61.AF904C06@insync.net \
    --to=milos@insync.net \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=milos@kprc.com \
    --cc=tsbogend@alpha.franken.de \
    /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.