You can call it murder, I'd call it effectively removing a future threat. And if it were my daughter, it wouldn't matter what you called it - I'd still kill the guy.
I did not RTFA -- If he was MASS PRODUCING, that is very different than making personal copies. Similarly, I do agree that giving money to those producing such pornography should be illegal. I was under the impression he was being jailed for copying pornography for personal use, and they used this to lock him up for longer than he would've been otherwise. If he was NOT mass producing, the burning should be of no consequence.
I don't care whether he was mass producing, making copies for himself, or just watching them on his computer while jerking off. I want his balls on a plate.
Now, before you dismiss me as some right-wing nut case, I should tell you that I'm considered very (perhaps too) liberal by my friends - pro-choice, oppose the death penalty (believe our judicial system is too prone to mistakes), support many social programs, believe same sex marriage should be legal, etc. However, I'm a human animal with a daughter and the thought of pedophiles triggers an instinct to kill in me. It's that simple. No rational argument will change it - kill the fucker.
Forgive me for posting without reading, but when I see a phrase like "scumbag pedophile", I get rather pissed off.
Me too - I'm friends with plenty of scumbags and none of them deserve to be compared with pedophiles.
All the people I worked with that pushed ITIL spent their time wasting mine in meetings, producing little and scampering around with the latest "cool" vendor. I'd be surprised if someone with an opensource leaning would be taken in by ITIL or if someone taken in by ITIL would produce something opensource. I'm just glad it died a quiet death at my place of employment.
Before you mod this a troll, go read up on ITIL. On the surface it doesn't look bad, but the extremes the consultants can push it to are ludicrous. And the consultants almost always will...
Wow. This is the first time that the first comment I read was well thought out, well written, and on topic. You'd get my Mod points if I had them.
I'd only like to stress your last sentence. Retaliation can only lead to bad things. These guys should get as much credit for a job well done as they can and use it as resume fodder to find a better gig - either in a different dept or a different company.
If you've been in the business a while, you should know 1 or 2 skilled infrastructure guys. Finding someone with the right balance of design, procurement, and build skills that is looking for some side work is an exercise left up to you.
Once you've identified this person, pay him to do the work and explain it to you at the same time - that where the multiplier comes in to play.
I've done this type of work for friends/relatives in the past. Just remember that business is business.
It's mainly the honor system "enforced" by two things: 1) the more people that know about something the harder it is to keep it secret and 2) most people aren't willing to go to jail just to protect their company's shareholders.
That presumes that management generally has given broad authority to the CIO to make substantive changes in business process, organizational structure and other critical areas of business operation.
Uh? Where the heck did you get that idea?
The CIO's jobs is provide technical leadership and direction to support the business processes, structure, and operation. To do this, they need to provide the "best cost" (notice I didn't say lowest - it's not always best) solutions to the business and justify them in profit/loss or risk/benefit. If part of the case involves changing a business process, then that should stand on the merits (yes, this means dollars) of the case.
That broad of control isn't usually given out, thus its incumbant on more senior management to have a good operational understanding of technology's role in the business. It's not just thumbs up or down based on cost.
Yes, but the keyword is "operational". Where the significant characteristics of two possible solutions are identical (e.g. functionality, maintainability, reliability, vendor viability, or whatever) then cost rules. If that's not the case, then the differences need to be weighted and/or costed. And yes, everything (and I mean everything) can be boiled down to dollars and is at successful companies on a regular basis.
When it comes to technology, managers often don't care and don't want to know, except when it costs money.
That's their job. Companies exist to make money - end of story. Technology for technologies sake is foolish and wasteful unless you're in an R&D department.
That being said, all technology spends (e.g. upgrades, redesigns, rewrites, replacements, etc.) can and should be boiled down to dollars that either fall into a profit/loss or risk/benefit catagory (hopefully over 3-5 years). If a CIO isn't doing this (or having it done for them) they should be fired.
If you think more subtlety is needed, then I hope you're a low to mid level SA/DBA/Developer because you don't understand the "business" side of the company that employs you. I'm not trying to be rude, but that's the brutal reality of the business world. On a lighter side, there'a always academia... if you'd prefer politics to dollars.
I haven't donated but I will when they take pay-pal.
I tried donating once about 2 years ago. Unfortunately (for Debian and the SPI), I raised a big stink about them not accepting Paypal, credit cards, or anything electronic. This wasn't received very well. I finally just sent them a check for $50 but it was never cashed. I don't know whether it was lost or if the treasurer just decided he didn't want my money.
Relevance is specific to the agreements of the parties involved. Not that is matters.
Larry provided a free product to the Linux community for several years. We all benefited from it. He then decided to stop providing it when he felt it was being used in bad faith - his product, his choice.
Isn't choice what this is all about? Why is everyone whining about it?
I accept that it might have been the only working solution at the time, but Linus would have done better if he'd said it was temporary until a good Open Source product came along.
Linus did say that. What part of "I will use the best tool for the job" was unclear? The best tool was proprietary with a very friendly non-commercial license. Go through the Kernel Cousins archives - on multiple occasions Linus said he would switch to an Open Source product as soon as one existed that met his needs.
All the people saying "I told you so" now are the same people that didn't bother to get off their high horses and pay attention to Linus' position. These are the people who ignored Linus' challenge to put up or shut up, i.e. quick whining and write an open source version control system that would meet his needs. An Open Source advocate that merely complained instead of writing code is a hypocrite in my book.
I'd say you don't know enough about UNIX systems to deserve root access. What exactly do you think you need it for? The only thing you really need is the ability to start Apache on port 80. Everything else can be done w/out priviledged access if setup properly.
You question should be a simple math problem. How much storage is required? What throughput do you need? Be sure to include expected growth over the depreciation period for both to keep the accountants happy (write-offs screw up runrate projections). Now it's just math based on tech specs to come up with several configuration options that meet your requirements. Once you have some options, a comparison matrix is one way to decide between the configurations you came up with based on cost, flexibility, scalability, vendor viability, and other "not strictly technical" factors.
Two quick comments about RAID5. First, the posts dismissing it as an option due to performance concerns are silly since your requirements are unknown. Second, another poster already brought up the fact that a 3 disk RAID5 is a bit odd - adding little additional storage while introducing a write penalty. But hey, if it meets your requirements go for it.
Please don't misquote me. I wrote "it seems a daunting task". And I don't beleive it's poorly designed - it's just a lot of information in a compact format. That seems to bather people who don't/won't take the time to understand the format. Once you get it all man pages make sense.
The first time someone told you "everything is a file" when describing Unix it probably sounded goofy/confusing. But after you understand what that means the power and control it gives you is awesome. man pages are like that - take the time to understand the format and all the information you need is right there in front of you.
You must excuse me for being a Unix user long before Google existed. man pages aren't impossible to read, you just need to learn to read them. I'll admit it seems a daunting task, but it's very useful. Try googling for information when the firewall is what you're trying to fix...
To learn how to search man pages, type "man more" if your pager is more or "man less" if your pager is less. And unlike Windows Help and OS X Help files you can use regular expressions. There's also no gui overhead - very nice when the equipment your working on is 800 miles away and only allowed to connect to the systems via SSH.
I guess if you had ever bothered to type "man man" I wouldn't be responding to your post...
Yes, for servers. But ask your IT manager to buy all new DELL Pentium 4GHZ workstations for the entire company because you need to code in Java and see what he says.
Why would I do that? It'd be a silly waste of money. (Rule #4: Every $100,000 is a head and the head you save may be your own.)
Right now all Prod applications run in a shared server environment - so our Dev, QA, & ITE regions are shared too. For example, I'm in the middle of consolidating all our Weblogic development (4 groups / 30ish developers) onto a Sun E2900 (8CPUs / 16 cores) from an aging E6500 and an E450. This allows us to share not only the hardware resources but the software licensing as well. Of course, this is just for Dev - the other regions are scaled horizontally according to capacity and availability requirements with like applications being grouped together.
BTW, I'm not a developer. I work in A&E making sure the infrastructure meets business and technical requirements while driving down run-rate.
People are slower and more expensive. Hardware gets faster and cheaper every year.
Anyone who has worked with budgets in large corporations can tell you Developer/Tester hours are generally the majority of the budget. Hardware is a drop in the bucket (and you can even capitalize it). On many projects I've worked on, Java has driven the people cost down resultig in a net savings even though we may have had to throw a crap load (official Business terminology) of CPU/memory at the application.
Slashdot Mirror
You can call it murder, I'd call it effectively removing a future threat. And if it were my daughter, it wouldn't matter what you called it - I'd still kill the guy.
Now, before you dismiss me as some right-wing nut case, I should tell you that I'm considered very (perhaps too) liberal by my friends - pro-choice, oppose the death penalty (believe our judicial system is too prone to mistakes), support many social programs, believe same sex marriage should be legal, etc. However, I'm a human animal with a daughter and the thought of pedophiles triggers an instinct to kill in me. It's that simple. No rational argument will change it - kill the fucker.
Me too - I'm friends with plenty of scumbags and none of them deserve to be compared with pedophiles.Those were the days - back when I knew everything and wouldn't take constructive critisism from anyone!
Before you mod this a troll, go read up on ITIL. On the surface it doesn't look bad, but the extremes the consultants can push it to are ludicrous. And the consultants almost always will...
I'd only like to stress your last sentence. Retaliation can only lead to bad things. These guys should get as much credit for a job well done as they can and use it as resume fodder to find a better gig - either in a different dept or a different company.
http://www.sun.com/software/solaris/get.jsp
For details on the network stack improvements, start here:
http://www.sun.com/bigadmin/content/networkperf/
Prove it? No need - just ask them. If they say it's not theirs, take it. If they say it is, 'nuff said...
Once you've identified this person, pay him to do the work and explain it to you at the same time - that where the multiplier comes in to play.
I've done this type of work for friends/relatives in the past. Just remember that business is business.
It's mainly the honor system "enforced" by two things: 1) the more people that know about something the harder it is to keep it secret and 2) most people aren't willing to go to jail just to protect their company's shareholders.
What are you talking about? Sun has been 64bit for years...
Uh? Where the heck did you get that idea?
The CIO's jobs is provide technical leadership and direction to support the business processes, structure, and operation. To do this, they need to provide the "best cost" (notice I didn't say lowest - it's not always best) solutions to the business and justify them in profit/loss or risk/benefit. If part of the case involves changing a business process, then that should stand on the merits (yes, this means dollars) of the case.
Yes, but the keyword is "operational". Where the significant characteristics of two possible solutions are identical (e.g. functionality, maintainability, reliability, vendor viability, or whatever) then cost rules. If that's not the case, then the differences need to be weighted and/or costed. And yes, everything (and I mean everything) can be boiled down to dollars and is at successful companies on a regular basis.
That's their job. Companies exist to make money - end of story. Technology for technologies sake is foolish and wasteful unless you're in an R&D department.
That being said, all technology spends (e.g. upgrades, redesigns, rewrites, replacements, etc.) can and should be boiled down to dollars that either fall into a profit/loss or risk/benefit catagory (hopefully over 3-5 years). If a CIO isn't doing this (or having it done for them) they should be fired.
If you think more subtlety is needed, then I hope you're a low to mid level SA/DBA/Developer because you don't understand the "business" side of the company that employs you. I'm not trying to be rude, but that's the brutal reality of the business world. On a lighter side, there'a always academia... if you'd prefer politics to dollars.
I tried donating once about 2 years ago. Unfortunately (for Debian and the SPI), I raised a big stink about them not accepting Paypal, credit cards, or anything electronic. This wasn't received very well. I finally just sent them a check for $50 but it was never cashed. I don't know whether it was lost or if the treasurer just decided he didn't want my money.
Larry provided a free product to the Linux community for several years. We all benefited from it. He then decided to stop providing it when he felt it was being used in bad faith - his product, his choice.
Isn't choice what this is all about? Why is everyone whining about it?
True, but his employer (which also happens to employ Linus) did agree not to reverse engineer Bitkeeper.
Linus did say that. What part of "I will use the best tool for the job" was unclear? The best tool was proprietary with a very friendly non-commercial license. Go through the Kernel Cousins archives - on multiple occasions Linus said he would switch to an Open Source product as soon as one existed that met his needs.
All the people saying "I told you so" now are the same people that didn't bother to get off their high horses and pay attention to Linus' position. These are the people who ignored Linus' challenge to put up or shut up, i.e. quick whining and write an open source version control system that would meet his needs. An Open Source advocate that merely complained instead of writing code is a hypocrite in my book.
but for $100 you can rent a close facsimile for ~30 minutes...
I'd say you don't know enough about UNIX systems to deserve root access. What exactly do you think you need it for? The only thing you really need is the ability to start Apache on port 80. Everything else can be done w/out priviledged access if setup properly.
Two quick comments about RAID5. First, the posts dismissing it as an option due to performance concerns are silly since your requirements are unknown. Second, another poster already brought up the fact that a 3 disk RAID5 is a bit odd - adding little additional storage while introducing a write penalty. But hey, if it meets your requirements go for it.
The first time someone told you "everything is a file" when describing Unix it probably sounded goofy/confusing. But after you understand what that means the power and control it gives you is awesome. man pages are like that - take the time to understand the format and all the information you need is right there in front of you.
To learn how to search man pages, type "man more" if your pager is more or "man less" if your pager is less. And unlike Windows Help and OS X Help files you can use regular expressions. There's also no gui overhead - very nice when the equipment your working on is 800 miles away and only allowed to connect to the systems via SSH.
I guess if you had ever bothered to type "man man" I wouldn't be responding to your post...
If they know how to find information they can learn and solve problems without you.
Right now all Prod applications run in a shared server environment - so our Dev, QA, & ITE regions are shared too. For example, I'm in the middle of consolidating all our Weblogic development (4 groups / 30ish developers) onto a Sun E2900 (8CPUs / 16 cores) from an aging E6500 and an E450. This allows us to share not only the hardware resources but the software licensing as well. Of course, this is just for Dev - the other regions are scaled horizontally according to capacity and availability requirements with like applications being grouped together.
BTW, I'm not a developer. I work in A&E making sure the infrastructure meets business and technical requirements while driving down run-rate.
Anyone who has worked with budgets in large corporations can tell you Developer/Tester hours are generally the majority of the budget. Hardware is a drop in the bucket (and you can even capitalize it). On many projects I've worked on, Java has driven the people cost down resultig in a net savings even though we may have had to throw a crap load (official Business terminology) of CPU/memory at the application.