From: patv@monmouth.com (Pat Villani)
Subject: [TUHS] 32I status as of 17 Nov 2003
Date: Mon, 17 Nov 2003 22:19:06 -0500 [thread overview]
Message-ID: <3FB98FAA.9090507@monmouth.com> (raw)
In-Reply-To: <oprysw7gl4ceuadk@smtp.borf.com>
Brantley Coile wrote:
>> 2. Will use coff executable format. May comply with Sys V ABI. The
>> latter is TBD.
>
>
> Please don't do that. There is no value in being Sys V ABI compliant and
> the original a.out work very well. I've used it for two and a half
> decades now, and still use it on Plan 9. There just needs to be magic
> numbers for the various formats. I would suggest looking at the
> 10Edition information for things that arn't as they currently are.
A large part of my decision is based on using the gcc tool chain. Since
coff is one of the binary formats, and it was a unix format, I thought
it would work here as well. I don't see a real need for the ABI, but
may do it if it is easy.
>> 8. 32I is the interim name. I would have preferred Unix version 7, but
>> can't for obvious trademark reasons.
>
>
> I'm not sure if the current trademark owners can retro actively
> disassociate a mark after the fact. If it WAS Unix 32V it still IS Unix
> 32v.
> I suppose if you do much more than port it to Intel one could argue
> that it's not Unix 32V anymore.
I was one of many who represented DEC at the Open Group during Digital
UNIX certification. I'm familiar with unix branding, and I know I can't
use the unix trademark, at least not without a lot of rework to the
original source and a lot of money to go to TOG for testing.
Technically, there is new, original code being developed that will be
combined with the original code. This is a new product, even if the
original code was called unix. Only the VAX binary can still be called
unix.
I'm an engineer, not a lawyer, but this is my understanding of the subject.
Pat
--
I respect faith, but doubt is what gets you an education. -- Wilson Mizner
next prev parent reply other threads:[~2003-11-18 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 16:40 patv
2003-11-17 21:41 ` Brantley Coile
2003-11-17 22:17 ` M. Warner Losh
2003-11-17 22:48 ` Brantley Coile
2003-11-17 23:20 ` M. Warner Losh
2003-11-18 3:40 ` Pat Villani
2003-11-18 3:19 ` Pat Villani [this message]
2003-11-18 0:13 macbiesz
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=3FB98FAA.9090507@monmouth.com \
--to=patv@monmouth.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;
as well as URLs for NNTP newsgroup(s).