From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Sir Ace <chandler@nateng.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Ok all
Date: Sun, 26 Jan 2003 14:52:05 -0700 [thread overview]
Message-ID: <20030126215205.GD28343@dsl2.external.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301252356110.25913-100000@jordan.eng.nateng.com>
On Sun, Jan 26, 2003 at 12:17:31AM -0800, Sir Ace wrote:
> > uhm...what are you building that takes 4 days?
> > Not even glibc or xfree86 takes that long.
>
> On 128 Meg of ram, and 1 100Mhz pa7200, openssl, openssh, 2.4.20 kernel,
> gcc 2.95.3, pine, and several other apps... Remembering things don't
> normally build the first time around, and tweaks must be made...
ok. but you definitely are not building gcc 2.95.3 - we've never used that.
gcc 3.0 is the first release for parisc.
> Ok, then I will give credit to everyone who got it this far, I am happy I
> might be able to get the workstations here in my office off of HP/UX 10.20
> and into this decade, even if I have to setup NFS-root clients to do it.
I've been using b180 w/parisc-linux as desktop/debian mirror for almost
a year now. only thing to crash the box was audio driver and test
kernels. But some things are missing that HPUX has: NetMeeting
support (T.120 specifically; GnomeMeeting supports H323), performance.
grant
next prev parent reply other threads:[~2003-01-26 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 8:17 [parisc-linux] Ok all Sir Ace
2003-01-26 21:52 ` Grant Grundler [this message]
2003-01-28 4:23 ` [parisc-linux] Kernel Sir Ace
2003-01-28 4:24 ` Randolph Chung
2003-01-28 4:30 ` Sir Ace
2003-01-28 4:30 ` Sir Ace
2003-01-28 4:35 ` Sir Ace
2003-01-28 4:54 ` [parisc-linux] kernel hang Sir Ace
2003-01-28 5:08 ` Derek Engelhaupt
2003-01-28 13:23 ` Joel Soete
2003-01-28 20:48 ` Sir Ace
2003-01-29 19:11 ` Sir Ace
2003-01-29 19:24 ` Grant Grundler
2003-01-28 9:07 ` [parisc-linux] Kernel Thibaut VARENE
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=20030126215205.GD28343@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=chandler@nateng.com \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox