Slashdot Mirror

The main download page is here:

Download the STL
http://www.sgi.com/tech/stl/download.html

STL v3.3 Source Code, as a tar file
http://www.sgi.com/tech/stl/stl.tar
STL v3.3 Source Code, as a zip file
http://www.sgi.com/tech/stl/stl.zip
STL v3.3 Source Code, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/stl.tar.gz

STL v3.3 Documentation, as a tar file
http://www.sgi.com/tech/stl/STL_doc.tar
STL v3.3 Documentation, as a zip file
http://www.sgi.com/tech/stl/STL_doc.zip
STL v3.3 Documentation, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/STL_doc.tar.gz

C++ I-O library (experimental)
http://www.sgi.com/tech/stl/standard_library.html
C++ I-O library (experimental), as a tar file compressed with gz
http://www.sgi.com/tech/stl/stdlib_20000608.tar.gz
C++ I-O library (experimental), as a zip file
http://www.sgi.com/tech/stl/stdlib_20000608.zip

The main download page is here:

Download the STL
http://www.sgi.com/tech/stl/download.html

STL v3.3 Source Code, as a tar file
http://www.sgi.com/tech/stl/stl.tar
STL v3.3 Source Code, as a zip file
http://www.sgi.com/tech/stl/stl.zip
STL v3.3 Source Code, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/stl.tar.gz

STL v3.3 Documentation, as a tar file
http://www.sgi.com/tech/stl/STL_doc.tar
STL v3.3 Documentation, as a zip file
http://www.sgi.com/tech/stl/STL_doc.zip
STL v3.3 Documentation, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/STL_doc.tar.gz

C++ I-O library (experimental)
http://www.sgi.com/tech/stl/standard_library.html
C++ I-O library (experimental), as a tar file compressed with gz
http://www.sgi.com/tech/stl/stdlib_20000608.tar.gz
C++ I-O library (experimental), as a zip file
http://www.sgi.com/tech/stl/stdlib_20000608.zip

The main download page is here:

Download the STL
http://www.sgi.com/tech/stl/download.html

STL v3.3 Source Code, as a tar file
http://www.sgi.com/tech/stl/stl.tar
STL v3.3 Source Code, as a zip file
http://www.sgi.com/tech/stl/stl.zip
STL v3.3 Source Code, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/stl.tar.gz

STL v3.3 Documentation, as a tar file
http://www.sgi.com/tech/stl/STL_doc.tar
STL v3.3 Documentation, as a zip file
http://www.sgi.com/tech/stl/STL_doc.zip
STL v3.3 Documentation, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/STL_doc.tar.gz

C++ I-O library (experimental)
http://www.sgi.com/tech/stl/standard_library.html
C++ I-O library (experimental), as a tar file compressed with gz
http://www.sgi.com/tech/stl/stdlib_20000608.tar.gz
C++ I-O library (experimental), as a zip file
http://www.sgi.com/tech/stl/stdlib_20000608.zip

The main download page is here:

Download the STL
http://www.sgi.com/tech/stl/download.html

STL v3.3 Source Code, as a tar file
http://www.sgi.com/tech/stl/stl.tar
STL v3.3 Source Code, as a zip file
http://www.sgi.com/tech/stl/stl.zip
STL v3.3 Source Code, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/stl.tar.gz

STL v3.3 Documentation, as a tar file
http://www.sgi.com/tech/stl/STL_doc.tar
STL v3.3 Documentation, as a zip file
http://www.sgi.com/tech/stl/STL_doc.zip
STL v3.3 Documentation, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/STL_doc.tar.gz

C++ I-O library (experimental)
http://www.sgi.com/tech/stl/standard_library.html
C++ I-O library (experimental), as a tar file compressed with gz
http://www.sgi.com/tech/stl/stdlib_20000608.tar.gz
C++ I-O library (experimental), as a zip file
http://www.sgi.com/tech/stl/stdlib_20000608.zip

The main download page is here:

Download the STL
http://www.sgi.com/tech/stl/download.html

