The collected works of jpstewart - Page 3

I took a quick look at sys/types.h (from IRIX 6.5.22), and it looks like mprot_t is only defined in an #ifdef block for kernel code. Two things you could try are:

1) Add -D_KMEMUSER to your CPPFLAGS or CFLAGS (although that may break other stuff)

2) Add -Dmprot_t=uchar_t to your CPPFLAGS (since that's essentially what sys/types.h is doing)

Either of those might help, but both suggestions are untested. None of my IRIX boxes are up and running at the moment.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei wrote:
Anyway, the more software the better, right?

It sure can't hurt to have software choices. Thanks for all your porting efforts, hamei!

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei wrote:
Helvetica does not seem to space correctly. If you type a line across the page, it line-breaks far too early. Yet the margin itself is fine : right-align and the text goes all the way to the right where it belongs (except that it still does not fill up the line.)

Hmm...is it a problem with mixed-up font metrics? It's almost as if it is calculating width using the metrics for Helvetica, but displaying Helevetica Narrow instead. What happens if you print the page? (Preferably on a PostScript printer, which would mean it would have Helvetica as a built-in font.) Does it come out right on paper, suggesting it's a problem with the screen fonts only?

What happens if you do a paragraph in Helvetica and another in Helvetica Narrow? Is the second paragraph the same or narrower still?

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
johnsmith wrote:
interface.c:211: storage size of `sleep_time' isn't known

Does the file in question have either #include <sys/time.h> or #include <sys/resource.h> somewhere in it? Both define struct timeval, so you'll need one (and only one!) of them.

Also note that the definition in sys/time.h (which is probably the correct route) is surrounded by a couple of ifdef statements, so you'll need to add -D_BSD_TYPES to your CPPFLAGS environment variable or compiler command line to actually have it work.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
johnsmith wrote:
Code:
ld32: FATAL   12 : Expecting n32 objects: /usr/freeware/lib/libgtkgl.so is o32.

As hamei mentioned, you need to be aware of the difference between lib (o32) and lib32 (n32) libraries. It appears you need to change /usr/freeware/lib to /usr/freeware/lib32 in this specific case. That's assuming, of course, that the freeware libgtkgl has an n32 library available.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
ClassicHasClass wrote:
Code:
% sh testcpu
AIX uppsala 1 6 000C3N50R3D
2


This is, technically, correct -- there are two physical cores. However, AIX recognizes four logical CPUs because of SMT


Interesting. On my Debian Linux boxes, which have Intel Hyperthreading enabled on their CPUs, the script detects the total number of logical cores rather than physical ones. It's surprsing, to say the least, that one platform counts physical cores and another counts logical ones. Personally, I'd consider that a bug.

Unfortunately, I don't see a quick work-around to get Linux to only count physical cores. (It's easy enough if all the cores are on one socket. Not so easy if you have multiple chips/sockets.) And I don't have any AIX experience at all to suggest how to get it to count logical ones the way Linux does. Sorry I can't be more helpful.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Check your $PKG_CONFIG_PATH environment variable, maybe your whole pkg-config installation, and specifically the glib*.pc and pango*.pc files in /usr/nekoware/lib/pkgconfig (or any other pkgconfig directories you might have on your system). It's quite likely that the configure script is using pkg-config to find Glib and Pango and maybe picking up the wrong one. It's also probably one of their *.pc files that is adding -pthread to CFLAGS.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I've taken a look at the GTK source (especially its configure script), and I'd be willing to bet that the -pthread flag is coming from pkg-config, and that it in turn is causing the failure to detect the correct version of Glib. The test compile fails because of the -pthread, but the configure script mis-interprets that failure to compile as a version mis-match. That would also explain why configure found the library when you passed --disable-glibtest. And since Pango requires Glib, that erroneous -pthread flag caused the Pango tests to fail (which were again mis-interpreted by configure to mean that you don't have Pango).

If you can't find and edit the offending *.pc file, you can set BASE_DEPENDENCIES_CFLAGS and BASE_DEPENDENCIES_LIBS to point to Nekoware instead. That'll cause the configure script to bypass pkg-config entirely. Note that it looks like you'll need to manually specify all the required libraries in that case (i.e., "-L/usr/nekoware/lib -lpango-1.0 -lglib-2.0 ..."), not just the directory.

Based on what I see in glib-2.0.pc on my Octane, I think you should (maybe) have -lpthread in your Libs line instead of just -pthread.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei wrote:
Code:
Making all in gdk-pixbuf
gmake[2]: Entering directory `/usr/people/dev/gtk+-2.12.12/gdk-pixbuf'
( cd . && glib-mkenums \
--fhead "#ifndef __GDK_PIXBUF_ENUM_TYPES_H__\n#define __GDK_PIXBUF_ENUM_TYPES_H__\n\n#include <glib-object.h>\n\nG_BEGIN_DECLS\n" \
--fprod "/* enumerations from \"@filename@\" */\n" \
--vhead "GType @enum_name@_get_type (void) G_GNUC_CONST;\n#define GDK_TYPE_@ENUMSHORT@ (@enum_name@_get_type())\n"         \
--ftail "G_END_DECLS\n\n#endif /* __GDK_PIXBUF_ENUM_TYPES_H__ */" \
gdk-pixbuf.h gdk-pixbuf-core.h gdk-pixbuf-transform.h gdk-pixbuf-io.h gdk-pixbuf-animation.h gdk-pixbuf-simple-anim.h gdk-pixbuf-loader.h ) > tmp-gdk-pixbuf-enum-types.h \
&& (cmp -s tmp-gdk-pixbuf-enum-types.h gdk-pixbuf-enum-types.h || cp tmp-gdk-pixbuf-enum-types.h gdk-pixbuf-enum-types.h ) \
&& rm -f tmp-gdk-pixbuf-enum-types.h \
&& echo timestamp > s-enum-types-h
env: perl -w: No such file or directory


Ah, yes. Sadly, I've seen that one before, too. Edit /usr/nekoware/bin/glib-mkenums to change the first ( shebang ) line from:
Code:
#!/usr/bin/env perl -w
to:
Code:
#!/usr/nekoware/bin/perl -w
It has the effect of making Glib depend on neko_perl, but it'll work.

I don't think IRIX can handle more than one argument in a shebang line, thus it's interpreting "perl -w" as a single argument to pass to /usr/bin/env. Hence its complaint about "perl -w" not existing. It should be looking for "perl" and passing "-w" as an argument to that, but it's not. (Not that you care about the reason behind the change.... I'm just rambling.)

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote:
As an unhelpful aside from the peanut gallery,

