From: Jan Rychter <jwr@icm.edu.pl>
To: ultralinux@vger.kernel.org
Subject: Re: Upgrading ultrapenguin to rh-5.1
Date: Tue, 30 Jun 1998 14:56:25 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222357631052@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222357631048@msgid-missing>
>>>>> "David" = David S Miller <davem@dm.cobaltmicro.com>:
>> 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 ?
Jakub> It depends if you have a 32bit SPARC or 64bit. If the latter,
Jakub> then you cannot do that.
David> Also even for 32-bit sparc, you will lose a number of bug fixes
David> we have done which I wasn't able to merge into rh's 5.1 rpms in
David> time.
So basically, what you're saying is that I should stick to ultrapenguin
as it will always be more up to date than RedHat ?
BTW, at the moment I only use it on an Ultra, but I also have two 32bit
machines to upgrade from RH4.2.
--J.
prev parent reply other threads:[~1998-06-30 14:56 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
1998-06-30 14:56 ` Jan Rychter [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-90222357631052@msgid-missing \
--to=jwr@icm.edu.pl \
--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.