Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment i have to admit (Score 1) 341

that i never understood their business model in the first place. what does RIM aside from undesirable vendor lock-in provide, that cannot be achieved with normal means such as imaps and smtp with ssl/tls? i (like many other people) have been using encrypted email services for decades.

Comment hard to even get a provider (Score 1) 406

i don't know how it looks in other parts of the world but here in austria it is close to impossible to even find a provider that will offer you a routable ipv6 address. i checked the biggest providers available in my area and the only thing i could get would have been a tunnel.

Comment the problem with linux on the corporate desktop (Score 1) 901

is maintainability. we have around 150 desktops here where i work (all servers except one run linux) and we were thinking about migrating the desktops to linux. i have used linux exclusively as a desktop OS for the last 8 years (also at work, i am a programmer), but i have to agree that it's just not possible to run and maintain a mid- to large scale client network of linux desktop computers. here's why:

1.) linux aims at providing the most possible freedom to its users
this is what you don't want when you administer hundreds of computers. you want the possibility to restrict the user as much as possible, so that they don't break everything all the time and require your assistance.

2.) AD, logonscripts, group policies, authentication
again the same story. linux is built from ground up to fulfill the user's wishes, not the admin's. just take for example some very basic thing like browser-settings. you cannot force firefox, konqueror, opera or whatever to use a proxy server while inhibiting the users to change it themselves. (yes transparent proxying but that sucks). it looks like chrome is trying to make something like that possible with the policies.d directory, but this is not widely available. the whole configuration-concept of unix-based programs is to load system-wide settings first, and let the user override them. windows' concept is exactly the other way around, which is why it is so successful in companies.

what is also done very well on windows is the logon process. no matter if the PDC is there you can still use your computer. did you ever try that on linux with /home mounted via NFS? impossible. kerberos and ldap auth are a step in the right direction on the server side, but client support for these things is poor at best.

3.) MS office
this point can be illustrated ad infinitum, so i won't go into details, but eveyone who actually works with office documents that contains at least macros, pivots or charts will agree that openoffice/libreoffice is not usable there, as soon as you need to be compatible with clients. MS access is another story of its own.

4.) printing
cups has improved a lot over the years, but there are still lots of specific printer features that you cannot use if you use cups. this is why we have exactly 1 windows server. especially larger printers (in the 3-10k euro area) work only half-assed via cups. either you cannot do accounting or page stats, or you cannot privilege jobs or whatever.

5.) ACL
there is no possibility to set ACLs via a gui on linux. also posix acls suck. i am very happy to see that nfs4 acls are more and more adopted, but there is still a long way to go until they will be widely available. you can just not explain some sales guy or client service lady how to use setfacl to share a document with a different group via commandline, when all they have to do in windows is check a checkbox.

it breaks my heart to say this as a long time linux user and open source developer, but linux on the corporate desktop is an illusion. not because linux is bad, but because the concept is fundamentally incompatible with what administrators of hundreds if clients need.

Slashdot Top Deals

Get hold of portable property. -- Charles Dickens, "Great Expectations"

Working...