From: "Collin Baillie" <collin@xorotude.com>
To: linux-mips@linux-mips.org
Subject: Re: Help with MOP network boot install on DECstation 5000/240
Date: Wed, 14 Jul 2004 14:57:52 +0800 [thread overview]
Message-ID: <000e01c4696f$f65cf4f0$0a9913ac@swift> (raw)
In-Reply-To: 20040713080320.GC18841@lug-owl.de
> [Thanks for *not* hijacking threads]
Sorry *blush*
> So it seems to try to get a file some times and gives up on it.
Oh.. I think it asks for the file, but the mopd server is not sending it. I
am only guessing though.
> Maybe you'd try Debian's install image?
Maybe, but on a _shared_ 31.2k dialup link, it takes a while to download...
and other people tend to get upset... I am using jigdo to get the 4 - 6 ISO
images.. if there's a better (smaller / faster to download) method, I'd love
to hear about it. I really would like to get to know Debian as I'm a
Slackware man and have had to use RedHat at work.. Debian would be another
nice addition to my Linux skillset.
> By the way, which mopd are you using? There are several of them around,
> some quite unuseable...
Umm.. 2.5.3. I downloaded one from linux-mips.org, and applied all the
patches in the order listed in the spec file, but it doesn't compile. So I
compiled another 2.5.3 (79k as opposed to the 48k tgz file I got from
linux-mips.org) and it compiles and responds, but still no file transfer. (I
am compiling/running on i386 arch, so I am wondering if all those patches
are necessary...)
I've read that MOP images usually have some special header in them (NetBSD
website) and someone mentioned that mopd-linux will fudge those headers if
the kernel doesn't have them... or something...
I am perservering with it, and will eventually get there... but for now, I
just thought someone might have more of a clue than I do.
Thanks,
Collin Baillie
next prev parent reply other threads:[~2004-07-14 6:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 18:50 Strange, strange occurence S C
2004-07-10 7:33 ` Niels Sterrenburg
2004-07-10 10:04 ` Ralf Baechle
2004-07-12 15:16 ` Kevin D. Kissell
2004-07-12 15:16 ` Kevin D. Kissell
2004-07-13 0:33 ` Ralf Baechle
2004-07-13 7:49 ` Help with MOP network boot install on DECstation 5000/240 Collin Baillie
2004-07-13 8:03 ` Jan-Benedict Glaw
2004-07-14 6:57 ` Collin Baillie [this message]
2004-07-14 9:54 ` Maciej W. Rozycki
2004-07-14 12:44 ` Jan-Benedict Glaw
2004-07-14 12:51 ` Maciej W. Rozycki
2004-07-14 13:30 ` Jan-Benedict Glaw
2004-07-15 11:33 ` Maciej W. Rozycki
2004-07-14 12:43 ` Jan-Benedict Glaw
2004-07-16 14:41 ` Collin Baillie
2004-07-16 15:04 ` Jan-Benedict Glaw
2004-07-16 15:13 ` Maciej W. Rozycki
2004-07-16 15:08 ` Maciej W. Rozycki
2004-07-16 16:31 ` Thiemo Seufer
2004-07-16 16:51 ` Maciej W. Rozycki
2004-07-16 18:56 ` Thiemo Seufer
2004-07-13 15:31 ` Strange, strange occurence Kevin D. Kissell
2004-07-13 15:31 ` Kevin D. Kissell
2004-07-14 12:02 ` Maciej W. Rozycki
2004-07-14 16:35 ` Dominic Sweetman
2004-07-14 17:45 ` Michael Uhler
2004-07-14 17:45 ` Michael Uhler
2004-07-15 1:34 ` Atsushi Nemoto
2004-07-15 1:53 ` Ralf Baechle
2004-07-16 12:24 ` Ralf Baechle
2004-07-16 16:05 ` Atsushi Nemoto
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='000e01c4696f$f65cf4f0$0a9913ac@swift' \
--to=collin@xorotude.com \
--cc=linux-mips@linux-mips.org \
/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