linux-mips
[Top] [All Lists]

Re: FAQ/

To: linux-mips@oss.sgi.com
Subject: Re: FAQ/
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date: Sun, 17 Dec 2000 07:57:53 +0100
In-reply-to: <3A3C194B.5E85C4CE@web.de>; from olaf.zaplinski@web.de on Sun, Dec 17, 2000 at 02:39:23AM +0100
Mail-followup-to: linux-mips@oss.sgi.com
References: <3A36AFFE.51C9F2B@web.de> <20001213135723.B3060@paradigm.rfc822.org> <3A3C0ACE.8A13EA97@web.de> <20001217020043.B29250@lug-owl.de> <3A3C194B.5E85C4CE@web.de>
Reply-to: jbglaw@lug-owl.de
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Sun, Dec 17, 2000 at 02:39:23AM +0100, Olaf Zaplinski wrote:
> - how to prepare your bootp server

Install bootp (or dhcpd, which can do bootp as well) and read its
documentation.

> - how to boot the kernel via bootp

This is specific to your machine's firmware.

> - how to start some install script *or* boot your mini-dist/root-fs via NFS,
> fdisk, cp and enjoy

less  ./linux/Documentation/nfsroot.txt

~~VeryShortVersion~~:
- Activate "IP Auto Configuration" in "Networking Options"
- Build NFS directly into your kernel; there, also activate NFS-Root
  support
- "root=/dev/nfs" as one command option when booting the kernel (this
  is the easyest method). Then, the client mounts /tftpboot/<IP-Addr>
  from the server which did the bootp reply. Otoh, you could
  configure your bootp server to provide a different boot server
  or boot path.

fdisk and cp (btw, you should better use tar in a pipe for that...)
should be no problem...

MfG, JBG

-- 
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)

Attachment: pgpo7LIzM1hxr.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>