For other readers of this thread, I will now present Sam's amazing guide to having reliable hard disks.
1. Secure the drive with four screws, two on each side. 2. Ensure your drives are adequatly cooled. 3. Install SMART monitoring software, and obey the following mantra.
When the software says the drive is too old, replace it. When the software says the drive is about to fail, swap it out and RMA it[0]. When the software predicts a failure in the future, plan[1] to replace it.
[0] If you don't have a replacement ready then run, don't walk, to the hardware store to buy one.
[1] The size of your margin of safety should be proportional to the value of the data on the drive, and quality of your backups.
Can you provide any figures of relative failure rates between different manufacturers/model numbers of hard drives? My understanding was that, excepting certain infamous models (120 GXP "Death Star") made by IBM/Hitachi, all consumer-level hard drives have the same, small, failure rate.
Since January 1st 2005 (I think), shops that accept signatures are held liable for fraudulant transactions by the card issuers, so there is an incentive for shops to move over to the new system.
Or read the lkml archives. Linus chose bitkeeper precisely because all the alternatives you mention don't cut it.
To be fair, at the time Linus moved to BK they didn't cut it. Everyone still used CVS; Subversion was still under development; I don't think Darcs, SVK or any of the implementations of Arch even existed yet.
The first element of argv is the name of the program that is being run. If you bothered to run your code in the interpreter, you'd have noticed that...
If the author wishes people to read his article, he should consider publishing it in a colour scheme that is easier to read than dark grey on garker grey.
One more thing: we don't know what country you are in, so all this advice may not apply to you anyway. Also I doubt many of Slashdot's readership are IP lawyers. If you want real advice, you must talk to a solicitor.
Whoops, I should clarify this: I'm talking about the code you created your derived work from in the first place. The code you wrote yourself, is owned by your employer, and they can do anything they want with it. However they are not free to do anything with the code they don't own, and derivative works thereof (this includes a work comprising the original code + your modifications).
The software in question is "owned" by the copyright holders (presumably ActieState and IBM). Therefore, your company's claims of ownership on the code are bogus, and any use it makes of the code must comply with the licensing terms that the code was obtained under (the GPL).
If you didn't care about your job, you would contact the copyright holders and inform them of what's going on--it is up to them to sue your employer, if they find that your employer is in breech of the license.
As for the patent: if it's not been patented already, then it's fair game. Get used to it.
The moral of the story: verbal agreements are meaningless. Get it in writing, or don't bother.
The backwards spinning myth has been applied to the Gamecube, PS2, Dreamcast, PSX... and water going down a plughole in the southern hemisphere. I think it'll be with us for a long time yet...;)
I'm taking some flack for this. Obviously being in one of the older TLDs like.net and.org is not a seal of approval. It doesn't give me any reason to bestow trust on a site. But being in.biz or.info increases a site's score in my internal bullshit filter. It makes me more suspicious of that site.
Part of it is because I think these extra domains are a pointless pollution of the DNS namespace. Part of it is because IME, these domains are mostly inhabited by peddlars of penis extensions, fake Rolex watches and generic Viagra.
Slashdot Mirror
Precicely! Someone who gets it. :)
For other readers of this thread, I will now present Sam's amazing guide to having reliable hard disks.
1. Secure the drive with four screws, two on each side.
2. Ensure your drives are adequatly cooled.
3. Install SMART monitoring software, and obey the following mantra.
When the software says the drive is too old, replace it. When the software says the drive is about to fail, swap it out and RMA it[0]. When the software predicts a failure in the future, plan[1] to replace it.
[0] If you don't have a replacement ready then run, don't walk, to the hardware store to buy one.
[1] The size of your margin of safety should be proportional to the value of the data on the drive, and quality of your backups.
Can you provide any figures of relative failure rates between different manufacturers/model numbers of hard drives? My understanding was that, excepting certain infamous models (120 GXP "Death Star") made by IBM/Hitachi, all consumer-level hard drives have the same, small, failure rate.
Since January 1st 2005 (I think), shops that accept signatures are held liable for fraudulant transactions by the card issuers, so there is an incentive for shops to move over to the new system.
/me chuckles
Or even (:tagname data)?
Get this man a copy of Practical Common Lisp!
Perhaps you should ask developers of distributions concerned?
To be fair, at the time Linus moved to BK they didn't cut it. Everyone still used CVS; Subversion was still under development; I don't think Darcs, SVK or any of the implementations of Arch even existed yet.
No dice.
Confused...
Are they just trying to keep the version numbers of Firefox and Thunderbird in lockstep?
Then they will blame falling sales on piracy...
Shades of http://bash.org/?142934? :)
No honour amongst thieves, eh? ;)
The first element of argv is the name of the program that is being run. If you bothered to run your code in the interpreter, you'd have noticed that...
What is with the "right to use your voice and likeness for any purpose"?
:)
Are they planning to hack in to your bank account?
Aren't there test suites that test the conformance of an implementation to all aspects of CSS2 standard already? And if not, why not?
If the author wishes people to read his article, he should consider publishing it in a colour scheme that is easier to read than dark grey on garker grey.
One more thing: we don't know what country you are in, so all this advice may not apply to you anyway. Also I doubt many of Slashdot's readership are IP lawyers. If you want real advice, you must talk to a solicitor.
Whoops, I should clarify this: I'm talking about the code you created your derived work from in the first place. The code you wrote yourself, is owned by your employer, and they can do anything they want with it. However they are not free to do anything with the code they don't own, and derivative works thereof (this includes a work comprising the original code + your modifications).
The software in question is "owned" by the copyright holders (presumably ActieState and IBM). Therefore, your company's claims of ownership on the code are bogus, and any use it makes of the code must comply with the licensing terms that the code was obtained under (the GPL).
If you didn't care about your job, you would contact the copyright holders and inform them of what's going on--it is up to them to sue your employer, if they find that your employer is in breech of the license.
As for the patent: if it's not been patented already, then it's fair game. Get used to it.
The moral of the story: verbal agreements are meaningless. Get it in writing, or don't bother.
The backwards spinning myth has been applied to the Gamecube, PS2, Dreamcast, PSX... and water going down a plughole in the southern hemisphere. I think it'll be with us for a long time yet... ;)
Sorry about that. It's been hard to see past all the bullshit posted in this forum lately. :)
I'm taking some flack for this. Obviously being in one of the older TLDs like .net and .org is not a seal of approval. It doesn't give me any reason to bestow trust on a site. But being in .biz or .info increases a site's score in my internal bullshit filter. It makes me more suspicious of that site.
Part of it is because I think these extra domains are a pointless pollution of the DNS namespace. Part of it is because IME, these domains are mostly inhabited by peddlars of penis extensions, fake Rolex watches and generic Viagra.
> The remix (somehow) makes money, but the actor doesn't get paid for appearing in
> what is bascially a 'new' work.
OH NOES! THE SKY SI FALLING!?
Why is it not up to the actor concerned, as to whether they want to participate in such a work?
Transposition type. I hope you are just being obtuse!
The law requires the permission of the copyright holder to use (as in, make a derivative work from) the code. The license grants the permission.