The biggest problem I have with speed limits is that they're the same regardless of weather conditions or traffic. We have a stretch of freeway locally where the speed limit is 80 km/h. On a cold, rainy morning in rush-hour traffic, exceeding that by much would be silly, although a lot of people do. On a bright sunny Saturday morning you could do 140 and not be dangerous.
I'll give you 1 guess as to when you'll find a speed-trap out on that highway, though.
Speeding may contribute to accidents. When you start talking about street racing or similarly reckless actions, sure.
Far more though are caused by tailgating, passing unsafely, running red lights, not having the vaguest clue how to merge, failing to signal, cutting people off, drinking and driving, and plain just being bad drivers. If cops actually cracked down on the morons who can't go 2 blocks without endangering someone's life, they might reduce accident rates. But they can't, because they're out on the freeway with their radar gun handing out $100 tickets to people who aren't a danger to anyone.
Give him a webmail account then. Geesh. How many executives send mail from client sites anyway? If they can figure out how to change outlook to talk to the local mail server they probably figure out how to use webmail.
So block all mail from domains registered to nameservers in blacklisted IP space. That's what we used to do before spammers started forging everything.
There is no one who "can't use SPF". If your DNS provider doesn't support it, make them support it or leave. It's not like it's hard to find someone competent to do DNS for you.
Besides, it will take a certain adoption rate before people start blindly blocking non-SPF-compliant domains.
No, it doesn't. You can add the addresses of your ISP's mail servers into your own SPF record or even refer to your ISP's SPF record if they publish one.
The major performance advantage MySQL claims over PostgreSQL in real world use is small queries executed in a primarily read-only environment. MySQL also performs deletes and updates very fast, in a single-user environment.
Locking issues cause MySQL to slow down greatly when the database is shared between readers and writers. In fact, any significant amount of concurrent write traffic has, IME, always caused MySQL to deadlock.
My own testing showed that MySQL, on a dual P4-2.4 with PHP could deliver about 630 pages/second with 1 very simple query per page. PostgreSQL delivered 480 pages/second with the same page. This is MySQL's optimum environment and it only beat PostgreSQL by 31%. Certainly something to consider, but hardly earth shattering.
Since PostgreSQL is so much more capable in every other way, it wasn't hard to decide to move everything to PostgreSQL.
Well 230 years is a pretty good run for a free country. You probably have a few more decades until it's gone completely. Enjoy your future dictatorship. Honestly, most people won't notice the difference.
Dual CPU Webservers are generally considered bad, as they don't scale near as well as 2+ webservers serving files via nfs or other technology.
While that may be true in your case, I disagree for the general case.
When rack space costs you money, a dual-CPU 1 RU box cannot be beat for web-serving efficiency, especially if you serve any volume of dynamic content. For my $day_job, dual-CPU boxes can serve almost exactly 200% of the traffic of a single CPU box, and cost us no more in rack space or network ports or power provisioning than the single CPU box. Oh, and they require the same amount of sysadmin time too, not that that amounts to much in a web cluster.
It doesn't hurt that you can constantly change your operating system to cause other people's products to have problems. Or fail to share internals that are necessary for good performance. But, certainly, nothing like that had anything to do with the success of MS Office.
If the Green Party is in fact fiscally conservative that would certainly differentiate them from the NDP.
Canada has lacked a libertarian party; I may have to check out our Green Party. I had until now assumed they were wacko lefties like the European and US versions.
Government services can't be easily moved since its inherently a local situation, such as teaching...thus their leverage is far stronger than is warranted in a free-market economy.
This is very key point. Public sector unions are the biggest cause of the rapidly increasing cost of government. And it's not the teachers and nurses that are the worst, they at least have good educations and work hard.
It's the janitors and the admin assistants making 2-3 times what their jobs are actually worth that are draining this country dry. Janitors in public schools make as much as most teachers. How much sense does that make? Is there really a shortage of people able to do those jobs? I think not.
Down with CUPE and the HEU. Outsource their asses.
Yeah, but try scripting your GUI. Wget is generally used in scripts as part of some other process, not as a means to itself. That's the beauty of command-line tools, you can easily script them and chain them together to do anything you want.
I can see both sides on this though. If a user for some reason decides to take a copy of a web site, wget is probably harder to use for them (the first time at least) than some Windows shareware they download to do it. But wget is used for so much more than that.
And your government can put you in jail indefinitely without trial, or send you to a secret court where you can be sent away for life without anyone knowing where you are.
Basically, we're all fucked.
The biggest difference is that the Canadian government rarely uses the powers it has. The US government seems hell-bent on doing anything it can get away with.
In theory, SPF should make it easier for these people to send E-mail. They can publish a valid SPF record for their domain, which should make mail from their system more trustworthy than mail from dynamic IP space is generally. Ie, the reason people block mail from dynamic IP space is because of the incredible amount of crud coming from trojanned Windows machines in that space.
If a real sender can somehow distinguish themselves via a valid SPF record, they might actually have better luck sending mail than they do now.
Slashdot Mirror
The biggest problem I have with speed limits is that they're the same regardless of weather conditions or traffic. We have a stretch of freeway locally where the speed limit is 80 km/h. On a cold, rainy morning in rush-hour traffic, exceeding that by much would be silly, although a lot of people do. On a bright sunny Saturday morning you could do 140 and not be dangerous.
I'll give you 1 guess as to when you'll find a speed-trap out on that highway, though.
Speeding may contribute to accidents. When you start talking about street racing or similarly reckless actions, sure.
Far more though are caused by tailgating, passing unsafely, running red lights, not having the vaguest clue how to merge, failing to signal, cutting people off, drinking and driving, and plain just being bad drivers. If cops actually cracked down on the morons who can't go 2 blocks without endangering someone's life, they might reduce accident rates. But they can't, because they're out on the freeway with their radar gun handing out $100 tickets to people who aren't a danger to anyone.
Give him a webmail account then. Geesh. How many executives send mail from client sites anyway? If they can figure out how to change outlook to talk to the local mail server they probably figure out how to use webmail.
So block all mail from domains registered to nameservers in blacklisted IP space. That's what we used to do before spammers started forging everything.
There is no one who "can't use SPF". If your DNS provider doesn't support it, make them support it or leave. It's not like it's hard to find someone competent to do DNS for you.
Besides, it will take a certain adoption rate before people start blindly blocking non-SPF-compliant domains.
No, it doesn't. You can add the addresses of your ISP's mail servers into your own SPF record or even refer to your ISP's SPF record if they publish one.
That's more than any dino-juice burners get, and the performance is better
Yeah but the dino-juice burners can stop for 3 minutes, fill the tank, and then go again. How long does it take to recharge those batteries?
And, as others have pointed out, there are diesel cars with better range per tank (my Jetta TDI included).
The major performance advantage MySQL claims over PostgreSQL in real world use is small queries executed in a primarily read-only environment. MySQL also performs deletes and updates very fast, in a single-user environment.
Locking issues cause MySQL to slow down greatly when the database is shared between readers and writers. In fact, any significant amount of concurrent write traffic has, IME, always caused MySQL to deadlock.
My own testing showed that MySQL, on a dual P4-2.4 with PHP could deliver about 630 pages/second with 1 very simple query per page. PostgreSQL delivered 480 pages/second with the same page. This is MySQL's optimum environment and it only beat PostgreSQL by 31%. Certainly something to consider, but hardly earth shattering.
Since PostgreSQL is so much more capable in every other way, it wasn't hard to decide to move everything to PostgreSQL.
Well 230 years is a pretty good run for a free country. You probably have a few more decades until it's gone completely. Enjoy your future dictatorship. Honestly, most people won't notice the difference.
aww, don't worry about it. Even the Nazis didn't come for most people, just the ones that challenged them.
Be a good little obedient citizen and all will be well. That's certainly in line with the principles of a free country. lol.
Dual CPU Webservers are generally considered bad, as they don't scale near as well as 2+ webservers serving files via nfs or other technology.
While that may be true in your case, I disagree for the general case.
When rack space costs you money, a dual-CPU 1 RU box cannot be beat for web-serving efficiency, especially if you serve any volume of dynamic content. For my $day_job, dual-CPU boxes can serve almost exactly 200% of the traffic of a single CPU box, and cost us no more in rack space or network ports or power provisioning than the single CPU box. Oh, and they require the same amount of sysadmin time too, not that that amounts to much in a web cluster.
This is a hedge bet against them being unable to contine to extend copyright terms indefinitely.
Are there any good open source anti-virus programs out there? We could sure use one.
http://www.clamav.net/
It doesn't hurt that you can constantly change your operating system to cause other people's products to have problems. Or fail to share internals that are necessary for good performance. But, certainly, nothing like that had anything to do with the success of MS Office.
ICON's did run some version of UNIX (that had a lot of NetWare'ish features tacked on as I recall). We had a lab of them in my high school.
In retrospect they were actually a pretty cool setup, though we had no real software for them and the teachers had no idea what to do with them.
If the Green Party is in fact fiscally conservative that would certainly differentiate them from the NDP.
Canada has lacked a libertarian party; I may have to check out our Green Party. I had until now assumed they were wacko lefties like the European and US versions.
AFAIK those schools in Seattle are run by the government. How is that anti-socialist exactly?
Government services can't be easily moved since its inherently a local situation, such as teaching...thus their leverage is far stronger than is warranted in a free-market economy.
This is very key point. Public sector unions are the biggest cause of the rapidly increasing cost of government. And it's not the teachers and nurses that are the worst, they at least have good educations and work hard.
It's the janitors and the admin assistants making 2-3 times what their jobs are actually worth that are draining this country dry. Janitors in public schools make as much as most teachers. How much sense does that make? Is there really a shortage of people able to do those jobs? I think not.
Down with CUPE and the HEU. Outsource their asses.
Yeah, but try scripting your GUI. Wget is generally used in scripts as part of some other process, not as a means to itself. That's the beauty of command-line tools, you can easily script them and chain them together to do anything you want.
I can see both sides on this though. If a user for some reason decides to take a copy of a web site, wget is probably harder to use for them (the first time at least) than some Windows shareware they download to do it. But wget is used for so much more than that.
djbdns supports zone transfers. The tcp server accepts AXFR commands, and axfr-get implements a client-side transfer into a djbdns-format zone file.
djbdns does support zone transfers. It's not the recommended way of running a secondary (rsync over ssh is), but you can do it if you really want to.
Well, all the short options you have there can be expressed with longer versions.
wget --no-clobber --force-directories --html-extension --recursive --level=5 --convert-links --page-requisites
seems to have the same functionality, and is less "cryptic", if you prefer. Many command line programs support both short and long options.
Yep, the solution to ageing isn't broccoli and exercise - it's cloning!
Depends if you still expect to be driving your car in 7 years. If you want a new car every 2 or 3 years, then leasing might make sense.
And your government can put you in jail indefinitely without trial, or send you to a secret court where you can be sent away for life without anyone knowing where you are.
Basically, we're all fucked.
The biggest difference is that the Canadian government rarely uses the powers it has. The US government seems hell-bent on doing anything it can get away with.
In theory, SPF should make it easier for these people to send E-mail. They can publish a valid SPF record for their domain, which should make mail from their system more trustworthy than mail from dynamic IP space is generally. Ie, the reason people block mail from dynamic IP space is because of the incredible amount of crud coming from trojanned Windows machines in that space.
If a real sender can somehow distinguish themselves via a valid SPF record, they might actually have better luck sending mail than they do now.