STL v3.3 Source Code, as a tar file
http://www.sgi.com/tech/stl/stl.tar
STL v3.3 Source Code, as a zip file
http://www.sgi.com/tech/stl/stl.zip
STL v3.3 Source Code, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/stl.tar.gz

STL v3.3 Documentation, as a tar file
http://www.sgi.com/tech/stl/STL_doc.tar
STL v3.3 Documentation, as a zip file
http://www.sgi.com/tech/stl/STL_doc.zip
STL v3.3 Documentation, as a tar file compressed with gzip
http://www.sgi.com/tech/stl/STL_doc.tar.gz

C++ I-O library (experimental)
http://www.sgi.com/tech/stl/standard_library.html
C++ I-O library (experimental), as a tar file compressed with gz
http://www.sgi.com/tech/stl/stdlib_20000608.tar.gz
C++ I-O library (experimental), as a zip file
http://www.sgi.com/tech/stl/stdlib_20000608.zip

Investor News: SGI Takes Action to Reduce Debt [more]

While Chapter 11 doesn't mean the company is dead (heck, airlines in chapter 11 are even merging these days) it would be very sad to see SGI go. One of the coolest things for me is the single system image computing, for example their Altix single system image supercomputers. High end scientific computing in the US has really thrown its weight behind clustering with off the shelf components (or, in IBM's case, custom components) working together over relatively slow interconnects. While this does work really well for types of problems that can be easily partitioned, not all problems can be easily dispersed. Additionally, many times researchers may not be the most proficient in MPI or other styles of programming that are really key to working well in a clustered system.

Single system image supercomputing offers a way to tackle some problems that can't be partitioned and also to make life easier for scientific programmers who are not well versed in distributed computing theory and practice. It would be a shame to see one of the last companies with that design philosophy disappear along with the technology and will to continue to implement supercomputer designs that don't follow the latest "fad".

ed

SGI Takes Action to Reduce Debt

SGI Announces Pre-Negotiated Reorganization

MOUNTAIN VIEW, Calif., (May 8, 2006)--Silicon Graphics (OTC: SGID) today announced that it has reached an agreement with all of its Senior Secured bank lenders and with holders of a significant amount of its Senior Secured debt on the terms of a reorganization plan that will reduce its debt by approximately $250 million, greatly simplifying its capital structure.

As part of this agreement with many of its major stakeholders, and as the next step in its previously announced plan to reorganize its businesses, the Company and its U.S. subsidiaries have filed voluntary petitions under chapter 11 of the U.S. Bankruptcy Code. SGI's non-U.S. subsidiaries, including European, Canadian, Mexican, South American and Asia Pacific subsidiaries were not included in the filing; will continue their business operations without supervision from the U.S. courts; and will not be subject to the requirements of chapter 11. The Company expects to file its Plan of Reorganization reflecting the agreement shortly, and to emerge from Chapter 11 within six months.

Read more at http://www.sgi.com/company_info/newsroom/press_rel eases/2006/may/sgi_reorg.html

... to mirror the STL progammer's guide (for personal use, of course).

It's sad to see them go, and not just for their cool h/w. This is the company that brought us OpenGL and, for a long time, the only useful STL documentation on the web (not to mention Irix had a working c++ compiler). I can almost forgive them for IRIX 6.5.

http://www.sgi.com/tech/stl/whats_new.html

last entry is "Release 3.3: June 8, 2000"

Seems to have a link right here...

http://www.sgi.com/company_info/newsroom/press_rel eases/2006/may/sgi_reorg.html

My question is; where they contributing anything new to the maket recently

Well, there's a link on the SGI homepage now. I like the way they avoid the wording "Chapter 11" like the plague...

Obviously the OP didn't read SGI's official release...

Here's the link from the SGI site about their debt reduction effort: STORY LINK. Cheers.

Info about the Chapter 11 is up now, via a press release:

http://www.sgi.com/company_info/newsroom/press_rel eases/2006/may/sgi_reorg.html

