What is "right"? Expending a few thousand per closet on well-equipped wiring points, in dormitory space where living space is cramped and valuable, or lowering the load on the switches so that they run reliably enough for casual use and using the same money, if it was ever available, to actually wire the rest of the dorm rooms? Or spending the money on pizza and beer to supply a few geeks to actually work out what the real issues are and fix those?
Spending money on "server-grade hardware" is not an automatic solution to a problem that has not been actually identified.
What you've actually described is security through obscurity.. Being proprietary does not keep it unpublished. The "proprietary technology" source code and utilities have been repeatedly stolen, published, and republished among the cracker crowd, and the tools they write get released and circulated among the script kiddie crowd eventually. And Cisco has repeatedly engaged in really unfortunate security standards for decades, with a lack of reporting of the incidents for both non-disclosure reeasons, and an unwillingness by corporatations to admit such cracking has occurred.
Moreover, Cisco update procedures and user interfaces and backup procedures are so painful that implementing an upgrade or patch is very risky indeed, and is often left idle long after the cracks are widely published. The result is that the firewall and routers which companies rely on to remain secure with their absolutely pitiful internal security is often easily pierced by anyone remotely competent.
More seriously, IOS is a high-performance but extremely poor interface toolkit on top of a lot of proprietary hardware. It doesn't matter much which kernel runs on it, unless they've been tuned out of all recognizability to deal with the high load, low latency issues of routing. And the kernels are pretty near the limits of their ability to tune performance to the hardware: the next level up is the compiler, and the next level up is the actual interface. And the extreaordinarily poor behavior of the user interface simply swamps kernel optimization for most 3rd party work.
That's a good interpretation, and a valid one, but not *quite* what I meant. Gangmembers sometimes have jobs. Those jobs may be in corporate buildings, even if the job is only minimum wage slinging burgers while they're on probation: that's one of many excuses for wanting unfettered and unmonitored access to the telephone switching system at every level.
The second part is quite right: any excuse for invading civil liberties is enough for someone, like the NSA or CIA or FBI or the DEA or any of a variety of federal offices (and state and local offices!) who've demonstrated their corrupt willingness to violate civil rights, local wiretapping laws, and common sense to gather whatever they consider important. Watergate was merely a prize example of this history of abuse. The McCarthy era hunt for Communists, previous hunts for Nazi sympathizers, Civil War era hunts for pro and anti slave trade activists, the Martin Luther King files at the FBI, the political investigations against protesters of major airport expansion projects cloaked as "anti-terror" operations, and other incidents throughout history demonstrate such abuses. Every government big enough and long-lasting enough has had such abuses.
Before you mock those who question the "war on drugs", be sure that this "war" is actually helping overall. Between ths silly criminalization of pot, and the active campaign of drug dealers facing court in ratting out anyone who looks like they might be sale-able, innocent or not, the war itself has a lot of innocent casualties. When my friend a few years back, despite being in California, couldn't get pot to help their AIDS suffering, or my friend in chemotherapy couldn't get pot to help their appetite, I was in touch with their families while they suffered and died.
You don't have to support terrorism, or meth use, to think that the "war" approaches used against them simply aggravate the problems, waste billions in needed reouseces, and kill innocents.
Having violated/. policies and actually Read The Fine Article, it was a good analysis. I wish more people would write their bug reports this well, and explain how they're going to address the problem.
I also wonder if they wouldn't benefit from a nice virtual environment system to do QA testing of new releases with? Capturing the full graphical behavior of an OS is difficult in virtual systems, due to the overhead of the virtualization itself, but it might be a lot cheaper than keeping a dozen different hardware configurations around.
And the fix wouldn't be understood or tested by the consumer, and thus extremely difficult to verify that it doesn't cause other bone-dead changes.
This is why I publish code to my clients, with documentation of what the change does, unlike many vendors and developers. (Like, oh, I dunno: Microsoft? Nvidia with its Linux binary blobs? The old Sun Linux binaries?)
I believe you: I suspect it's due to the decreasing costs of junk fax sent over Internet portals, coupled with people not bothering to prosecute. But I remember when it got *REALLY* bad, and was eating reams of paper and printing supplies if you were a small business.
Does it constitute even 1% of your legitimate faxes?
You tell which one is missing by listing the number and check-out of the one that hasn't been returned. That seems a very, very basic operation for such a system.
Sometimes you have to scan things during surgery, especially for keyhole surgery, to make sure where the instrument is relative to the target. I wouldn't expect an MRI to be so necessary during surgery, but I believe I've heard of a case of yanking someone from surgery straight to the MRI to see exactly where the stroke or blood clot had happened during surgery and follow it up with treatment ASAP.
Note that I'm not a radiologist, just an interested technical person who's worked with such people's IT needs in passing.
Disconnecting hard drives is a big problem for external devices. So is power saving, and laptop use especially. I'll bet that Seagate will sell a "Mac-compatible" version fairly soon that voids this problem, and it'll be compatible with Linux.
But this is an amazingly foolish mistake on Seagate's part.
And all of them will shun the product for having *anything* to do with the name of a Peachtree product. I've had to clean up the mess left by that pile of debris several times, and will start to twitch spasmodically at the mere sound of the word Peach-ack-pbth-seizure-starting....
Give the ISP's legal leverage to act against them, and make the ISP's responsible for botnets so they have a reason to do so. This will cause some ISP's to limit free access to port 25 on home networks: we can get over that.
A lot of them also got lied to. Their dealers misled them on what they could hope to afford or what the resale value of their houses might be, or what the costs of maintaining a house are. Losing a job, a medical emergency, or a new child can destroy a family's ability to afford an excess mortgage, in ways the mortgage can and scummy mortgage agents do deliberately obscure.
There's been a lot of fraud exposed on the news about this lately. It's a nasty business, much like selling used cars.
Well, yes, but it has to be a good mix. We saw bad mixes for years with junk mail (which remains awful) and junk fax (which finally got stomped in the US by the junk fax law).
The junk fax law could be extended to cover spam: some US congressmen have tried, repeatedly, to do so, but been blocked by lobbyists like the Direct Marketing Association (which has both legitimate and spammer on-line members who fear such legislation). And the junk fax law has stood up well to challenges on free speech issues. But it would require throwing out that awful excuse to spam called the CAN-SPAM Act.
Someone who's actually used it! Cool! I hope you don't a few questions?
Don't the sponges biodegrade inside the body? Do they need to encapusalete?
Do you have any issues with the RFID tags being ruined by X-ray equipment? Or being ruined by MRI's done on patients who had to be pulled straight from surgery to the MRI chamber for whatever reason?
The idea is to reduce the manpower needed to track the sponges. In a messy abdominal surgery, or open heart, you'll go through dozens. Being able to say "it's spong 12345, that was from the pack we opened last" is amazingly helpful to finding the missing sponge, and it's a lot less labor intensive than counting and double checking when the double counting is liable to introduce its own miscounts either way.
Because it doesn't "cost nothing". Surgical staff, and the time in the OR, is hideously expensive. Double-checking and hunting for lost sponges when you've gotten a wadded up sticky, clotted mass from swishing out someone's lacerated colon is difficult and nasty and chews through expensive time. Holding up the theater because some new, rattled surgical intern or nurse in training lost track of sponges is worse.
3 minutes per hour spent counting is a serious cost.
There are problems. RFID is expensive per tag, and typically has a range of feet, where a tag still inside the patient may be detected by a scanner within the same surgical arena. No one has time to walk the new or removed sponges across the room, they go in a medical waste bin right there.
And I don't want the job of designing an RFID scanner nor RFID tags that will operate safely and reliably in a room of delicate radiological instrument, such as the X-ray and CT devices used to monitor interesting events during surgery.
I sat in and watched a relative getting open heart surgery. It's messy, it's nasty, and it goes on for hours. And other surgical staff may be asked to help: a nurse with small hands may be asked to hold something in place in a delicate bit of work, because her fingers may fit better.
Good surgery is not a one-man operation, it's a team. And teams can lose track of small objects.
Slashdot Mirror
What is "right"? Expending a few thousand per closet on well-equipped wiring points, in dormitory space where living space is cramped and valuable, or lowering the load on the switches so that they run reliably enough for casual use and using the same money, if it was ever available, to actually wire the rest of the dorm rooms? Or spending the money on pizza and beer to supply a few geeks to actually work out what the real issues are and fix those?
Spending money on "server-grade hardware" is not an automatic solution to a problem that has not been actually identified.
What you've actually described is security through obscurity.. Being proprietary does not keep it unpublished. The "proprietary technology" source code and utilities have been repeatedly stolen, published, and republished among the cracker crowd, and the tools they write get released and circulated among the script kiddie crowd eventually. And Cisco has repeatedly engaged in really unfortunate security standards for decades, with a lack of reporting of the incidents for both non-disclosure reeasons, and an unwillingness by corporatations to admit such cracking has occurred.
Moreover, Cisco update procedures and user interfaces and backup procedures are so painful that implementing an upgrade or patch is very risky indeed, and is often left idle long after the cracks are widely published. The result is that the firewall and routers which companies rely on to remain secure with their absolutely pitiful internal security is often easily pierced by anyone remotely competent.
He'd benefit more from blocking Bittorrent, I hate to admit.
That's not an OS issue. It's a command interface issue. Much of it is built into bash.
The user interface people writing IOS need to read Eric Raymond's document on user interface, at http://www.catb.org/~esr/writings/cups-horror.html. It applies to closed source interfaces as well.
More seriously, IOS is a high-performance but extremely poor interface toolkit on top of a lot of proprietary hardware. It doesn't matter much which kernel runs on it, unless they've been tuned out of all recognizability to deal with the high load, low latency issues of routing. And the kernels are pretty near the limits of their ability to tune performance to the hardware: the next level up is the compiler, and the next level up is the actual interface. And the extreaordinarily poor behavior of the user interface simply swamps kernel optimization for most 3rd party work.
That's a good interpretation, and a valid one, but not *quite* what I meant. Gangmembers sometimes have jobs. Those jobs may be in corporate buildings, even if the job is only minimum wage slinging burgers while they're on probation: that's one of many excuses for wanting unfettered and unmonitored access to the telephone switching system at every level.
The second part is quite right: any excuse for invading civil liberties is enough for someone, like the NSA or CIA or FBI or the DEA or any of a variety of federal offices (and state and local offices!) who've demonstrated their corrupt willingness to violate civil rights, local wiretapping laws, and common sense to gather whatever they consider important. Watergate was merely a prize example of this history of abuse. The McCarthy era hunt for Communists, previous hunts for Nazi sympathizers, Civil War era hunts for pro and anti slave trade activists, the Martin Luther King files at the FBI, the political investigations against protesters of major airport expansion projects cloaked as "anti-terror" operations, and other incidents throughout history demonstrate such abuses. Every government big enough and long-lasting enough has had such abuses.
Before you mock those who question the "war on drugs", be sure that this "war" is actually helping overall. Between ths silly criminalization of pot, and the active campaign of drug dealers facing court in ratting out anyone who looks like they might be sale-able, innocent or not, the war itself has a lot of innocent casualties. When my friend a few years back, despite being in California, couldn't get pot to help their AIDS suffering, or my friend in chemotherapy couldn't get pot to help their appetite, I was in touch with their families while they suffered and died.
You don't have to support terrorism, or meth use, to think that the "war" approaches used against them simply aggravate the problems, waste billions in needed reouseces, and kill innocents.
Gang members, and political opponents, work in offices with PBX's.
Hey, I'm a /. reader, too. It's not hard to get dumped by someone you never actually went out with, believe me!
Having violated /. policies and actually Read The Fine Article, it was a good analysis. I wish more people would write their bug reports this well, and explain how they're going to address the problem.
I also wonder if they wouldn't benefit from a nice virtual environment system to do QA testing of new releases with? Capturing the full graphical behavior of an OS is difficult in virtual systems, due to the overhead of the virtualization itself, but it might be a lot cheaper than keeping a dozen different hardware configurations around.
And the fix wouldn't be understood or tested by the consumer, and thus extremely difficult to verify that it doesn't cause other bone-dead changes.
This is why I publish code to my clients, with documentation of what the change does, unlike many vendors and developers. (Like, oh, I dunno: Microsoft? Nvidia with its Linux binary blobs? The old Sun Linux binaries?)
I believe you: I suspect it's due to the decreasing costs of junk fax sent over Internet portals, coupled with people not bothering to prosecute. But I remember when it got *REALLY* bad, and was eating reams of paper and printing supplies if you were a small business.
Does it constitute even 1% of your legitimate faxes?
You tell which one is missing by listing the number and check-out of the one that hasn't been returned. That seems a very, very basic operation for such a system.
Sometimes you have to scan things during surgery, especially for keyhole surgery, to make sure where the instrument is relative to the target. I wouldn't expect an MRI to be so necessary during surgery, but I believe I've heard of a case of yanking someone from surgery straight to the MRI to see exactly where the stroke or blood clot had happened during surgery and follow it up with treatment ASAP.
Note that I'm not a radiologist, just an interested technical person who's worked with such people's IT needs in passing.
Disconnecting hard drives is a big problem for external devices. So is power saving, and laptop use especially. I'll bet that Seagate will sell a "Mac-compatible" version fairly soon that voids this problem, and it'll be compatible with Linux.
But this is an amazingly foolish mistake on Seagate's part.
And all of them will shun the product for having *anything* to do with the name of a Peachtree product. I've had to clean up the mess left by that pile of debris several times, and will start to twitch spasmodically at the mere sound of the word Peach-ack-pbth-seizure-starting....
[Connection lost]
Give the ISP's legal leverage to act against them, and make the ISP's responsible for botnets so they have a reason to do so. This will cause some ISP's to limit free access to port 25 on home networks: we can get over that.
A lot of them also got lied to. Their dealers misled them on what they could hope to afford or what the resale value of their houses might be, or what the costs of maintaining a house are. Losing a job, a medical emergency, or a new child can destroy a family's ability to afford an excess mortgage, in ways the mortgage can and scummy mortgage agents do deliberately obscure.
There's been a lot of fraud exposed on the news about this lately. It's a nasty business, much like selling used cars.
Well, yes, but it has to be a good mix. We saw bad mixes for years with junk mail (which remains awful) and junk fax (which finally got stomped in the US by the junk fax law).
The junk fax law could be extended to cover spam: some US congressmen have tried, repeatedly, to do so, but been blocked by lobbyists like the Direct Marketing Association (which has both legitimate and spammer on-line members who fear such legislation). And the junk fax law has stood up well to challenges on free speech issues. But it would require throwing out that awful excuse to spam called the CAN-SPAM Act.
And ICANN is very carefully designed not to have cojones, and the fraudsters know it.
Someone who's actually used it! Cool! I hope you don't a few questions?
Don't the sponges biodegrade inside the body? Do they need to encapusalete?
Do you have any issues with the RFID tags being ruined by X-ray equipment? Or being ruined by MRI's done on patients who had to be pulled straight from surgery to the MRI chamber for whatever reason?
The idea is to reduce the manpower needed to track the sponges. In a messy abdominal surgery, or open heart, you'll go through dozens. Being able to say "it's spong 12345, that was from the pack we opened last" is amazingly helpful to finding the missing sponge, and it's a lot less labor intensive than counting and double checking when the double counting is liable to introduce its own miscounts either way.
Because it doesn't "cost nothing". Surgical staff, and the time in the OR, is hideously expensive. Double-checking and hunting for lost sponges when you've gotten a wadded up sticky, clotted mass from swishing out someone's lacerated colon is difficult and nasty and chews through expensive time. Holding up the theater because some new, rattled surgical intern or nurse in training lost track of sponges is worse.
3 minutes per hour spent counting is a serious cost.
There are problems. RFID is expensive per tag, and typically has a range of feet, where a tag still inside the patient may be detected by a scanner within the same surgical arena. No one has time to walk the new or removed sponges across the room, they go in a medical waste bin right there.
And I don't want the job of designing an RFID scanner nor RFID tags that will operate safely and reliably in a room of delicate radiological instrument, such as the X-ray and CT devices used to monitor interesting events during surgery.
I sat in and watched a relative getting open heart surgery. It's messy, it's nasty, and it goes on for hours. And other surgical staff may be asked to help: a nurse with small hands may be asked to hold something in place in a delicate bit of work, because her fingers may fit better.
Good surgery is not a one-man operation, it's a team. And teams can lose track of small objects.