From: Randy McCaskill <rmccask@comm-data.com>
To: ultralinux@vger.kernel.org
Subject: Re: Ultralinux tftp boot on an SS2?
Date: Fri, 12 Jun 1998 03:57:26 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222357631008@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222357631003@msgid-missing>
Here is the tftpboot file I used with a sparc 2. Try it and see if it
works for you.
http://www.comm-data.com/~rmccask/ultrapenguin-1.0.9-tftpboot.img
I think that the install script is built into the tftpboot file as a
ramdisk so the one from RH4.2 will probably choke. It is possible that
the one I have above might not be completely thrilled with any changes
that have been made since I grabbed it, but I suspect that it will work.
-Randy
On Thu, 11 Jun 1998, Lars Kellogg-Stedman wrote:
> The problem looks like it's part of the tftpboot process...I'm booting
> off a Mac running LinuxPPC (tried it with kernel 2.1.103 and 2.1.24);
> according to a tcpdump of the install process the tftp fetch hanging
> close to the end with the client (the machine I'm trying to install on)
> repeatedly ACKing the server.
>
> I *can* get the standard RH4.2/sparc install to boot. Is there any
> chance I can use the older installer with the Ultralinux distribution?
>
> Thanks,
>
> -- Lars
>
> --
> Lars Kellogg-Stedman * lars@bu.edu * (617)353-8277
> Office of Information Technology, Boston University
------
Randy McCaskill
rmccask@comm-data.com ! Poodle... The other white meat.
http://www.comm-data.com/~rmccask/ ! -- Sherman's Lagoon
prev parent reply other threads:[~1998-06-12 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-11 20:21 Ultralinux tftp boot on an SS2? Lars Kellogg-Stedman
1998-06-11 20:35 ` Randy McCaskill
1998-06-12 2:24 ` Lars Kellogg-Stedman
1998-06-12 3:57 ` Randy McCaskill [this message]
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=marc-linux-ultrasparc-90222357631008@msgid-missing \
--to=rmccask@comm-data.com \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.