Damn right --- I can remember one or two times I did things like that as a 5~8yo and the worst of it is that I still remember it:( I remember switching the price tags on a pair of fishing rods which was sort of stupid since I couldn't afford either of them *whoops*.
While the prize money isn't a lot, it might actually have an interesting effect in bringing about the less well funded but no less ingenious developers into the foray while the typical high ranking developers/companies pay less attention. It's certainly something I'd be interested in participating in (the aerial navigation).
Your 3x3 matrix didn't make sense to me at first until you mentioned how every other desktop is thus 1 desktop away, ingenious! Nice tip, now I have to work out how to make Fluxbox do that.
I noticed my DV cam is on the list, DCR-HC15E, the question is, what sort of deterioration should I be looking for? Maybe it's just me but I could swear that the quality of the video I get out of the unit these days appears less than what I originally was getting when I first bought it and that was/before/ I read about this story. Perhaps there's a way to accellerate the process of failure (if the weakness is there).
Incidently, living in a hot humid environment here too (North Eastern Australia)
It is heartbreaking to see our blood, sweat, and tears over the past 2 years blurred by the confusion and frustration surrounding this new technology. It is also unfortunate when bands such as ourselves, Foo Fighters, Coldplay, etc... (just a few of the new releases with copy protection) are the target of this criticism, when there is no possible way to avoid this new industry policy.
[Bolding mine]
Not sure about there being "no possible way" - perhaps when it comes time to renew their contract with Sony they'll consider going to alternative solutions. Worse comes to worse, perhaps they won't ever be able to escape Sony but they'll serve as a warning for others.
If the large corps keep on with this process it'll typically generate a new band of recording studios who don't and thus are seen as somewhat more friendly (though the cycle will probably still go on).
When I received the letter re Linux it quite honestly scared the daylights out of me. There was this letter that started out saying "this is a notice, not a letter of demand" but then it goes on talking about moderately large sums of money and potential legal fees.
What was doubly annoying though was that the letter appeared to be sent out without checking to see if the recipient was applicable. None of the services or products that I had on my WWW site used the word "linux" in them, they simply happen to be able to/execute/ on linux too (so linux was listed as a "compatible OS".
I still consider the email to be bordering very close to spam.
Next time, a registered letter in the post after each site is checked for relevance would be a far more reputable manner of distribution.
I received the letter in/email/ as well - what bothers me is that none of my products or service have linux used in their names,/none/. I know that the various projects I have OpenSourced will run in linux but that's the extent of it.
The letter was sent out in the evening and quite honestly is immediately ranked as spam/scam in my eyes such to the point where I started hunting around for a way to contact Linus or a group representing Linus to inform him of this.
In the end I wrote back a simple email saying that we didn't use Linux in our product names (why limit ourselves to linux when there's so many other OS's too).
If the guy wanted to be taken seriously it should have been a mailout using the registered postal service.
Looks like this was really a bit of a fishing expedition to me.
It might balance out... Some people download once and install on multiple machines. Some people download multiple times on a single machine (different versions).
Quite right, the +/-1% was most likely incorrect. The source, I cannot recall. That's what I get for replying to/. before coffee.
After coffee I would have written something like "It'll be okay because the Iraq invasion and subsequent burnoffs along with..." hrmm, nope, can't think of anything to combine GWBush/Iraq/Microsoft/Intel/Apple/NataliePortman, better have another coffee.
The combustion of materials for fire are rather sensitive to the percentage of oxygen in our atmosphere. Another +1% of O2 and we'd have a fireball raging, another -1% of O2 and things would not ignite in the free atmosphere. Subsequently if these microbes/algae get started with creating more O2 it'd simply be consumed by more fire.
I remember back in 1987 using smilies/emoticons on BBS. No doubt they were certainly used before then as I was showed them by a crusty old BBS admin.
Offset backups first, then RAID
on
Basics of RAID
·
· Score: 1
Personally, I prefer daily backups to another HDD (use rsync, it's great), that way, if I make a major *oops* during the day I know I have a very recent backup immediately available, this is something that RAID cannot protect you from (the human failure).
If then I've still got money to spare, I'll look at mirroring.
We just dumped access via password, forced everyone to work using RSA keys, at the very least, it certainly actually makes people's jobs easier since now they can login without a password if they want:-)
While having more surface area for larger caches or what ever is a wonderful thing, where this stacking concept can really help out is helping with clock sync issues.
Now that we're pushing into the GHz speeds on chips it is getting rather difficult to keep the whole chip in sync across the distances that the signal has to travel. By stacking the various segments of the chip you've eliminated another obstical for higher clockspeeds.
Absolutely agreed on your points - there is one situation where a small binary patch does become useful, where it's a legacy system which simply cannot be swapped out for the 'latest version', non of us like those situations but they do exist:-(
Thanks for the pointers - amazing,/. being useful after all:-)
Hey, since you know about these moka pots --- have you ever seen one of these http://www.pldaniels.com/mokapot.jpg ? (the moka pot, not the mug or the LCD panels;-)
It was sent to me from Italy along with some Segafredo vacuum packed grind.
While I sympathise with this fellows' plight, I think that he could have gone a little bit further to rewrite the letter in a 'diplomatic' language.
Using phrases like "disgusting bias" and "...who can afford disgustingly overpriced software... " do nothing for trying to get your message across. Additionally using FULL CAPS (even for one word) and other e-emphasis methods are not suggested. You simply come across as a screaming annoyance.
All that said, I hope he has success with his attempts. For myself, I'll resort to still using my accountant.
I have to say this is/one/ of the many reasons why I release my code under the BSD licence... there's plenty of people like yourself who are in a tight situation (legally) and need a toolkit/lib.
When people against the BSD licence shout tales of horror and evil when you release something under the BSD licence... is there something wrong with donating something and expecting nothing in return?
It's as if you've wretched a knife between their ribs by the very notion of giving away something for free, with no restrictions.
It's the software developers choice what they want to do with their code, not someone elses.
Slashdot Mirror
What would be -really- nice is LyX on windows that doesn't require running amok trying to install a handful of other packages.
Damn right --- I can remember one or two times I did things like that as a 5~8yo and the worst of it is that I still remember it :( I remember switching the price tags on a pair of fishing rods which was sort of stupid since I couldn't afford either of them *whoops*.
While the prize money isn't a lot, it might actually have an interesting effect in bringing about the less well funded but no less ingenious developers into the foray while the typical high ranking developers/companies pay less attention. It's certainly something I'd be interested in participating in (the aerial navigation).
Your 3x3 matrix didn't make sense to me at first until you mentioned how every other desktop is thus 1 desktop away, ingenious! Nice tip, now I have to work out how to make Fluxbox do that.
I noticed my DV cam is on the list, DCR-HC15E, the question is, what sort of deterioration should I be looking for? Maybe it's just me but I could swear that the quality of the video I get out of the unit these days appears less than what I originally was getting when I first bought it and that was /before/ I read about this story. Perhaps there's a way to accellerate the process of failure (if the weakness is there).
Incidently, living in a hot humid environment here too (North Eastern Australia)
It is heartbreaking to see our blood, sweat, and tears over the past 2 years blurred by the confusion and frustration surrounding this new technology. It is also unfortunate when bands such as ourselves, Foo Fighters, Coldplay, etc... (just a few of the new releases with copy protection) are the target of this criticism, when there is no possible way to avoid this new industry policy.
[Bolding mine]
Not sure about there being "no possible way" - perhaps when it comes time to renew their contract with Sony they'll consider going to alternative solutions. Worse comes to worse, perhaps they won't ever be able to escape Sony but they'll serve as a warning for others.
If the large corps keep on with this process it'll typically generate a new band of recording studios who don't and thus are seen as somewhat more friendly (though the cycle will probably still go on).
When I received the letter re Linux it quite honestly scared the daylights out of me. There was this letter that started out saying "this is a notice, not a letter of demand" but then it goes on talking about moderately large sums of money and potential legal fees.
/execute/ on linux too (so linux was listed as a "compatible OS".
What was doubly annoying though was that the letter appeared to be sent out without checking to see if the recipient was applicable. None of the services or products that I had on my WWW site used the word "linux" in them, they simply happen to be able to
I still consider the email to be bordering very close to spam.
Next time, a registered letter in the post after each site is checked for relevance would be a far more reputable manner of distribution.
I received the letter in /email/ as well - what bothers me is that none of my products or service have linux used in their names, /none/. I know that the various projects I have OpenSourced will run in linux but that's the extent of it.
The letter was sent out in the evening and quite honestly is immediately ranked as spam/scam in my eyes such to the point where I started hunting around for a way to contact Linus or a group representing Linus to inform him of this.
In the end I wrote back a simple email saying that we didn't use Linux in our product names (why limit ourselves to linux when there's so many other OS's too).
If the guy wanted to be taken seriously it should have been a mailout using the registered postal service.
Looks like this was really a bit of a fishing expedition to me.
It might balance out...
Some people download once and install on multiple machines.
Some people download multiple times on a single machine (different versions).
Quite right, the +/-1% was most likely incorrect. The source, I cannot recall. That's what I get for replying to /. before coffee.
..." hrmm, nope, can't think of anything to combine GWBush/Iraq/Microsoft/Intel/Apple/NataliePortman, better have another coffee.
After coffee I would have written something like "It'll be okay because the Iraq invasion and subsequent burnoffs along with
The combustion of materials for fire are rather sensitive to the percentage of oxygen in our atmosphere. Another +1% of O2 and we'd have a fireball raging, another -1% of O2 and things would not ignite in the free atmosphere. Subsequently if these microbes/algae get started with creating more O2 it'd simply be consumed by more fire.
A blue LED really helps show up those yellow dots. They'll come up looking like tiny specks of black pepper.
I recently had some manual covers printed out at OfficeWorks using their colour laser Xerox machine - sure enough the microdots were there.
I remember back in 1987 using smilies/emoticons on BBS. No doubt they were certainly used before then as I was showed them by a crusty old BBS admin.
Personally, I prefer daily backups to another HDD (use rsync, it's great), that way, if I make a major *oops* during the day I know I have a very recent backup immediately available, this is something that RAID cannot protect you from (the human failure).
s / is a great page to learn about using rsync to make easy backups.
If then I've still got money to spare, I'll look at mirroring.
http://www.mikerubel.org/computers/rsync_snapshot
We just dumped access via password, forced everyone to work using RSA keys, at the very least, it certainly actually makes people's jobs easier since now they can login without a password if they want :-)
Hey, was I the only one who thought the /human/ in the video was cute? Does that mean I'm not able to be a true /. person (oh Good!).
While having more surface area for larger caches or what ever is a wonderful thing, where this stacking concept can really help out is helping with clock sync issues.
Now that we're pushing into the GHz speeds on chips it is getting rather difficult to keep the whole chip in sync across the distances that the signal has to travel. By stacking the various segments of the chip you've eliminated another obstical for higher clockspeeds.
This one is a Bialetti system (it pressures up then pops, rather than the continuous feed) but is just branded by Segafredo.
Oh well, it works well (though the first time you use it it scares you a little) and makes some fine coffee.
Thanks.
Absolutely agreed on your points - there is one situation where a small binary patch does become useful, where it's a legacy system which simply cannot be swapped out for the 'latest version', non of us like those situations but they do exist :-(
/. being useful after all :-)
Thanks for the pointers - amazing,
I wonder if it'd be possible to create a binary patch for prebuilt binaries ?
Anyone got some suggestions?
Hey, since you know about these moka pots --- have you ever seen one of these http://www.pldaniels.com/mokapot.jpg ? (the moka pot, not the mug or the LCD panels ;-)
It was sent to me from Italy along with some Segafredo vacuum packed grind.
While I sympathise with this fellows' plight, I think that he could have gone a little bit further to rewrite the letter in a 'diplomatic' language.
...who can afford disgustingly overpriced software... " do nothing for trying to get your message across. Additionally using FULL CAPS (even for one word) and other e-emphasis methods are not suggested. You simply come across as a screaming annoyance.
Using phrases like "disgusting bias" and "
All that said, I hope he has success with his attempts. For myself, I'll resort to still using my accountant.
I have to say this is /one/ of the many reasons why I release my code under the BSD licence... there's plenty of people like yourself who are in a tight situation (legally) and need a toolkit/lib.
:-)
Who knows, maybe you've even used one of mine
When people against the BSD licence shout tales of horror and evil when you release something under the BSD licence... is there something wrong with donating something and expecting nothing in return?
It's as if you've wretched a knife between their ribs by the very notion of giving away something for free, with no restrictions.
It's the software developers choice what they want to do with their code, not someone elses.
If people feel that choosing the BSD licence "bit them on the arse" then they chose the wrong licence to start with.
You don't put your code out under the BSD licence with the hidden hope that someone will raise you up on their shoulders via their wealth.
People shouldn't complain about licences when it was their own choice initially.
If you're seeking an alterior motive when putting code out under a BSD licence then you deserve to bit "bitten in the arse".