From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: I got 64 bit terminals
Date: Sat, 29 Nov 2014 19:09:49 +0900 [thread overview]
Message-ID: <c77f444e5d632ee46343afe3e7399f1f@saturn.jitaku.localdomain> (raw)
Well, I started to use two 64 bit terminals, one is from
network boot, and the other has own local cwfs.
You can uncomment the lines as:
link
....
# ether82557 pci
....
# vganvidia +cur
frp /sys/src/9/pc64/pc64 file.
The latter need to copy the ../pc/nv_dma.h to ../pc64.
The result?
only the difference between 64 and 32 bit versions I got is
4095M memory: 1694M kernel data, 2401M user, 3026M swap.☺
However, there is no advantage, in other words, to use 32 bit terminals,
then I started to use 54 bit vcersion.
何のこっちゃ
Kenji
reply other threads:[~2014-11-29 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c77f444e5d632ee46343afe3e7399f1f@saturn.jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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).