From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "ZSH workers mailing list" <zsh-workers@math.gatech.edu>
Subject: ZSH on 64 bit systems
Date: Tue, 17 Nov 1998 11:37:39 +0300 [thread overview]
Message-ID: <000f01be1205$88d59df0$21c9ca95@mowp.siemens.ru> (raw)
I plan update my server to new 64 bit version of OS, and am interested in
any experience with running ZSH on such sort of systems. Some background
information:
the system is ReliantUNIX 5.44 from SIEMENS (before Siemens Nixdorf). This
version has 64 bit kernel and provides three user execution environments
32 bit
this is fully compatible with previous versions; existing binaries will
run without recompilation.
Virtual process memory is limited to 2GB; file system size is limited to
4GB; file size is
limited to 2GB. It is not possible to access large files (over 2GB)
64 on 32
This is implementation of LFS model. Both explicit and mixed models are
supported. Virtual
process memory is still limited to 2GB; file access is full 64 bit.
Special compiler flags are
needed to enable either model. Most types have the same size as on 32
bit system;
depending of LFS model either off_t is 64 bit, or off64_t &co should be
used instead
true 64 bit
In this model, process runs in true 64 bit environment; virtual memory
is almost unlimited :))
full access to large files is provided. The size of most basic types
cheanges, notably
sizeof(int) = 4
sizeof(long) = 8
sizeof(void *) = 8
sizeof(off_t) = 8
The simplest way is to compile ZSH in true 64 bit mode. Unforunately, *any*
attempt to mix int and void * is doomed.
I gave it test-drive, and ZSH at least did run. But there was so much
warnings about possible truncation of large integer, that I am really
unsure.
regards
/andrej
next reply other threads:[~1998-11-17 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 8:37 Andrej Borsenkow [this message]
1998-11-17 9:28 Sven Wischnowsky
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='000f01be1205$88d59df0$21c9ca95@mowp.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).