It would seem I need one myself... There must be some law (such as Godwin) which states that any post calling someone out for poor grammar, spelling or punctuation will have X chance of containing one as well.
Accidents on the bridges is a complete red herring anyway.
As an electric car, there is no such thing as "idling". The car is either moving or not.
The A/C, radio, etc. power draw is so much less than what is needed for propulsion, getting stuck on the bridge for an hour is not going to reduce your range by a significant amount.
But, that doesn't mean this car is for everyone. It doesn't have to be. If it doesn't fit your situation, don't buy it. That doesn't mean it might not work for someone else.
...weighs less than a Neal Stephenson novel and has a sharper, brighter image than that monster
Nobody has a sharper, brighter image than Neal Stephenson! This review is heresy! And calling him a monster, that's just going too far (even if you did slog through the Baroque Cycle).
Are you kidding? The Baroque Cycle was a rollicking good time. Anathem, on the other hand, could lead to some calling him cruel, though I agree monster is a bit much.
I'm curious which particular drives you've had trouble with? Because like some others here, I've had success doing this with recent vintage "high capacity" drives.
You do have to watch out for board revisions, etc. to make sure you're actually using an identical board, not just one that fits.
Not doubting you, I'm just curious for more specifics. I wouldn't discount this method out of hand, it may be just certain drives that have this problem.
If a company's security is that bad on the wired network, what makes you think they'll magically wise up and properly implement their wireless? I'm guessing "Linksys" and no encryption is just as likely there.
Sometimes you don't have a choice. Depends on the products you bought and when those vendors update their product and/or when you can afford to upgrade to the newer version. Money doesn't grow on trees, and you can't control other organizations schedules. I know of where I speak on this. Work in the health care industry some time.
Been there, done that. Hopefully won't have to again any time soon. Industries I prefer to avoid as an IT worker: Healthcare, Education, Government. Also, watch out for Law offices and Accounting firms. Strange politics at those places.
But, back on-topic: many industries have these broken (or at least fragile) apps, from 3rd party vendors or otherwise.
IT shops with apps like that should be managing patches for their users, whether with something like SUS or whatever manual process suits their environment. Allowing automatic updates is just asking for it.
there is no excuse for leaving production systems unpatched for four months.
We have a particular set of servers for an application, and the company that made the software in question (FujiFilm's Synapse PACS) does not want patches installed on those servers, or the workstations that run the client app until they confirm it doesn't conflict with their software. Thankfully, this particular patch was approved, but there are other MS patches that have not been approved in over a year (or there was when I last checked, anyway). Similarly, some other devices (like an Ultrasound machine made by Siemens) run software on top of a Windows OS, but the admins do not have administrator access to it, and installing updates could very well cause the device to stop working. It's not always quite as simple as you pretend it is.
Those systems you mention should in no case be connected to the Internet. To do so would be just asking for it.
I have to disagree strongly with you here. You have it exactly backwards.
Each example you give is dead wrong. One Linux kernel? Not so. One C compiler? Not even close. One bash shell? Nope, wrong again. Every one of those has more than one product line or version or competing product in wide usage, not to mention other complete alternatives, like using a BSD kernel in a Debian system.
The "whole concept of Open Source" most certainly does not revolve around universal adoption of one solution to the detriment of any other. That's one great distinguishing feature of the open source model - choice.
One could argue that computing and the Internet would not be as ubiquitous as they are today without having had a defacto standard. There is an even stronger argument at the cost savings to businesses and governments in not having to train and retrain new employees on how to use numerous computer systems.
Standards != Monoculture.
In fact a "defacto standard" is much less desirable than following well-documented, open standard protocols. The Internet was specifically designed to link disparate computer systems so that they could communicate properly.
Having things only work properly on one "defacto standard" system limits the growth and ubiquity of things like the modern internet.
And as far as "companies getting taken offline," there is no excuse for leaving production systems unpatched for four months. Microsoft could not make it easier to apply security updates unless they came onsite and installed them for you. That's not as much a convicted monopolist issue as it is shoddy, lazy network management.
Agreed. The problem at hand is not so much companies getting taken offline because of direct infection, it is massive hordes of zombie PC's from home users to organizations too small to have dedicated IT staff. And that is something attributable to the crappiness of the system promulgated by the convicted monopolist.
Most hot-swap drive caddies these days are just rails that you screw onto the sides of the drive. The drive connectors plug directly into the backplane.
Yes and no. I'm not familiar with every line of SOx, but I'll bet you five bucks it is actually those in "senior management" who are legally responsible for protecting those records, not the sysadmin.
It is your responsibility to follow procedure, and that should include password escrow of some sort, ultimate responsibility for which falls to "senior management".
If they abuse it and destroy those systems, that is exactly what the penalties in the legislation are for. Not "throw the sysadmin in jail because he obeyed his boss".
Any CCNA or CCIE worth his salt could have reset those passwords, given physical access to the hardware. If they hired the most expensive consultants they could find, that's their lookout. $5000 could conceivably cover it.
If I hire Norm Abrams for my home improvement project, I know he'll do an excellent job. But I'd better be willing to pay him for it.
FYI, CCP is not an American company. They're Icelandic.
Not that their economy (or anyone's) is in particularly good shape either, but just correcting your mistake that this has anything to do with nationality.
Indeed. I have had Netware servers with 4 years uptime at branch offices. Right now I have one that's been up over 2 years.
You'd regret it if you tried that with Windows.
I wouldn't be surprised if quite a few did get it. Even younger music lovers might, that song has enjoyed somewhat of a revival the last few years. And well it should.
Indeed. If their bill is within an order of magnitude of that, they certainly won't notice the few cents a day a car takes to charge up. Heck, that's probably the cheapest employee benefit they could offer, for the goodwill it would produce.
And how many people buy a new car in any given year, really? Even when these do come to dealer showrooms instead of being DIY projects, it's not like you'll instantly have 50 of them in the company parking lot.
See all those light poles in the parking lot? I bet those run on electricity, unless your company uses gaslights or perhaps tar-soaked burning rags? See that beakout box at the bottom of the pole?
So how, exactly, do you propose the maintainers be alerted to security risking bugs (so that they can fix them) without disclosing the bugs to the selfsame maintainers?
The government keeps getting more and more paranoid.. and less and less relevant.. until they're sitting in their reinforced compound polygraphing their employees weekly and timing the average time it takes to page-down and read the latest memo on TPS reports.
Read it too fast and you're in trouble because you couldn't have adequately digested its fascinating implications. Read it too slowly and you're not being productive enough, slacker!
Um.. Do you have any idea what most government employees make? When I was looking for a job a few years back, it was about half or less what I make in a regular private-sector company, and for jobs that required more work. I literally could not afford to take one of those jobs.
Slashdot Mirror
*ahem*
It would seem I need one myself... There must be some law (such as Godwin) which states that any post calling someone out for poor grammar, spelling or punctuation will have X chance of containing one as well.
Containing one what, exactly?
Accidents on the bridges is a complete red herring anyway.
As an electric car, there is no such thing as "idling". The car is either moving or not.
The A/C, radio, etc. power draw is so much less than what is needed for propulsion, getting stuck on the bridge for an hour is not going to reduce your range by a significant amount.
But, that doesn't mean this car is for everyone. It doesn't have to be. If it doesn't fit your situation, don't buy it. That doesn't mean it might not work for someone else.
It is still an interesting idea. A purpose built trailer with a 12 KW engine + fuel tank => unlimited travel.
Err, A purpose built trailer with a 12 KW engine + fuel tank = a Car.
...weighs less than a Neal Stephenson novel and has a sharper, brighter image than that monster
Nobody has a sharper, brighter image than Neal Stephenson! This review is heresy! And calling him a monster, that's just going too far (even if you did slog through the Baroque Cycle).
Are you kidding? The Baroque Cycle was a rollicking good time. Anathem, on the other hand, could lead to some calling him cruel, though I agree monster is a bit much.
I'm curious which particular drives you've had trouble with? Because like some others here, I've had success doing this with recent vintage "high capacity" drives.
You do have to watch out for board revisions, etc. to make sure you're actually using an identical board, not just one that fits.
Not doubting you, I'm just curious for more specifics. I wouldn't discount this method out of hand, it may be just certain drives that have this problem.
If a company's security is that bad on the wired network, what makes you think they'll magically wise up and properly implement their wireless? I'm guessing "Linksys" and no encryption is just as likely there.
Sometimes you don't have a choice. Depends on the products you bought and when those vendors update their product and/or when you can afford to upgrade to the newer version. Money doesn't grow on trees, and you can't control other organizations schedules. I know of where I speak on this. Work in the health care industry some time.
Been there, done that. Hopefully won't have to again any time soon. Industries I prefer to avoid as an IT worker: Healthcare, Education, Government. Also, watch out for Law offices and Accounting firms. Strange politics at those places.
But, back on-topic: many industries have these broken (or at least fragile) apps, from 3rd party vendors or otherwise.
IT shops with apps like that should be managing patches for their users, whether with something like SUS or whatever manual process suits their environment. Allowing automatic updates is just asking for it.
Why do you think these planes cost so much then? All that fake engineering is expensive.
You put a bunch of graphics artists on a terminal server and see how it goes.
You'd have the same problem with RDP to a desktop machine. Heck, that is basically what TS is anyway.
This has nothing to do with where they store their files or after-hours access from home. The topic here is powering down PC's after hours.
there is no excuse for leaving production systems unpatched for four months.
We have a particular set of servers for an application, and the company that made the software in question (FujiFilm's Synapse PACS) does not want patches installed on those servers, or the workstations that run the client app until they confirm it doesn't conflict with their software. Thankfully, this particular patch was approved, but there are other MS patches that have not been approved in over a year (or there was when I last checked, anyway). Similarly, some other devices (like an Ultrasound machine made by Siemens) run software on top of a Windows OS, but the admins do not have administrator access to it, and installing updates could very well cause the device to stop working. It's not always quite as simple as you pretend it is.
Those systems you mention should in no case be connected to the Internet. To do so would be just asking for it.
I have to disagree strongly with you here. You have it exactly backwards.
Each example you give is dead wrong. One Linux kernel? Not so. One C compiler? Not even close. One bash shell? Nope, wrong again. Every one of those has more than one product line or version or competing product in wide usage, not to mention other complete alternatives, like using a BSD kernel in a Debian system.
The "whole concept of Open Source" most certainly does not revolve around universal adoption of one solution to the detriment of any other. That's one great distinguishing feature of the open source model - choice.
One could argue that computing and the Internet would not be as ubiquitous as they are today without having had a defacto standard. There is an even stronger argument at the cost savings to businesses and governments in not having to train and retrain new employees on how to use numerous computer systems.
Standards != Monoculture.
In fact a "defacto standard" is much less desirable than following well-documented, open standard protocols. The Internet was specifically designed to link disparate computer systems so that they could communicate properly.
Having things only work properly on one "defacto standard" system limits the growth and ubiquity of things like the modern internet.
And as far as "companies getting taken offline," there is no excuse for leaving production systems unpatched for four months. Microsoft could not make it easier to apply security updates unless they came onsite and installed them for you. That's not as much a convicted monopolist issue as it is shoddy, lazy network management.
Agreed. The problem at hand is not so much companies getting taken offline because of direct infection, it is massive hordes of zombie PC's from home users to organizations too small to have dedicated IT staff. And that is something attributable to the crappiness of the system promulgated by the convicted monopolist.
Most hot-swap drive caddies these days are just rails that you screw onto the sides of the drive. The drive connectors plug directly into the backplane.
Yes and no. I'm not familiar with every line of SOx, but I'll bet you five bucks it is actually those in "senior management" who are legally responsible for protecting those records, not the sysadmin.
It is your responsibility to follow procedure, and that should include password escrow of some sort, ultimate responsibility for which falls to "senior management".
If they abuse it and destroy those systems, that is exactly what the penalties in the legislation are for. Not "throw the sysadmin in jail because he obeyed his boss".
Any CCNA or CCIE worth his salt could have reset those passwords, given physical access to the hardware. If they hired the most expensive consultants they could find, that's their lookout. $5000 could conceivably cover it. If I hire Norm Abrams for my home improvement project, I know he'll do an excellent job. But I'd better be willing to pay him for it.
FYI, CCP is not an American company. They're Icelandic. Not that their economy (or anyone's) is in particularly good shape either, but just correcting your mistake that this has anything to do with nationality.
The previous comment was funny. This one is the troll, you stupid fucks.
Err, no, that's a flame. A Troll is when you try to get people to reply to your post as if it were serious and...
Damn it!
Indeed. I have had Netware servers with 4 years uptime at branch offices. Right now I have one that's been up over 2 years. You'd regret it if you tried that with Windows.
I wouldn't be surprised if quite a few did get it. Even younger music lovers might, that song has enjoyed somewhat of a revival the last few years. And well it should.
It's a cold and it's a broken Hallelujah...
Indeed. If their bill is within an order of magnitude of that, they certainly won't notice the few cents a day a car takes to charge up. Heck, that's probably the cheapest employee benefit they could offer, for the goodwill it would produce.
And how many people buy a new car in any given year, really? Even when these do come to dealer showrooms instead of being DIY projects, it's not like you'll instantly have 50 of them in the company parking lot.
See all those light poles in the parking lot? I bet those run on electricity, unless your company uses gaslights or perhaps tar-soaked burning rags? See that beakout box at the bottom of the pole?
No, you've just watched "It's a Wonderful Life" one too many times..
Nice try, though.
So how, exactly, do you propose the maintainers be alerted to security risking bugs (so that they can fix them) without disclosing the bugs to the selfsame maintainers?
Wow. I think you just blew my mind.
The government keeps getting more and more paranoid.. and less and less relevant.. until they're sitting in their reinforced compound polygraphing their employees weekly and timing the average time it takes to page-down and read the latest memo on TPS reports.
Read it too fast and you're in trouble because you couldn't have adequately digested its fascinating implications. Read it too slowly and you're not being productive enough, slacker!
Um.. Do you have any idea what most government employees make? When I was looking for a job a few years back, it was about half or less what I make in a regular private-sector company, and for jobs that required more work. I literally could not afford to take one of those jobs.