While I agree that people should strive to improve usability and have a uniform interface - User stupidity is something that exists in every market, from automobiles to manufacturing and heavy machinery. There is a reason we have fabled tales of people turning off their monitors instead of their pc's, or don't know what an address bar is because all they can ever manage to remember is typing an address in the google search page. Hell, getting your finger chopped off because you forgot to lock a sliding lift door. Improving software will make these a greater portion of your calls, too - because otherwise the software performs great! They just forgot to do something and panicked when it didn't do what they expected.
As a tech, you learn ways around this - but don't underestimate stupidity, please.
Wait a second. You're proposing raising taxes so that you pay for your expenses in opposition to reducing spending with the same tax? Neither of these have the goal of leaving debt for younger generations and, if done equally, accomplish the same thing in terms of paying off debt.
If your expenses are 1000 and you tax people for 950 from 800 - you're leaving a debt of 50$ opposed to 200$ If your expenses are 1000 and you are taxing 800, but lower state spending to 850 you've saved the same, and are only contributing 50$ to debt.
Personally, I'd like to see both done, but I was under the impression that Prius' and other class B cars produced less wear and tear on roads. Combine that with people driving less and shouldn't you actually end up with a situation where Roads are cheaper to maintain? Or are they largely fixed operating costs and therefore we need to be taxed differently to maintain them? In any event I don't see raising gas taxes as being seen particularly favorable by the public - no matter how it's done. We just got out of paying 4.00$ a gallon down to 1.50 afterall..
Another thing is people aren't necessarily driving any less than they were when gas prices were 3.00$ a gallon either - I know I'm not (commutes aren't particularly flexible in this regard) so perhaps the government just got too comfortable with higher tax incomes? Would this tax be repealed if gas prices rise again?
Regardless of your disputing the way the Grandparent post portrayed his argument, I must admit I'm inclined to agree with him.
1) The news article is light on details about who is classified as a sex offender. If public urination leads to forfeiting your passwords... that's bad. I'm less objectionable if we're talking about felony offenses. I also don't know what kind of charge rape would be for having sex with a similarly aged under 18 year old girl would be, particularly if Daddy decides to take revenge, but I would also object to this law applying to such situations.
2) This doesn't just invade the privacy of the convicted sex offender. It invades the privacy of whomever they are communicating with. Some will doubtlessly be informed such as friends and family - but coworkers? And buddy - I don't know about you but I don't actually look up my neighborhoods sex offenders. I don't have kids, so do I now need to police everyone I e-mail because someone wants to imprison people in the comfort of their own homes?
I get that serious sex crimes are repeated and jail time does nothing to dissuade their impulses. I also get that most of them have been victimized themselves and are stuck in a vicious cycle. Great - More jail time. Seriously, computer crimes are punished more.
Well we can't very well Attribute the Benefit of assumption to either one, since the article linked nothing to back up its claims. (Although I think you'll find other posters have determined the CFL's to have saved their cost of fuel in the first half hour or two and a half days of use)
The innocent-until proven guilty system, as well as other aspects of American criminal procedure, are just that - procedures, not substantive law - to protect the innocent. The US criminal justice system would rather let 10 guilty people go free than 1 innocent be convicted, since putting someone in a cage (or killing them, in rare cases) is a very serious thing. But innocent until proven guilty was never intended to prevent societal ostracization. That's what free thinking people do when they think someone is a bad person - just like your juvenile post tried to do with me.
This is fine, but keep in mind that this is why you should consider long and hard before even charging somebody. After all apparently looking guilty is enough to ruinyourlife.
I'm not sure why this was marked as a troll, because it's fairly accurate. Various companies I've worked for have requested customized versions of software to fit their needs and performance demands; they are big enough to do it. While that company might be big enough to throw money at licenses, they may not have the talent to reprogram an open source project to accomplish the same thing.
I guess it has more to do with what you're storing. Only recent data would be lost, so you wouldn't lose the entire document - just the latest revision. Really - that's an issue for any pending writes during a shutdown.
It's supposed to tolerate these faults for modifying data because it writes additional or replacement information somewhere else and then updates the index. So - you still might lose the data, but you won't have your index pointing at something corrupt due to a partial write.
Storage space was my primary concern - I just wanted enough redundancy to survive a drive failure. I have 1.3tb usable space and it's almost full, so raid 10 wouldn't cut it =/
In terms of priority, Space>redundancy>speed. I'm just dissapointed that it's actually slower than a single disk - by a lot.
I should add that I have previously experimented with TCP_NODELAY SORCVBUF=8192 SO_SNDBUF=8192 and this also negatively impacted file transfers in a similar way.
This has some really nice information - I saved it.
My experience shows a default transfer rate of: tcp 73.5MB/s udp 88.8MB/s
When enabling jumbo frames on both systems: tcp 103MB/s udp 115MB/s
However, I also noticed that this negatively impacted SMB transfer rates. They went from 24MB/s to about 9MB/s - so I suspect there's some optimizing to be done with samba as well. I'm not sure I like adjusting this as it might negatively affect systems that don't use jumbo frames... Do you have any experience configuring samba to work well with this?
Maybe - but software raid has some advantages. 1) It's not tied to a particular piece of hardware to function. Meaning in the event of a catastrophic failure (motherboard dies, or raid controller card) Anything I have will work. 2) It is usable while rebuilding the raid, which the raid controller I have most certainly is not (And takes a great deal more time to build)
Sadly, my off the shelf pc is woefully insufficient... I get 24MB/s max from a raid over gigabit...
The pc was originally an AMD 1800+ with SDRAM.
there are 8 drives total, one boot (80 gig IDE)
7 250 gig Seagates, all IDE - Originally they were all on a separate controller, and I used a raid controller to do it (acting as ide, no raid, in this case) the 7 250 gigs are setup in a software raid5 configuration in linux. Individually hdparm rates them as 60MB/s, and the whole raid as 70MB/s but for whatever reason file transfers from the raid to the boot drive topped out at 20-30MB/s. The gigabit card was also on the same PCI bus. However, copying from the boot drive over the network went at 50MB/s.
Thinking it might be a PCI bus limitation somehow, I moved the raid into a newer motherboard, sporting a 2200+ and ddr memory. Now being limited in ide controllers, all 7 drives are plugged into the raid controller in a master/slave setup. I get similar performance (average is now 23MB/s vs 20) and the gigabit ethernet controller is onboard.
I can't figure it out -_- I also don't have the money for a second raid controller (to put them all on their own channel) or to rebuild the pc with a PCI-E bus and sata.... so for now, that 20MB/s will have to be sufficient.
Maybe, But you might not be so eager to bring them coffee if it takes you an extra 40% longer on your commute because vital traffic ways are conjested..
In Phoenix, AZ your neighborhood determines if you have SRP or APS. SRP, at least, gives you the option of buying your electricity from renewable sources, but you don't get to choose who your provider is.
This would be cool, but could also be memory intensive. Routers have ram dedicated to a routing table, and if you're planning to implement this like I think you are, you're going to have the server run a bunch of traceroutes to determine how packets are traveling to their destination and sort them appropriately.
That or you could make assumptions about an isp's range and provide a bias to any ip within the same/16 range - but I'm pretty sure this is nowhere near ideal either.
So true. Nukes have a huge advantage compared to the anti nukes so worst case scenario you drag the fight out till they build mass nukes and overwhelm your nuke defense.
Is there anything actually limiting raid sync times? Drives are writing faster, processors are MUCH faster - couldn't they sync up faster as well?
I mean really, In a raid 5 you're reading from all the different disks, calculating parody, and writing that information to the drive - aside from all the calculations you've got essentially a disk (probably less) of data to write.
Slashdot Mirror
While I agree that people should strive to improve usability and have a uniform interface - User stupidity is something that exists in every market, from automobiles to manufacturing and heavy machinery. There is a reason we have fabled tales of people turning off their monitors instead of their pc's, or don't know what an address bar is because all they can ever manage to remember is typing an address in the google search page. Hell, getting your finger chopped off because you forgot to lock a sliding lift door. Improving software will make these a greater portion of your calls, too - because otherwise the software performs great! They just forgot to do something and panicked when it didn't do what they expected.
As a tech, you learn ways around this - but don't underestimate stupidity, please.
Wait a second.
You're proposing raising taxes so that you pay for your expenses in opposition to reducing spending with the same tax? Neither of these have the goal of leaving debt for younger generations and, if done equally, accomplish the same thing in terms of paying off debt.
If your expenses are 1000 and you tax people for 950 from 800 - you're leaving a debt of 50$ opposed to 200$
If your expenses are 1000 and you are taxing 800, but lower state spending to 850 you've saved the same, and are only contributing 50$ to debt.
Personally, I'd like to see both done, but I was under the impression that Prius' and other class B cars produced less wear and tear on roads. Combine that with people driving less and shouldn't you actually end up with a situation where Roads are cheaper to maintain? Or are they largely fixed operating costs and therefore we need to be taxed differently to maintain them? In any event I don't see raising gas taxes as being seen particularly favorable by the public - no matter how it's done. We just got out of paying 4.00$ a gallon down to 1.50 afterall ..
Another thing is people aren't necessarily driving any less than they were when gas prices were 3.00$ a gallon either - I know I'm not (commutes aren't particularly flexible in this regard) so perhaps the government just got too comfortable with higher tax incomes? Would this tax be repealed if gas prices rise again?
You probably won't read this but...
Regardless of your disputing the way the Grandparent post portrayed his argument, I must admit I'm inclined to agree with him.
1) The news article is light on details about who is classified as a sex offender. If public urination leads to forfeiting your passwords ... that's bad. I'm less objectionable if we're talking about felony offenses. I also don't know what kind of charge rape would be for having sex with a similarly aged under 18 year old girl would be, particularly if Daddy decides to take revenge, but I would also object to this law applying to such situations.
2) This doesn't just invade the privacy of the convicted sex offender. It invades the privacy of whomever they are communicating with. Some will doubtlessly be informed such as friends and family - but coworkers? And buddy - I don't know about you but I don't actually look up my neighborhoods sex offenders. I don't have kids, so do I now need to police everyone I e-mail because someone wants to imprison people in the comfort of their own homes?
I get that serious sex crimes are repeated and jail time does nothing to dissuade their impulses. I also get that most of them have been victimized themselves and are stuck in a vicious cycle. Great - More jail time. Seriously, computer crimes are punished more.
Well we can't very well Attribute the Benefit of assumption to either one, since the article linked nothing to back up its claims. (Although I think you'll find other posters have determined the CFL's to have saved their cost of fuel in the first half hour or two and a half days of use)
I guess that would have more to do with whom you believe carries the Burden of Proof
The innocent-until proven guilty system, as well as other aspects of American criminal procedure, are just that - procedures, not substantive law - to protect the innocent. The US criminal justice system would rather let 10 guilty people go free than 1 innocent be convicted, since putting someone in a cage (or killing them, in rare cases) is a very serious thing. But innocent until proven guilty was never intended to prevent societal ostracization. That's what free thinking people do when they think someone is a bad person - just like your juvenile post tried to do with me.
This is fine, but keep in mind that this is why you should consider long and hard before even charging somebody. After all apparently looking guilty is enough to ruin your life.
I'm not sure why this was marked as a troll, because it's fairly accurate. Various companies I've worked for have requested customized versions of software to fit their needs and performance demands; they are big enough to do it. While that company might be big enough to throw money at licenses, they may not have the talent to reprogram an open source project to accomplish the same thing.
I guess it has more to do with what you're storing. Only recent data would be lost, so you wouldn't lose the entire document - just the latest revision. Really - that's an issue for any pending writes during a shutdown.
How about parental release forms for different types of restrictions? or prior to providing them in the first place?
It's supposed to tolerate these faults for modifying data because it writes additional or replacement information somewhere else and then updates the index. So - you still might lose the data, but you won't have your index pointing at something corrupt due to a partial write.
Storage space was my primary concern - I just wanted enough redundancy to survive a drive failure. I have 1.3tb usable space and it's almost full, so raid 10 wouldn't cut it =/
In terms of priority, Space>redundancy>speed. I'm just dissapointed that it's actually slower than a single disk - by a lot.
I should add that I have previously experimented with TCP_NODELAY SORCVBUF=8192 SO_SNDBUF=8192 and this also negatively impacted file transfers in a similar way.
This has some really nice information - I saved it.
My experience shows a default transfer rate of:
tcp 73.5MB/s
udp 88.8MB/s
When enabling jumbo frames on both systems:
tcp 103MB/s
udp 115MB/s
However, I also noticed that this negatively impacted SMB transfer rates. They went from 24MB/s to about 9MB/s - so I suspect there's some optimizing to be done with samba as well. I'm not sure I like adjusting this as it might negatively affect systems that don't use jumbo frames... Do you have any experience configuring samba to work well with this?
Maybe - but software raid has some advantages. 1) It's not tied to a particular piece of hardware to function. Meaning in the event of a catastrophic failure (motherboard dies, or raid controller card) Anything I have will work. 2) It is usable while rebuilding the raid, which the raid controller I have most certainly is not (And takes a great deal more time to build)
Sadly, my off the shelf pc is woefully insufficient ... I get 24MB/s max from a raid over gigabit ...
The pc was originally an AMD 1800+ with SDRAM.
there are 8 drives total, one boot (80 gig IDE)
7 250 gig Seagates, all IDE - Originally they were all on a separate controller, and I used a raid controller to do it (acting as ide, no raid, in this case) the 7 250 gigs are setup in a software raid5 configuration in linux. Individually hdparm rates them as 60MB/s, and the whole raid as 70MB/s but for whatever reason file transfers from the raid to the boot drive topped out at 20-30MB/s. The gigabit card was also on the same PCI bus. However, copying from the boot drive over the network went at 50MB/s.
Thinking it might be a PCI bus limitation somehow, I moved the raid into a newer motherboard, sporting a 2200+ and ddr memory. Now being limited in ide controllers, all 7 drives are plugged into the raid controller in a master/slave setup. I get similar performance (average is now 23MB/s vs 20) and the gigabit ethernet controller is onboard.
I can't figure it out -_- I also don't have the money for a second raid controller (to put them all on their own channel) or to rebuild the pc with a PCI-E bus and sata.... so for now, that 20MB/s will have to be sufficient.
Maybe, But you might not be so eager to bring them coffee if it takes you an extra 40% longer on your commute because vital traffic ways are conjested ..
In Phoenix, AZ your neighborhood determines if you have SRP or APS. SRP, at least, gives you the option of buying your electricity from renewable sources, but you don't get to choose who your provider is.
I'm pretty sure charity donations count as a deduction on your taxes.
I would!
The mormons I know have 9 kids
9 * n = a lot of kids !
I'm just curious - but why do you care about our survival as a species in an event that may not happen in the foreseeable future?
I mean, this goes beyond caring about yourself, your children, or your children's children. This goes a bit beyond survival instinct.
This would be cool, but could also be memory intensive. Routers have ram dedicated to a routing table, and if you're planning to implement this like I think you are, you're going to have the server run a bunch of traceroutes to determine how packets are traveling to their destination and sort them appropriately.
That or you could make assumptions about an isp's range and provide a bias to any ip within the same /16 range - but I'm pretty sure this is nowhere near ideal either.
So true. Nukes have a huge advantage compared to the anti nukes so worst case scenario you drag the fight out till they build mass nukes and overwhelm your nuke defense.
so i fail at words too apparently =)
Parity.
Is there anything actually limiting raid sync times? Drives are writing faster, processors are MUCH faster - couldn't they sync up faster as well?
I mean really, In a raid 5 you're reading from all the different disks, calculating parody, and writing that information to the drive - aside from all the calculations you've got essentially a disk (probably less) of data to write.
Just watch out for terrorists trying to take Dylithium Resin!