Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alistair Lambie <alambie@wellington.sgi.com>
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
	SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: root-be-0.03.tar.gz
Date: Thu, 22 Jan 1998 13:37:23 -0800	[thread overview]
Message-ID: <199801222137.NAA24653@fir.engr.sgi.com> (raw)
In-Reply-To: <34C7AE9F.25A38E49@wellington.sgi.com>

Alistair Lambie writes:
 > Alex deVries wrote:
 > > 
 > > On Wed, 21 Jan 1998, Mike Shaver wrote:
 > > > Alex deVries wrote:
 > > > I _must_ start working on EFS again.  I assume I've missed the 2.2
 > > > freeze, but I could still help a lot of people by getting off my a** and
 > > > finishing it.  My apologies to those who are waiting on it.
 > > 
 > > Let me know if I can help.
 > > 
 > > Here's a question:  is it possible to boot off of the local disk without
 > > the image being on an EFS partition? Will I ever be able to have my
 > > machine have no EFS partition? How will ARC find the image?
 > > 
 > Couldn't we just put the vmlinux in the volume header and load it from
 > there....in fact you probably wouldn't even need sash.  Use dvhtool under irix
 > to add the image.  You may need to make a bigger volume header to fit it.  I'm
 > not 100% sure if this will work, but it's worth a try.
...

       vmlinux probably will not fit without repartitioning.  Also, except
for early development, that is pretty tedious.  I would assume that production
Indy linux systems would have just the volume header and linux partitions,
with no IRIX.  

  reply	other threads:[~1998-01-22 21:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-21 18:59 root-be-0.03.tar.gz Alex deVries
1998-01-21 19:38 ` root-be-0.03.tar.gz Mike Shaver
1998-01-21 20:26   ` root-be-0.03.tar.gz Alan Cox
1998-01-21 20:26     ` root-be-0.03.tar.gz Alan Cox
1998-01-22  6:04   ` root-be-0.03.tar.gz Alex deVries
1998-01-22  6:11     ` root-be-0.03.tar.gz Mike Shaver
1998-01-22 12:04       ` root-be-0.03.tar.gz Oliver Frommel
1998-01-22 18:18         ` root-be-0.03.tar.gz William J. Earl
1998-01-23  3:57         ` root-be-0.03.tar.gz ralf
1998-01-23 17:43           ` root-be-0.03.tar.gz William J. Earl
1998-01-23 22:24           ` root-be-0.03.tar.gz Thomas Bogendoerfer
1998-01-24 13:16             ` root-be-0.03.tar.gz ralf
1998-01-25 11:47               ` root-be-0.03.tar.gz Thomas Bogendoerfer
1998-01-22 10:29     ` root-be-0.03.tar.gz Alan Cox
1998-01-22 10:29       ` root-be-0.03.tar.gz Alan Cox
1998-01-22 20:39     ` root-be-0.03.tar.gz Alistair Lambie
1998-01-22 21:37       ` William J. Earl [this message]
1998-01-22 22:18         ` root-be-0.03.tar.gz Alistair Lambie

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=199801222137.NAA24653@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=alambie@wellington.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