From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Jack Johnson <knapjack@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] yes, it runs Plan 9, slowly
Date: Thu, 19 May 2005 08:42:38 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0505190837280.24293@enigma.lanl.gov> (raw)
In-Reply-To: <6e35c0620505172153101f0f8@mail.gmail.com>
On Tue, 17 May 2005, Jack Johnson wrote:
> http://www.transmeta.com/developers/tm8820rdk.html
just try to register to buy and you'll see the problem with transmeta.
"I want to buy a board"
"OK, tell us your life story"
That still happens. OK, so I'm a, living at b, in c, at d, etc. from
Africa, proceed.
"OK, first, sign this IP agreement, then queue up and get a number to
buy"
https://ssl.transmeta.com/devkit/reg_to_buy.cgi
That's what happened last time I try it.
ok, Agree.
c... User unknown [[ hey, who checked that?]]
System Development Kit Registration
Register to Buy Confirmation
You will receive an email with your purchase authorization code and
contact information for your sales region. If you do not receive this
email within an hour, please let us know by sending an email to us at
devkit@transmeta.com.
yep, you have to get a purchase authorization code from a chip vendor to
buy a damn board from a board vendor. woo ha!
Generally, vendors like to sell you stuff. Transmeta wants to sell you
stuff but also tie you up in 'code morphing' legalese. It gets old. I
think I see dead people.
ron
next prev parent reply other threads:[~2005-05-19 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 23:11 Ronald G. Minnich
2005-05-17 23:38 ` Bruce Ellis
2005-05-18 2:44 ` Ronald G. Minnich
2005-05-18 4:53 ` Jack Johnson
2005-05-19 14:42 ` Ronald G. Minnich [this message]
2005-05-19 14:54 ` Wes Kussmaul
2005-05-20 4:45 ` Lucio De Re
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=Pine.LNX.4.58.0505190837280.24293@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=knapjack@gmail.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).