From: sah@borf.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] oddity
Date: Thu, 20 Jul 2000 07:28:33 -0400 [thread overview]
Message-ID: <Pine.LNX.4.10.10007200726020.866-100000@linux.borf.com> (raw)
In-Reply-To: <008e01bff1f3$4b540e10$618c1e18@san.rr.com>
Yes, the standalone runs fine. Since the 3c509 was questioned, I put
both i82559's in the test terminal and the auth/cpu server. The
fileserver is using an i82557. Still, the same game.
Sam
On Wed, 19 Jul 2000, Eric Dorman wrote:
> > I've my fileserver and auth/cpu server up now, and am attempting to boot
> > terminals. The terminal sets to boot from ether0, finds its kernel from
> > the network, and starts to boot. It then hangs.
> [xx]
> this sounds like terminal hardware weirdness. i get something similar
> when my ne2000-clone ethernet is somehow screwed up or has the
> wrong irq.
>
> can the terminals run the distribution standalone?
>
> > Sam
>
> --eric
>
>
next prev parent reply other threads:[~2000-07-20 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 14:33 sah
2000-07-20 2:36 ` Eric Dorman
2000-07-20 11:28 ` sah [this message]
2000-07-19 15:54 Russ Cox
2000-07-19 18:15 ` Peter LeBlond
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=Pine.LNX.4.10.10007200726020.866-100000@linux.borf.com \
--to=sah@borf.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).