From: Olaf Zaplinski <olaf.zaplinski@web.de>
To: linux-mips@oss.sgi.com
Subject: Re: FAQ/
Date: Sun, 17 Dec 2000 02:39:23 +0100 [thread overview]
Message-ID: <3A3C194B.5E85C4CE@web.de> (raw)
In-Reply-To: 20001217020043.B29250@lug-owl.de
Huh, I don't expect comfort. But I expect a x68 Linux users guide to the
world of MIPS systems. Okay, I know my RM 200 quite well, had compiled
several progs under Sinix, put it in LE mode and installes WinNT 4.0. I use
Linux since the 0.something kernel. The problem is that the Debian WWW site
consists of lots of "404" errors. On the ftp site there is no docu at all
that would tell me how to proceed. For Hardhat, I have found this
information.
What I want: a documentation of the form:
- how to prepare your bootp server
- how to boot the kernel via bootp
- how to start some install script *or* boot your mini-dist/root-fs via NFS,
fdisk, cp and enjoy
That would be enough.
Olaf
Jan-Benedict Glaw wrote:
>
> On Sun, Dec 17, 2000 at 01:37:34AM +0100, Olaf Zaplinski wrote:
> > Where do I find it? I saw the debian-mipsel dist on ftp.rfc822.org, but as
> > there is no doc at all, this dist is unusuable... perhaps I am lucky with
> > that, I strongly dislike the Debian dist.
>
> Btw, what kind of doc do you expect? The MIPS port is, well, everything
> but a "customer linux" right now. It's more-or-less working for
> people who know what they do. There's no installer comparable to
> a regular PC installation (insert boot CDROM, press enter sometimes,
> ready). Everything you can expect is a tarball, which can be
> mounted via nfsroot. There you can find a kernel inside which you
> can boot over bootp/tftp (or via mop, if you have not so much luck).
> Then, you can locally fdisk/mkfs/mount your HDDs and copy everything
> by hand. That's the installation.
>
> Anything else still needs to be written. I've started an approach
> of a clean debian root filesystem (ftp.lug-owl.de) you may want
> to try. However, Debian is currently the only distribution supporting
> those machines at all. The declinux image is heavily outdated and
> ships a totally broken libc with it... It's no fun!
>
> MfG, JB"Nur die Harten komm'n in'n Garten, alle Weichen geh'n in Teich!"G
> PS: http://oss.sgi.com/mips/mips-howto.html
>
> --
> Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
> /* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
> keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
> "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
>
> ----------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
next prev parent reply other threads:[~2000-12-17 1:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 23:08 FAQ/ Olaf Zaplinski
2000-12-13 12:57 ` FAQ/ Florian Lohoff
2000-12-17 0:37 ` FAQ/ Olaf Zaplinski
2000-12-17 0:41 ` FAQ/ Jan-Benedict Glaw
2000-12-17 1:00 ` FAQ/ Jan-Benedict Glaw
2000-12-17 1:29 ` FAQ/ H.Heinold
2000-12-17 2:34 ` FAQ/ Ralf Baechle
2000-12-17 6:50 ` FAQ/ Jan-Benedict Glaw
2000-12-17 9:03 ` FAQ/ Karsten Merker
2000-12-17 9:21 ` FAQ/ Harald Koerfgen
2000-12-17 15:28 ` FAQ/ Ralf Baechle
2000-12-17 17:19 ` FAQ/ Klaus Naumann
2000-12-17 18:24 ` FAQ/ Ralf Baechle
2000-12-17 18:32 ` FAQ/ Vince Weaver
2000-12-17 19:34 ` FAQ/ Warner Losh
2000-12-17 19:33 ` FAQ/ Warner Losh
2000-12-18 10:59 ` FAQ/ Florian Lohoff
2000-12-17 1:39 ` Olaf Zaplinski [this message]
2000-12-17 6:57 ` FAQ/ Jan-Benedict Glaw
2000-12-17 11:14 ` FAQ/ Karel van Houten
2000-12-17 11:14 ` FAQ/ Karel van Houten
2000-12-17 11:12 ` FAQ/ Karel van Houten
2000-12-17 14:32 ` FAQ/ H.Heinold
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=3A3C194B.5E85C4CE@web.de \
--to=olaf.zaplinski@web.de \
--cc=linux-mips@oss.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