Isn't that what the Internet is for? :lol:

vishnu wrote:
I hasten to point out that gtk has been an unadulterated horrorshow since the day of its inception.

I enjoy a good challenge every now and then; that's what makes me determined to get things working. Besides, hamei's first problem was actually autoconf making too many (unfounded) assumptions. And the second was also unrelated to GTK itself. The real "horrorshow" hasn't even begun yet! :!:

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
That's actually a fairly easy one to fix, too. From my own notes from building a custom pixman, the autoconf test is broken (again!). It checks for mprotect and mmap functions, and then assumes that means that MAP_ANONYMOUS is available...which it isn't on IRIX. So you need to manually set ac_cv_func_mprotect=no by prepending it to the configure command. Try:
Code:
ac_cv_func_mprotect=no ./configure --prefix=/usr/nekoware ...


EDIT: I see duck posted while I was writing my response. I should point out that in general, he's right about MAP_ANONYMOUS potentially being a big problem on IRIX. It's probably only in the specific case of pixman that my suggestion applies, since pixman will then use alternate code after the configuration change.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
octane2 wrote:
Can anyone tell from the pinout whether this display supports sync on green

I can't tell from the pinout, but the PDF you linked in your first post has detailed specfications (on the page before the pinout chart). No mention of sync on green, just "Separate sync, composite, and digital video T.M.D.S." If sync on green was supported, I would expect it to say so there.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Wow, that's neat to hear! I've got an A2500/UX in pieces* waiting to be assembled just so that I can play around with Amix. Now it seems I may not need the actual hardware.

(* actually it's a standard A2000 that I bought new in 1989 and used for more than 5 years. I recently pulled it out of storage and bought the add-ons to upgrade it to the equivalent of an A2500/UX. I haven't had a chance to put everything together yet.)
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
mia wrote: This makes me think, does this also mean that netbsd/openbsd and perhaps m68k linux can now work on winuae?

According to winuae.net , yes! Under "New Features" for WinUAE 2.6.0 it says: "Full 68030, 68040 and 68060 MMU emulation. Amix, Linux, NetBSD, Enforcer, WHDLoad MMU option and more fully working."
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Nice!

