From: "Paul J.Y. Lahaie" <pjlahaie@ottawa.com>
To: "hppa-linux@puffingroup.com" <hppa-linux@puffingroup.com>
Subject: [hppa-linux] General port design questions
Date: Wed, 10 Feb 1999 10:41:06 -0500 [thread overview]
Message-ID: <36C1A892.F353A6D3@ottawa.com> (raw)
When we get to the point where we can start working on the kernel,
which system call interface should we chose? Do we go the LinuxAlpha
port route and try to maintain compatibility with HP-UX
structures/system calls as much as possible so a compatibility layer
becomes easier, or do we leverage the work already done by the MkLinux
project and build on top of that? What would be the pros and cons of
each direction?
- Paul
----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.
next reply other threads:[~1999-02-10 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 15:41 Paul J.Y. Lahaie [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-10 17:44 [hppa-linux] General port design questions Jason Eckhardt
1999-02-10 19:09 ` Alex deVries
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=36C1A892.F353A6D3@ottawa.com \
--to=pjlahaie@ottawa.com \
--cc=hppa-linux@puffingroup.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