From the release:
"As part of this agreement with many of its major stakeholders, and as the next step in its previously announced plan to reorganize its businesses, the Company and its U.S. subsidiaries have filed voluntary petitions under chapter 11 of the U.S. Bankruptcy Code. SGI's non-U.S. subsidiaries, including European, Canadian, Mexican, South American and Asia Pacific subsidiaries were not included in the filing; will continue their business operations without supervision from the U.S. courts; and will not be subject to the requirements of chapter 11. The Company expects to file its Plan of Reorganization reflecting the agreement shortly, and to emerge from Chapter 11 within six months."

It may not be all that "recent", but if you're a C++ programmer, you might want to download a copy of this documentation before the bankruptcy trustees pull the plug on the server:

http://www.sgi.com/tech/stl/

SGI disagrees with you:

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

"XFS: A high-performance journaling filesystem

XFS combines advanced journaling technology with full 64-bit addressing and scalable structures and algorithms. This combination delivers the most scalable high-performance filesystem ever conceived. "

I dunno, the language on this page makes it sound like it was an experimental demo which existed first, and then someone saw and decided would look cool in the movie, not the other way around.

At least that scene showed actual software used correctly.

That program was real, although only for IRIX systems. It's still available as a download here. There is a free implementation for BSD/Linux systems here as well.

I know this might not be entirely useful, but we've got a card from SGI that does this:

http://www.sgi.com/products/visualization/media/di g_media.html#graphics_capture

http://techpubs.sgi.com/library/manuals/4000/007-4 663-002/pdf/007-4663-002.pdf

"
The Silicon Graphics SGC option is a video frame capture PCI-X card that allows a stream
of digital computer resolution video (as compared to Standard Definition or High
Definition Digital TV signals) to be read into the memory of a Silicon Graphics Prism
system. The computer resolution video is delivered in a digital form to the card via a
single link DVI-D connector.
The card itself is seen as an OpenML 1.1 device, and can be programmed for use by
applications, video ingest from external DVI sources, or it can be used directly by
OpenGL Vizserver to support a Visual Area Networking (VAN) environment. Multiple
cards may be configured in a single system to support multiple input streams in an SGI
Reality Center or multiple remote VAN sessions. Note that the SGC card is required
when OpenGL Vizserver is used with the hardware compositor.
"

I guess you need an SGI computer though :(

Just what I was going to say! Project Ultra-Violet is what they're calling it.

SGI has a 2nd generation product based on this: RASC, which is a node board with 2 FPGA chips that integrates (same access to shared memory) with the rest of the machines Itanium node boards.

Just what I was going to say! Project Ultra-Violet is what they're calling it.

SGI has a 2nd generation product based on this: RASC, which is a node board with 2 FPGA chips that integrates (same access to shared memory) with the rest of the machines Itanium node boards.

SGI Announced their version "Multi-Paradigm Computing" in July 2004. Cray is 2 years behind the game.
http://www.sgi.com/features/2004/july/project_ultr aviolet/ [sgi.com]

SGI Announced their version "Multi-Paradigm Computing" in July 20004. Cray is 2 years behind the game.
http://www.sgi.com/features/2004/july/project_ultr aviolet/

Physical Disk Sector Sizes Supported

512 bytes through to 32 kilobytes (in powers of 2), with the caveat that the sector size must be less than or equal to the filesystem blocksize.

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

Probably not "cheap" by any stretch of the imagination. http://www.sgi.com/products/visualization/prism/st reaming_video.html

Scroll down to the GeoProbe movie -- they mention a system with 512 GB of "shared memory". And mention linux.

That's 1GB of unified memory, so less than 1GB is available for textures ; (

It took them long enough; this is definitely the direction to go.

Almost 4 years ago Silicon Graphics gave a final revision hurrah to their best graphics product: InfiniteReality. A pipe sported 1GB dedicated texture memory, 10GB of frame buffer memory, 8 channels per pipe, and 192GB/s internal memory bandwidth.

And an Onyx system could have up to 16 pipes! That's 8.3M pixels per pipe, or 133M pixels from a full system! And all in 48-bit RGBA. And those are just the raw numbers, there were a great many high end features only found on InfiniteReality. Don't ask what it costs ; )

