[708] in SIPB_Linux_Development
machtype/@sys
daemon@ATHENA.MIT.EDU (Mark W. Eichin)
Mon Sep 19 12:55:26 1994
Date: Mon, 19 Sep 1994 12:54:41 +0500
From: "Mark W. Eichin" <eichin@MIT.EDU>
To: yandros@MIT.EDU
Cc: netbsd-dev@MIT.EDU, linux-dev@MIT.EDU
In-Reply-To: yandros@MIT.EDU's message of Sun, 18 Sep 1994 15:11:55 -0400 <199409181911.PAA09885@lola-granola.MIT.EDU.MIT.EDU>
Hmm. i386_netbsd1 has the advantage of being *correct* for an @sys value.
>> we've never run netbsd on a 386, to my knowledge.
It is more relevant to note that we've never built netbsd to *not* run
on a 386 -- gcc -m486 only adjust the scheduling, it doesn't use any
non-core instructions. 386 is commonly used as a description for the
32-bit class of chips. x86 is often used to include *all* of the
series, including those that only run 16-bit code.
It needs a version number, since NetBSD has already broken executable
format compatibility with itself once, and may very well do it again.
The only thing left is to shorten "netbsd" and I'm afraid that's not a
very good choice either. It's not the same as 386bsd or FreeBSD, and
"BSD" by itself as often as not means 4.3...
I don't particularly care what you do with machtype, though it would
be good to avoid past mistakes (sun4bin was *wrong* after all).
