From: Matthew Wilcox <matthew@wil.cx>
To: Alex deVries <alex@linuxcare.com>
Cc: "Phillip D. Beal" <pdbeal@louisville.edu>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 715/80 problem
Date: Sun, 14 Jan 2001 20:13:56 +0000 [thread overview]
Message-ID: <20010114201356.A32402@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3A61F329.5E315E9F@linuxcare.com>; from alex@linuxcare.com on Sun, Jan 14, 2001 at 01:42:49PM -0500
On Sun, Jan 14, 2001 at 01:42:49PM -0500, Alex deVries wrote:
> "Phillip D. Beal" wrote:
> > Well, the odd thing is that the network setup works fine for a 735 and
> > 755, but not the 715. But wait, you said a 715 uses bootp not rboot,
> > and I know the 735 and 755 use the rbootd and can boot from my network
> > setup.
>
> Wait! I said that 715/new uses bootp, but 715/old uses rbootd.
>
> And I don't believe you when you say that your 735 and 755 netboot
> properly. I'd be convinced if you showed me both a) the output of
> 'rbootd -d' and b) console output.
why's it so hard to believe he might have rbootd configured correctly,
but have made a typo in his tftpd / bootpd configuration?
Phillip, have you tried using tftp to fetch the image, for example?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-01-14 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 2:37 [parisc-linux] 715/80 problem Phillip D. Beal
2001-01-12 4:40 ` Alex deVries
2001-01-12 10:20 ` Andrew Shugg
2001-01-14 3:35 ` Phillip D. Beal
2001-01-14 6:04 ` Alex deVries
2001-01-14 18:02 ` Phillip D. Beal
2001-01-14 18:42 ` Alex deVries
2001-01-14 20:13 ` Matthew Wilcox [this message]
2001-01-15 14:51 ` Phillip D. Beal
2001-01-15 0:03 ` Grant Grundler
2001-01-15 16:44 ` [parisc-linux] Booting C100 Greg Ingram
2001-01-15 17:29 ` Grant Grundler
2001-01-15 17:57 ` Greg Ingram
2001-01-15 18:58 ` Grant Grundler
2001-01-15 19:22 ` Greg Ingram
2001-01-15 19:57 ` Ryan Bradetich
2001-01-15 23:50 ` Grant Grundler
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=20010114201356.A32402@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=alex@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=pdbeal@louisville.edu \
/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