Sorry for the passionate post. It seems that Slashdot is very PC-ish and narrow in its viewpoint (Imagine a Beouwolf of... Can it run Doom3 ... etc.) so I couldn't resist blabbing about high-end kit that's off topic.

I've had the pleasure of using a small Onyx system. Too bad SGI is dead dead dead. Still they provide a good target for everyone to shoot for. Some day the above power will be available for a few hundred dollars for the average person. Though I think it will be atleast 5 years before the quality and features of InfiniteReality4 are at a consumer level. And never will we have workstations like SGI's again ; (

...hrm...I seem to remember a company called Silicon Graphics, or was it SGI...they had a great filesystem back when they were still in business - cxfs or something, IIRC. Oooh, they left their web site running - must be by mistake since I'm sure they went out of business a while ago...

http://www.sgi.com/products/storage/tech/file_syst ems.html

"...architected to address single files as large as 9 million terabytes..."

"...and filesystems as large as 18 million terabytes...".

the only performance numbers I could find are :

http://www.vets.ucar.edu/Reports/CXFSPerformance/i ndex.html

I recommend getting her an SGI Tezro workstation, while SGI's still around. She'll be awed by the stylish enclosure and rocksolid IRIX operating system running on an XFS foundation. As her pre-school colleagues grapple with color precision and flawed volumetrics, she will be smooth sailing by the smooth CFD visualizations on her scientific-grade machine. As SGI folds during her later years, she'll appreciate your foresight in giving her a piece of computing history. Don't be late; start her off on a real computer.

While it sucks you've lost data because of XFS, mant people use it heavily every day without issue (I'm one of them) I've deployed XFS across mail, database, and web servers without issue. Your statements about are total FUD. The reason the last 'release' was in 2003 is not long after that, XFS was accepted into the kernel itself. Thus there we no longer a need to 'release' XFS patches for the kernel. If you look at the command packages, you'll see them being updated on a regular basis.

As for bugs, I think your statement of bugs not being fixed is incorrect as well. Check the closed bug list. You'll see many that are being closed. Also, in your open bug list above, it does appear rather long. But MANY of those bugs are from users who opened a bug saying 'XFS Crashed On Me' and then never followed up with more info. The XFS developers haven't cleaned many of those out it seems. Bugs in the 200s date from 2003, bugs from the 300's from 2004. Late 300's and 400's from 2005.

So I hate you've had data loss - I wouldn't wish that on anybody (having experienced a RAID5 triple disk failure combined with backup tape failure. Thank goodness for OnTrack!) But don't post FUD about a filesystem that has performed very well for a lot of people and continues to be improved and innovative.

While it sucks you've lost data because of XFS, mant people use it heavily every day without issue (I'm one of them) I've deployed XFS across mail, database, and web servers without issue. Your statements about are total FUD. The reason the last 'release' was in 2003 is not long after that, XFS was accepted into the kernel itself. Thus there we no longer a need to 'release' XFS patches for the kernel. If you look at the command packages, you'll see them being updated on a regular basis.

As for bugs, I think your statement of bugs not being fixed is incorrect as well. Check the closed bug list. You'll see many that are being closed. Also, in your open bug list above, it does appear rather long. But MANY of those bugs are from users who opened a bug saying 'XFS Crashed On Me' and then never followed up with more info. The XFS developers haven't cleaned many of those out it seems. Bugs in the 200s date from 2003, bugs from the 300's from 2004. Late 300's and 400's from 2005.

So I hate you've had data loss - I wouldn't wish that on anybody (having experienced a RAID5 triple disk failure combined with backup tape failure. Thank goodness for OnTrack!) But don't post FUD about a filesystem that has performed very well for a lot of people and continues to be improved and innovative.

XFS is one of the worst formats I've ever worked with. Not only have I lost gigs of data from terabytes of XFS partitions, but they've all been results of XFS bugs. A cursory glance at their bug list, and you'll see why it's not a prudent choice.

Let me get you started:

http://oss.sgi.com/bugzilla/buglist.cgi?query_form at=specific&order=relevance+desc&bug_status=__open __&product=&content=

