From: MattS@ilx.com
To: ultralinux@vger.kernel.org
Subject: RE: Now that UltraLinux is Dead
Date: Wed, 28 Apr 1999 15:20:30 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92531335805246@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92531177003080@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]
well, that's what I meant :) UltraPenguin. Not UltraLinux.. Sorry.. My
mistake..
> -----Original Message-----
> From: Jakub Jelinek [SMTP:jj@sunsite.ms.mff.cuni.cz]
> Sent: Wednesday, April 28, 1999 11:20 AM
> To: MattS@ilx.com
> Cc: ultralinux@vger.rutgers.edu
> Subject: Re: Now that UltraLinux is Dead
>
> > Everyone seems to be shocked and/or dismayed that the UltraLinux project
> is
> > no more..Since this decision has already been made, and seems
> unchangeable,
> > I would like to turn to more practical matters and thank everyone who
> > contributed to the project. I haven't been using UP for very long, but
> the
> > experience I had was a very positive one, and I just bought two Old
> Sparc's
> > to hack on because I enjoyed working w/ linux on the sparc so much.
>
> UltraLinux project is definitely not dead, so you don't have to be
> shocked.
> We'll definitely continue working on Linux for SPARC machines (be it
> kernel
> work or userland stuff). The issue is just I spent quite a few hours a
> week
> maintaining a distribution, and those hours will be better spent hacking
> kernel, X servers, 64bit userland and other things.
>
> UltraPenguin was a distribution created so that users can easily try out
> what we hacked on. In 1.0, it was just a few packages changed against
> RedHat
> 4.2, 1.1 was a bunch of changes because at the time we created it there
> was
> no glibc based distribution for SPARCs, then RedHat came with glibc based
> 5.1 and later 5.2 and UltraPenguin 1.1.9 was that plus a bunch of changes
> we
> did during the time. Now it does not make sense to keep maintaining the
> whole distribution any longer. What we hack up will either David publish
> as
> RedHat errata (if it will be important bugfix), or we can publish it on my
> ftp site, but still as a single rpm or a couple of rpms you update into
> your
> distribution. And the upcoming changes like finally a real 64bit userland
> will hopefully appear in any distribution you will choice, be it RedHat
> X.Y
> or Debian Z.W.
>
> 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)
> ___________________________________________________________________
[-- Attachment #2: Type: text/html, Size: 5007 bytes --]
prev parent reply other threads:[~1999-04-28 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 15:01 Now that UltraLinux is Dead MattS
1999-04-28 15:19 ` Jakub Jelinek
1999-04-28 15:20 ` MattS [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-92531335805246@msgid-missing \
--to=matts@ilx.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.