From: Jude DaShiell <jdashiel@shellworld.net>
To: <blinux-list@redhat.com>
Subject: Re: red hat system almost talking
Date: Tue, 11 Sep 2001 20:18:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.33.0109112013510.13682-100000@ns.shellworld.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0109091457070.1105-100000@rupin.localnet>
Okay, this may work. I found out I was using the red hat distribution
kernel since it had porky near the top of it for a descriptor string for
where it was compiled. I got some help from Bill over the phone and
downloaded his version of vmlinuz-2.2.16-22 and tried updating the kernel.
This download was done with ncftpget and unfortunately turned out to be
corrupted. Maybe we can get brick numbers for all files and do downloads
in future and compare brick numbers. This doesn't guarrantee a perfect
file download, but does make it more likely. I tried a coupld other
things and managed to trash /boot. So it's reinstall time again but this
time should be easier.
Jude <jdashiel@shellworld.net>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Mike Gorse
` red hat system almost talking: question related to comments Cheryl Homiak
` Jude DaShiell
` Janina Sajka
` Cheryl Homiak
` S. Massy
` red hat system almost talking L. C. Robinson
` Jude DaShiell
` L. C. Robinson
` Jude DaShiell [this message]
` Janina Sajka
` Janina Sajka
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.BSF.4.33.0109112013510.13682-100000@ns.shellworld.net \
--to=jdashiel@shellworld.net \
--cc=blinux-list@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).