Slashdot Mirror

It is also worth noting that Microsoft have had Windows 2000 going through a C2 evaluation for over 18 months with a proper hardware configuration unlike the previous NT 4.0 evaluation.

Prevents:

This sir is mac bong only slightly used I'm only asking 3.50 (say it like tweefiffy, ok?) I'm trying to save up to buy a origin 2000 to grow weed in.

Check this out, it's very interesting.

http://www.sgi.com/features/2001/dec/fleet_numeric al/index.html

http://www.sgi.com/features/2001/jun/weather/

http://www.sgi.com/newsroom/press_releases/2001/ju ne/navy_weather.html

Check this out, it's very interesting.

http://www.sgi.com/features/2001/dec/fleet_numeric al/index.html

http://www.sgi.com/features/2001/jun/weather/

http://www.sgi.com/newsroom/press_releases/2001/ju ne/navy_weather.html

Check this out, it's very interesting.

http://www.sgi.com/features/2001/dec/fleet_numeric al/index.html

http://www.sgi.com/features/2001/jun/weather/

http://www.sgi.com/newsroom/press_releases/2001/ju ne/navy_weather.html

Yikes! Links make it a lot easier for people to figure out what's going on!

"A year ago, there seemed to be two promising Linux HA [high availability] frameworks--along with lots and lots of experimental things: SGI's FailSafe, and Kimberlite from Mission Critical Linux. The FailSafe software website now seems very out of date, although the mailing list remains active, and there seems to be forward momentum. On the other hand, Redhat seems to have forked the development of Kimberlite, calling the fork Redhat Cluster Manager. They don't seem to be making development source available, at least to the public. Are these two projects still relevant? What's the current status of Open Source HA?"

Try also linux-ha.org and open cluster

"until someone actually sends a mission with equipment on board, it's all speculation as to what designs might conceivably be used."

Been there, done that. You can too.

Although I cannot find a specific-cool link at their site, the Human Performance Lab in the Department of Kinesthetics has been doing some mightly cool motion capture and analysis of atheletes, normal people and people with physical limitations for years. Very cool Sun based motion tracking system. My climbing partner in Uni used to be the technician for the capture / analysis systems. They were SPARC systems at the time, from sun.
As other posters have mentioned, motion capture and motion synthesis tend to be very different problems, although in an end product (if it is a rendering) may contain elements of both.
Alias' tools still tend to be some of the better products out there for synthesis. If you are serious about capture, I know that the U of C department would at least be a starting place for software sources. I know that it wasn't an inexpensive setup.

You gotta look for the release overlay (and if you still have a valid support contract, you can download the maintainance overlay, rather than get it by mail) at support.sgi.com. Beware, these overlays are massive.

I sure hope you are right about Alpha or PA-RISC.

Has SGI really gone Itanium? They have waffled on a LOT of things for years now. They kind of went wintel then backed out, then kind of went x86 linux then backed out. Are they planning any new ia-64 products? The 750 is a legacy product and the Pro64 compiler seems to be gone.

I sure hope you are right about Alpha or PA-RISC.

Has SGI really gone Itanium? They have waffled on a LOT of things for years now. They kind of went wintel then backed out, then kind of went x86 linux then backed out. Are they planning any new ia-64 products? The 750 is a legacy product and the Pro64 compiler seems to be gone.

I sure hope you are right about Alpha or PA-RISC.

Has SGI really gone Itanium? They have waffled on a LOT of things for years now. They kind of went wintel then backed out, then kind of went x86 linux then backed out. Are they planning any new ia-64 products? The 750 is a legacy product and the Pro64 compiler seems to be gone.

26^3 = 9 x 10^18 = 9 exabytes

check out the feature list.

According to this page at SGI, XFS supports filesystems that are "9 exabytes" big, which is roughly 1,000,000 terabytes. Under kernel 2.4, the limit is still 2TB, but when the block devices are converted to 64bit, it'll be larger...

