Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux@cthulhu.engr.sgi.com
Subject: initrd is working and new test image
Date: Sat, 13 Mar 1999 13:19:44 +0100	[thread overview]
Message-ID: <19990313131944.A809@alpha.franken.de> (raw)

Hi,

since there are still some people out there, who have problems with
Linux/MIPS on their Indys, I was looking for way to rule out more
setup problems. One way is to get initrd working for Linux/MIPS,
so setting up the nfs root directory won't be necessary anymore.
I hope Puffin will get some time to get us a more decent RedHat
installer.

To build a kernel with an initrd, you need configure initrd into your
kernel, then make boot (right now it works only with ecoff kernels) 
and use arch/mips/boot/addinitrd to combine vmlinux.ecoff with your initrd.

For now, I've built a new kernel with an attached initrd. This initrd
contains a shell (ash) and some utilities (ls, mount, etc.) plus the
needed shared libraries. When you boot this kernel, you should see
the message will "Welcome to Linux/MIPS" and should be dropped into a single 
user shell.

So people with the problem seeing only "Freeing unused kernel memory",
please try it, and report your experiences.

I hope to get the kernel uploaded before monday (depends how crappy the line
to ftp.linux.sgi.com this time is). You can find it

ftp://ftp.linux.sgi.com/pub/linux/mips/test/vmlinux-indy-initrd-990313.gz

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-03-14 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-13 12:19 Thomas Bogendoerfer [this message]
1999-03-16 11:59 ` initrd is working and new test image Tom Woelfel
1999-03-16 20:52   ` 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=19990313131944.A809@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --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