From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: Mach64 problems in UltraPenguin 1.1.9
Date: Tue, 27 Apr 1999 14:16:05 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92522264607830@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92522154306389@msgid-missing>
>
> While I'm mentioning this, I want to officially announce that we're
> stopping general maintenance of UltraPenguin. It is just too much
> duplicated work for Jakub and myself to keep both RedHat and
> UltraPenguin working and up to date at the same time.
Heh, I wanted to announce that today too.
As most of the differences between RedHat 5.2 and UltraPenguin 1.1.9 have
been merged into RedHat 6.0 (at the moment I can think of tape installation
only which did not make it in, but maybe I forgot something), it really has
no sense to go for UltraPenguin 1.2. Use RedHat 6.0 instead.
Maybe we'll still use UltraPenguin in the future as a testbed for some SPARC
hacks, but at the moment consider it as a distribution with historical value
only.
I'll put in some README explaining this.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux | http://ultra.linux.cz/ | http://ultra.penguin.cz/
Linux version 2.2.5 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________
next prev parent reply other threads:[~1999-04-27 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-27 13:58 Mach64 problems in UltraPenguin 1.1.9 Steve Dunham
1999-04-27 14:11 ` David Miller
1999-04-27 14:14 ` Edwin Kremer
1999-04-27 14:16 ` Jakub Jelinek [this message]
1999-04-27 14:17 ` Steve Dunham
1999-04-27 14:54 ` Edwin Kremer
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-92522264607830@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.