Novatium chooses SUSE Linux Enterprise Server and Novell eDirectory for their
Nova netPC
,----[ Quote ]
| Novatium Solutions Pvt. Ltd, one of India’s fastest growing utility computing
| services providers, has opted to build its entire infrastructure on Novell
| Open Workgroup Suite, with Novell Identity Manager and eDirectory providing
| control over users and access rights. Novell Open Workgroup Suite provides a
| comprehensive infrastructure and productivity solution, including SUSE Linux
| Enterprise Server.
`----
http://press-releases.techwhack.com/15236/novatium/
Related (from Doug on NetPC):
From: Paul Mantz
Sent: Wednesday, December 04, 1996 4:36 AM
To: Jimm Allchin (Exchange), Moshe Dunie
Cc: MArshall Brumer
Subject: Intel follow-up
On the NetPC - Pat thinks we are beinn slow to follow-up and get the
spec's out, and he is telling his guys to go ahead and start drafting.
They want to have a review for the industry i January. We need to engage
with them, and get ahead of them, and get the OEMs involved. I think we
should also get a few large account customers involved in order to get
some reality in discussions and (eg) get focus off $743 price point. I
guess the PC'98 guy is also their NetPC guy.
..
From: Valere See
Sent: Thursday, December 05, 1996 7:14 AM
To: Bill Veghte; David Williams (POSD); Rob Short;
Cc: Carl Stork; Dan Plastina; Chuck Lenzmeier
Subject: RE Intel follow-up
do you have a list of issues on this topic? we have a conference call
with them (intel) re NetPC today at 9, and pending your response we can
bring them up or try to stave off a little, but the latter isn't really
a good choice - we're running out of time, as everyone is painfully aware.
..
yup, it would be crazy to Intel define this
the only urgent issue I can think of is defining how it boots, if we let
Intel do this in a proprietary way we're screwed.
..
Note the flag below on the NetPC. we need to get cranking on this. I
know it is difficult to do a spec until the sw work is crisply defined
but having Intel draft this spec and take it to the industry will cause
up more headaches in the long run if we don't get out in front.
Thanks!
..
From: Valere See
Sent: Thursday, December 05, 1996 8:03 AM
To: Bill Veghte; David Williams (POSD); Rob Short; Chuck Lenzmeier
Cc: Carl Stork; Dan Plastina
Subject: RE Intel follow-up
.. if we don't dive right in with something, Intel will undoubtedly be
happy to dictate terms to us ,-))
(thanks for the input chuck)
..
From Valere See
Sent. Thursday. December 05. 1996 8 13 AM
To Bill Veghte; David Willliams (POSD), Rob Short, Chuck Lenzmeier
Cc. Carl Stork, Dan Plastina
Subject: RE Intel follow-up
ok. no problem please let us know what comes of the talks with Lanworks
next week, but this set of issues will be enough to get us going today
thanks again
..
http://edge-op.org/iowa/www.iowaconsumercase.org/011607/2000/PX02597.pdf
Path:
border1.nntp.ams.giganews.com!nntp.giganews.com!xlned.com!feeder1.xlned.com!newsfeed.freenet.de!news.albasani.net!newsfeed.datemas.de!news.datemas.de!not-for-mail
Message-ID: <eu0ii0$272$1@xxxxxxxxxxxxxxx>
From: Doug Mentohl <doug_mentohl@xxxxxxxxxxxxx>
Newsgroups: comp.os.linux.advocacy
Subject: don't let Intel mention the NetPC ..
Date: Fri, 23 Mar 2007 12:39:16 +0000
Lines: 281
Organization: Datemas.de http://www.datemas.de
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: news.datemas.de
1dac2TEHfQAsX94OUZaOi67DtUJdZxpHKIaA03ctkJx7rFr23jQyZDIwqi8SDaTOALddgFD57irHgehbpKwiAgr73ApjA3C+DbYEMoAbW/eFcWXHM7eiO7bY5g45XWopEm0aqBvUhF/NbMgt3KNEzMleV4k3Ycq+A4scRRiG0vJGmRvZWImq8w==
X-Complaints-To: abuse@xxxxxxxxxx
NNTP-Posting-Date: Fri, 23 Mar 2007 12:52:17 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1)
Gecko/20061023 SUSE/2.0-30
Xref: ellandroad.demon.co.uk comp.os.linux.advocacy:507683
From: Jim Allchin (Exchange)
Sent: Tuesday, December 02, 1997 10:33 AM
To: Paul Maria
Cc: Marshall BnJmer
Subject: RE; Impasse on Intel Lean Client Announce
From: Paul Mantz
Sent: Tuesday. gecemoer 02, 1997 9:58 AM
To: Jim Aileron (Exchange)
Co: Marshall Brumer
Subject: RE. Impasse on Intel Lean Client Announce
I think you should brng up th s issue at next suitable meetmg with
Geisinger and ask why things turned out the way they did, and then
forward that to Billg We should let Gelsinger know that is is issue
Billg has asked about, and is something he will likely discuss with Andy
at next 1-1. This could cause Gelsinger to get very defensive, but
without I don’t think much will change.
--Original Message---
From: Jim Allchin (Exchange)
Sent: Monday, December 01, 1997 5:02 PM
To: Paul Mantz
Cc: Marshall Brumer
Subject; FW: Impasse on In|el Lean Client Announce
How would you like to follow up on what bill asks below?
thanks,
jim
- Original Message -
From: Bill Gates
Sent: Wednesday, November 25. 1997 11:00 AM
To: Jonathan Roberts; Jim Allchin (Exchange); Paul Maritz Cc: John
Frederiksen; Bill Shaughnessy; Adam Taylor; Pat Fox; Marshall Brumer;
Tina Brusca (Exchange); Carl Stork (Exchange); Phil Holden; Steve Ballmer
Subject: RE: impass on Intel Lean Client Announce
This arrangement is fine with me.
We have to work with Intel and its just crazy to get cross-wise with
them. I hope we can reach an agreement here it's awful to have Intel
sending a contrary message.
They did 2 things that amaze me:
a) They kept the NC specification around despite saying they would not.
b) They snuck in a server specification.
There is some failure in communication, I don’t understand why things
are so out of whack at this late stage.
Someone needs to figure out and tell me how we do better in the future.
-----Original Message----
From: Jonathan Roberts
Sent: Wednesday, Noveml~er 26, 1997 10:31 AM
To: Jim Allchin (Exchange); Paul Marttz
Cc: John Frederiksen; Bill Shaughnessy; Adam Taylor, Pat Fox; Marshall
Brumer, Tina Brusca; Carl Stork (Exchange); Bill Gates; Phil Holden;
Steve Ballmer
Subject: RE: Impasse on Intel Lean Client Announce
Just talked to Will Swope (Pat Geisinger was providing real time
feedback to Will as we spoke offline). Marshall and I told him the only
way for us to participate in the release is if:
1) No NC mention in any speofication
2) No uber Server spec. They can modify the Server 98/99 spec through
normal processes and then an independent Unix Server specification. They
cannot do a server spec that could supercede 98/99 for Windows NT
implementations.
Will is going to work the issue on his side and call me back at 2pm
today. The arrangement above was acceptable to Jim, Paul and Bill. if it
is not acceptable to you, please let me know by 2pm. Also I gave him
Jonnffe’s pager number to resolve any residual concerns regarding Hydra
pricing and positioning. We are ready to send them the pre-release of
the reviewers so they know exactly what we are saying
Thanks
Jonathan
- Original Message
From: Jim Allchin (Exchange)
Sent: Tuesay, November 25. 1997 7:35 PM
To: Jonathan Roberts: Paul Maritz
Cc: John Frederiksen;Bill Shaughnessy; Adam Taylor; Pat Fox: Marshall
Brumer; Tina Brusca; Carl Stork (Exchange); Bill Gates
Subject: RE: Impasse on Intel Lean Client Announce
I have since had 2 additional phone calls with Pat.
In the first call Pat agreed to remove the words "Network Computer" fom
the spec if we would participate and work with them on thee Hyda client
positioning/pricing. I asked what the client/positioning issue was and
he said Intel was not up to speed. I said at a minimum we would share
our current thoughts and take any input they have. I said we have had
discussions with Intel on this. but we would do it again in more detail.
I told him that we didn’t have pricing worked out so that would be short
discussion. We agreed that this would take place tomorrow. Jonro will
drive ensuring this happens. Nothing in our positioning/thinking has
changed so I am not sure if there would be any issue coming out of this
or not.
In my opinion though the client is only a par of the problem. The
unbelievable thing is that they created a totally independent server
hardware spec. It is independent from Serer 98, In my second call with
Pat I told him that after thinking about it I just didn’t want to
participate at all in their announcement because of the server spec. I
told him we didn't need the spec (we have one); it would be confusing to
OEMs (which one should they support); and on top of that they sent it to
us with zero time to review it.
He then brainstormed on ways that might get us to agree. He said "what
if we don’t release it on Tuesday?" I said that didn't matter. We
didn’t need the spec and I saw no good in it for us. He said "ok, what
if I had two press releases? one for the client and one for the server.
MS would be only in thee client spec and not the server spec." I told
him that I would think about it, but I thought that was only a little
bit better. In reality we would be associated with the server spec if we
are in the announcement at all.
I have since talked to jonro and asked him to call intel tomorrow (after
the Hydra discussion) and tell intel that the finally decision is "no -
we are not going to participate". I am very pissed over Intel doing this
server spec. It is so damn confusing. They are doing this for two
reasons: Unix and to get control of the server spec in the future. Their
plan is obvious. I think their view is in the future the server spec
will be a Intel only spec that they will update each year. Our joint
spec will just become a little add-on to their spec (and their
initiatives). That is, the "real" spec would be the Intel spec. I told
him that if they wanted a Unix hardware reference, they should just have
done that, They didn't.
I am about to leave for a plane so I will be hard to reach until
tomorrow night. I expect they will escalate to Paul on this tomorrow. My
position is clear from above.
jim
From: Jonathan Roberts
Sent: Tuesay, November 25. 1997 6:22 PM
To: Bill Shaughnessy; Jim Allchin (Exchange)
Cc: Pat Fox: Adam Taylor; Phil Holden; Marshall Brumer; Tina Brusca
Subject: RE: Impasse on Intel Lean Client Announce
Net, net, we believe in the Terminal/Diskless NetPC pincer. We don't
believe in the NC and can't understand why Intel does. it is illogical
and is definitionaly counter to both Intel and Microsoft's interests. We
also believe that Intel and Microsoft have to take a leadership position
on what clients we think accounts should deploy. If we don't have an
opinion on this, why will people believe our POV on why they should
deploy "full" clients? Strategies have to have logical integrity. Right
now, Intel's does not.
I am increasingly comfortable with not participating in this release. We
don't know what else Intel has up their sleaves and we can remain
consistent in our opposition to the NC. Finally, if Intel has done as
bad a job enrolling other vendors supports as they have ours, this will
just be another announcement that fades away, like their Oracle
announcement in Japan last year.
- Original Message -
From: Bill Shaughnessy
Sent: Tuesay, November 25. 1997 4:53 PM
To: Jonathan Roberts; Jim Allchin (Exchange)
Cc: Pat Fox; Adam Taylor; Phil Holden; Marshall Brumer; Tina Brusca
(Exchange)
Subject: RE: Impasse on Intel Lean Client Announce
Here is a short summary of the conference call with Pat Geisinger today.
Key points include:
* Jim voiced strong concerns against the server spec. The fact we only
received it today (99 pages) and Intel expecting our support by Tuesday
is totally unacceptable. It's worth noting that there is no appeared
synergy between this spec and Server 98. We were clear that there is not
enough time to adequately review this document between now and Tuesday.
* Jim made it clear that we do not equate "Lean" and the NC together.
"It's an oxymoron". Intel disagres with this interpretation.
* We reiterated our hard core position against using the NC in the
specification and press release. This is consistent with Billg's
position as of Friday's Windows review.
* We acknowledge via Q&A's that Intel will position their spec to
support the NCs, and we have no
..
From: Jonathan Roberts
Sent: Tuesay, November 25. 1997 2:53 PM
To: Jim Allchin (Exchange)
Cc: Pat Fox; Bill Shaughnessy; Adam Taylor; Phil Holden; Marshall
Brumer; Tina Brusca
Subject: RE: Impasse on Intel Lean Client Announce
Jin, you have a 4:00pm conference call with Pat Geisinger to discuss
their Lean Client announce. Folks on the to: line (sans Adam who is
recruiting) wil brief you at 3:45pm. After over 2 hours of discussion
with Will Swope and Ron Peck today and countless hours over the last
week, we are agreeing to disagree and are not supporting the release or
the announcement that will happen on Tuesday Dcember 2nd. As trivial as
it seems, it all comes down to Intel's insistance and our obstinate
refusal to allow them to use the term "Network Computer" in their
hardware specification. We took the lead from Billg's very hardware
attitude in our Friday review. They are willing to modify, minimize,
qualify, etc the term in any way. However, our position has been that if
it is used at all there is an implied endorsement. We don't have a
problem with them commenting in Q&A that people could build NC with this
specification, however we do have a problem with an explicit mention.
They don't understand why we are so whacked out. They see themselves as
niching the NC in purely the terminal replacement space and are simply
acknowledging that customers will be requesting this device. They are
adopting a "we don't create a market" attitude, we simply respond to it.
if someone wants it, they will provide it. Our unsuccessful counter
response was, Microsoft and Intel do lead the market. NCs are bad for
both of us. We should encourage people to either use a terminal or use a
diskless NetPC (which we can put on the front burner if need be). If in
Q&A people ask, can people build NCs with this spec, they can say, yes!
our silicon loves every device, but a managed PC is a better option.
Finally, we object to the fact that we received the 99 page server spec
today and aren't in a position to endorse it on Tuesday. The Client
Spec, which we received last week is littered with the term NC
everywhere. Valeriec provided extensive feedback on this to them, but we
have not seen the results.
Seems we have three options:
1) Intel to pull explicit reference to NC and comment on it in the Q&A.
2) Microsoft to accept their position that they are simply being open to
the market situation and work with them to minimize the implied
endorsement. In both 1 & 2 we are in press release and scrub spec.
3) Microsoft agrees to disagree on this announcement and don't
participate in release and spec.
We will coordinate Q&As. Our public position will be, this is yet
another great way to build Windows terminals. We don't believe there is
a market demand for anything called an NC.
4) We go nuclear and release our own WBT spec, press release with our
own OEMs, and directly counter the Intel spec.
1 and 3 seem to be the only acceptable options to me. It certainly hurts
us both if we are perceived to have a schism over the NC. I just as soon
be confused.
Jonathan
http://edge-op.org/iowa/www.iowaconsumercase.org/011607/2000/PX02799.pdf
-------
Isn't it curious that MS, suffering from a severe case of freudian
projection, accuses the other fella of doing exactly what they are
about. Getting control of the spec and releasing a yearly update to
throw confusion in the other camp. The business domain must be a
terrifying place when viewed from the Redmondite perspective.
Analysis: The NetPC would hit sales of "full" clients so think up bogus
technical arguments why it is a bad idea. At the same time release our
own WBT spec, just in case we don't succeed in aborting this baby.
'We wants it, we needs it. Must have the precious. They stole it from
us. Sneaky little hobbitses. Wicked, tricksy, false!'
|
|
