From: Paul Bame <bame@noam.fc.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dave@hiauly1.hia.nrc.ca (John David Anglin),
alan@linuxcare.com.au (Alan Modra),
marteaut@esiee.fr, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Include trouble
Date: Tue, 28 Nov 2000 14:21:05 -0700 [thread overview]
Message-ID: <E140sBV-0005ao-00@noam.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 28 Nov 2000 20:02:26 GMT." <E140qxQ-0004wV-00@the-village.bc.nu>
= Go 32bit. Linus will probably refuse to touch a 32bit port using longlong
= internally for off-t
Hmmm, too bad, since we have few palinux backwards compatibility issues and
could just have the __USE_FILE_OFFSET64 glibc magic be a no-op rather
than supporting all those extra *64 syscalls. Plus we'd need
considerably fewer syscall translators to run 32-bit apps on 64-bit
kernel (but might need more for 32-bit hpux apps). It seems illogical
to make a file-system-related data type different based on cpu
word size but I understand this isn't simple -- oh well.
Seems like the consensus is 32-bit off_t on 32-bit kernel and just
live with all those *64 syscalls -- many not supported on palinux
yet I notice.
-P
next prev parent reply other threads:[~2000-11-28 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 20:31 [parisc-linux] Include trouble Thomas Marteau
2000-11-28 4:59 ` Alan Modra
2000-11-28 9:19 ` Alan Modra
2000-11-28 17:37 ` John David Anglin
2000-11-28 19:27 ` Paul Bame
2000-11-28 20:02 ` Alan Cox
2000-11-28 21:21 ` Paul Bame [this message]
2000-11-28 21:58 ` Alan Cox
2000-11-28 20:24 ` John David Anglin
2000-11-28 20:33 ` John David Anglin
2000-11-28 23:27 ` Alan Modra
2000-11-28 15:07 ` [parisc-linux] Mouse driver for PS/2 Thomas Marteau
2000-11-28 17:21 ` Helge Deller
2000-11-28 19:30 ` Thomas Marteau
2000-11-28 20:41 ` Helge Deller
2000-11-28 17:49 ` Grant Grundler
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=E140sBV-0005ao-00@noam.fc.hp.com \
--to=bame@noam.fc.hp.com \
--cc=alan@linuxcare.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=marteaut@esiee.fr \
--cc=parisc-linux@thepuffingroup.com \
/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