Ok, now you might say to yourself, "Well, they're fixing the bugs, so the version I'm on isn't subject to them". In which case, I'd say you're sorely mistaken. First, check the date of their last release:

FTP

Check out the latest the latest. What? 2003? Haven't there been any bug fixes since then?

Truth be told, ext3 may be worse on paper, but at least they:

a. Acknowledge their bugs.
b. Attempt to patch their bugs.
c. Admit they're not the world's cure for every problem.
d. Are backed by a company that will be around for the next few years.
e. Have recent changes that fix bugs reported within the past year +.

XFS is one of the worst formats I've ever worked with. Not only have I lost gigs of data from terabytes of XFS partitions, but they've all been results of XFS bugs. A cursory glance at their bug list, and you'll see why it's not a prudent choice.

Let me get you started:

http://oss.sgi.com/bugzilla/buglist.cgi?query_form at=specific&order=relevance+desc&bug_status=__open __&product=&content=

Ok, now you might say to yourself, "Well, they're fixing the bugs, so the version I'm on isn't subject to them". In which case, I'd say you're sorely mistaken. First, check the date of their last release:

FTP

Check out the latest the latest. What? 2003? Haven't there been any bug fixes since then?

Truth be told, ext3 may be worse on paper, but at least they:

a. Acknowledge their bugs.
b. Attempt to patch their bugs.
c. Admit they're not the world's cure for every problem.
d. Are backed by a company that will be around for the next few years.
e. Have recent changes that fix bugs reported within the past year +.

XFS is one of the worst formats I've ever worked with. Not only have I lost gigs of data from terabytes of XFS partitions, but they've all been results of XFS bugs. A cursory glance at their bug list, and you'll see why it's not a prudent choice.

Let me get you started:

http://oss.sgi.com/bugzilla/buglist.cgi?query_form at=specific&order=relevance+desc&bug_status=__open __&product=&content=

Ok, now you might say to yourself, "Well, they're fixing the bugs, so the version I'm on isn't subject to them". In which case, I'd say you're sorely mistaken. First, check the date of their last release:

FTP

Check out the latest the latest. What? 2003? Haven't there been any bug fixes since then?

Truth be told, ext3 may be worse on paper, but at least they:

a. Acknowledge their bugs.
b. Attempt to patch their bugs.
c. Admit they're not the world's cure for every problem.
d. Are backed by a company that will be around for the next few years.
e. Have recent changes that fix bugs reported within the past year +.

"It's a Unix system!"

SGI, to be specific, circa 1992.

Let me tell you that the support for NTFS and SAMBA servers on SGI servers is really not there anymore.

For the samba problem, you didn't just go to http://freeware.sgi.com/index-by-alpha.html and search for samaba, download it, and use inst to install it?

SGI systems used to come with a CD that had the most popular stuff from the freeware site.
You didn't look through the CD's in the IRIX box ?

Well, you can look as easily as I can...though I couldn't tell you how 'real' these numbers are :

http://www.sgi.com/products/visualization/prism/fe atures.html

"Increase productivity by achieving maximum performance on all your data with world-leading over 1TB/second interconnect technology (changing number/second)"

http://www.sgi.com/products/servers/altix/4000/fea tures.html

Of course, this is remote memory, not local...(I assume)

"Scalable System Size

Scales to 512P system size and as much as 128 TB globally addressable memory

NUMAlink 4 interconnect, MPI support

        * 6.4 GB/s bandwidth, http://www.sgi.com/products/workstations/tezro/fea tures.html

"Industry-leading architecture based on the SGI® 3000 family features 3.2GB-per-second memory bandwidth"

Of course, that's just marketing BS...

Well, you can look as easily as I can...though I couldn't tell you how 'real' these numbers are :

http://www.sgi.com/products/visualization/prism/fe atures.html

"Increase productivity by achieving maximum performance on all your data with world-leading over 1TB/second interconnect technology (changing number/second)"

http://www.sgi.com/products/servers/altix/4000/fea tures.html

Of course, this is remote memory, not local...(I assume)

