Player goes into jungles and swamps on foot. Enemy is better than player 99% of the time. Player may or may not get help from support lines. Player may randomly be hit by leftover chemicals from air strikes to destroy enemy troops. Pretty good scenario.
Hey, he can always say: Give me a job or I'll just post duplicate links to your site on Slashdot.
Seriously though, building a large, loyal customer base is a serious management achievement. Getting the site name into the Jargon file (Slashdot Effect) is another. Building a/legitimate/ large DDOS tool is another achievement (see slashdot effect).
[Obl. spelling joke: That first line should be spelled differently]
My apologies for missing the sarcasm. Too many people are dead serious when they speak about the one true language. As for the right tool, TMTOWTDI:P Use the tool you know works. I would rather that programmers know more than one language, and the strengths and weaknesses o the language. Just because you can do everything in sendmail.cf macros, does not mean you should. Different languages exist for a reason, and the developer should be able to judge what best fits the situation.
Not really. I have seen good C code, good Perl code, unmaintainable Java code, bad Python code. It finally depends on the quality of the programming team, which designs and implements the program. I am an administrator primarily, with enough knowledge of code to know buggy programs. Writing code is easy, writing good code is hard.
I prefer to learn more than one language, and use the right tool for the right job. I have no desire to implement graphics in C, or high performance on low memory systems in Java.
Perl is great for text processing, for database work, but not for numeric manipulation. IDEs are nice for doing user interfaces (unless the user is a poweruser/admin, in which case, shell access has to be available for piping data around.)
Finally, it boils down to the right tool for the right job, and one language does not fit all requirements. And programmer discipline is always needed for good code.
Perl's greatest strengths are in text manipulation. Perl has some fantastic regex support. www.cpan.org [Central Perl Archive Network] has Perl modules for almost everything you need it for. To talk to a SQL handling RDBMS, perl -MCPAN -e 'install DBI' perl -MCPAN -e 'install DBD::DBtype'
DBI is like ODBC, a wrapper over DBMS specific drivers.
If you want to talk to a Directory server, install Net::LDAP.
Perl greatest strength is its flexibility, and tis weakness as well. It takes some effort to write good code in Perl, because it is so easy to write very bad unmaintainable Perl code. You need to discipline yourself when writing Perl.
Easy enough. You run your MX, smarthost through our mail servers. We offered static IPs if you wanted those too (10 USD/annum for static ip, Secondary MX and PTR record of choice. There were no inbound blocks, and no throttling unless you really abused the network and kept up 2+ GB/day of traffic. Occasional bursts were allowed). There was no requirement that you use our address to relay mail, just that you have a valid IP in our network.
The whole reason why we were forced to block 25 outbound was direct to MX spam. I had a couple of spammers on the network that did direct to MX, and explaining to management why a paying customer needs to be kicked off is hard. Much easier to do when you have the logs and can just say ===> AUP violation (abuse of ISP servers) and terminate directly. Plus, you don't have to explain each time how the RFC 2822 headers help trace a mail.
If you did want to do direct to MX, you had to justify to the mail server admin about why you wanted to do that, and that you were competent to run a mail server properly (keep it closed, don't spam was all we asked, BTW). I haven't heard one client of ours complain about that particular policy, or leave because of it.
It was much easier to assume clueless customers and let them prove their competence rather than to assume clueful customers and weed out the incompetents, because the incompetents outnumber the clued.
It kept spammers from using the network. We did get a couple on dialup, and they lost their accounts within minutes of getting a complaint at abuse@domain.
AFAIK, at that point of time, we were the only ISP to have egress filtering implemented too. Unhappily, that company has now been taken over by a bigger company, whch removed the egress filtering, and the mail filters and are happily running open relays. Sucks to have a pair of finely tuned postfix boxes delivering spam.
I used to work at a small ISP, before it got taken over by a bigger clueless one. We were using postfix ( http://www.postfix.org ) with PCRE support. Incoming mail was first passed through a few DNSBLs (ordb, wirehub.nl and relays.osirusoft.com)
We had all mails checked through a simple regex body check, which looked for a few keywords like US1918 and phrases like "To unsubscribe please click". These were bounced (at that time Postfix didn't have the lovely discard keyword).
We used regular expressions from the postfix site to additionally capture spam.
We blocked outbound port 25/tcp to force dialup and cable users to relay through our servers (so that we had logs).We had no limits on how many iusers you sent mail to, but if you were complained about with proof as headers, then the logs got checked and the user terminated. Also, you could use any identity you liked (we didn't have the from user@our.domain limitation).
Additionally, I had log parsers which watched for connections coming in from ips and notifying me when they would go above limits within certain time periods. This was mostly useful in catching virus infected machines.
Today, I would run amavisd-new with clamav (http://clamav.elektrapro.com) for this.
I had about 5-6 false positives with this for about 9000 users with about 20K mails/day.
Mail to postmaster@our.domain, abuse@our.domain was exempt from all checks.
Using blacklists saved about 5% of our bandwidth, which in USD would have been about 50000 USD.
It should be easy enough to write a Perl script to read your logs and throttle customers down to a maximum rate.
Staff? Who needs staff? We all know that all that filtering of plain text is done by Perl scripts. All those schools can easily get together to hire someone to create a regex list generator (no need for fancy optimizations, just basics).
Giving up moderation points for this post, but on what standards do you measure an acceptable wage? Indian labour is cheap, so will you agree to accept our wages? I wouldn't mind working for US wages, but the *average* salary of a US citizen is about 4 to 5 times what the middle management makes around here. IT salaries here are about 4-8K pa.
If you want to say equivalent salaries, based on living costs, then expect work to still come to India because the cost of moving software across the world is low.
Oh, and think of the fact that we see low costs as an asset to be leveraged in business. Your International union idea is bound to fail for these reasons.
Hmmm, becuase OOP essentially is a way of working to a standard API. Just under a different name. OO is a *design* methodology, not a coding one.
OO is essentially designing an API.
You can do OO work in C as well as spaghetti code in C. Its pretty easy, provided you spend enough time on doing the basic design correctly and never forgetting the original requirements.
Actually, not so easy to maintain. And in schools, I would insist that students learn both commercial and Free Software. The plan from Microsoft implies that MSware will be compulsory, with no mention of alternate software (MS Office, MS Windows....)
What I recommend is that schools have dual boot capabilities and students learn to use both Unix and Microsoft.
The local language issue hasn't been fixed in any way, with loads of broken stuff even in Windows. There are multiple attempts for converting OpenSource/Free Software into Indic, while Microsoft is supporting a few languages, officially. Support for the remaining languages is promised n the next release of windows.
Also remember that the syllabus is set for 10 years, so there will be no modifications until the next revision. I think that cost is just too high.
Most hardware available is old. Plenty of schools still run 386/486 processors. There is no way that Win2K can be made available without spending lots of money on hardware. Linux/BSD will run fine on the older boxen.
www.openantivirus.org Save the antivirus costs. tightVNC can probably replac Citrix. firewall *can* be replaced with a Free software box (OpenBSD+required proxies --> zorp might be what you need, or squid + postfix/qmail might suffice)
Well, Amavisd-new uses the Perl Net::SpamAssassin, runs as a daemon and works nicely in a mail hub. clamav is a GPLed antivirus scanner. Filter out viruses and spam at one go.
Hmmmm, I would rather pay for the better programmer. Run time might not matter for the desktop, but on the server side, it does matter a whole lot. Unless you are just comparing web applications, server side performance matters a whole lot. There is a *significant* cost difference between high performance apps and low performance apps in runtime. On low end hardware, Perl is 2-3 times as fast as Java for the same application (daemonized SNMP monitor for a few devices on a switched network). Oh, and Perl used less resources too. And I don't want Perl doing the truly high performance stuff either. I prefer to use C code.
Slashdot Mirror
o Vietnam
Player goes into jungles and swamps on foot.
Enemy is better than player 99% of the time.
Player may or may not get help from support lines.
Player may randomly be hit by leftover chemicals from air strikes to destroy enemy troops.
Pretty good scenario.
The X server runs locally. The client runs on the remote system and has a display on the local system.
VNC runs a similar setup, but exports the entire display.
If you have ssh tunneling for X enabled,
$ssh user@remote
$export DISPLAY=
$soffice &
OpenOffice over X? Wasn't this stuff exactly what x was designed to do? Run GUI applications transparently over a network.
Hey, he can always say: Give me a job or I'll just post duplicate links to your site on Slashdot.
/legitimate/ large DDOS tool is another achievement (see slashdot effect).
Seriously though, building a large, loyal customer base is a serious management achievement. Getting the site name into the Jargon file (Slashdot Effect) is another.
Building a
[Obl. spelling joke: That first line should be spelled differently]
My apologies for missing the sarcasm. Too many people are dead serious when they speak about the one true language. :P
As for the right tool, TMTOWTDI
Use the tool you know works. I would rather that programmers know more than one language, and the strengths and weaknesses o the language.
Just because you can do everything in sendmail.cf macros, does not mean you should. Different languages exist for a reason, and the developer should be able to judge what best fits the situation.
Not really. I have seen good C code, good Perl code, unmaintainable Java code, bad Python code.
It finally depends on the quality of the programming team, which designs and implements the program.
I am an administrator primarily, with enough knowledge of code to know buggy programs.
Writing code is easy, writing good code is hard.
I prefer to learn more than one language, and use the right tool for the right job.
I have no desire to implement graphics in C, or high performance on low memory systems in Java.
Perl is great for text processing, for database work, but not for numeric manipulation.
IDEs are nice for doing user interfaces (unless the user is a poweruser/admin, in which case, shell access has to be available for piping data around.)
Finally, it boils down to the right tool for the right job, and one language does not fit all requirements.
And programmer discipline is always needed for good code.
Perl's greatest strengths are in text manipulation.
Perl has some fantastic regex support.
www.cpan.org [Central Perl Archive Network] has Perl modules for almost everything you need it for.
To talk to a SQL handling RDBMS,
perl -MCPAN -e 'install DBI'
perl -MCPAN -e 'install DBD::DBtype'
DBI is like ODBC, a wrapper over DBMS specific drivers.
If you want to talk to a Directory server, install Net::LDAP.
Perl greatest strength is its flexibility, and tis weakness as well. It takes some effort to write good code in Perl, because it is so easy to write very bad unmaintainable Perl code. You need to discipline yourself when writing Perl.
Easy enough. You run your MX, smarthost through our mail servers. We offered static IPs if you wanted those too (10 USD/annum for static ip, Secondary MX and PTR record of choice. There were no inbound blocks, and no throttling unless you really abused the network and kept up 2+ GB/day of traffic. Occasional bursts were allowed). There was no requirement that you use our address to relay mail, just that you have a valid IP in our network.
The whole reason why we were forced to block 25 outbound was direct to MX spam. I had a couple of spammers on the network that did direct to MX, and explaining to management why a paying customer needs to be kicked off is hard. Much easier to do when you have the logs and can just say ===> AUP violation (abuse of ISP servers) and terminate directly. Plus, you don't have to explain each time how the RFC 2822 headers help trace a mail.
If you did want to do direct to MX, you had to justify to the mail server admin about why you wanted to do that, and that you were competent to run a mail server properly (keep it closed, don't spam was all we asked, BTW). I haven't heard one client of ours complain about that particular policy, or leave because of it.
It was much easier to assume clueless customers and let them prove their competence rather than to assume clueful customers and weed out the incompetents, because the incompetents outnumber the clued.
It kept spammers from using the network. We did get a couple on dialup, and they lost their accounts within minutes of getting a complaint at abuse@domain.
AFAIK, at that point of time, we were the only ISP to have egress filtering implemented too.
Unhappily, that company has now been taken over by a bigger company, whch removed the egress filtering, and the mail filters and are happily running open relays. Sucks to have a pair of finely tuned postfix boxes delivering spam.
I used to work at a small ISP, before it got taken over by a bigger clueless one.
We were using postfix ( http://www.postfix.org ) with PCRE support.
Incoming mail was first passed through a few DNSBLs (ordb, wirehub.nl and relays.osirusoft.com)
We had all mails checked through a simple regex body check, which looked for a few keywords like US1918 and phrases like "To unsubscribe please click". These were bounced (at that time Postfix didn't have the lovely discard keyword).
We used regular expressions from the postfix site to additionally capture spam.
We blocked outbound port 25/tcp to force dialup and cable users to relay through our servers (so that we had logs).We had no limits on how many iusers you sent mail to, but if you were complained about with proof as headers, then the logs got checked and the user terminated.
Also, you could use any identity you liked (we didn't have the from user@our.domain limitation).
Additionally, I had log parsers which watched for connections coming in from ips and notifying me when they would go above limits within certain time periods. This was mostly useful in catching virus infected machines.
Today, I would run amavisd-new with clamav (http://clamav.elektrapro.com) for this.
I had about 5-6 false positives with this for about 9000 users with about 20K mails/day.
Mail to postmaster@our.domain, abuse@our.domain was exempt from all checks.
Using blacklists saved about 5% of our bandwidth, which in USD would have been about 50000 USD.
It should be easy enough to write a Perl script to read your logs and throttle customers down to a maximum rate.
http://personals.ufies.org/home.html
Good luck
Staff? Who needs staff? We all know that all that filtering of plain text is done by Perl scripts.
All those schools can easily get together to hire someone to create a regex list generator (no need for fancy optimizations, just basics).
Erase last word
Namaste == Hello.
Kathmandu is the capital of Nepal, an independent sovereign nation.
Giving up moderation points for this post, but on what standards do you measure an acceptable wage?
Indian labour is cheap, so will you agree to accept our wages? I wouldn't mind working for US wages, but the *average* salary of a US citizen is about 4 to 5 times what the middle management makes around here.
IT salaries here are about 4-8K pa.
If you want to say equivalent salaries, based on living costs, then expect work to still come to India because the cost of moving software across the world is low.
Oh, and think of the fact that we see low costs as an asset to be leveraged in business. Your International union idea is bound to fail for these reasons.
Hmmm, becuase OOP essentially is a way of working to a standard API. Just under a different name.
OO is a *design* methodology, not a coding one.
OO is essentially designing an API.
You can do OO work in C as well as spaghetti code in C. Its pretty easy, provided you spend enough time on doing the basic design correctly and never forgetting the original requirements.
perl -MCPAN -e 'install HTML::Template'
perl -MCPAN -s 'install Text::Template'
Works well for me.
And don't embed HTML in print statements.
HEREDOC (if templates don't work for you)
Swatantra == Self Reliance, Independance. French Libre.
Actually, not so easy to maintain. And in schools, I would insist that students learn both commercial and Free Software. The plan from Microsoft implies that MSware will be compulsory, with no mention of alternate software (MS Office, MS Windows....)
What I recommend is that schools have dual boot capabilities and students learn to use both Unix and Microsoft.
The local language issue hasn't been fixed in any way, with loads of broken stuff even in Windows. There are multiple attempts for converting OpenSource/Free Software into Indic, while Microsoft is supporting a few languages, officially. Support for the remaining languages is promised n the next release of windows.
Also remember that the syllabus is set for 10 years, so there will be no modifications until the next revision. I think that cost is just too high.
Most hardware available is old. Plenty of schools still run 386/486 processors. There is no way that Win2K can be made available without spending lots of money on hardware. Linux/BSD will run fine on the older boxen.
Just my 1 INR.
It varies between 48-49 INR for 1USD, but I would suggest using 50 INR == 1USD for back of the envelop calculations.
www.openantivirus.org
Save the antivirus costs.
tightVNC can probably replac Citrix.
firewall *can* be replaced with a Free software box (OpenBSD+required proxies --> zorp might be what you need, or squid + postfix/qmail might suffice)
Well, Amavisd-new uses the Perl Net::SpamAssassin, runs as a daemon and works nicely in a mail hub.
clamav is a GPLed antivirus scanner. Filter out viruses and spam at one go.
Wave particle duality from quantum physics. Light behaves like a wave and a particle at the same time.
Rather nice pun
Hmmmm, I would rather pay for the better programmer.
Run time might not matter for the desktop, but on the server side, it does matter a whole lot.
Unless you are just comparing web applications, server side performance matters a whole lot.
There is a *significant* cost difference between high performance apps and low performance apps in runtime. On low end hardware, Perl is 2-3 times as fast as Java for the same application (daemonized SNMP monitor for a few devices on a switched network). Oh, and Perl used less resources too.
And I don't want Perl doing the truly high performance stuff either. I prefer to use C code.
For some reason, I am thinking of:
Beware of the leopard
I think you mean, it fork(2)'ed.