From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 installation disc question
Date: Wed, 24 Oct 2007 15:25:12 -0400 [thread overview]
Message-ID: <9C4D3C46-AB6E-4A74-AD5A-C72058FCB3D0@mac.com> (raw)
In-Reply-To: <3e1162e60710241222md620d3dyb2b5f849a19c60c2@mail.gmail.com>
I was trying this out via Boot Camp, and it stuck before the CD menu
even showed up. At least you got it booting! :-)
On Oct 24, 2007, at 3:22 PM, David Leimbach wrote:
>
>
> On 10/24/07, Pietro Gagliardi <pietro10@mac.com> wrote: OK, that's
> fine. So I still don't know what is wrong, but I'll try
> drawterm when I get Plan 9 up on the network (see my Broadcom emails;
> I'm buying a card soon)
>
>
> I gave up on graphics for VMWare Fusion Plan 9, going to resort to
> drawterm I think. However my venti is hanging and the CPU on my
> MBP is getting awfully fast on the first boot after install and I
> login with glenda.
>
>
> On Oct 24, 2007, at 12:30 PM, David Leimbach wrote:
>
> >
> >
> > On 10/23/07, Bakul Shah < bakul+plan9@bitblocks.com> wrote: > Mac OS
> > X is still 32bit last I checked. You're likely having an EFI
> related
> > > issue.
> >
> > MacOS X 10.4.9+ is already 64 bit capable, at least on the
> > MacBook Pro
> >
> > $ sysctl machdep.cpu.brand_string
> > machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU T7400 @
> > 2.16GHz
> >
> > $ sysctl hw.optional.x86_64
> > hw.optional.x86_64: 1
> >
> > $ cat > ilp.c <EOF
> > #include <stdio.h>
> > int main(int c, char**v) {
> > printf("i:%d l:%d ll:%d p:%d\n",
> > sizeof(int), sizeof(long), sizeof(long long), sizeof
> > (void*));
> > }
> > EOF
> >
> > $ cc -m32 ilp.c -o ilp4
> > $ cc -m64 ilp.c -o ilp8
> >
> > $ file ilp4 ilp8
> > ilp4: Mach-O executable i386
> > ilp8: Mach-O 64-bit executable x86_64
> >
> > $ ilp4
> > i:4 l:4 L:8 p:4
> > $ ilp8
> > i:4 l:8 L:8 p:8
> >
> > it's increasingly offtopic but yes :-)
> >
> > The whole system is not 64bit end to end. Objective C and Cocoa
> > aren't yet 64bit, and I've yet to fail to get alignment errors with
> > certain C memory allocation functions on my MBP with Tiger.
> >
> > I hope it's all fixed Friday, not that I see me using 64bit apps
> > too much, I don't think I have enough RAM, even if the extra
> > registers give me a bit of a performance boost :-)
> >
> > Dave
>
>
next prev parent reply other threads:[~2007-10-24 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 19:18 Pietro Gagliardi
2007-10-23 22:27 ` erik quanstrom
2007-10-23 22:32 ` David Leimbach
2007-10-23 22:36 ` Pietro Gagliardi
2007-10-23 22:40 ` David Leimbach
2007-10-23 22:40 ` Lyndon Nerenberg
2007-10-24 3:32 ` Bakul Shah
2007-10-24 16:30 ` David Leimbach
2007-10-24 19:14 ` Pietro Gagliardi
2007-10-24 19:22 ` David Leimbach
2007-10-24 19:25 ` Pietro Gagliardi [this message]
2007-10-24 10:18 ` [9fans] old things Charles Forsyth
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=9C4D3C46-AB6E-4A74-AD5A-C72058FCB3D0@mac.com \
--to=pietro10@mac.com \
--cc=9fans@cse.psu.edu \
/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).