From: Alan BRASLAU <alan.braslau@cea.fr>
To: Michael Krauss <michael.krauss@gmx.de>,
Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 64-bit kfreebsd
Date: Sat, 29 May 2010 14:11:44 +0200 [thread overview]
Message-ID: <201005291411.44501.alan.braslau@cea.fr> (raw)
In-Reply-To: <201005290803.o4T83ZGu009056@oxalide.extra.cea.fr>
On Saturday 29 May 2010 10:09:07 you wrote:
> On Fri, 28 May 2010 18:09:17 +0200 Mojca Miklavec wrote:
> > > (I do not know why, for "freebsd" x86_64 maps to "freebsd" and not
> > > "freebsd- amd64")
>
> I am not sure what this discussion is about, I just got this part
> forwarded by Mojca. But if you talk about the case statement in
> first-setup.sh I don't know why there is a x86_64 branch for FreeBSD at
> all. On FreeBSD AMD64 you get:
>
> [mickraus@gandalf ~]\$ uname -s
> FreeBSD
> [mickraus@gandalf ~]\$ uname -m
> amd64
>
> This is on an E6300 Intel processor.
Yes, it can get confusing:
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
----------------------------------------
> > > As far as I know, 64 bit linux/freebsd/kfreebsd use the same
> > > distributions ("amd64") for both Intel and AMD processors.
>
> Same for official FreeBSD AMD64. There is no special version of FreeBSD
> for 64bit x86 CPU from Intel. There is a IA64 version of FreeBSD that
> is often mistaken as built for those Intel AMD64 clones. But this
> version is actually build for the Itanium Architecture, descendant of
> PA-RISC. Summary: FreeBSD AMD64 is used for all 64bit x86 CPUs.
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.
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
next parent reply other threads:[~2010-05-29 12:11 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 [this message]
2010-05-29 21:37 ` Martin Schröder
2010-05-30 8:53 ` Michael Krauss
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=201005291411.44501.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--cc=michael.krauss@gmx.de \
--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).