Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: shaver@neon.ingenia.ca, miguel@nuclecu.unam.mx, ariel@sgi.com,
	linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sat, 16 Aug 1997 22:33:17 +0200 (MET DST)	[thread overview]
Message-ID: <199708162033.WAA20565@informatik.uni-koblenz.de> (raw)
In-Reply-To: <m0wzheO-0005FiC@lightning.swansea.linux.org.uk> from "Alan Cox" at Aug 16, 97 01:08:12 pm

> > If I stick all the RH stuff in an initrd and then they do FTP install,
> > then they should be able to use it via boot /vmlinux or boot -f
> > bootp()..., no?
> 
> 2.1.4x blows up with an initrd - hopefully fixed in 2.1.50/soon but that
> means the SGI one will corrupt and explode atm

There are also additional MIPS bugs in the RAMdisk / initrd stuff.
Shame on me, I have not used (-> debugged) it since the new style
ramdisk code was merged ...

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: shaver@neon.ingenia.ca, miguel@nuclecu.unam.mx, ariel@sgi.com,
	linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sat, 16 Aug 1997 22:33:17 +0200 (MET DST)	[thread overview]
Message-ID: <199708162033.WAA20565@informatik.uni-koblenz.de> (raw)
Message-ID: <19970816203317.FVeqy7ojvXHBqsEORjFZEXfMTUlhVMjCvgOZ1sQ2ISo@z> (raw)
In-Reply-To: <m0wzheO-0005FiC@lightning.swansea.linux.org.uk> from "Alan Cox" at Aug 16, 97 01:08:12 pm

> > If I stick all the RH stuff in an initrd and then they do FTP install,
> > then they should be able to use it via boot /vmlinux or boot -f
> > bootp()..., no?
> 
> 2.1.4x blows up with an initrd - hopefully fixed in 2.1.50/soon but that
> means the SGI one will corrupt and explode atm

There are also additional MIPS bugs in the RAMdisk / initrd stuff.
Shame on me, I have not used (-> debugged) it since the new style
ramdisk code was merged ...

  Ralf

  parent reply	other threads:[~1997-08-16 20:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-15 20:17 boot linux - wish Ariel Faigon
1997-08-15 20:17 ` Ariel Faigon
1997-08-15 20:23 ` Mike Shaver
1997-08-15 21:47   ` Miguel de Icaza
1997-08-15 22:03     ` Alex deVries
1997-08-16  1:05     ` Mike Shaver
1997-08-16  1:05       ` Mike Shaver
1997-08-16 12:08       ` Alan Cox
1997-08-16 12:08         ` Alan Cox
1997-08-16 14:15         ` Mike Shaver
1997-08-16 14:15           ` Mike Shaver
1997-08-16 20:33         ` Ralf Baechle [this message]
1997-08-16 20:33           ` Ralf Baechle
1997-08-15 20:38 ` Alex deVries
1997-08-15 20:53   ` Mike Shaver
1997-08-15 20:53     ` Mike Shaver
1997-08-15 20:59     ` Alex deVries
1997-08-19 10:38     ` Oliver Frommel
1997-08-15 21:46   ` Miguel de Icaza
1997-08-16  5:08     ` Eric Kimminau
1997-08-16  6:18       ` Ralf Baechle
1997-08-16  6:18         ` Ralf Baechle
1997-08-16 20:25       ` Miguel de Icaza
1997-08-16 21:54         ` Vincent Renardias
1997-08-16 22:07           ` Ralf Baechle
1997-08-16 22:07             ` Ralf Baechle
1997-08-17 12:33             ` Alan Cox
1997-08-17 12:33               ` Alan Cox
1997-08-18  4:25     ` Kernel with working initrd? Alex deVries
1997-08-19  1:37     ` Current problems Alex deVries

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=199708162033.WAA20565@informatik.uni-koblenz.de \
    --to=ralf@mailhost.uni-koblenz.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ariel@sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=miguel@nuclecu.unam.mx \
    --cc=shaver@neon.ingenia.ca \
    /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