Call me crazy, but I like the older/slower systems better for some reason. Maybe it's just because you could do so much with so little hardware back then, before software bloat got us to where we are today. And the programmers who got the software to do so much in so little space get my respect, too.

I have an R4K Indigo that I was going to install IRIX 4.0.5 on until I discovered my CD is completely corrupt. I'd actually prefer to have gotten a R3K instead (in part because it's even older; in part becuase I already have an R4K system, my Indigo2). And you say you have the beige keyboard and old monitor. That makes for an impressively complete old system.

So from my crazy, backwards, retro-focused viewpoint that is one very nice machine you have there!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
That's a nice photo. I love the monitor. I don't think I've ever seen one of the old beige monitors before, only the granite models.

Enjoy that setup!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
recondas wrote: Back from a road trip along the east coast into the Canadian Maritimes. In chronological order the route went through NC, VA, WVA, MD, PA, NJ, NY, CT, MA, NH, ME, NB, PEI, NS, NB, ME, NH, VT, NY, PA, MD, WVA, VA, and back to NC.

Wow! That sounds like a nice, but very long, trip. Mind if I ask how many days you were on the road and/or how many miles you covered?

It sure looks like you got some spectacular photos out of it, too!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
recondas wrote: Twelve days, four thousand miles.

That's a lot of mileage for only twelve days. I'd be exhausted trying to cover half that distance in that amount of time (by car; motorcycles aren't my thing). Maybe the added dose of fresh air on the motorcycle helps you stay awake!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
BetXen wrote: On the OS side, it is for the moment running 6.5.22, but is very slow.

If you want to stick with 6.5.22, upgrade your RAM! The R4K Indigo can handle up to 384MB, and (in my experience) anything under 128MB is just too little for 6.5.x. 192MB and up is more realistic for actual use. I was quite pleased with the performance boost I got on my Indigo2 when going from 64MB to 320MB. (I realize it's not the same machine, but still....)

Of course, if you prefer the older IRIX versions anyway, then there's probably no need to upgrade RAM.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
blowout6 wrote: Also, I'd imagine there should be driving / racing simulation software.

I wonder how feasible it would be to get TORCS running on IRIX. I suspect it would be better on an Onyx than anything in my humble collection, if it could run on IRIX at all.

Probably any simulator (even driving ones) will be like the high-end flight simulators the other posters have been discussing: they'll be proprietary software and may require specialized hardware (in addition to the IRIX machine).
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
jan-jaap wrote: Strangely, the airflow is back-to-front. Ideally I should mount it in the back of the rack, but that's not very convenient.

That seems to be somewhat common on switches. I guess in a data centre environment it makes sense to mount the switch at the back of the rack. Putting the switch ports at the back where the servers' ports are can simplify cabling --- no need to pull cables through to the front of the rack. I'll have to check the airflow on my 4100s now. I never thought about that until you mentioned it.

jan-japp wrote: As a bonus, it also come with Extended Fabric, Fabric Watch, Performance Monitor and Trunking licenses. That should keep me busy for a while 8-)

Congratulations on a nice score! Those licenses cost a fortune on their own. Have fun with it. :D
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I've had an Indigo for about a year and half now. Apparently I never properly introduced him to the forum.

At the moment, all I can do is get the PROM-level hinv info. This machine was going to be my IRIX 4.0.5 playground, but I discovered that my 4.0.5 CD is damaged. So the machine is still waiting for an operating system. I'm thinking about NetBSD instead. Certainly not IRIX 6.5 since my other SGIs are already running that much faster than this little guy could!

Code: Select all

hinv -v
System: IP20
Processor: R4000 50 Mhz, with FPU
Primary I-cache size: 8 Kbytes
Primary D-cache size: 8 Kbytes
Secondary cache size: 1024 Kbytes
Memory size: 96 Mbytes
Graphics: LG1
SCSI Disk: scsi(0)disk(1)
SCSI Tape: scsi(0)tape(2)

The tape is an original SGI DDS/DAT drive, but other than that there's nothing special about this Indigo. I replaced the TOD clock battery a little over a year ago, so no troubles on that front.

I might consider selling/trading this system for an Indigo R3000 Elan instead. I don't have an R3K system of any sort and would like one so that I can compare it to the faster machines. Especially since my Indigo2 has a 250MHz R4400 and that's a much faster specimen from the R4K family. And I just have this weird fascination with older/slower hardware.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote: I've got Sun Studio 11 and Sparkworks 1.129 on my Blade 2500 but since it's 64 bit there's no point trying to compile it on that?

Just pass the "-m32" option to the compiler to compile in 32-bit mode. So either set CC="cc -m32", or set CC="cc" and CFLAGS="-m32", or similar. There are plenty of ways to compile 32-bit code on a 64-bit machine.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote: I'm getting system header errors, could somebody kindly do me the favor of checking what version of /usr/include/inttypes.h you have? Mine says:

Module: inttypes.h
$Revision: 1.4 $
$Date: 1998/06/23 00:38:11 $

It's failing with:

Code: Select all

cc-1020 CC: ERROR File = /usr/include/inttypes.h, Line = 188
The identifier "va_list" is undefined.


va_list is defined in varargs.h but that won't compile either:


va_list is also defined in stdarg.h which is included by inttypes.h (at least on my system). So I'd suggest checking:

1) Does your version of inttypes.h actually include stdarg.h before any mention of va_list?
2) Does your version of stdarg.h have typedef char *va_list somewhere?
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I'll also say thanks for the warning.

