From owner-freebsd-chat@FreeBSD.ORG Mon Jun 9 02:42:49 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53F7637B401 for ; Mon, 9 Jun 2003 02:42:49 -0700 (PDT) Received: from perlpimp.codersluts.net (adsl-19-42-24.asm.bellsouth.net [68.19.42.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B22C43FAF for ; Mon, 9 Jun 2003 02:42:47 -0700 (PDT) (envelope-from sektie@codersluts.net) Received: from perlpimp.codersluts.net (sektie@localhost.codersluts.net [127.0.0.1])h59Ag5Aa078760; Mon, 9 Jun 2003 05:42:09 -0500 (EST) (envelope-from sektie@codersluts.net) From: "sektie" To: Makoto Matsushita , rsidd@online.fr Date: Mon, 9 Jun 2003 05:42:05 -0500 Message-Id: <20030609103115.M77088@codersluts.net> In-Reply-To: <20030607181751T.matusita@jp.FreeBSD.org> References: <20030606125417.A3489@online.fr> <20030607181751T.matusita@jp.FreeBSD.org> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 66.223.56.152 (sektie) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 cc: chat@freebsd.org Subject: Re: Peeve: why "i386"? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2003 09:42:49 -0000 Personally, I don't care. I'm just about the most OCD person about my computers that I have ever seen (ex: cvsup ports nightly, if 'pkg_version | grep "<"' returns something more than two nights in a row, my cell phone gets an SMS). Everything has to be beautiful and perfect, but I really don't care what the documentation says. That's for a person more anal than myself to complain about. However, I do think that switching it from 'i386' to 'x86' wouldn't be that big a deal. If you know what i386 is, then x86 isn't going to confuse you (ia-32, eh, not so sure about that one). If you don't know what i386 is, then I seriously doubt you are going to be looking at anything more complex than a mac or winxp. The question isn't "are people going to understand?"; it's "who is going to put the effort into doing that much work in the documentation?". More power to ya if ya have the time. Why not do something more useful, though, like reverse engineer the DLink 520+? I'd give massive hugs to the person that comes up with drivers for that. Getting rid of that clunky Linksys and letting my fbsd server be the access point as well would take care of me having to replace the crossover cable every 2 weeks due to a teething 2 year old... Much love, Randi sektie@codersluts.net http://perlpimp.codersluts.net/ ---------- Original Message ----------- From: Makoto Matsushita To: rsidd@online.fr Cc: chat@freebsd.org Sent: Sat, 07 Jun 2003 18:17:51 +0900 Subject: Re: Peeve: why "i386"? > rsidd> Debian (to take a random example): > rsidd> http://www.debian.org/ports/ > rsidd> Intel x86 / IA-32 (``i386'')... > (other messages deleted) > > Please note that "(Put your favorite OS except FreeBSD) calls it > ia32, so should we" is bad idea, since FreeBSD is FreeBSD :-) And, the > message you mention is that "i386" is very common name for PCs, they > cannot simply says it's x86 and/or IA-32. > > We're not teacheres of computer architecture; the name should be > common to us, rather than strict meanings. > > -- - > Makoto `MAR' Matsushita > _______________________________________________ > freebsd-chat@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chat > To unsubscribe, send any mail to "freebsd-chat-unsubscribe@freebsd.org" ------- End of Original Message -------