About 14 years ago I told a close friend that one day Linux would rule the technology marketplace and Microsoft wasn't going to last. He didn't believe me.
Well, today, the first half of that is more or less true. Linux is in every set-top box out there, TVs, phones, and probably things I've not even heard of - and it's predominant in all those areas. Android sales are almost 60 times as high as Windows Phone sales. All this despite 12 years ago Linux being a marginal hobbyist and academic OS, with the most similar thing to the WinCE devices of the time being the Matchbox PC from Stanford labs.
One of the problems with OSS is that updating often breaks libraries...
I haven't had that happen in years and years. Debian 3.0 era (though I suppose jumping distro releases in RHEL has the tendency to break RPMs on occasion).
which if you have compiled 3rd party software installed can be a real barrier to updating.
That's your problem. You've got crap not built from packages. Why didn't you package them? There's a good case for doing so. (Either you need to build things from source and package them, use packages, or drop your binaries fully outside the system tree - eg./opt - and modify the $PATH.)
We have one machine that has not been updated with any patches for 2-3 years now because they will break installed apps.
Are there no updates for those apps? I've not yet seen an app which wouldn't deal with the newer versions of a library, not even proprietary stuff.
"Equality" of privilege has been not only been met, but it's been surpassed. You're familiar with affirmative action?
Equality of capability is another thing entirely. Those are things typically earned. The Irish in this country managed to pull themselves up fairly well, and they've only been here as long as the slave Africans and their descendants have been and were treated roughly the same as the blacks.
If your complaint is that blacks don't get treated like whites on average, maybe looking at the average demographic behavior of said 'races' is in order.
There is absolutely no evidence even suggesting Zimmerman killed him because he was black. Suggesting it is a statement of reverse racism: you don't like the fact that a black man was killed (and he was a man, not a boy) by a non-black (mixed Hispanic), but because blacks are a minority (just barely) the killer was obviously motivated by race hatred.
You have, apparently, never been in a all-in fight.
It takes precisely one well-placed hit to incapacitate someone. The human fist can knock someone out cold with a single blow. Most people have a very "fragile jaw" and the correct hit to the front or sides of the jaw can leave them, if not unconscious, delirious with pain.
A blow at the right angle to the nose can kill someone instantly.
The fact is that your life is in danger as long as your opponent is within proximity of you and capable of inflicting harm. For instance, it has repeatedly been shown that someone with a knife can reach and impale a person 25 feet away before that (trained) person can draw a holstered, non-concealed weapon (and officers are trained with this knowledge) and bring it to bear. If an assailant is still mobile within throwing distance, with obvious intent of harm, your life is quite threatened, be assured.
Now, whether Zimmerman was the actual antagonist and 'attacker' is another story. He may have started it then gotten himself in for more than he'd bargained. Judging by the man's history, that doesn't appear to be the case.
A wind turbine tower only has a 15 year (or so) life. The turbine itself has to be replaced several times in the life of the tower and requires constant maintenance. The cement for the tower has to be imported, unless you're building them somewhere like Mexico. The mining of cement materials, like lime, is markedly more destructive than the (for instance) lime byproduct of burning coal. This then has to be done every 15 years.
Meanwhile, the area around air turbines is not "polluted", but it's fairly desolate. Wildlife does not like to live there. Birds which fly near the towers will often be killed.
With the cost of gas and oil on its way up it's a wonder that any one would be against the use of renewable energy sources."
Quite possibly because wind turbines are horribly ecologically destructive, economically costly devices which are actually an energy net-loss for the size necessary for industrial generation, while costing taxpayer money to subsidize someone else's false industry? That, and they're annoying (at best) to live near.
Why, yes, I am a white male. I'm also at the "top of the pile" in almost every regard: above average intelligence, over-achieving and multi-talented. Hell, I'm even somewhat attractive - or at least enough so that I receive unsolicited approaches from the opposite sex. But that's redundant, because I'm already successful in that department (with a wife).
Your view may change when your boss says "I'm either going to fire you and bring sexual harassment charges against you or you're going to quit" because she was intimidated by you professionally, or when a female coworker with office political sway starts making moves on you and you're damned if you do and damned if you don't, because either way nobody will believe your story over her's.
I'm not blaming PCness for not being at the top, I'm blaming it for putting artificial barriers in place in front of me for racist and sexist reasons, while giving preference to other less-capable people based on race and gender. Hiring a white male out of preference against the alternatives is illegal, so why is the opposite not also illegal?
The PSU's I've had the most problems with have been Supermicro, so your 'build your own' criteria doesn't really stand my experience. I'll take the reliability of good desktop components over server components almost any day.
I'd be interested in seeing this on sourceforge or similar. I've not seen anyone implement anything quite like this yet. Ever consider selling it and offering support for it, or getting it packaged for distros?:)
What this sounds like to me is a combination of two things: fighting the impending irrelevancy and threat of the iPhone and Android, and trying to lock in another profit center to deal with the fact that they're not the only game in town anymore (literally).
Irrelevancy: Look, what these next gen consoles are up against is the cheapest of the cheap: we're at a point where you can get a $100 device running Android, hook it to your TV, and play any number of games off Google Play for free or near free. They're not up against their old consoles, particularly with how mature and well featured some of the Android games are getting. (There are FPS games on Play which rival the original Counterstrike in features and surpass it on graphics by quite a bit, all playable on your phone...)
Profit center: Again, $50-60 games which might suck on a $400 console you might buy if there are a couple games on it you like does not hold a candle to the $4 and under games. Since most people probably buy a console (due to the cost) once there are games they want to play available, and only buy a handful of games (what parent wants to regularly 'feed' their kids' console at $50/game or who wants to risk $50 on something that's horrible?).
Hollywood accounting: I suspect that the game industry has succumbed to Hollywood accounting. They claim a loss on the games or that they're not making a profit for accounting reasons, making it look like everyone's "losing" money. I'm sorry, but as popular as even the worst games are, they're selling them for $50+ each. I understand development costs are higher now than they used to be due to the epic nature of many movies, but there's little reason (IMO) for the disproportionate claims.
If that's the case, they've got a lot of explaining to do. Windows/Samba interoperability has been getting progressively worse over the past several years. Not only have updates to Windows broken Samba file servers (particularly, things which haven't been fixed or won't be fixed at any point, relying on registry hacks instead), but Samba updates have clobbered quite a few things, as well.
What is your basis of understanding?
My impression has been that almost all of their efforts have been put forward towards making linux work better for their virtualization efforts with HyperV (such as driver contributions and scheduler), but then, I've not been paying much attention.
If you've got 3TB drives in use in RAID, you're a fool for not running double parity. Like you said, the time required is just too long; you need to be able to survive a 2-disk failure.
Nothing too scientific, mostly just seat of the pants engineering. "This is running hot, it needs more fans". IF something gets close to over temp while running at maximum (eg. the dd) then you don't have enough cooling. Good engineering of mechanical/electrical needs at least a 30% overhead for worst case, and 50% over likely for thermal or electrical maximums.
I once had a drive which had no reported errors until one day, Sector 0 of the disk was unreadable. SMART would not work for some time prior to that (which I chalked up to a software failure, since the drive was performing fine). What I presume happened was the part of the disk where the SMART data and drive information is stored failed first.
5600 lines?! What exactly is BASH doing in 5600 lines which could not be done in, say, about 56 lines of conditional statements, a loop or three, and dd using "seek="?
From what I've noticed, DOAs are, in all likelihood, the result of improper handling more so than they are manufacturing problems.
For sensitive applications which have high costs associated with replacement, you'd probably want to be very sure you're getting your disks from somewhere that respects drives as sensitive mechanical devices. From what I've seen, getting a different production run can make a big impact on the drives, but getting them from another supplier seems to be more effective (possibly due to manuf runs going to only one or two specific clients? just guessing on that).
LOL at your static strap statement. That has almost no baring except in estimated overall electrical lifecycle. It might lead to a premature failure, but then again, it might not. Percussive damage to a drive WILL cause it to fail early, or not work at all.
To a degree, you can rule with certainty that everything is working.
New equipment does tend to have ghosts. Given enough systems, with homogeneous roles, it doesn't matter: if it starts to fail, you pull it and put another one in.
If you've got an environment with only a few servers with dedicated roles, having a new 'production server' go tits up is a very bad thing. For a system like this, you really do want to do a 'burn in' period, IMO for at least a couple weeks, where the system is not being depended upon. Your 4-year-old system doing the same thing at relatively diminished capability is not nearly as bad as doing a cut-over and having things go south, then.
You do, however, want to do a "burn in" on that new equipment. My preference is to stress a new piece of equipment with something like building kernels (which will stress every significant subsystem to some degree) while doing file operations (eg. something like bonnie+ if you're not copying files to the machine) for a period of at least a week without any stability or significant performance problems. This is due to the following subjective observations:
* getting a system with a defective disk is not uncommon these days. It's not common, so it's not a serious concern. * Short of initial failure of the disk/DOA status, the disks will likely run a number of months before your first failure (depending on how many you've got, of course) * Instability, inconsistent behavior, flaky RAM, or odd behavior from RAID or NIC controllers, and 'ghosts' can almost invariably be traced back to the PDU or PSU. These seem to die within about two weeks to a month if they're defective/poorly designed. With a server, troubleshooting this can be a huge bitch due to how loud they are and the multiple-dependence issue on the PDU. This is kind of an end game for me, and I have a hard time trusting any of the equipment after I've had a PSU fail. * if you plan on taxing the system at all, you'll probably have a driver related performance problem somewhere down the line. Better to find it before you need the performance. * Every once in a while, you've got a bad solid state device (RAM, CPU, SSD). These seem to either work, or not work, if they pass initial "does it work?"
RAID5 is not graceful. It's like a 4-wheeled vehicle getting a flat: you can limp along at 5mph, sure, but until you pull over, stop, and replace the tire, you're not going anywhere fast.
RAID6, or RAID10, are significantly more graceful.
The cultural expectation in the West has been, for quite some time, that if you're a white male, you're a sexual predator. That's what Women's Studies has been teaching to Education and Business majors now for several generations, and is often considered a requirement (as I understand things). Many convictions today of sexual harassment, as well as rape trials, are based on that thin veil of sexism and racism.
You joke, but given current Western moores, anyone who's white and male is to be considered to be a sexual predator of one sort or another. (Women, behaving the same way, however, are just liberated.)
Slashdot Mirror
Print the presentations as PDFs. They're much more compatible than the crap HTML output by your plugin, and can be saved and read anywhere.
AD/GPO control isn't an artificial advantage, it's (IMO) the only advantage IE has.
In contrast, imagine how much time you waste through malware infections directly caused by IE.
About 14 years ago I told a close friend that one day Linux would rule the technology marketplace and Microsoft wasn't going to last. He didn't believe me.
Well, today, the first half of that is more or less true. Linux is in every set-top box out there, TVs, phones, and probably things I've not even heard of - and it's predominant in all those areas. Android sales are almost 60 times as high as Windows Phone sales. All this despite 12 years ago Linux being a marginal hobbyist and academic OS, with the most similar thing to the WinCE devices of the time being the Matchbox PC from Stanford labs.
One of the problems with OSS is that updating often breaks libraries...
I haven't had that happen in years and years. Debian 3.0 era (though I suppose jumping distro releases in RHEL has the tendency to break RPMs on occasion).
which if you have compiled 3rd party software installed can be a real barrier to updating.
That's your problem. You've got crap not built from packages. Why didn't you package them? There's a good case for doing so. (Either you need to build things from source and package them, use packages, or drop your binaries fully outside the system tree - eg. /opt - and modify the $PATH.)
We have one machine that has not been updated with any patches for 2-3 years now because they will break installed apps.
Are there no updates for those apps? I've not yet seen an app which wouldn't deal with the newer versions of a library, not even proprietary stuff.
"Equality" of privilege has been not only been met, but it's been surpassed. You're familiar with affirmative action?
Equality of capability is another thing entirely. Those are things typically earned. The Irish in this country managed to pull themselves up fairly well, and they've only been here as long as the slave Africans and their descendants have been and were treated roughly the same as the blacks.
If your complaint is that blacks don't get treated like whites on average, maybe looking at the average demographic behavior of said 'races' is in order.
There is absolutely no evidence even suggesting Zimmerman killed him because he was black. Suggesting it is a statement of reverse racism: you don't like the fact that a black man was killed (and he was a man, not a boy) by a non-black (mixed Hispanic), but because blacks are a minority (just barely) the killer was obviously motivated by race hatred.
You have, apparently, never been in a all-in fight.
It takes precisely one well-placed hit to incapacitate someone. The human fist can knock someone out cold with a single blow. Most people have a very "fragile jaw" and the correct hit to the front or sides of the jaw can leave them, if not unconscious, delirious with pain.
A blow at the right angle to the nose can kill someone instantly.
The fact is that your life is in danger as long as your opponent is within proximity of you and capable of inflicting harm. For instance, it has repeatedly been shown that someone with a knife can reach and impale a person 25 feet away before that (trained) person can draw a holstered, non-concealed weapon (and officers are trained with this knowledge) and bring it to bear. If an assailant is still mobile within throwing distance, with obvious intent of harm, your life is quite threatened, be assured.
Now, whether Zimmerman was the actual antagonist and 'attacker' is another story. He may have started it then gotten himself in for more than he'd bargained. Judging by the man's history, that doesn't appear to be the case.
How is this any less of an argument than "roads cause noise pollution and harm wildlife", which I hear greens pushing all the time?
A wind turbine tower only has a 15 year (or so) life. The turbine itself has to be replaced several times in the life of the tower and requires constant maintenance. The cement for the tower has to be imported, unless you're building them somewhere like Mexico. The mining of cement materials, like lime, is markedly more destructive than the (for instance) lime byproduct of burning coal. This then has to be done every 15 years.
Meanwhile, the area around air turbines is not "polluted", but it's fairly desolate. Wildlife does not like to live there. Birds which fly near the towers will often be killed.
If it were my provider, I'd leave and tell all my friends and acquaintances precisely which provider it is.
This behavior is worse than inexcusable. Sure, it's a 'cheap' service but the reprecussions for this are massive to the user.
With the cost of gas and oil on its way up it's a wonder that any one would be against the use of renewable energy sources."
Quite possibly because wind turbines are horribly ecologically destructive, economically costly devices which are actually an energy net-loss for the size necessary for industrial generation, while costing taxpayer money to subsidize someone else's false industry? That, and they're annoying (at best) to live near.
Why, yes, I am a white male. I'm also at the "top of the pile" in almost every regard: above average intelligence, over-achieving and multi-talented. Hell, I'm even somewhat attractive - or at least enough so that I receive unsolicited approaches from the opposite sex. But that's redundant, because I'm already successful in that department (with a wife).
Your view may change when your boss says "I'm either going to fire you and bring sexual harassment charges against you or you're going to quit" because she was intimidated by you professionally, or when a female coworker with office political sway starts making moves on you and you're damned if you do and damned if you don't, because either way nobody will believe your story over her's.
I'm not blaming PCness for not being at the top, I'm blaming it for putting artificial barriers in place in front of me for racist and sexist reasons, while giving preference to other less-capable people based on race and gender. Hiring a white male out of preference against the alternatives is illegal, so why is the opposite not also illegal?
The PSU's I've had the most problems with have been Supermicro, so your 'build your own' criteria doesn't really stand my experience. I'll take the reliability of good desktop components over server components almost any day.
I'd be interested in seeing this on sourceforge or similar. I've not seen anyone implement anything quite like this yet. Ever consider selling it and offering support for it, or getting it packaged for distros? :)
What this sounds like to me is a combination of two things: fighting the impending irrelevancy and threat of the iPhone and Android, and trying to lock in another profit center to deal with the fact that they're not the only game in town anymore (literally).
Irrelevancy: Look, what these next gen consoles are up against is the cheapest of the cheap: we're at a point where you can get a $100 device running Android, hook it to your TV, and play any number of games off Google Play for free or near free. They're not up against their old consoles, particularly with how mature and well featured some of the Android games are getting. (There are FPS games on Play which rival the original Counterstrike in features and surpass it on graphics by quite a bit, all playable on your phone...)
Profit center: Again, $50-60 games which might suck on a $400 console you might buy if there are a couple games on it you like does not hold a candle to the $4 and under games. Since most people probably buy a console (due to the cost) once there are games they want to play available, and only buy a handful of games (what parent wants to regularly 'feed' their kids' console at $50/game or who wants to risk $50 on something that's horrible?).
Hollywood accounting: I suspect that the game industry has succumbed to Hollywood accounting. They claim a loss on the games or that they're not making a profit for accounting reasons, making it look like everyone's "losing" money. I'm sorry, but as popular as even the worst games are, they're selling them for $50+ each. I understand development costs are higher now than they used to be due to the epic nature of many movies, but there's little reason (IMO) for the disproportionate claims.
It doesn't increase interoperability. It increases the likelihood (or possibility) of dependence.
If that's the case, they've got a lot of explaining to do. Windows/Samba interoperability has been getting progressively worse over the past several years. Not only have updates to Windows broken Samba file servers (particularly, things which haven't been fixed or won't be fixed at any point, relying on registry hacks instead), but Samba updates have clobbered quite a few things, as well.
What is your basis of understanding?
My impression has been that almost all of their efforts have been put forward towards making linux work better for their virtualization efforts with HyperV (such as driver contributions and scheduler), but then, I've not been paying much attention.
If you've got 3TB drives in use in RAID, you're a fool for not running double parity. Like you said, the time required is just too long; you need to be able to survive a 2-disk failure.
Nothing too scientific, mostly just seat of the pants engineering. "This is running hot, it needs more fans". IF something gets close to over temp while running at maximum (eg. the dd) then you don't have enough cooling. Good engineering of mechanical/electrical needs at least a 30% overhead for worst case, and 50% over likely for thermal or electrical maximums.
I once had a drive which had no reported errors until one day, Sector 0 of the disk was unreadable. SMART would not work for some time prior to that (which I chalked up to a software failure, since the drive was performing fine). What I presume happened was the part of the disk where the SMART data and drive information is stored failed first.
5600 lines?! What exactly is BASH doing in 5600 lines which could not be done in, say, about 56 lines of conditional statements, a loop or three, and dd using "seek="?
From what I've noticed, DOAs are, in all likelihood, the result of improper handling more so than they are manufacturing problems.
For sensitive applications which have high costs associated with replacement, you'd probably want to be very sure you're getting your disks from somewhere that respects drives as sensitive mechanical devices. From what I've seen, getting a different production run can make a big impact on the drives, but getting them from another supplier seems to be more effective (possibly due to manuf runs going to only one or two specific clients? just guessing on that).
LOL at your static strap statement. That has almost no baring except in estimated overall electrical lifecycle. It might lead to a premature failure, but then again, it might not. Percussive damage to a drive WILL cause it to fail early, or not work at all.
To a degree, you can rule with certainty that everything is working.
New equipment does tend to have ghosts. Given enough systems, with homogeneous roles, it doesn't matter: if it starts to fail, you pull it and put another one in.
If you've got an environment with only a few servers with dedicated roles, having a new 'production server' go tits up is a very bad thing. For a system like this, you really do want to do a 'burn in' period, IMO for at least a couple weeks, where the system is not being depended upon. Your 4-year-old system doing the same thing at relatively diminished capability is not nearly as bad as doing a cut-over and having things go south, then.
You do, however, want to do a "burn in" on that new equipment. My preference is to stress a new piece of equipment with something like building kernels (which will stress every significant subsystem to some degree) while doing file operations (eg. something like bonnie+ if you're not copying files to the machine) for a period of at least a week without any stability or significant performance problems. This is due to the following subjective observations:
* getting a system with a defective disk is not uncommon these days. It's not common, so it's not a serious concern.
* Short of initial failure of the disk/DOA status, the disks will likely run a number of months before your first failure (depending on how many you've got, of course)
* Instability, inconsistent behavior, flaky RAM, or odd behavior from RAID or NIC controllers, and 'ghosts' can almost invariably be traced back to the PDU or PSU. These seem to die within about two weeks to a month if they're defective/poorly designed. With a server, troubleshooting this can be a huge bitch due to how loud they are and the multiple-dependence issue on the PDU. This is kind of an end game for me, and I have a hard time trusting any of the equipment after I've had a PSU fail.
* if you plan on taxing the system at all, you'll probably have a driver related performance problem somewhere down the line. Better to find it before you need the performance.
* Every once in a while, you've got a bad solid state device (RAM, CPU, SSD). These seem to either work, or not work, if they pass initial "does it work?"
RAID5 is not graceful. It's like a 4-wheeled vehicle getting a flat: you can limp along at 5mph, sure, but until you pull over, stop, and replace the tire, you're not going anywhere fast.
RAID6, or RAID10, are significantly more graceful.
The cultural expectation in the West has been, for quite some time, that if you're a white male, you're a sexual predator. That's what Women's Studies has been teaching to Education and Business majors now for several generations, and is often considered a requirement (as I understand things). Many convictions today of sexual harassment, as well as rape trials, are based on that thin veil of sexism and racism.
You joke, but given current Western moores, anyone who's white and male is to be considered to be a sexual predator of one sort or another. (Women, behaving the same way, however, are just liberated.)