I'll have to put "inspect SS20 PSU" near the top of my "to do" list. Now that I know about the potential for trouble lurking in there, I'd certainly prefer to fix the PSU before any serious problems crop up or any damage is done.

That was a great tip to share.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
duck wrote:

Code: Select all

knightrider% date && uptime
Sat Jan 25 17:19:51 EET 2014
5:19PM  up 507 days, 21:10, 5 users, load averages: 0.15, 0.35, 0.38


No UPS .

I want your power company! That's really impressive.

I'm hard pressed to get uptimes like that with a UPS. I've got 20 minutes of battery power but around here the power tends to go out for less than a minute or for several hours. There's no middle ground. The brief power flickers happen too often for my tastes. The major outages happen every year or two, it seems. The last one (over 4 hours) was just 34 days ago. Although at that time, people in nearby cities were in the dark for the better part of a week thanks to an ice storm. So I got off lucky.

I did once have a trio of Dell PowerEdge 1750 servers running Linux all make it (just) past 800 days of uptime before the power went out for several hours. That was my best uptime but can't compare to anything I've seen a long while. And almost always due to power outages.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Well, I inspected my SS20's PSU last night. Fortunately there are no signs of leaking electrolytes...yet. Which is a good thing, because looking at it suggests that re-capping it is going to be beyond my (current) soldering skill level. Those daughter boards are going to be tricky to work with for sure. Here's hoping mine keeps working until I get more comfortable with soldering circuit boards! (I'm definitely a software guy.)

Again, thanks for the warning. I wouldn't have thought to inspect my PSU without it. And even bigger thanks for the very detailed replacement parts list. It looks like a lot of work must have gone into finding suitable replacements for all those capacitors. It will make it a lot easier for the rest of us to fix ours when (not if!) the time comes.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Nice! I've long wanted an ANS just because of how rare and obscure they are. (And they run Unix!) Since that's unlikely to ever actually happen, I enjoyed reading about yours.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
SAQ wrote: If you want an Apple product that runs UNIX get A/UX

Oh, that's on the wish list, too! (And more likely to actually happen.) It's the rarity of the ANS line that I find appealing. (The "what the heck is that?" factor, I guess.) That same rarity is what makes ClassicHasClass' write-up and pictures so interesting.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I recently won an ebay auction for a beige Indigo keyboard and mouse set which prompted me to try to play with this machine again. I tried to install NetBSD to no avail. It wouldn't read the CD I'd burned NetBSD onto. That led me to suspect that maybe it was the drive (an HP DVD-ROM in an external enclosure that I also use with my Octane) causing my earlier problems. So I tried a known-good 6.5.18 installation tools CD. Again, it wouldn't read the CD.

So I pulled the HP DVD-ROM from the external case and dropped in an old Plextor CD-RW that had recently been "retired" from another machine. Lo and behold, that drive read any CD I threw at it and the Indigo.

Since there was nothing wrong with my 4.0.5F CD, I went ahead and installed that:

uname -a:

Code: Select all

IRIX IRIS 4.0.5F 08280217 IP20


hinv -v:

Code: Select all

1 50 MHZ IP20 Processor
FPU: MIPS R4010 Floating Point Chip Revision: 0.0
CPU: MIPS R4000 Processor Chip Revision: 2.2
On-board serial ports: 2
Data cache size: 8 Kbytes
Instruction cache size: 8 Kbytes
Secondary unified instruction/data cache size: 1 Mbyte
Main memory size: 96 Mbytes
Integral Ethernet: ec0, version 1
CDROM: unit 3 on SCSI controller 0
Tape drive: unit 2 on SCSI controller 0: DAT
Disk drive: unit 1 on SCSI controller 0
Integral SCSI controller 0: Version WD33C93B, revision C
Iris Audio Processor: revision 10
Graphics board: LG1


/usr/gfx/gfxinfo -v

Code: Select all

Graphics board 0 is "LG1MC" graphics.
Managed (":0.0") 1024x768
LG2 revision 3, REX revision 1.5, VC1 revision B, MC rev B ffi
14" monitor, video option not installed.


The good old DAT drive in the Indigo happily ran through a full backup using IRIX's backup manager. I didn't expect that to work so well on the first try, considering the age of the drive. I'll have to get networking set up soon, but I'm having plenty of fun with the system as it is!

Until today I'd only ever used IRIX 6.5.x, nothing older. I'm actually quite surprised at how nice IRIX 4.0.5 is from an end-user standpoint compared to SunOS 4.1.4 considering they're of similar vintage (AFAIK). I haven't tried any programming on it yet, but I suspect that will be an "adventure" if/when I do.

Here of some photos of what it looked like when I got it. All I've had to do cosmetically was clean the dust off of it!

indigo_front.jpg
The front of the machine.

indigo_bays.jpg
The drive bays, showing the original SGI DAT drive.

indigo_rear.jpg
The rather dusty back of the machine, but it's all in great cosmetic condition.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
foetz wrote: nice machine and a good call running irix there. doesn't make much sense running anything else.

I agree. I was only considering *BSD because I thought my 4.0.5 CD was bad and didn't want to go with 6.5.x with so little RAM. I was very happy to find that with a different CD drive I was able to install 4.0.5.

foetz wrote: 4 is also interesting from a dev perspective because that was the coff era and the compiler doesn't know a lot yet

I had forgotten that the IDO was a seperately licensed product (unlike the Developer Foundation CDs that come with the base 6.5 install set) so even getting GCC (up to 3.x is supported AFAIK) runing will be a challenge. But that's another project for another day. I'm still very excited to have the little guy up and running.

ClassicHasClass wrote: That /is/ a very nice classic Indigo.

Thanks! That means a lot coming from someone with as nice a collection as yours is! Although when you call it a " classic Indigo" it makes me affraid you're going to try to claim it as your own! :lol:

Thanks for the comments guys!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Wow, that's fascinating info. Thanks for sharing!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
I'm shocked at how little disk space 4.0.5F takes up and yet is still so full-featured. After a full install (and I do mean full --- I simply did 'install *' --- I'll figure out what to remove later), I get:

