From: Chad Carlin <chad@roctane.dallas.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: New to Linux
Date: Mon, 23 Nov 1998 14:38:37 -0600 [thread overview]
Message-ID: <3659C7CD.1B134991@roctane.dallas.sgi.com> (raw)
In-Reply-To: 19981105031325.P359@uni-koblenz.de
Help.
Here is what I have:
Indy: R4k indy w/ a 1GB and a 500MB disk. I have an external 9GB from my
other system that I am temorarily (I hope) using to boot IRIX on my Linux
Indy.
Software:
Linux-installer-0.2.tar
root-be-0.04.cpio
SRPMS
vmlinux-indy-2.1.99.tar.gz
instructions
I read the instructions. The one with all of the tftp and nfs setup. Is
this for after I boot Linux, so I can install the rest of the software?
BTW I tested this by booting miniroot from my other Indy.
I also read the INSTALL instructions. I was able to successfully: ./mke2fs
drive, ./installer drive, cjwsh> MAKEDEV, cpio root-be-0.04.cpio, and
./e2fsck -fy drive. Finally I did the, gzip -dc vmlinux.gz > /vmlinux. All
of this went OK.
It's the "boot vmlinux root=/dev/sda0" that makes the indy panic! Do I do
this from PROM or sash? I don't think that I can read the efs filesystem
without sash. Is there a better way to determine what device my e2fs root
filesystem is at?
Tell me if I'm getting this proceedure right.
1)Boot vmlinux kernel and mount e2fs filesystem as /.
2)Use tftp to install the stuff that I downloaded in the SRPMS directory.
3)Somehow I will end up with a system that can boot without having IRIX on
a local disk.
BTW is there anyway to mount this e2fs filesystem from with IRIX?
Thanks for any and all input. Flame me if you must.
Chad
prev parent reply other threads:[~1998-11-23 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-31 2:28 Linus is down ? (fwd) Ariel Faigon
1998-10-31 2:28 ` Ariel Faigon
1998-11-05 2:13 ` ralf
1998-11-23 20:38 ` Chad Carlin [this message]
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=3659C7CD.1B134991@roctane.dallas.sgi.com \
--to=chad@roctane.dallas.sgi.com \
--cc=chad@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