From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: status of UltraPenguin?
Date: Sun, 18 Oct 1998 15:59:21 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90873041330746@msgid-missing> (raw)
>
> Hello Jakub,
>
> the UltraPenguin home page mentions -for some time already- the release
> of a final release (followup on 1.0.9) "soon".
>
> Could you inform me about the status? Will it be on hold for a 2.2 kernel?
Ok, this is not the first question, so I'll answer to everybody.
I thought 1.1 will come soon after 1.0.9, but during the time we were
fighting little bugs in 1.0.9, redhat came with 5.1, so I have mistakenly
merged a few packages and the result is some broken things in the
distribution, me already not knowing which rpms have changed from stock
redhat and which not (and why).
So, I've started two days ago with boot images, which I'm merging from
current sparc rawhide with UP changes (and enhancing it, so it will finally
autoprobe all sbus SCSI/NET cards and stuff like that). After that's done,
I'll take a snapshot from rawhide as of a particular date and go one package
by one and create a new distribution based on merge of rawhide with 1.0.9.
I think I'm gonna to call that 1.0.10, then ask people to test it and
release 1.1 quickly.
A couple of things I want to have:
the compiler will be egcs-current (ie. later than 1.1b, as major SPARC
backend rewrite happened after 1.1b). The compiler will be 64/32bit, like
binutils, so we'll drop sparc64-linux-* compilers/binutils.
I want to ship both libstdc++ 2.8 and 2.9, our UP rpms will use 2.9, but you
should be able to install e.g. netscape which relies on 2.8.
If people help me, I'd like to maintain full binary compatibility with
redhat 4.2/sparc (the dynamic loader UP 1.0.9 should be just fine, just we
need to have more dynamic libraries).
The kernel corruption bug is gone, so once I finish merging boot images,
I'll put there new kernels and come out with tftp/floppy images for both to
be done 1.0.10 and 1.0.9. After 1.0.10 is on ftp, I plan do test CD-ROM
images (or even earlier), I have still not decided whether to put the whole
600M or whatever iso image on ftp, or put up some nice scripts somewhere, or
ask somebody to press a bunch of CDs...
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.125 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________
next reply other threads:[~1998-10-18 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-18 15:59 Jakub Jelinek [this message]
1998-10-19 1:52 ` status of UltraPenguin? Brandon S. Allbery
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-90873041330746@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.