"Scalable System Size

Scales to 512P system size and as much as 128 TB globally addressable memory

NUMAlink 4 interconnect, MPI support

        * 6.4 GB/s bandwidth, http://www.sgi.com/products/workstations/tezro/fea tures.html

"Industry-leading architecture based on the SGI® 3000 family features 3.2GB-per-second memory bandwidth"

Of course, that's just marketing BS...

Do you mean a Tezro (http://www.sgi.com/products/workstations/tezro/) with "the industry-leading VPro V12 graphics"...

lotst of IRIX-specific software has already been made open source or the patent surrounding it has been sold.

See e.g. http://oss.sgi.com/projects/

and many of those things like GLX (what allows to use opengl in X environments) was done by SGI. There's a list of OSS projects at the SGI site

There's a LOT of SGI people around the linux kernel (and not just for XFS) for example. Things like the numa-aware slab allocator, cpusets, or the swap migration (new in 2.6.16) or other tons of scalability improvements that I can't remember habe been done by SGI people. If SGI loses, Linux loses a bit of horsepower.

http://www.sgi.com/fun/gallery/images/jp_poster.gi f

The title of the article at the Register is misleading. Like all politically calculated red herrings, a soundbite was used in order to lure your attention away from the context of the full statement.

What statement?

Let me give you the link to the SEC quarterly filing so you can judge for yourself.
http://www.sec.gov/Archives/edgar/data/802301/0001 19312506023752/d10q.htm

What context?

After laying out what the company is doing to right itself, it also lays out possible business transactions that could change it's fiscal profile. The final sentence in this last paragraph of the summary is:

If we fail to implement one or more of these alternatives successfully and we have a significant shortfall against our fiscal 2006 operating plan, we could be forced to seek protection under bankruptcy laws.

What motive does the Register have?

I am glad you ask, the Register does not provide you any link, instead they falsely suggest "Starts 3D 'For Sale' sign design." I think it is convenient that they do not let you corroborrate the context of their research and see the definition of sensationalist editorialism.

Two sides to every story!

I have been working at SGI for nearly a year, the company has a history of trouble executing (grumble grumble management) but it has great products and a lot of smart, good, and honorable people.

SGI has a new CEO as of THIS WEEK. See the last paragraph of the quarterly annoucements press release:
http://www.sgi.com/company_info/newsroom/press_rel eases/2006/january/q206_results.html

Many companies would like to have the revenue and people resources SGI has. While the company continues to decline, it is easy to be a pessimist. But I am there helping change things for the better, it is an incredible opportunity and a good work environment. How many places can claim this even when the company is healthy?

Thanks for listening to my positive rant to set the record straight. I dislike journalism leading the sheep to false conclusions.

As far as I understand it, it seems the Standard Implementation is licensed under a BSD, mozilla alike license

http://www.sgi.com/products/software/opengl/licens e.html

From SGI's own OSS project page: "...and in order for OpenGL to continue as the only cross-platform 3D graphics standard, it must succeed on Linux as well as the many other platforms it already is available on. As the original creators and strongest supporters of OpenGL, we're putting substantial resources into making sure all this happens."

So, step up foo! SGI could be the defacto open platform hardware solution provider on linux. I'm a self professed Nvidia fanboi, but I'd gladly pay $200 for something comparable to just an FX5900.

Don't forget the Standard Template Library.

Might wanna download all the docs before the bankruptcy court pulls the plug on the servers.

"Linux" has rwx-rwx-rwx. That's it.

That's simply false, unless for some stupid reason you're using an antiquated filesystem. There is full support for file-system level ACLs in Linux. For example, XFS supports POSIX ACLs, and the SuSE folks include instructions on implementing POSIX ACLs in Linux (pdf) on a couple of different filesystems in their administration guide.

It's not like this is particularly new, either. It's just that you aren't forced to use ACLs, and by default they are configured to be overridden by the traditional mode bits (which, by the way, are surprisingly more powerful in the hands of an expert than many people realize).

Let's try to discuss actual shortfalls in Linux, rather than making them up out of ignorance, hm?