From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Re: FAQ/
Date: Sun, 17 Dec 2000 07:57:53 +0100 [thread overview]
Message-ID: <20001217075752.B5352@lug-owl.de> (raw)
In-Reply-To: <3A3C194B.5E85C4CE@web.de>; from olaf.zaplinski@web.de on Sun, Dec 17, 2000 at 02:39:23AM +0100
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
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 #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2000-12-17 6:58 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 ` FAQ/ Olaf Zaplinski
2000-12-17 6:57 ` Jan-Benedict Glaw [this message]
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=20001217075752.B5352@lug-owl.de \
--to=jbglaw@lug-owl.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