So a computer is a box. It has four sides, a top and a bottom. Some may not have four sides, this is irrelevant.
The solution to this is a hard hack (well one solution anyway). Case is opened without putting a magnet in JUST the right place (or some other measure) and memory is fried.
I'm not sure about the months, weeks or even days. Sometimes it can be hours, sometimes even minutes, it all depends on a bug.
My bug report work flow:
1 - Make sure I'm not the bug 2 - Grab the source 3 - Browse 4 - Figure out (approximately) what point in the code my bug is coming from 5 - Write a bug report like this:
Hi,
Your program foo just killed my cat. No shit, killer pokes aren't funny dammit and you said this would work on a commodore PET! My cat had a seizure and its dead claws are now embedded in my skull as I write this.
As far as I can tell, its fate was sealed somewhere around line 2113. Looking at your commit logs, it looks like someone got ahold of the user "hsimpson"'s password, please ask him to change it.
I would help diagnose this more, but I have to get this cat off my head.
See? Even if I know _nothing_ about the code, I do know _something_ about the bug.. and can usually provide a little bit of information beyond 'its fucked up, fix it'.. which is the gist of the common bug report.:)
Most bug trackers are smart enough to send e-mail to a developer, or a list of developers.
I think 99% of all submitted bugs are read (or at least glanced at), however the bug trackers are often way behind and (gasp) sometimes those e-mails are just ignored or forgotten.
Sometimes its as simple as a language barrier, sometimes just very busy people.. or sometimes you happen upon a developer who is 300x more sick of the program than you are:)
If you instill, in your kids, very early on a strong unbreakable sense of self.. you can afford them privacy and not cram lowjacks up their derriers.
Yes, I am also a parent, and I refuse to instill unreasonable fears in my child by tracking her like the CIA.
If you want your child to be safe, take care to ensure that they won't be inclined to seek approval from any person to form the cornerstone of their personal esteem early on. You can do that easily, spend time with them, don't yell at them and whatever you do don't hit them. Take an interest in their lives early on and they won't resent your interest later.
Shoving a GPS up their ass is just counterproductive, if your goal is to produce a happy, confident adult.
The problem is not that redundancy wasn't implemented. The problem is that redundancy doesn't handle 'flapping' hardware very well. The NIC intermittently failed, causing the redundancy to switch cards several times. This can play havoc on systems that work on a LAN and assume the MAC address to stay the same.
That's what got me curious, it looked like they were using takeover instead of bonding devices.
The most well engineered system in the world can not hope to escape a ~9 minute ARP cache upstream, which makes me wonder why it was designed the way that it was.
I'm not thinking in an antagonistic sense, I'm more wondering what changed in the network _after_ the system was deployed.
Whatever happened to testing of installed hardware? You'd think they might csider that sort of thing important when it involves the lives of thousands of people. Then again, maybe they were drunk at the time.
Well, when we set up some cheap NAS boxes with redundant nics.. some load balancers and other goodies.. we tested it by yanking cables on the bonded nics and making sure everything still worked.
This was for an e-commerce site.. I would agree in hoping more testing with real failures would be done on systems that monitor air traffic.
Also, we were very drunk when yanking cables during our test.. so I don't think intoxication is really a factor. In fact, turning a drunken monkey loose in a data center with a clearance to pull cables is _very_ good fail over testing:)
Run like hell because there's a very good chance some vendor just farted in your data center and called it a cloud.
It could also allude to the 'vaporware' that has yet to accomplish anything other than dynamic provisioning and configuration of virtual servers. Sure that's neat, but it doesn't warrant a buzzword.
Marketing loves buzzwords. They could not get what they do to fit any of the accepted definitions of 'grid' , so they picked 'cloud'.
I'm not saying its not useful, just separate the worth from the hype.. currently the hype still tips the scales.
I also have a VPS (Xen) on the same network that can connect to both database servers.
I fully agree, shared hosting is rapidly becoming a dinosaur. You just can't predict usage. One site on the front page of Slashdot, Digg.. or in the scope of stumblers makes 500 other sites very unhappy.
A good host will isolate everything, so that its very easy for you to move things around as needed. I'll park domains on a shared server, then move them to a vm when I get around to developing them.
But either way, kind of getting off topic. The fact remains is that most good hosts have absolutely no issues with differences in MySQL version nuances.
Apparently, MySQL AB (prior to purchase) were the ones contemplating making the move to more proprietary tools. It was set in motion and left on the table, then Sun purchased them.
Sun basically said "We have no need to put this in play, we don't make our money from a single product like MySQL AB did.."
A lot of people Criticized Sun for the idea, however the idea was the brainstorm of MySQL AB, not Sun.
Hosting providers that are worth their weight will typically use external MySQL (clusters) and offer various versions. They've learned the painful lesson that running a bunch of over-allocating services that are open to the world on one box only leads to customers canceling due to down time.
For instance, the $20 I pay a month gets me access to 4.x and 5.x, each version being its own shared cluster.
Attempting to fix this would draw legislative fire from congress.
I've been thinking about that too.
For the sake of discussion, lets say that some event happened that forbade patenting the 'method of' anything.
What happens then? There are so many highly ambiguous patents already issued which companies paid between $10,000 and $25,000 to obtain, not counting the costs of litigation.
Would those just instantly become null and void? I doubt it unless the government bought them all back under the idea of eminent domain (as patents are considered to be property). What would be the compensation? Each one will be argued to be worth millions and a company asset. I can hear the argument now.. 'if you take our patents you seriously devalue our company'.
It would be a happy day to hear that the madness will end, but the next day would bring litigation as usual. I don't think we'll hear the end of these things until they stop issuing them and all that are issued have expired.
A lot could happen in that time.
Maybe I'm wrong, perhaps the patent office would review every single software patent and begin invalidating bogus ones.. but the lawsuits that follow would tie that up for years.
I think if anything we'll see that they can take your house to build a highway.. but they have incredible difficulties taking your patent to unplug innovation.
All of which is a roundabout way of saying: Carl Icahn is a vocal, over-exposed pain in the ass. Whenever he talks, put your hand over your wallet, and pay very careful attention to what he's doing with his own.
Schwab
OK, so if you resist a hostile takeover by Microsoft, they send an old billionaire to come fart in your office?
Why, oh why couldn't they have gone after Enron? That combination of gases could have fueled an entire city for a decade.
More importantly, OLPC should be putting software into the hands of these kids, not just a license to use a copy of some software owned by someone else. I think its easier to discuss the negative, as in what we should not be putting into children's hands.
Learning materials that are locked with DRM and require a proprietary operating system to use would be a good example of what *not* to put in the hands of children.
If those materials were DRM free, then I'd agree, do whatever it takes to get the units where they can do some good.
While there is no DRM on the XP units as of now, it is not at all unreasonable to suggest that those units will soon use DRM given Microsoft's history.
The arguments against DRM go way beyond idealistic concerns, they venture very far into the realm of realistic, practical concerns.
If someone from Microsoft or OLPC would just come out and say "There will be no DRM on the OLPC, ever.", I'd shut up... so would a lot of other people.
I'll probably never use this distro, because I find Gnome quite unfriendly. (I acknowledge that others have other opinions.) A common misconception is that you are married to whatever desktop the distro installs. You are not.
A simple 'apt-get install kde' will give you something that you might find more agreeable.
I made a kind of hybrid, gnome is the base but the layout is KDE, and I brought most of the KDE programs in (KATE is my editor of choice). This lets you keep up on the themes / etc in gnome, but still have something easy and intuitive to use.
the other 2% are self-absorbed twits who want everyone to know how clever they are for coming up with a "recursive" algorithm. I think that you meant "acronym".
Or better yet, just call it "Linux." By that token, people should just forget their (pick one) first or last name, because 98% of the people that they know just call them by one of those names.
That way my Mom won't have to ask me "are you running regular Linux on your computer in the basement or that Agnew Linux?" every time she hears a Linux story on public radio.
There, I do feel your pain. My mother is 68 and called me the minute that she saw "Revolution OS".
I think escaping the basement would solve more problems for you than helping to ensure the GNU project doesn't get credit for the work that they did (and continue to do).
The mere existence of the non-free repository wouldn't prevent the FSF from considering Debian a Free operating system. They class OpenBSD as non-free even though the base system is 100% Free Software, because the ports system contains build infrastructure required to create packages from non-Free software (e.g. Opera). The modified BSD license does not qualify as completely free in the eyes of the FSF. It is compatible with the GPL (however the GPL takes precedence when mixing), this produces the famous one way effect.
The modified BSD license allows you to place additional restrictions on a program that someone else created and then distribute copies with those additional restrictions, i.e. no source code.
You can't do that with a program licensed under the GPL. You must give everyone that receives a copy of the program from you the same freedoms that you had with the program. If you make changes, you must convey the modified source upon request by anyone who receives a binary copy.
Agreed, I immediatly hated the name. The OSS crowd still has a bit to learn about branding, etc. So you guys would prefer (yet another) obscure but mutually recursive acronym for a project?:)
$5 to whoever lists (all of) the things that HURD stands for without looking it up:P
Slashdot Mirror
So a computer is a box. It has four sides, a top and a bottom. Some may not have four sides, this is irrelevant.
The solution to this is a hard hack (well one solution anyway). Case is opened without putting a magnet in JUST the right place (or some other measure) and memory is fried.
Do X rays fry memory? Anyone?
Actually, looks like the blog is toast for now. Nothing more to see here, move along, move along.
I'm not sure about the months, weeks or even days. Sometimes it can be hours, sometimes even minutes, it all depends on a bug.
My bug report work flow:
1 - Make sure I'm not the bug
2 - Grab the source
3 - Browse
4 - Figure out (approximately) what point in the code my bug is coming from
5 - Write a bug report like this:
Hi,
Your program foo just killed my cat. No shit, killer pokes aren't funny dammit and you said this would work on a commodore PET! My cat had a seizure and its dead claws are now embedded in my skull as I write this.
As far as I can tell, its fate was sealed somewhere around line 2113. Looking at your commit logs, it looks like someone got ahold of the user "hsimpson"'s password, please ask him to change it.
I would help diagnose this more, but I have to get this cat off my head.
See? Even if I know _nothing_ about the code, I do know _something_ about the bug .. and can usually provide a little bit of information beyond 'its fucked up, fix it' .. which is the gist of the common bug report. :)
It is, I picked up the link from a usenet LUG today and spent an hour laughing my ass off. The blog is really worth a read .. check out (in particular)
"How to write a Gnome application"
and
"How to write a KDE application"
Its funny, laugh.
Most bug trackers are smart enough to send e-mail to a developer, or a list of developers.
I think 99% of all submitted bugs are read (or at least glanced at), however the bug trackers are often way behind and (gasp) sometimes those e-mails are just ignored or forgotten.
Sometimes its as simple as a language barrier, sometimes just very busy people .. or sometimes you happen upon a developer who is 300x more sick of the program than you are :)
If you instill, in your kids, very early on a strong unbreakable sense of self .. you can afford them privacy and not cram lowjacks up their derriers.
Yes, I am also a parent, and I refuse to instill unreasonable fears in my child by tracking her like the CIA.
If you want your child to be safe, take care to ensure that they won't be inclined to seek approval from any person to form the cornerstone of their personal esteem early on. You can do that easily, spend time with them, don't yell at them and whatever you do don't hit them. Take an interest in their lives early on and they won't resent your interest later.
Shoving a GPS up their ass is just counterproductive, if your goal is to produce a happy, confident adult.
Sorry, work less, parent more.
The problem is not that redundancy wasn't implemented. The problem is that redundancy doesn't handle 'flapping' hardware very well.
The NIC intermittently failed, causing the redundancy to switch cards several times.
This can play havoc on systems that work on a LAN and assume the MAC address to stay the same.
That's what got me curious, it looked like they were using takeover instead of bonding devices.
The most well engineered system in the world can not hope to escape a ~9 minute ARP cache upstream, which makes me wonder why it was designed the way that it was.
I'm not thinking in an antagonistic sense, I'm more wondering what changed in the network _after_ the system was deployed.
Whatever happened to testing of installed hardware? You'd think they might csider that sort of thing important when it involves the lives of thousands of people. Then again, maybe they were drunk at the time.
Well, when we set up some cheap NAS boxes with redundant nics .. some load balancers and other goodies .. we tested it by yanking cables on the bonded nics and making sure everything still worked.
This was for an e-commerce site.. I would agree in hoping more testing with real failures would be done on systems that monitor air traffic.
Also, we were very drunk when yanking cables during our test .. so I don't think intoxication is really a factor. In fact, turning a drunken monkey loose in a data center with a clearance to pull cables is _very_ good fail over testing :)
Windows Vista
But his computer isn't "Windows Vista ready", you insensitive clod!
Intel may beg to differ!!
I think you misspelled EMACS
Hmm, nope:
(P)erfect (E)macs (R)e-writing (L)anguage
He got it right.
Run like hell because there's a very good chance some vendor just farted in your data center and called it a cloud.
It could also allude to the 'vaporware' that has yet to accomplish anything other than dynamic provisioning and configuration of virtual servers. Sure that's neat, but it doesn't warrant a buzzword.
Marketing loves buzzwords. They could not get what they do to fit any of the accepted definitions of 'grid' , so they picked 'cloud'.
I'm not saying its not useful, just separate the worth from the hype.. currently the hype still tips the scales.
I also have a VPS (Xen) on the same network that can connect to both database servers.
I fully agree, shared hosting is rapidly becoming a dinosaur. You just can't predict usage. One site on the front page of Slashdot, Digg .. or in the scope of stumblers makes 500 other sites very unhappy.
A good host will isolate everything, so that its very easy for you to move things around as needed. I'll park domains on a shared server, then move them to a vm when I get around to developing them.
But either way, kind of getting off topic. The fact remains is that most good hosts have absolutely no issues with differences in MySQL version nuances.
I've grown rather fond of Mercurial in the last year. I also like Bazaar, still wrapping my head around Git.
One thing is for sure, people are as adamant about their choice in a DRCS as they are about their choice in database servers.
I'm just happy to see a DRCS (no matter which one) in use. It makes things so much easier.
I'm going to go hide from the Subversion fans now.
God damn it. How did I post that to the wrong article?
Tabbed browsing strikes again!
And beer had nothing to do with it? :)
It was interesting to see Sun's reaction.
Apparently, MySQL AB (prior to purchase) were the ones contemplating making the move to more proprietary tools. It was set in motion and left on the table, then Sun purchased them.
Sun basically said "We have no need to put this in play, we don't make our money from a single product like MySQL AB did .."
A lot of people Criticized Sun for the idea, however the idea was the brainstorm of MySQL AB, not Sun.
Hosting providers that are worth their weight will typically use external MySQL (clusters) and offer various versions. They've learned the painful lesson that running a bunch of over-allocating services that are open to the world on one box only leads to customers canceling due to down time.
For instance, the $20 I pay a month gets me access to 4.x and 5.x, each version being its own shared cluster.
The crown will plainly show the prisoner who now stands before you, was caught red handed 0wn1ng people, 0wn1ng people of an almost HUMAN nature.
This will not do.
Sorry, couldn't resist.
Attempting to fix this would draw legislative fire from congress.
I've been thinking about that too.
For the sake of discussion, lets say that some event happened that forbade patenting the 'method of' anything.
What happens then? There are so many highly ambiguous patents already issued which companies paid between $10,000 and $25,000 to obtain, not counting the costs of litigation.
Would those just instantly become null and void? I doubt it unless the government bought them all back under the idea of eminent domain (as patents are considered to be property). What would be the compensation? Each one will be argued to be worth millions and a company asset. I can hear the argument now .. 'if you take our patents you seriously devalue our company'.
It would be a happy day to hear that the madness will end, but the next day would bring litigation as usual. I don't think we'll hear the end of these things until they stop issuing them and all that are issued have expired.
A lot could happen in that time.
Maybe I'm wrong, perhaps the patent office would review every single software patent and begin invalidating bogus ones.. but the lawsuits that follow would tie that up for years.
I think if anything we'll see that they can take your house to build a highway .. but they have incredible difficulties taking your patent to unplug innovation.
All in the name of progress.
All of which is a roundabout way of saying: Carl Icahn is a vocal, over-exposed pain in the ass. Whenever he talks, put your hand over your wallet, and pay very careful attention to what he's doing with his own.
Schwab
OK, so if you resist a hostile takeover by Microsoft, they send an old billionaire to come fart in your office?Why, oh why couldn't they have gone after Enron? That combination of gases could have fueled an entire city for a decade.
Learning materials that are locked with DRM and require a proprietary operating system to use would be a good example of what *not* to put in the hands of children.
If those materials were DRM free, then I'd agree, do whatever it takes to get the units where they can do some good.
While there is no DRM on the XP units as of now, it is not at all unreasonable to suggest that those units will soon use DRM given Microsoft's history.
The arguments against DRM go way beyond idealistic concerns, they venture very far into the realm of realistic, practical concerns.
If someone from Microsoft or OLPC would just come out and say "There will be no DRM on the OLPC, ever.", I'd shut up
Maybe they did and I just didn't see it?
A simple 'apt-get install kde' will give you something that you might find more agreeable.
I made a kind of hybrid, gnome is the base but the layout is KDE, and I brought most of the KDE programs in (KATE is my editor of choice). This lets you keep up on the themes / etc in gnome, but still have something easy and intuitive to use.
I think escaping the basement would solve more problems for you than helping to ensure the GNU project doesn't get credit for the work that they did (and continue to do).
The modified BSD license allows you to place additional restrictions on a program that someone else created and then distribute copies with those additional restrictions, i.e. no source code.
You can't do that with a program licensed under the GPL. You must give everyone that receives a copy of the program from you the same freedoms that you had with the program. If you make changes, you must convey the modified source upon request by anyone who receives a binary copy.
The OSS crowd still has a bit to learn about branding, etc. So you guys would prefer (yet another) obscure but mutually recursive acronym for a project?
$5 to whoever lists (all of) the things that HURD stands for without looking it up
Well, ok