From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Was: Problems with bridging on Sparc64
Date: Tue, 03 Feb 2004 15:53:43 +0000 [thread overview]
Message-ID: <200402031553.44155.crn@netunix.com> (raw)
On Tuesday 03 February 2004 12:37 pm, Small, Jim wrote:
> David,
>
> Please excuse my ignorance, but is there an easy way to build the bridging
> tools/library as 64bit binaries or are you saying that the dependence on
> SIOCDEVPRIVATE makes it extremely difficult without redesigning the
> bridging software?
As a slight aside, do we have any standards in place for the migration
to 64 bit ?. So far we have :-
a) 64 bit kernel should be standard for Ultras by now in all distributions.
b) A small number of applications such as the above NEED to be
compiled for 32 or 64 bit.
c) Most 32 bit applications are OK on 64 bit kernels and there is no
advantage in compiling as 64 bit.
d) Some applications would benefit from having a 64 bit version.
With more systems (especially X86) becoming 64 bit capable we
could be heading for a horrid mess with each distribution doing
incompatible things.
My suggestion if no standards exist :-
The installer should put 64 bit apps in /bin64 and make a symlink
from /bin or /sbin only if the machine supports 64 bit.
It is probably a bad idea to have such applications under /usr
because /usr should be capable of being NFS shared RO by multiple
machines.
What does the team think ?
next reply other threads:[~2004-02-03 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 15:53 C.Newport [this message]
2004-02-03 20:18 ` Was: Problems with bridging on Sparc64 Ben Collins
2004-02-03 21:21 ` Ben Collins
2004-02-03 21:26 ` C.Newport
2004-02-03 23:02 ` C.Newport
2004-02-03 23:17 ` Ben Collins
2004-02-03 23:20 ` David S. Miller
2004-02-04 0:14 ` C.Newport
2004-02-04 8:01 ` Baurjan Ismagulov
2004-02-04 13:46 ` Ben Collins
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=200402031553.44155.crn@netunix.com \
--to=crn@netunix.com \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.