From: Michael Krauss <michael.krauss@gmx.de>
To: Alan BRASLAU <alan.braslau@cea.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: 64-bit kfreebsd
Date: Sun, 30 May 2010 10:53:55 +0200 [thread overview]
Message-ID: <20100530084825.2E707C9BB3@balder.ntg.nl> (raw)
In-Reply-To: <201005291411.44501.alan.braslau@cea.fr>
On Sat, 29 May 2010 14:11:44 +0200 Alan BRASLAU wrote:
> uname -s uname -m uname -p
> ----------------------------------------
> Intel Q9400 (Core2 Quad):
> FreeBSD amd64 amd64
> GNU/kFreeBSD x86_64 amd64
> Linux x86_64 unknown
> 32bit os (same processor):
> FreeBSD ? (untested) ?
> GNU/kFreeBSD i686 i386
> GNU/Linux i686 unknown
> ----------------------------------------
> Intel pentium 4:
> FreeBSD ? (untested) ?
> GNU/kFreeBSD i686 i386
> GNU/Linux i686 unknown
> ----------------------------------------
I have collected data from two different machines with a FreeBSD 8.0
i386 LiveCD:
uname -s uname -m uname -p
----------------------------------------
Intel E6300 (Core2 Duo):
FreeBSD amd64 amd64
32bit os (same processor):
FreeBSD i386 i386
----------------------------------------
Intel Pentium M:
FreeBSD i386 i386
> The official 64bit OS name is "amd64" for FreeBSD, GNU/kFreeBSD and
> Linux. However, uname -m gives differing results and depends on the
> version of the running OS, not the real underlying processor; A 64bit
> processor can run a 32bit OS.
So both (uname -m and uname -p) don't depend on the installed CPU just
on the version of FreeBSD. Probably the implementation of uname(3) is
different in FreeBSD libc und GNU libc. Unix is such a homogeneous
environment, isn't it ;-)
Kind regards,
Michael Krauss
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-05-30 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimzqONTFQj_Q3qSFz1aqtnYI5uMqdLdtSvAdzzw@mail.gmail.com>
[not found] ` <AANLkTillA6ypgtyWrmanGCLN1LgIsXZYYjX2rYvbDotv@mail.gmail.com>
[not found] ` <201005290803.o4T83ZGu009056@oxalide.extra.cea.fr>
2010-05-29 12:11 ` Alan BRASLAU
2010-05-29 21:37 ` Martin Schröder
2010-05-30 8:53 ` Michael Krauss [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100530084825.2E707C9BB3@balder.ntg.nl \
--to=michael.krauss@gmx.de \
--cc=alan.braslau@cea.fr \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).