From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] Plan9 under parallels; kernel rebuild
Date: Tue, 12 Dec 2006 16:51:04 -0800 [thread overview]
Message-ID: <3e1162e60612121651xe45e0dt80527e02286fa831@mail.gmail.com> (raw)
In-Reply-To: <74DA1E20-3937-4513-98FF-7E0B76F3C9CC@telus.net>
Let me know how it turns out! :-) I'd be glad to know it's
maintainable beyond first installation. I've honestly not tried it,
and started using a much newer drawterm to connect to a CPU box I put
together (AMD Athlon 2800+), it's pretty sweet.
Dave
On 12/12/06, Paul Lalonde <plalonde@telus.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I dug around a bit, and duplicated an old pcibussize function (that
> just passed through to a pcibusmap and life is good. I guess I could
> have re-written the (one) call point just as trivially.
> Runs now, and sees the outside world.
>
> Now to turn it into a CPU server.
>
> Paul
>
> On 12-Dec-06, at 4:33 PM, David Leimbach wrote:
>
> > keep in mind that the source that runs well on parallels is not the
> > same as the source on sources. I don't know if the BIOS changes JMK
> > did ever got merged in.
> >
> > Dave
> >
> > On 12/12/06, Paul Lalonde <plalonde@telus.net> wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> I've been following David Leimbach's directions on getting plan9 to
> >> run under parallels, and have run into a glitch while rebuilding the
> >> kernel. At link I get:
> >> configure: undefined: pcibussize in configure
> >>
> >> Any quick clues as to what's up? It's a recent plan9 iso - about 2
> >> weeks old.
> >>
> >> Paul
> >>
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.5 (Darwin)
> >>
> >> iD8DBQFFf0b3pJeHo/Fbu1wRAsAPAJ0UYwAfsIJqzk39qfbEi94pWt9gpgCggmK8
> >> wM4r9Hh68/NAvxaT7V8UseE=
> >> =gRh0
> >> -----END PGP SIGNATURE-----
> >>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFFf01QpJeHo/Fbu1wRAiXRAKCaqMtOCxGmiTLRAMaGnZGwPupHoACfTB7l
> wCGcs+robSnUApdS9riBqpg=
> =OIq9
> -----END PGP SIGNATURE-----
>
prev parent reply other threads:[~2006-12-13 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 0:19 Paul Lalonde
2006-12-13 0:33 ` David Leimbach
2006-12-13 0:46 ` Paul Lalonde
2006-12-13 0:51 ` David Leimbach [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=3e1162e60612121651xe45e0dt80527e02286fa831@mail.gmail.com \
--to=leimy2k@gmail.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).