They're involved in the distribution [LWN.net]

They're involved in the distribution

Posted Jul 6, 2007 15:09 UTC (Fri) by moltonel (guest, #45207)
In reply to: They're involved in the distribution by coriordan
Parent article: Microsoft's proclamation on GPLv3

In an eweek article, they have a quote from "Bruce Lowry, a Novell
spokesperson" saying "Customers who have already received SUSE Linux
Enterprise certificates from Microsoft are not affected in any way by
this, since their certificates were fully delivered and redeemed prior to
the publication of the GPLv3".

So it sounds like Microsoft does not plan to be "distributing" GPL code in
this manner anymore, and that what has allready been distributed is
protected the the GPL's grandfather clause.

Well, that may not be a huge victory (Did anybody expect Microsoft to
sudenly give up on its patents or start GPL'ing his code because of GPLv3
and the Novel deal ?), but it's something. It'll be interesting to watch
the GPLv3 / Novell deal interpretation match in the next few weeks.

(Log in to post comments)

They're involved in the distribution

Posted Jul 6, 2007 19:12 UTC (Fri) by mmarq (guest, #2332) [Link]

"" Well, that may not be a huge victory... ""

It might be, because for the first time i remember, 'something' is going to force the hand of Microsoft. It usually goes the other way around.

I don't believe that Novell will stop distributing GPLv3, only to appease M$. So Microsoft will drop the coupons, squeal treats, FUD about interoperability,... the usual when they lose on something... and or...

About this interoperability 'illusion' (miss a better word), i believe its about time to embrace and extend M$ deployments.

a) Most of shops have Windows Desktops and Servers.

b) Most of shops can have at least 1 OSS server (Linux...)

c) Samba and NFS are in the business for NAS so important for almost all organisations.

Solution:

Data Storage and or Database

. Use a OSS server implementation... Linux!?... of course

Application Server

. Put the Windows servers(application server) at second plan, with all the relevant applications for windows needed for the organization , in a separated machine because M$ will treat with license withdrawal if it runs on a VM.

. The server dosent need to have the organisation data storage with it, 'au contraire' it will be imperious that it don't. It cant be booted into it also (http://www.etherboot.org/wiki/index.php ) because M$ will retaliate.

.It is only to serve applications to clients in a standalone network administered fashion:

a) Interfaces to the applications will go trough a cgwin or Xorg(why not ?) NX server. (can be much improved !?)

b) Connects to the organization data storage trough a 'FUSE ON WINDOWS' (http://asbjorn.it/blog/2007/01/fuse-for-windows/ ) driver.(still on development)

Exchange

There are good connectors.
There is OpenExchange that can deal with Windows clients.

Authentication

Use Samba or a LDAP server.
If Samba would support FUSE it would be perfect.
It is imperious that Windows servers will not be Domain Controllers.

Clients/Desktops

Use native Linux Desktops where possible.
Use LTSP when possible to save money.
In those Desktops machines where it is not possible to use native Linux, mostly because of absence of good drivers, Samba can authenticate them anyway and there is a NX+cgwin for windows already able to run Linux applications and fuse on windows would help a lot when stable and proper implemented.

** OBVIOUSLY MICROSFT WILL TRY TO SABOTAGE ALL OR ANY OF THIS, DEAL OR NO DEAL **
( that is the reason i call 'Illusion' this interoperability spree)

What can M$ do ?

. Cgwin(xorg ?), NX, 'Fuse on Windows' will be userspace applications, they cant do nothing but Automatic Update bombing them. So it is *intensely recommended* to use nlite( http://www.nliteos.com/ ) for a previous setting up, the GPLed xpy (http://xpy.whyeye.org/about/ ) for cleaning and Autopatcher (http://autopatcher.com/ ) for updates.

. With the so powerful machines 'we' have today, using user space applications will not be a problem.

. Does Microsoft hold patents to their authentication method ?... i bet it does. But inst Samba a clean-room implementation, ?... and it must obey a published protocol and API, which they(M$) are compelled by court of law to deliver, right ?... So i dont see M$ suing anyone over this anytime soon... unless if with their deals they are prepared to pull out a SCO stile coup, and claim breach of contract and ask for repairs... watch out Novell because it wont be patents !

In case of trouble there is always the alternative to run Microsoft in a subordinated separated network... feasible more and more each time that their presence on the organizations networks will be vanishing.

So, who needs a Microsoft deal ?

They're involved in the distribution

Posted Jul 6, 2007 22:46 UTC (Fri) by mmarq (guest, #2332) [Link]

Well i just came across this remarkable good(commercial) application server based on Nx protocol among others;

http://www.2x.com/applicationserver/asfeatures.htm

and

http://www.2x.com/loadbalancer/lbfeatures.htm

It truly is highly feasible to the wide spectrum of the SMB. How much better can RH, Ubuntu, Mandriva... do (can Novell also do it without M$ trying to hit them ?)

for companion there is Thinstation

http://thinstation.sourceforge.net/wiki/index.php/ThIndex

with the remarkable feature that it was tried on co-linux with windows...

http://thinstation.sourceforge.net/Thinstation_and_CoLinu...

so the bottom line is that there isnt a need to wait for FUSE on windows to start the revolution. Not feasible in all parts, but feasible in many shops.