I just got my 4.3 cds and since there isn't a 4.3 mips version on it,

I've been searching around on the ftp sites to find a version. I've seen

4.3 out there on a few servers but I don't see mips in any of them. Is

there still going to be a 4.3 mips release? Any idea when?

The CDs only contain the binaries for a few architectures.  This is

documented all over the order site.  The rest are going to be

available via the FTP site on the release date.
BTW, you don't mean mips.  You mean sgi.  mips is a cpu architecture, not

a machine.

On Thu, 17 Apr 2008 15:20:00 -0600
Uh, not true.  I have two "MIPS" machines downstairs (yes, made by MIPS, not

sgi).  But, you are probably right that what he has are sgi's; mips didn't make

very many machines.
-d

This is an issue that has always confused me.  It is obvious that the

binaries for OpenBSD must be different for each cpu architecture, but

why are they sometimes different for machines that have the same cpu

architecture?
For example, there are different binaries for OpenBSD on hp300 and

mvme68k machines, even though they both have a Motorola 680x0 cpu.

There are also different binaries for zaurus and armish machines, even

though they both have an ARM cpu.  Why?
Is it because these machines have limited memory, and there is only room

for those drivers that are needed by the specific machine, or is there

something more subtle going on?

They don't boot the same way.
The cpu is wired via a different mmu to the memory.  Yes, hp300's

can have alternative mmu's.
The interrupt pins are different.
The rom of the machine is different, and you need to talk to it,

in different ways.
The memory is in a different place, yes, physical memory is mapped

differently.
The serial ports are different chips, in different places.  You need

to talk to them early, sometimes.
The clock chips are different.
etc etc etc etc
The packages are the same for a cpu architeecture.  But the binaries

do contain small differences from time to time.  We try to constrain

the issues which leak into userland, but nothing is perfect yet.
Shrug.
No.  It is because the machines are FUNDUMENTALLY VERY DIFFERENT.
No go put that Ford part into your Toyota car.

On Thu, Apr 17, 2008 at 01:41:07PM -0700, John N. Brahy wrote:

| I just got my 4.3 cds and since there isn't a 4.3 mips version on it,

| I've been searching around on the ftp sites to find a version. I've seen

| 4.3 out there on a few servers but I don't see mips in any of them. Is

| there still going to be a 4.3 mips release? Any idea when?
Probably when 4.3 is released ;)
The fact that you get CD's before the actual release is just a cool

privilige you get in return for ordering early. The mips port (and I'm

assuming you're talking about sgi/mips64 here) is not on the CD's but

according to what I've been reading on source-changes@ it should be

part of the FTP release for 4.3. And now I'm not in any way in the

know, but my guess would be that it'll be released officialy on May

1st. So 2 more weeks to wait, excellent time to test out -current on

your machine so just install the latest snapshot !
Until that time, a little patience, please ;)
Cheers,
Paul 'WEiRD' de Weerd
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]

                 http://www.weirdnet.nl/

Hi,
I seemed to be successful installing OpenBSD -current for SGI. When I

reboot the system after the install I get this error:
Boot file not found on device:

pci(0)scsi(0)disk(1)rdisk(0)partition(8)/sash

Autoboot failed

Unable to continue; press <enter> to return to the menu:
I think I'm gun shy from my mac installs but there is a p partition on

the drive that takes up the first 3515 blocks of the drive and I'm

thinking I have to leave that there. Please correct me if I'm wrong.

Otherwise I did the normal install...
Anyone have any suggestions on what do to right?
Thanks,
John

Yes, you need to leave it there - the SGI Volume Header takes up the first few 
Assuming your installation has completed correctly, all you need to do is

change the OSLoader variable in your ARCS firmware from ``/sash'' (or

``sash'') to ``boot'' - it's still looking for the IRIX boot loader. This is

easily done by typing ``setenv OSLoader boot" at the ARCS console (enter

Maintenance Mode and select ``Enter Command Monitor").

--

----------------------------------------------------------------------------

             => Joel Sing | joel@ionix.com.au | 0419 577 603 <=

----------------------------------------------------------------------------
         "Real stupidity beats artificial intelligence every time."

          - Terry Pratchett, Hogfather

Oh, I wanted to ask this for quite some time:
Can I create this volume header without an IRIX installation?
The disk in my O2 died, I have another SCA disk (from a Sun), wiped clean.

And my old IRIX CDs have read errors, so I can't even install IRIX from

scratch just to prepare the disk.
Any workarounds?
Thanks,

chakl

The OpenBSD installation media (which you can boot either from cd-rom or

over the network) can create a volume header if none is found on the disk.
Miod

You can easily install on a "blank" disk - the installer will create a SGI

Volume Header on the disk if one is not already present. If one already

exists it will give you the option to keep it or replace it. Once bsd.rd is

booted you could even manipulate it manually (using sgivol(8)) if you really

wanted to do so, however there is generally no need.
Grab a current cd43.iso (or netboot a bsd.rd) and give it a whirl!

--

----------------------------------------------------------------------------

             => Joel Sing | joel@ionix.com.au | 0419 577 603 <=

----------------------------------------------------------------------------
         "Real stupidity beats artificial intelligence every time."

          - Terry Pratchett, Hogfather

Your CDs are *pre* release.  4.3-release for all currently supported

architectures, including one for MIPS, will be available for download from

your nearest mirror on May 1.
For information on the SGI MIPS-based architecture, see

http://www.openbsd.org/sgi.html  -- earlier MIPS-based architectures have been

discontinued.  See http://www.openbsd.org/plat.html for details.