The difference is the ease of use. It's just so incredibly easy for stupid programmers to copy code off the Iternet and introduce that into your proprietary codebase. I don't blame the GPL. I blame the bad education of the people.
Can be tricky, if you have a bunch of young programmers hacking on a closed source codebase and they don't care about these things. You need to educate your programmers about licencing issues and have a monitoring process of your codebase that can identify blatant violations of your licensing policy. Otherwise your codebase will end up depending on GPL libraries or include verbatim copies ("look, ma, what I found on the Internet") of GPL code. If you ever ship a release with such code, be prepared of the whole thing collapsing on you one day.
I know that Holliwood excercices strict control as to when a new movie is released in a country. But withholding The Matrix from New Zealand for 7 years is a bit harsh, isn't it?
There is no essential difference to a checksum clearing house like Razor. But their system needs way to much coerced effort from different parties that it will ever make it out of very large mail providers.
I don't know if there is an RFC that mandates a static address for an MTA. But in current practice an MTA with a dynamic address is considered "rogue" by recieving MTAs. On a dynamic address you will also have a hard time to get a proper reverse DNS entry. If you want to run your own MTA, get a static address with proper reverse DNS entries. You can moan that your setup doesn't violate any RFC, but nobody will listen. SMTP was invented before SPAM. So don't be surprised that it doesn't work the same as 20 years ago.
You can safely block those for quite long. Those IP ranges must not send email directly, ever. They must relay through their ISP's smarthost. Even if they are running their own MTA. It doesn't matter if the current user of that IP spams or not.
From an energetic point of view it's certainly more efficient to directly use the cow's food as fuel for a generator. Agreed, you can't milk it and heat with its poo...
If you can, be very selective from where you can connect via SSH. Sure there is no need for all the chinese address space to have free access to your SSH port. If you administer the machines from behind a dynamic IP, there is a solution. Register a dyndns name and have your dynamic address updated automatically. Then make a cronjob that updates a firewall rule from that address once an hour or so.
Definitely annoying to get phone calls from random people about your unsupported free software. That happened to me too with my infamous LFN Tools, though I didn't even publish any contact information. Scary, those stalkers. I mean I am happy to give some basic support by email. But expecting me to answer silly phone calls... what do these people think?
We use XML a lot to pass business objects around. Often through web services (SOAP), but not only. We never document the XML structure itself (although there is some documentation in our WSDL files). Instead we describe the business objects. Each object has a name and a list of fields. The field has a type (primitive or Object type), a length, a multiplicity (1, 0..1, 1..n, 0..n usually) and a description. All the semantics go into the description. The meaning of some fields may depend on the performed operation. This should be described together with the description of the operation. The objects and fields are then represented as XML elements with the same name. We hardly ever use attributes.
Sample:
Object: Person Fields: name string(32) 1 The last name fname string(32) 1 The first name dob date 0..1 Date of birth kid Person 0..n The persons children
Before even considering to tune the kernel for a specific workload, just try and tune user space. Tune your algorithms. Don't blame the kernel if your algorithm is inefficient. If the kernel has problems to cache your disk load, cache it yourself (hi, PostgreSQL). Your application knows its work load best. The kernel could only do an educated guess. Java VMs have specific tuning options for server and desktop. Use them. Then the kernel also has some tuning paramters (on kernel command line and in/proc). If you have latency problems, reduce interrupts. Last but not least you can turn Linux into a real-time OS and use a real-time capable language. If that's still not enough, try a different platform. And if that doesn't help... I don't want to see that code.
It's perfectly fine to embed and ship a LGPL library with your closed source app. You don't need to mention it even. If you are using a BSD or Apache licensed library, however, you must include the the attribution statement in the documentation. I guess that is what most software doesn't do. Another case is when you are shipping a patched version of an LGPL library, then you need to offer the source code of that patched version to your customer. Mind that "source code" also includes build scripts. That may be a major PITA for most companies.
Where "you" is the person that received the software in binary form in the first place. It doesn't mean either that the company has to offer the code to anyone. But of course "you" can redistribute their source.
AFAIK most ISPs in Switzerland don't offer IPv6. So organizations would need to use 6to4 or tunnel using a tunnelbroker. While possible it just doesn't issue any pressure to ISPs. So we are replacing NAT with 6to4... Not exactly sure that's the point of having IPv6.
Slashdot Mirror
The difference is the ease of use. It's just so incredibly easy for stupid programmers to copy code off the Iternet and introduce that into your proprietary codebase. I don't blame the GPL. I blame the bad education of the people.
Can be tricky, if you have a bunch of young programmers hacking on a closed source codebase and they don't care about these things. You need to educate your programmers about licencing issues and have a monitoring process of your codebase that can identify blatant violations of your licensing policy. Otherwise your codebase will end up depending on GPL libraries or include verbatim copies ("look, ma, what I found on the Internet") of GPL code. If you ever ship a release with such code, be prepared of the whole thing collapsing on you one day.
I know that Holliwood excercices strict control as to when a new movie is released in a country. But withholding The Matrix from New Zealand for 7 years is a bit harsh, isn't it?
Where does SCO take the money from to pay that Fortune guy...?
Linux could do that easily with WINE and the binfmt_misc kernel module.
There is no essential difference to a checksum clearing house like Razor. But their system needs way to much coerced effort from different parties that it will ever make it out of very large mail providers.
This is the loophole that the new license GPL variant (whose name I forgot at the moment) is trying to close.
You mean the AGPL.
I don't know if there is an RFC that mandates a static address for an MTA. But in current practice an MTA with a dynamic address is considered "rogue" by recieving MTAs. On a dynamic address you will also have a hard time to get a proper reverse DNS entry. If you want to run your own MTA, get a static address with proper reverse DNS entries. You can moan that your setup doesn't violate any RFC, but nobody will listen. SMTP was invented before SPAM. So don't be surprised that it doesn't work the same as 20 years ago.
I guess you mean permanent null-routing of the DROP list for instance. Should be done on your ISP's router.
hijacked PCs on dynamic IP addresses
You can safely block those for quite long. Those IP ranges must not send email directly, ever. They must relay through their ISP's smarthost. Even if they are running their own MTA. It doesn't matter if the current user of that IP spams or not.
about 19 seconds on a 2.80MHz Pentium IV :-)
You should think scientists know how to distinguish Mhz from GHz
From an energetic point of view it's certainly more efficient to directly use the cow's food as fuel for a generator. Agreed, you can't milk it and heat with its poo...
If you can, be very selective from where you can connect via SSH. Sure there is no need for all the chinese address space to have free access to your SSH port. If you administer the machines from behind a dynamic IP, there is a solution. Register a dyndns name and have your dynamic address updated automatically. Then make a cronjob that updates a firewall rule from that address once an hour or so.
Definitely annoying to get phone calls from random people about your unsupported free software. That happened to me too with my infamous LFN Tools, though I didn't even publish any contact information. Scary, those stalkers. I mean I am happy to give some basic support by email. But expecting me to answer silly phone calls... what do these people think?
We use XML a lot to pass business objects around. Often through web services (SOAP), but not only. We never document the XML structure itself (although there is some documentation in our WSDL files). Instead we describe the business objects. Each object has a name and a list of fields. The field has a type (primitive or Object type), a length, a multiplicity (1, 0..1, 1..n, 0..n usually) and a description. All the semantics go into the description. The meaning of some fields may depend on the performed operation. This should be described together with the description of the operation. The objects and fields are then represented as XML elements with the same name. We hardly ever use attributes.
Sample:
Object: Person
Fields:
name string(32) 1 The last name
fname string(32) 1 The first name
dob date 0..1 Date of birth
kid Person 0..n The persons children
XML:
<Person>
<name>Doe</name>
<fname>John</fname>
<dob>1974-12-31+02:00</dob>
<kid>
<Person>
<name>Doe</name>
<fname>Harry</fname>
<dob>1991-12-1+02:00</dob>
</Person>
</kid>
<kid>
<Person>
<name>Doe</name>
<fname>Sally</fname>
<dob>1993-12-2+02:00</dob>
</Person>
</kid>
</Person>
all executable files are shown with a red warning flag
You see, in the light of buffer overflows, any file may be "executable".
Before even considering to tune the kernel for a specific workload, just try and tune user space. Tune your algorithms. Don't blame the kernel if your algorithm is inefficient. If the kernel has problems to cache your disk load, cache it yourself (hi, PostgreSQL). Your application knows its work load best. The kernel could only do an educated guess. Java VMs have specific tuning options for server and desktop. Use them. Then the kernel also has some tuning paramters (on kernel command line and in /proc). If you have latency problems, reduce interrupts. Last but not least you can turn Linux into a real-time OS and use a real-time capable language. If that's still not enough, try a different platform. And if that doesn't help... I don't want to see that code.
I've never heard of a successful open source project using dual licensing!
You must have heard of MySQL.
It's perfectly fine to embed and ship a LGPL library with your closed source app. You don't need to mention it even. If you are using a BSD or Apache licensed library, however, you must include the the attribution statement in the documentation. I guess that is what most software doesn't do. Another case is when you are shipping a patched version of an LGPL library, then you need to offer the source code of that patched version to your customer. Mind that "source code" also includes build scripts. That may be a major PITA for most companies.
Where "you" is the person that received the software in binary form in the first place. It doesn't mean either that the company has to offer the code to anyone. But of course "you" can redistribute their source.
You get implicit (web) backup as well :-)
You're honestly abusing email as kind of a SCM tool? Creative...
AFAIK most ISPs in Switzerland don't offer IPv6. So organizations would need to use 6to4 or tunnel using a tunnelbroker. While possible it just doesn't issue any pressure to ISPs. So we are replacing NAT with 6to4... Not exactly sure that's the point of having IPv6.
I have used Mantis in my former job for that kind of stuff. As far as I remember it does all you want.
However you can change the URL to https and it seems to stick.
They will have the session cookie by that time.