MIPS version of OpenBSD 4.3?

</script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> </div><br /> 这是从misc@openbsd.org邮件列表中的一个问题，一个user在4.3 release光盘中找不到For MIPS的版本，所以发问。从Theo的回答中我们可以窥见很多东西，虽然很不具体，所以转到这里来。<br /><br />问题:<br /> <meta content=" http-equiv="Content-Type" charset="utf-8"" text=""> rel="File-List" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_filelist.xml" /> rel="themeData" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_themedata.thmx" /> rel="colorSchemeMapping" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_colorschememapping.xml" />

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?

Theo的回答：

1st:

rel="File-List" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_filelist.xml" /> rel="themeData" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_themedata.thmx" /> rel="colorSchemeMapping" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_colorschememapping.xml" />

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.

 

一个follow-up的问题(带有>的行)和Theo的回答(inline):

rel="File-List" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_filelist.xml" /> rel="themeData" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_themedata.thmx" /> rel="colorSchemeMapping" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_colorschememapping.xml" /> rel="File-List" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_filelist.xml" /> rel="themeData" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_themedata.thmx" /> rel="colorSchemeMapping" href="file:///F:/DOCUME~1/ACHENG/LOCALS~1/Temp/msohtmlclip1/01/clip_colorschememapping.xml" />

> 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?

 

Because the machines are VERY DIFFERENT.

 

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

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

 

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

 

A processor is not a complete machine.

 

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

> though they both have an ARM cpu.  Why?

 

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.

 

The real answer for now is a very simple: Because.

 

> 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?

 

No.  It is because the machines are FUNDUMENTALLY VERY DIFFERENT.

 

No go put that Ford part into your Toyota car.