Subject: Re: amd64 stable for production ?
To: None <netbsd-users@netbsd.org>
From: matthew sporleder <msporleder@gmail.com>
List: netbsd-users
Date: 12/12/2006 09:21:28
On 12/12/06, Gilles Gravier <Gilles@gravier.org> wrote:
> Hi!
>
> Christos Zoulas wrote:
> > On Dec 12, 10:46am, Gilles@Gravier.org (Gilles Gravier) wrote:
> > -- Subject: Re: amd64 stable for production ?
> >
> >
> > No, but I needed a 64 bit grep, awk, sed, sort, etc... I just think that all
> > the applications that have the potential to use a lot of memory should be
> > 64 bit.
> >
> > | I think Solaris counts very well.
> >
> > Yes, if your needs are modest.
> >
> Like 50% of the worlds air traffic control run on Solaris. How much of
> what's left runs on NetBSD?
>
> Yep... modest needs... definitely.
>
> I guess I've posted my last comment on this thread.
>


As a solaris admin, I feel like I should defend here.  :)
I've been bitten by 32-bit grep/strings/less/awk/etc before, but
-some- of their shells tools are available in 64-bit mode in
/usr/bin/sparcv9.

ls:             ELF 64-bit MSB executable SPARCV9 Version 1,
dynamically linked, stripped
(for really full directories)
sort:           ELF 64-bit MSB executable SPARCV9 Version 1,
dynamically linked, stripped
(for really big files)
uptime:         ELF 64-bit MSB executable SPARCV9 Version 1,
dynamically linked, stripped
(for really, really long-running systems)

However, the world's air traffic control is -hopefully not- running on
shell scripts, so is that really an argument?

If NetBSD is 64-bit capable, I think it should go there so you can get
the full benefit of your hardware.  If it slows down some of your
tools, compile them 32 bit yourself or file a pr and request
optimization.  There are probably tricks to make things work faster
both ways.