Consider yourself lucky. I've had to deal with cops that committed perjury on the witness stand, threaten, fail to follow up on the with the most basic of calls (In one instance I had the information needed to detain a 'hacker' here in my own state, and the police refused to follow up); officers that won't take fundamental action....
I've had to deal with Judges that don't follow the law, and DA's that falsify information. (I've set a president in the state where a DA can present false information, which is objected to, and the defense is not permitted to rebut it)
Reading a lot of comments about him being a nut job. My question is - what if he isn't? Is it possible that as a administrator of a SAN/Network, he saw some significant security issues, and when he presented them to his supervisors was slammed for reporting the problem -- including being fired? I know from experience the feeling: Management does not like to know that they've screwed up, and will fight kicking and screaming rather that admit that they've done something wrong. For me -- most recently this includes bogus Business Requirements, and critical Business Requirements that are not being met. I've found significant security holes in the where I currently work. Presented the problems to management. The response - don't call use, we'll call you.
For me, hard drives are a comity. I need 750GB / month to handle the recording that I do. This number went up 'recently' when I started recording in HDef. With this drive offering, I can reduce my hard drive need to once every other month -- until all broadcasts are in HDef.
I've still not sure what I'm going to do with 20 copies of "Enterprise" that I've been recording on the SciFi channel though.
Or he could... ... Start making a stink about that fact that these companies violated the law, violated our rights, and now after the fact are looking to get a deal for it.
This morning I heard on the news that one senator (sorry didn't get his name) was holding up that the companies did the "Patriotic" thing by doing what bush had asked for. My response to this: If they were to do the patriotic thing, they would have gone public with the illegal request in the first place.
Perhpas a bunch of them should watch A Few Good Men, "Dawson: We were supposed to fight for the people who couldn't fight for themselves."
One contract that I was at had an incompetent DBA. (The first time I began to question her abilities was when she asked if changing the desktop bitmap would impact system performance). When I found out she was terminated (about 15 minutes before a meeting I was going to host) I found a.mid file with this on it. Only my manager knew the real reason for the song playing in the background...
My grandmother decided to leave AOL. AOL however, would not leave her. She kept getting billed, and could not disconnect for MONTHS after the fact. I never did find out what the end result was, but (in the past) it was normal for AOL to 'not' disconnect your service when you asked them to...
Re:RAID5 is stupid, RAID 10 or no RAID
on
What NAS To Buy?
·
· Score: 1
Interesting: My original post is labeled as "Flamebait"; when info on a real HW problem is made available. Here is some follow up to the email; the problem never was 'fixed', only patched as noted below. Several subsequent emails long after this resulted in no discernable action on the part of DELL to correct the problem.
I don't extrapolate anything: I offer advise based on years of hands on experience, and others have chosen to extrapolate that DELL equipment sucks.
From: Paul Tilley (Dell Computers)
Sent: Monday, October 18, 2004 4:00 PM
To: Removed
Subject: Dell SCSI RAID Reminder
All,
The document linked below describes some possible scenarios with SCSI RAID solutions, and how to address them. Many of you have Dell servers with RAID controllers in them, and some of these systems I'm sure are several years old. As a SCSI RAID system ages, the risks of double-fault scenarios (as described in the document) become more likely. So I feel it is important to make you aware of these recommendations.
There is also a procedure in the document for automating this process. BTW, Dell is currently working on a RAID firmware-based background consistency-check, and I will let you know here as soon as it is available.
Please let me know if you have any questions. I do not want to alarm anyone - the odds of a double-fault occurring are minimal. But applying preventative maintenance will lower the odds even more.
Thanks!
Paul Tilley
DELL
Systems Consultant
xxx-xxx-xxx
From: IPAK (OTG Service Pack) Team (Internal)
Sent: Friday, January 16, 2004 5:19 PM
To: IPAK (OTG Service Pack) Notification
Subject: DATA LOSS ISSUE NOTIFICATION: Dell Servers with PERC 2 or 3Di (Adaptec) Controllers
Importance: High
DATA LOSS ISSUE NOTIFICATION: Dell Servers with PERC 2 or 3Di (Adaptec) Controllers
Issue: Datacenter Platform Standards Hardware Engineering team is providing notification of a potential data loss risk on Dell Platforms that contain PERC 2 or 3Di (Adaptec) Array Controllers. Over the past two months we have had an unacceptable number of escalations reporting this issue. We have escalated this issue to Dell and they have been able to reproduce the problem and are in the process of developing a fix/solution. In the interest of avoiding further data loss, we are requesting a hold on all Dell servers with a PERC 2 or PERC 3Di until further notice.
This issue is not related to IPAK installs or the OS. The catalyst for this event may be as simple as a warm or cold boot of an affected Dell server.
Affected Servers: Attached is a list of OTG datacenter servers (source ITCONFIG 1/16) that may have a PERC 2 or PERC 3Di controller installed:
Dell Perc2-3Di install list.xls
Keep in mind that this list contains all of the servers that may have a PERC 2 or PERC 3Di controller installed and that some of the servers on the list may not contain the affected controllers. Systems that contain only PERC 3DC controllers are not affected by this issue.
Models that may have a PERC 2:
PE6400
PE6450
Recommended Action: DO NOT reboot these servers unless there is no other option. DO NOT upgrade, IPAK, change configurations, or move the server. This hold will last until a solution has been provided by Dell. We should receive a detailed explanation from Dell early next week with an ETA to a fix or solution. We will provide daily status to IPAKINFO starting Monday.
Re:RAID5 is stupid, RAID 10 or no RAID
on
What NAS To Buy?
·
· Score: 1
Actually I'm talking about business model of hiding a known problem in the hope that the problem will not be found. The ironic thing is that I will usually recommend that for home and non-enterprise systems -- I'll always recommend DELL first.
Re:RAID5 is stupid, RAID 10 or no RAID
on
What NAS To Buy?
·
· Score: 1
Context of article: 'my private backup' (I presume this to mean "at home"); as was my instance. Hiring someone to monitor systems at home is a little silly.
I know DELL has a strong militant following, and has a strong bias in favor of DELL; however when I was working at MS, I followed up with the issue I was having with my DELL equipment. The email response that I received addressing the problem was sent from the rep for DELL; it was sent locked down so I couldn't even get a screen shot of it, admitting to the problem and the extent of it, and that "Dell was working on it". Years later, DELL had not fixed the problem. The problem relates to the PERC 2/3, and that it does not properly report a failed drive. What is worse in my opinion is that DELL had withheld this information. The problem was reported as multiple drives in an array would fail, and the system would be re-booted: the failed drives would 'kill' the RAID-5 array. (The system would not 'flag' the drives as failed until the next system reboot)
Re:RAID5 is stupid, RAID 10 or no RAID
on
What NAS To Buy?
·
· Score: 0, Flamebait
.... and the only problem with that is with DELL, there is no warning when the drives fail. I made the mistake of using a DELL enterprise solution: DELL servers only check for drive failure on boot up. I currently have a dead enterprise server with two failed drives. (Compaq would at least check the drives, and if one failed while 'running' you would know about it. I can't comment on HP, I can only hope (and presume) that they adopted the Compaq method of detecting a drive failure.
Whew, I'm glad to know that our business partners are secure. Our business just decided to use "Citi", and they have assured us that they are secure. Oh - wait, isn't Citi the same as "CitiBank"?
On the more serious side: They insist on using REAL customer data for testing, their test systems are not in sync with production, their test practices are VERY bad....
It comes as no surprise that they've had a break-in.
First the obvious: Have a white list tied with caller ID.
Next: Be able to exclude out of "area" calls (I get to define what the "area" is)
Next: For non-white listed numbers, have the disconnect signal sent (The there tone noise followed by "The number you have reached..."), followed by a question that requires a human to answer in a timely mannor:
Examples: ...Enter 1234 backwards ...Enter the sum of 1000 plus 1 ...Enter the number one thousand followed by the number you dialed ...Enter the area code for the number you just dialed ...Enter the year as for digits ...Enter the age of the person you called ...Enter the number of pets owned by the person you called ...Enter the number of presidents running for office ...Enter the number of presidents in office.
By having a few questions - asked at random, that are always changing, the cat and mouse game can go on for years. And, adding some random 'noise' between the words (both low and high frequency, our side of normal human hearing) one could 'trick' the computers performing the dialing in to 'false' answers to the questions.
This has nothing to do w/ storing 1's and 0's. It has everything to do with your credit score. If they don't have the information, you can't fight it. If they have any information it must be secured, so why are they bitching and wining about the amount of data? Look behind the question to see the real answer.
With Google's new "change the route" - it's cool. Yahoo's maps (old) is better, the new one has issues with moving the maps around (It frequently wants to go back!).... Mapquest sucks (Honest Question: why does anyone use it? - have you seen any of the other map tools?) Yahoo maps also lets me type in notes when I print out the map to actually _drive_ somewhere.
Some history of MS DOS....
Wish I had time for the long version but.... DOS 3.1 - 3.3 was stable, IBM released PC DOS 4.0, buggy as hell. MS said "what???" - and fixed some of the bugs for MS DOS 4.01. MS DOS 5.0 was rock stable; many of the so called 'bugs' were in fact bugs in the applications that were now showing up. V5 was fairly short lived (although it was popular) as MS released MS-DOS 6.0, which introduced MANY new bugs, thanks to a *VERY* bad and annoying PM. But it sold; and MS was sued by Stacker for the compression technology, and lost. (Yet another interesting story, Wikipedia only glosses over it. Oh, to have the text from that phone call again!). This begot MS DOS 6.21, and MS DOS 6.22. Also Winkipedia history is wrong: There never was a "MS-DOS 4.0 - June 1988 - derived from IBM's codebase rather than Microsoft's".
Re:News?.... Minor correction
on
DOS 5 Upgrade Video
·
· Score: 2, Informative
Follow up points --
As this would be an electrical car, there won't be 180F under the hood (Unless there is a REAL problem with global warming)
And when we go to the 'energy station' of the future: Why won't have a sugar & enzymes that we can drop in and replace? ..... and, if this will only work in CA, that would reduce the green house gasses by 50%;-) but on a serious note - if it would work for 40% of the cars on the road now, that would put a serious dent w/ problems and petroleum based energy.
Slashdot Mirror
Consider yourself lucky. I've had to deal with cops that committed perjury on the witness stand, threaten, fail to follow up on the with the most basic of calls (In one instance I had the information needed to detain a 'hacker' here in my own state, and the police refused to follow up); officers that won't take fundamental action....
I've had to deal with Judges that don't follow the law, and DA's that falsify information. (I've set a president in the state where a DA can present false information, which is objected to, and the defense is not permitted to rebut it)
You can have ours....
The first is 58 years old, weighs about 245lb, 5' 3"....
The second one has short grey curly hair, weights about 195 lb, 5' 7"
Reading a lot of comments about him being a nut job. My question is - what if he isn't? Is it possible that as a administrator of a SAN/Network, he saw some significant security issues, and when he presented them to his supervisors was slammed for reporting the problem -- including being fired? I know from experience the feeling: Management does not like to know that they've screwed up, and will fight kicking and screaming rather that admit that they've done something wrong. For me -- most recently this includes bogus Business Requirements, and critical Business Requirements that are not being met. I've found significant security holes in the where I currently work. Presented the problems to management. The response - don't call use, we'll call you.
commodity; nothign lik benig dislex er, dislex well - havenig a hard time spellin'
For me, hard drives are a comity. I need 750GB / month to handle the recording that I do. This number went up 'recently' when I started recording in HDef. With this drive offering, I can reduce my hard drive need to once every other month -- until all broadcasts are in HDef. I've still not sure what I'm going to do with 20 copies of "Enterprise" that I've been recording on the SciFi channel though.
Or he could...
... Start making a stink about that fact that these companies violated the law, violated our rights, and now after the fact are looking to get a deal for it.
This morning I heard on the news that one senator (sorry didn't get his name) was holding up that the companies did the "Patriotic" thing by doing what bush had asked for. My response to this: If they were to do the patriotic thing, they would have gone public with the illegal request in the first place.
Perhpas a bunch of them should watch A Few Good Men, "Dawson: We were supposed to fight for the people who couldn't fight for themselves."
One contract that I was at had an incompetent DBA. (The first time I began to question her abilities was when she asked if changing the desktop bitmap would impact system performance). When I found out she was terminated (about 15 minutes before a meeting I was going to host) I found a .mid file with this on it. Only my manager knew the real reason for the song playing in the background...
Yo-ho
Our two senators voted 'Nay'; the bad news is that 69 other jacks voted 'Yea'. To bad that I can't vote them out of office.
... and this /. story explains my brothers phone call late last night.
My grandmother decided to leave AOL. AOL however, would not leave her. She kept getting billed, and could not disconnect for MONTHS after the fact. I never did find out what the end result was, but (in the past) it was normal for AOL to 'not' disconnect your service when you asked them to...
I don't extrapolate anything: I offer advise based on years of hands on experience, and others have chosen to extrapolate that DELL equipment sucks.
From: Paul Tilley (Dell Computers)
Sent: Monday, October 18, 2004 4:00 PM
To: Removed
Subject: Dell SCSI RAID Reminder
All,
The document linked below describes some possible scenarios with SCSI RAID solutions, and how to address them. Many of you have Dell servers with RAID controllers in them, and some of these systems I'm sure are several years old. As a SCSI RAID system ages, the risks of double-fault scenarios (as described in the document) become more likely. So I feel it is important to make you aware of these recommendations.
http://support.dell.com/support/topics/global.aspx/support/kb/en/document?dn=1090190&c=us&l=en&s=gen&cs=
There is also a procedure in the document for automating this process. BTW, Dell is currently working on a RAID firmware-based background consistency-check, and I will let you know here as soon as it is available.
Please let me know if you have any questions. I do not want to alarm anyone - the odds of a double-fault occurring are minimal. But applying preventative maintenance will lower the odds even more.
Thanks!
Paul Tilley
DELL
Systems Consultant
xxx-xxx-xxx
From: IPAK (OTG Service Pack) Team (Internal)
Sent: Friday, January 16, 2004 5:19 PM
To: IPAK (OTG Service Pack) Notification
Subject: DATA LOSS ISSUE NOTIFICATION: Dell Servers with PERC 2 or 3Di (Adaptec) Controllers
Importance: High
DATA LOSS ISSUE NOTIFICATION: Dell Servers with PERC 2 or 3Di (Adaptec) Controllers
Issue: Datacenter Platform Standards Hardware Engineering team is providing notification of a potential data loss risk on Dell Platforms that contain PERC 2 or 3Di (Adaptec) Array Controllers. Over the past two months we have had an unacceptable number of escalations reporting this issue. We have escalated this issue to Dell and they have been able to reproduce the problem and are in the process of developing a fix/solution. In the interest of avoiding further data loss, we are requesting a hold on all Dell servers with a PERC 2 or PERC 3Di until further notice.
This issue is not related to IPAK installs or the OS. The catalyst for this event may be as simple as a warm or cold boot of an affected Dell server.
Affected Servers: Attached is a list of OTG datacenter servers (source ITCONFIG 1/16) that may have a PERC 2 or PERC 3Di controller installed:
Dell Perc2-3Di install list.xls
Keep in mind that this list contains all of the servers that may have a PERC 2 or PERC 3Di controller installed and that some of the servers on the list may not contain the affected controllers. Systems that contain only PERC 3DC controllers are not affected by this issue.
Confirmed affected models are:
PE6300
PE2450
PE1550
PE1650
Models that may have a PERC 2:
PE6400
PE6450
Recommended Action: DO NOT reboot these servers unless there is no other option. DO NOT upgrade, IPAK, change configurations, or move the server. This hold will last until a solution has been provided by Dell. We should receive a detailed explanation from Dell early next week with an ETA to a fix or solution. We will provide daily status to IPAKINFO starting Monday.
Thank you,
Datacenter Platform Standards - HW Engineering
Actually I'm talking about business model of hiding a known problem in the hope that the problem will not be found. The ironic thing is that I will usually recommend that for home and non-enterprise systems -- I'll always recommend DELL first.
Context of article: 'my private backup' (I presume this to mean "at home"); as was my instance. Hiring someone to monitor systems at home is a little silly.
I know DELL has a strong militant following, and has a strong bias in favor of DELL; however when I was working at MS, I followed up with the issue I was having with my DELL equipment. The email response that I received addressing the problem was sent from the rep for DELL; it was sent locked down so I couldn't even get a screen shot of it, admitting to the problem and the extent of it, and that "Dell was working on it". Years later, DELL had not fixed the problem. The problem relates to the PERC 2/3, and that it does not properly report a failed drive. What is worse in my opinion is that DELL had withheld this information. The problem was reported as multiple drives in an array would fail, and the system would be re-booted: the failed drives would 'kill' the RAID-5 array. (The system would not 'flag' the drives as failed until the next system reboot)
.... and the only problem with that is with DELL, there is no warning when the drives fail. I made the mistake of using a DELL enterprise solution: DELL servers only check for drive failure on boot up. I currently have a dead enterprise server with two failed drives. (Compaq would at least check the drives, and if one failed while 'running' you would know about it. I can't comment on HP, I can only hope (and presume) that they adopted the Compaq method of detecting a drive failure.
Whew, I'm glad to know that our business partners are secure. Our business just decided to use "Citi", and they have assured us that they are secure. Oh - wait, isn't Citi the same as "CitiBank"?
On the more serious side: They insist on using REAL customer data for testing, their test systems are not in sync with production, their test practices are VERY bad....
It comes as no surprise that they've had a break-in.
I'm surprised it wasn't claimed as one of the "Lost" email messages. Oh, they can't claim it was lost, as the lost email was actually "read" messages.
No; RTFA. It is part of MS licensing; most anyone can 'downgrade' to an older, lower (better) version of the Win OS.
First the obvious: Have a white list tied with caller ID.
...Enter 1234 backwards
...Enter the sum of 1000 plus 1
...Enter the number one thousand followed by the number you dialed
...Enter the area code for the number you just dialed
...Enter the year as for digits
...Enter the age of the person you called
...Enter the number of pets owned by the person you called
...Enter the number of presidents running for office
...Enter the number of presidents in office.
Next: Be able to exclude out of "area" calls (I get to define what the "area" is)
Next: For non-white listed numbers, have the disconnect signal sent (The there tone noise followed by "The number you have reached..."), followed by a question that requires a human to answer in a timely mannor:
Examples:
By having a few questions - asked at random, that are always changing, the cat and mouse game can go on for years. And, adding some random 'noise' between the words (both low and high frequency, our side of normal human hearing) one could 'trick' the computers performing the dialing in to 'false' answers to the questions.
This has nothing to do w/ storing 1's and 0's. It has everything to do with your credit score. If they don't have the information, you can't fight it. If they have any information it must be secured, so why are they bitching and wining about the amount of data? Look behind the question to see the real answer.
With Google's new "change the route" - it's cool. Yahoo's maps (old) is better, the new one has issues with moving the maps around (It frequently wants to go back!).... Mapquest sucks (Honest Question: why does anyone use it? - have you seen any of the other map tools?) Yahoo maps also lets me type in notes when I print out the map to actually _drive_ somewhere.
Some history of MS DOS....
Wish I had time for the long version but.... DOS 3.1 - 3.3 was stable, IBM released PC DOS 4.0, buggy as hell. MS said "what???" - and fixed some of the bugs for MS DOS 4.01. MS DOS 5.0 was rock stable; many of the so called 'bugs' were in fact bugs in the applications that were now showing up. V5 was fairly short lived (although it was popular) as MS released MS-DOS 6.0, which introduced MANY new bugs, thanks to a *VERY* bad and annoying PM. But it sold; and MS was sued by Stacker for the compression technology, and lost. (Yet another interesting story, Wikipedia only glosses over it. Oh, to have the text from that phone call again!). This begot MS DOS 6.21, and MS DOS 6.22. Also Winkipedia history is wrong: There never was a "MS-DOS 4.0 - June 1988 - derived from IBM's codebase rather than Microsoft's".
Drive space came in MS DOS 6.
... and send the request to Vastech, located on Bonaventura Drive in San Jose.
Follow up points --
..... and, if this will only work in CA, that would reduce the green house gasses by 50% ;-) but on a serious note - if it would work for 40% of the cars on the road now, that would put a serious dent w/ problems and petroleum based energy.
As this would be an electrical car, there won't be 180F under the hood (Unless there is a REAL problem with global warming)
And when we go to the 'energy station' of the future: Why won't have a sugar & enzymes that we can drop in and replace?
Ok, but CAN you bring the sugar bags onto the flight? It can be used as a rocket fuel and here; and as an explosive Sugar has a LOT of energy!