Date: Wed, 20 Jan 1999 10:53:06 -0000 From: paul@originative.co.uk To: peter.jeremy@auss2.alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: RE: Directory structure on current.freebsd.org Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDB9@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Peter Jeremy [mailto:peter.jeremy@auss2.alcatel.com.au] > Sent: Wednesday, January 20, 1999 6:21 AM > To: freebsd-current@FreeBSD.ORG > Subject: Re: Directory structure on current.freebsd.org > > > Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de> wrote: > >In releases/snapshots they're called "axp" and "x86", while in > >ports they're called "alpha" and "i386". > > I agree that having two different names is confusing. > > DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not > sure that either is an especially better choice. > > > "x86" could imply that we're > >running on 286, too, and it's more in line with "sparc64"), > > I personally find "i386" a pain because it is used to specify both an > architecture (IA-32) and a particular implementation (80386) of that > architecture. In some cases it may not be clear which is meant. I think the architecture names are more appropriate than any cpu related name. For the alpha, while we might all use alpha in everyday speech axp is more specific when it comes to releases since the alpha release of the alpha code can get a tad confusing, I think that's why it was changed in the first place. It'd be nice if i386 could become IA32 but it probably won't happen. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A6D02246E1ABD2119F5200C0F0303D10FDB9>