Code: Select all

% df -k
Filesystem                 Type  kbytes     use   avail %use  Mounted on
/dev/root                   efs   15715    8571    7144  55%  /
/dev/usr                    efs 1017756  267929  749827  26%  /usr


Install ing the full IDO (including C, C++, Fortran77, and Pascal compilers), it gets up to:

Code: Select all

% df -k
Filesystem                 Type  kbytes     use   avail %use  Mounted on
/dev/root                   efs   15715    8574    7141  55%  /
/dev/usr                    efs 1017756  357842  659914  35%  /usr


I'm sure there's plenty of stuff that I'll never use that could be trimmed out of there, too! Considering that I'm typing this on a (four year old) Linux box with 12GB of RAM , seeing a full install with developer option using less than 0.4GB of disk is rather impressive. (People wonder why I like playing with old hardware and software. It's impressively effecient stuff!)

IRIX 4.0.5 looks mighty similar to 6.5.x, too. The toolchest is rather familiar, but not completely identical. There's no Icon Catalog and no icons on the desktop itself, but there is the WorkSpace window which combines several features of both with a bit of file management on top.
workspace1.jpg
The top of the WorkSpace window.


Scrolling down to the bottom of the WorkSpace window shows icons for some image tools. The imgsnap icon is highlighted in pale yellow as a result of me using it to take the screenshot.
workspace2.jpg
The bottom of the WorkSpace, with the imgsnap icon active.


And last but not least, winterm shell windows haven't changed much over the years.
winterm.jpg
A familiar looking shell window.


The filesystem layout sure is different. /var is missing, for example! Most of what I'd expected to see there is under /usr so that's no big deal now that I know where to look. The installer defaulted to making / only 8MB but that was too small, so I doubled it. Other than that, it's been pretty smooth sailing with 4.0.5.

This old boy has quickly become my favourite system in the collection! At least until I try compiling stuff.... The warnings in this thread from foetz are rather foreboding.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
jan-jaap wrote: How something can be airmail and still take 3 weeks to arrive is a little beyond me

I hope you've got a tracking number for that package. Watching a package progress through the postal/courier system can be downright entertaining. I just received a package that spent 8 days making a journey that Google Maps says you can drive in 7 hours. I know postal trucks aren't the fastest things on the road, but still! I've also received courier packages from the United States to me in Canada that travelled US->Canada->US->Canada. And its first trip to Canada landed 1500km from here for no apparent reason. It made me think they just randomly flung the package at Canada, missed the mark, and tried again.

Tracking international packages can be fun, as long as you don't expect a logical or effecient path.

hamei wrote: The post offices have international agreements where the price is set by the sending country, but do they keep track ? Do they balance how much each country sends versus how much it receives ? Or do they just say "To heck with it" and let it all balance out in the wash ?

The last couple of paragraphs in the "Overview" section of the Wikipedia article about the Universal Postal Union addresses that. In short, there are fees these days.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Wow! :!:

That's a very detailed write-up, foetz. Well done. I particularly liked the fact that you didn't just review the software but also provided a fair bit of history in the intro. It's clear you've put a lot of work into this. Thanks for writing it!
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Wow! Congrats on finding such an awesome Amiga. I know how rare the A4000Ts are, and then 060 and upgraded graphics, too! You must be super excited. I'm sure you'll have tons of fun with it...more than enough to justify its price tag.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
What's the status of the RAID component devices look like? Is the whole array showing as failed because too many component devices are thought to be failed? If so, does the management interface let you manually/forcibly re-enable the component devices?

I have zero experience on POWER systems or their RAID controllers. But I used to have an IBM ServeRAID 6M in a PC server. Just about any unclean shutdown of the system (but particularly those that happened as a result of bad RAM) would cause the 6M to think that two devices in its RAID-5 array had died. Booting from the ServeRAID CD and using its interface to change the drives' status from "Faulty" back to "On-line" was all that was needed. The data on the disk(s) was all there so the controller didn't re-sync/re-build the array. So I had no data loss at all. In my case, it was just a confused controller but a healthy array.

Again, I have no idea how your POWER system compares to my ServeRAID 6M, but your situation (hardware failure leading to a crash leading to a hosed array) sounds just like what I experienced. It might be worth a try if the tools allow it, and if you can accept the fact that it might not work at all.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
Glad to hear it all worked out for you.

And sorry the info I posted wasn't useful. I had hoped that there might be some similarity between IBM's PC ServeRAID cards and the ones for their POWER systems. What I hadn't realized (and really should have :oops: ) was that your system was a generation or two newer (using SAS) than the old ServeRAID 6M (U320 SCSI) that I'd used. I hope I didn't waste too much of your time with my irrelevant ramblings.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
vishnu wrote: If you do `make dist` from the top of the source tree it should rebuild the whole package into a cross platform tar.gz and excise all the GNU-isms from the makefiles. I say "should" because not everyone uses the auto tools the way they're intended

It would appear that Netsurf doesn't use autotools at all. They've got their own build system, AFAICT.

I had a quick look at it and its instructions. It doesn't look like Netsurf's QUICK-START instructions will work. That method relies heavily on their custom env.sh script which doesn't look good for IRIX. The Netsurf BUILDING-GTK instructions, however, do look viable. I'll keep working on it over the weekend and see how far I get. (Unless somebody else beats me to the finish line!)

So far I've seen some minor annoyances, but nothing terrible. It seems to assume GNU make and GNU install, for example. Their build system doesn't know about MIPS Pro (nor would I expect it to, really). Those shouldn't be show stoppers, though. (But who knows what lurks in the depths!)
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500, T5240
HP C8000
With only a minor tweak to the Makefiles, I've built most of the included libraries with GCC on IRIX. I'm not 100% sure yet, but I think the ones that didn't build aren't strictly necessary anyway. I'm planning to work on the NetSurf core later today.

Building with MIPS Pro will be a different story. Their custom build system looks (at first glance) to be fairly portable. But then the Makefiles for the individual libraries go and add GCC-specific options to the compiler command line. Depending on how it goes with GCC, I may or may not attempt to build with MIPS Pro.

Details (and patches) to follow.
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500, T5240
HP C8000