You're buying yourself a ticket to disaster if you use Ext2 on "mission critical" servers.
Better use XFS. From the link below you can download a modified Red Hat distribution (just XFS was added to the Red Hat kernel, there's no other change) which allows you to install directly on XFS:

http://oss.sgi.com/projects/xfs/

XFS is the filesystem used by SGI (Silicon Graphics) on their 1024-CPU video servers and supercomputers.

Also, you state: "The $400 high end video cards made by the likes of nvidia outperform most of the 'high end' graphics workstations."

I don't know where you work, but high-end graphics workstations (say, from SGI) far outperform the latest consumer hardware. And don't tell me you said "most" -- you also said "high-end" graphics workstations, so even your little $20k defense counts.

You're right in saying gaming drives the 3D card industry, but it does not LEAD the 3D card industry.

Also, NVidia doesn't make consumer graphics cards.

Troll.

Here's a cool approach from SGI. If only they could do this on PCs...

According to this it's neither, it's an introsort which has O(n log n) worst case performance. Another interresting comparison between C and C++ sorts is given here

Suprised no-one's mentioned the SGI F220. 22-inch widescreen, 1600x1024, video inputs.

Linux clusters were used by Dreamworks to do the images, and SGI Octanes, O2's, and Origins were used for the rendering. SGI's article details it to some extent.

Not to "me too!" this thread, but I also program with the STL on Solaris, and I find it excellent.

I own the STL Tutorial and Reference Guide and Effective STL.

On the web, I use the SGI docs and also the Rogue Wave Docs since the Solaris STL is from Rogue Wave. I find them both adequate for 99% of the programming that I do. The one thing to note on Solaris is that the STL is missing a hash map. The hashmap is technically not part of the STL spec yet, but it most likely will be for the next iteration, and the stlport implementation has one available.

Several people have mentioned one of the downsides being unintelligible error messages. This is true, but I think that (on Solaris anyways) error messages coming from templated code generally suck.

Not to "me too!" this thread, but I also program with the STL on Solaris, and I find it excellent.

I own the STL Tutorial and Reference Guide and Effective STL.

On the web, I use the SGI docs and also the Rogue Wave Docs since the Solaris STL is from Rogue Wave. I find them both adequate for 99% of the programming that I do. The one thing to note on Solaris is that the STL is missing a hash map. The hashmap is technically not part of the STL spec yet, but it most likely will be for the next iteration, and the stlport implementation has one available.

Several people have mentioned one of the downsides being unintelligible error messages. This is true, but I think that (on Solaris anyways) error messages coming from templated code generally suck.

Learn who owns what. Learn how to handle pointers and references in an intelligent manner. Garbage collection is neat but is no substitute for good programming.

Read Those Fine Manuals. See SGI STL Tech Pages for a good online STL reference. Pay particular attention to stated efficiencies. You can use an iterator to loop through any container, but not all containers are created equal.

Get a good compiler. Template and inline code bloat can be minimized by selecting a decent compiler and flags.

You can use things like for_each, but remember you can also use a standard for with iterators.

Erm... set_intersection does precisely this, and in one line too...

Don't read headers to learn STL. Get a good book like Nicolai Josuttis's _The_C++_Standard_Library or visit SGI's STL Site

Don't inherit from an STL container. They are not designed for inheritance (no virtual destructors). Instead, keep your current model and prefer aggregation.

Also, the methods are written along the lines of, "if it's not optimal, you have to write the code yourself." I'm sorry - that sucks. Sometimes I need to remove an element from a Vector. Maybe I should be using another Container. Or maybe the API should allow it, but make it clear in the documentation that it's not efficient. I vote for the latter.

Doesn't the vector::erase method do what you want?

We used the MSDN STL documentation, and while Microsoft's implementation may agree with that API spec, Solaris' certainly didn't. See the signature of the map::delete method for an interesting example.

SGI's reference is excellent. It covers the entire STL standard (the few SGI-specific extensions are clearly marked), and is very well written.

With ext3 filesystem?

http://acl.bestbits.at/

With xfs filesystem?

http://oss.sgi.com/projects/xfs/

Just add samba 2.2.3a that has acl support and stir. What did I need that NT server for again?

Some machines have special hardware features. Usually you can get the same features with a PCI card, but not always. However, this is no longer something you'll see on a consumer-level machine.

SGI is a prime example. They sell some impressive graphics systems that don't have any real competition in the PC or Mac worlds. But these are not toys for individuals -- they're expensive tools that big companies buy, and then only after carefully weighing the alternatives.

Over the years, SGI has tried to market its alternatives to the commodity PC. Kind of pointless -- people who need PCs buy PCs. They did finally wise up to this, but much too late.

There used to be more systems like this (the Amiga is a prime example), but all except the Mac have essentially disappeared. And even the Mac makes little comprimises with the commodity marketplace -- like that obscene PC-compatible keyboard.

If you're thinking that owning a Sun will offer you a novel user experience, forget it. Solaris totally lags behind in UI design. That's why Sun has turned to the GNOME people to help them update it. People buy Sun workstations to run high-performance software -- from the command line!

Whoops! I seem to have ended up totally agreeing with crow. Oh well!

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

It looks like most of the movie industry is still heavily invested in SGI, especially for managing huge amounts of data: Disney, Digital Dream, Industrial Light & Magic, Pixar, Star Wars, South Park, Mummy, Matrix, Academy Awards, Sony Imageworks, Final Fantasy, More Academy Awards, More Pixar, Weta (LOTR), Shrek

SGI were/are doing work on linux on the MIPS Origin 2k machines to prepare for the IA-64 Origin 3k and have linux running on 64 node 128 CPU Origin 2k, see:

http://oss.sgi.com/projects/LinuxScalability/

--paulj

Another good package (although platform limited) is SGI's Teleffect; it allows keyboard/mouse sharing between NT/2K and Irix boxes. It comes bundled with contemporary versions of Irix, don't know about availablility or licensing as a standalone product.

This is really bad news for SGI. I'd heard that DreamWorks was disatisfied with SGI, but they must be totally disillusioned to abandon SGI's famous massively parallel systems in favor of a Linux cluster! Makes you wonder who will buy the Itanium supercomputers SGI is betting its future on.

Hey, don't forget 64-bit Irix, too. (First, too, if you believe their claim.) Is it any surprise Billyware is behind the curve, as usual?

(BTW...the file system monitor tools fam and imon add a feature to Linux that was missing for way too long; generic and instant update of file status for X. This effectively ties the desktop and the current file system state together eliminating the need to 'refresh' an application to find out what's really there. After having this under OS/2 and seeing how poorly it was handled under Windows (9x & NT forks), I was glad to see SGI port and support this for Linux and IRIX (other Unix-like systems can add this support as well if they don't have something like it already).)