Screw that ltsp shit that is a pain in the ass to work with. It is just easier to light up gdm on the server and load linux on the clients (yes on the drives). Not just modify the last line in the inittab to query the server for a login.
Let me give you a little piece of advice. Slap linux on the client machines. Spend the money and buy sizable server like a 2 or 4 way with as much memory as you can fit in it. On that server just light off gdm. Now on each client modify the inittab to query the server for a login. You will now get at least another 4 years out of those machines. You can keep all of the money you would have lost in hardware, support and licensing for day to day operations. If you value your job take my advice.
Say someone where to take the code a gentleman posted below with a autoback initiated in script and then picked a open relay and fired it at a few million email addresses? Say for instance that it also sent copies of itself to others in the process? Say for instance it also calls cmd.exe to delete anything it can in the system directories.
Wait till the cross exam when his remarks get blown to hell and back.... In court a witness can get up and say anthing especially when the word thinks is involved. Of course by doing so you risk the chance as this fellow has done of getting lashed and dragged through the mud during cross examination.
Ok I guess I could make a slight amendment. A better option would be to use the GPL only on GPL systems and pay for licensing on propiatary operating systems and or those not licensed under the GPL and or LGPL.
You are asking me to enter into a one way contract by asking me to support a BSD or MIT license. I give source to the community because the community gives source to me. I feel obligated to place my code under a GPL license that so in the future you will not have to repurchase something I gave to you for free. My friend you have a ok idea but it is one that I will never support.
A far better solution would to be to immediately change all of our source code licenses to allow only running on GPL systems.
Everyone just needs to place a little ammendment in their source code with the following statement.
Due to Microsoft's unwillingness to provide technical interoperatablity documentation I hearby make a amendment to the GPL license that accompanies this software.
It is hearby against the terms of this license to run, link, compile and or execute any of the software contained in this package on a operating system that is not exclusively distributed under the GPL and or LGPL licenses.
Do it now and deny the use of our hard work on closed systems
I personally refuse to support and or recommend anyone using SOAP web services due to the patent fiasco. I asked on the xml-rpc list if anyone knew of a xml-rpc gateway and Dave Winer immediately jumped to the challange and put up a public gateway.
SOAP really does not do anything that is not provided by nice simple been around for a long time xml-rpc. We should ask google to quit using SOAP and pick up a xml-rpc interface to their search engine now. Personally I will never use SOAP due to it's bloated implementation and the fact that it's design was soley driven by MS with no reguard to the community.
Yes and it is fools passing around FUD that will cause the problems. Tell me please how it is any more insecure than someone downloading a exe off of a web server somewhere and executing it? Hell I will even go so far as to say that and ftp are far more dangerous. How many shops use Outlook? running outlook you might as well have screw my box tatoo'd on your forehead. And please tell me how someone is going to do a http post to a client behind my firewall, yea right.
SOAP is nothing more than a poorly designed and implemented version of xml-rpc. Try getting two soap services talking together one time. Interop does not exist in the SOAP world. Take a look at xml-rpc for some lib's that work (without the hype).
Let's see 2 page spec vs 200, come on people wake up!
Well you are only partially right.... Yes the execution environment holds up wide spread acceptance. The problem lies in the developers that distribute the applications and not with anything that sun does or does not do. It is the job of the application installer to ensure a proper runtime environment. This is the one thing that is horribly missing in most distributed java applications. I recently did a install of limewire on a machine and that is one program that is written to install correctly. It was a simple installation and no I did not have to set up class paths or any crap like that it just worked. Perhaps developers should concentrate on deployment a little just as well?????
Bo ha ha ha, sure I will look at the source when they GPL it. Until then I guess I will have to keep using my totally cross - platform and mature java. On second thought why on earth would I even care?
You my man are a damned idiot, think about what you are saying. Why did Sun have to lay off all of those java engineers? Because the pricks in Redmond are sapping the life out of the java platform.
If one would sit back and think for a moment what people find comfortable you only have to look to the browser to find what you are looking for. The linux desktop should emulate a web page. Hell I have not seen too damn many people that cannot navigate through a browser interface. Now lets see a little innovation, we take the geco rendering engine and make it the desktop. Next we use a local apache web server and build our desktop on that. Microsoft tried to do it but they really did a suck ass job of it, which is why it did not work. I am willing to bet that we could do a bang up job.
Oh don't get me wrong we still need UI applications but for heads down productivity in a general environment a command line app rules. Yea it is boring as shit but I can teach a monkey to use it, this is of course a good thing because most users I know are just ever so slightly smarter than a monkey.
In the beginning there was the command line!
on
Jef Raskin Talks Skins
·
· Score: 2, Insightful
Now I have been UI programming for years but thinking back on it all the command line applications are by far the most productive. Have you ever seen a data entry person using cobol programs on a mainframe? That type of interface is generally for business applications the most productive I have ever seen. Desktops are for people that like to play, if you want to see efficient and consistant interfaces there is no need to look further than the good ole command line.
Who gives a rats about Don Box. He is one huge M$ schill and almost purely reponsible for the messy SOAP protocol. The Fact of the matter is that XML-RPC did everyting that SOAP does but did it in a manner that WAS more efficient. The comes along M$, IBM and Don Box and decides that we need this stuff modeled in such a way that it is easier to produce COM hooks. SOAP was designed with one thing an one thing only in mind, M$. OS programmers where continually bitching about it during the RFC development process but that stuff was just thrown aside. Hell Don Box told us Open Source developers to shutup and he would address the issues (Yea Right) . SOAP is horribly inefficent and SLOW in comparison to XML-RPC. Where I work this is why we are sticking with our XML-RPC implementations and will not touch SOAP with a 10 ft pole.
So it takes little engineering skills to build a battle bot? Yea right I bet you would have less than a 2% chance of building anyting that was remotely competitive.
Slashdot Mirror
If terminal server actually worked, someone might give a damn.....
Screw that ltsp shit that is a pain in the ass to work with. It is just easier to light up gdm on the server and load linux on the clients (yes on the drives). Not just modify the last line in the inittab to query the server for a login.
I can have a full up setup running in 15 minutes.
Let me give you a little piece of advice. Slap linux on the client machines. Spend the money and buy sizable server like a 2 or 4 way with as much memory as you can fit in it. On that server just light off gdm. Now on each client modify the inittab to query the server for a login. You will now get at least another 4 years out of those machines. You can keep all of the money you would have lost in hardware, support and licensing for day to day operations. If you value your job take my advice.
Say someone where to take the code a gentleman posted below with a autoback initiated in script and then picked a open relay and fired it at a few million email addresses? Say for instance that it also sent copies of itself to others in the process? Say for instance it also calls cmd.exe to delete anything it can in the system directories.
;)
Ahhhh amusing it would be
Wait till the cross exam when his remarks get blown to hell and back.... In court a witness can get up and say anthing especially when the word thinks is involved. Of course by doing so you risk the chance as this fellow has done of getting lashed and dragged through the mud during cross examination.
Ok I guess I could make a slight amendment. A better option would be to use the GPL only on GPL systems and pay for licensing on propiatary operating systems and or those not licensed under the GPL and or LGPL.
I like that much better....
You are asking me to enter into a one way contract by asking me to support a BSD or MIT license. I give source to the community because the community gives source to me. I feel obligated to place my code under a GPL license that so in the future you will not have to repurchase something I gave to you for free. My friend you have a ok idea but it is one that I will never support.
A far better solution would to be to immediately change all of our source code licenses to allow only running on GPL systems.
Everyone just needs to place a little ammendment in their source code with the following statement.
Due to Microsoft's unwillingness to provide technical interoperatablity documentation I hearby make a amendment to the GPL license that accompanies this software.
It is hearby against the terms of this license to run, link, compile and or execute any of the software contained in this package on a operating system that is not exclusively distributed under the GPL and or LGPL licenses.
Do it now and deny the use of our hard work on closed systems
Google xml-rpc interface
I personally refuse to support and or recommend anyone using SOAP web services due to the patent fiasco. I asked on the xml-rpc list if anyone knew of a xml-rpc gateway and Dave Winer immediately jumped to the challange and put up a public gateway.
Thanx Dave
SOAP really does not do anything that is not provided by nice simple been around for a long time xml-rpc. We should ask google to quit using SOAP and pick up a xml-rpc interface to their search engine now. Personally I will never use SOAP due to it's bloated implementation and the fact that it's design was soley driven by MS with no reguard to the community.
Yes and it is fools passing around FUD that will cause the problems. Tell me please how it is any more insecure than someone downloading a exe off of a web server somewhere and executing it? Hell I will even go so far as to say that and ftp are far more dangerous. How many shops use Outlook? running outlook you might as well have screw my box tatoo'd on your forehead. And please tell me how someone is going to do a http post to a client behind my firewall, yea right.
And your post back to the client is going to get through my PIX firewall how?
I did not know that marketing people read slashdot.
no idl? Take a look at the Introspect extension methods that most all of the implementations supply.
It is also so limited that I use it at work to transfer literally thousands of xml and binary files every single day.
SOAP is nothing more than a poorly designed and implemented version of xml-rpc. Try getting two soap services talking together one time. Interop does not exist in the SOAP world. Take a look at xml-rpc for some lib's that work (without the hype).
Let's see 2 page spec vs 200, come on people wake up!
Well you are only partially right.... Yes the execution environment holds up wide spread acceptance. The problem lies in the developers that distribute the applications and not with anything that sun does or does not do. It is the job of the application installer to ensure a proper runtime environment. This is the one thing that is horribly missing in most distributed java applications. I recently did a install of limewire on a machine and that is one program that is written to install correctly. It was a simple installation and no I did not have to set up class paths or any crap like that it just worked. Perhaps developers should concentrate on deployment a little just as well?????
Shut off popups in mozilla, problem solved...
Bo ha ha ha, sure I will look at the source when they GPL it. Until then I guess I will have to keep using my totally cross - platform and mature java. On second thought why on earth would I even care?
GPL It and I will have a look, if it's not GPL you know where you can put it......
Yea MS has never tried to mess with java on the server by putting in com hooks and shit.
Nobody said shit about a damn applet...
You my man are a damned idiot, think about what you are saying. Why did Sun have to lay off all of those
java engineers? Because the pricks in Redmond are sapping the life out of the java platform.
If one would sit back and think for a moment what people find comfortable you only have to look to the browser to find what you are looking for. The linux desktop should emulate a web page. Hell I have not seen too damn many people that cannot navigate through a browser interface. Now lets see a little innovation, we take the geco rendering engine and make it the desktop. Next we use a local apache web server and build our desktop on that. Microsoft tried to do it but they really did a suck ass job of it, which is why it did not work. I am willing to bet that we could do a bang up job.
Oh don't get me wrong we still need UI applications but for heads down productivity in a general environment a command line app rules. Yea it is boring as shit but I can teach a monkey to use it, this is of course a good thing because most users I know are just ever so slightly smarter than a monkey.
Now I have been UI programming for years but thinking back on it all the command line applications are by far the most productive. Have you ever seen a data entry person using cobol programs on a mainframe? That type of interface is generally for business applications the most productive I have ever seen. Desktops are for people that like to play, if you want to see efficient and consistant interfaces there is no need to look further than the good ole command line.
Who gives a rats about Don Box. He is one huge M$ schill and almost purely reponsible for the messy SOAP protocol. The Fact of the matter is that XML-RPC did everyting that SOAP does but did it in a manner that WAS more efficient. The comes along M$, IBM and Don Box and decides that we need this stuff modeled in such a way that it is easier to produce COM hooks. SOAP was designed with one thing an one thing only in mind, M$. OS programmers where continually bitching about it during the RFC development process but that stuff was just thrown aside. Hell Don Box told us Open Source developers to shutup and he would address the issues (Yea Right) . SOAP is horribly inefficent and SLOW in comparison to XML-RPC. Where I work this is why we are sticking with our XML-RPC implementations and will not touch SOAP with a 10 ft pole.
So it takes little engineering skills to build a battle bot? Yea right I bet you would have less than a 2% chance of building anyting that was remotely competitive.