From: Tethys <tethys@ml.com>
To: ultralinux@vger.kernel.org
Subject: Upgrade from RH4.2?
Date: Wed, 20 May 1998 16:17:16 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356531058@msgid-missing> (raw)
It is possible to upgrade from RedHat 4.2 to UltraPenguin? I need
to use my machine on a day to day basis for work, and don't want
to risk a complete reinstall. However, some things about RH4.2 are
proving to be a real problem -- the lack of a working gdb springs
to mind. I've recompiled from source, too, but that still doesn't
fix it. There are other problems too (e.g., buggy X server that I
can't debug due to 1. lack of time and 2. lack of a debugger!)
Will the change from libc5 to glibc2 be enough to make an upgrade
more hassle than it's worth?
It's an SS20/HyperSparc with dual CG6 framebuffers. I'll probably
wait for ultrapenguin-devel to become ultrapenguin-current, first
(assuming it doesn't take too long!).
Tet
--
``Live free or die; death is not the worst of evils'' - General George Stark
--------------------+--------------+----------------------------------------
tethys@ml.com | Micro$oft: | Linux, the choice of a GNU generation.
tet@astradyne.co.uk | Just say no! | See http://www.uk.linux.org for details
reply other threads:[~1998-05-20 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-90222356531058@msgid-missing \
--to=tethys@ml.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.