From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: Upgrading ultrapenguin to rh-5.1
Date: Tue, 30 Jun 1998 09:23:31 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222357631049@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222357631048@msgid-missing>
>
> I'm considering an upgrade of ultrapenguin-1.0.9 to RedHat-5.1 -- any
> particular pitfalls I should watch out for ? Would redhat's standard
> upgrade procedure work ?
It depends if you have a 32bit SPARC or 64bit. If the latter, then you
cannot do that.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.106 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________
next prev parent reply other threads:[~1998-06-30 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-30 9:08 Upgrading ultrapenguin to rh-5.1 Jan Rychter
1998-06-30 9:16 ` David S. Miller
1998-06-30 9:23 ` Jakub Jelinek [this message]
1998-06-30 14:56 ` Jan Rychter
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-90222357631049@msgid-missing \
--to=jj@sunsite.ms.mff.cuni.cz \
--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.