Sun just leaked yet another ground-breaking technology news : sexed servers. They choosed a female one, because they are so much caring for their users request.
But maybe it's PMS time now. Just imagine a bunch of sysadmin trying to convince the managment that boxes of tampaxes are _mandatory_ to run their web server.
Next dowtime : headaches and baby blues.
(I'still hesitating between flamebait/funny myself)
I recommended for the boycott before, partly because I tought that those RIAA/SDMI guys had some secret weapon. But I went on and read about the SDMI organisation, and I do think everybody on the "fair use/ free beer" side can get some rest for some more nights.
No time to go back an re-read my sources, but the SDMI seems to be run by some dictatorial guru, that drags a lot of unwilling industry leaders behind, and especially the hardware manufacturers.
Look at the salon article : lot of the SDMI people probably learned about the cracking like you and me : in that very article. Because the real SDMI zealots are trying to hide the facts. I'm pretty sure more that one has it's job on stake in that issue : that might be the end of SDMI by implosion, or worse, because the SDMI member wants its end !!!
Just to put matter in perspective : no need to be too paranoid there.
The principle behind this meta-patent, also known as recursive patenting, is to patent the patenting process itself.
We want to patent the following idea :
- someone find an "genuine" original idea/process/device/ice cream
- to prevent it to be stolen by someone else, the aforementionned person goes to the patent office, and protects its ideas through the mean of a patent, obtained by a suitable process.
This is also known as patenting, but what's original there is that nobody ever though to patent the patent process itself.
That's what we want to do !
Surprising that nobody thought of it before, since :
- every former patent submission is going to be included, and superceded by this meta-patent
- every next patent submission is going to go through the process patented in this patent, thus invalidated thereafter : this is the ultimate patent !
- since it's recursive nature, it's a patent on itself, and thus protected from every attempt to do something more original.
After this patent is validated (and it will be !), I'll have the power to sue god himself for patent infringment, thus insuring me a steady source of revenue from the (20 ?) next years to come.
I liked that book : the end a bit sad, but I never forgot it.
Hint to (too young) moderators : like in "Grape of wrath", this book deals with "slower" people and mices... and more stuff... So mod this mouse up, and let's keep on reading.
"Flowers for Algernon" by Daniel Keyes.
Published by Harcourt Brace (1966) and by Bantam Books (1967). Reissued in the Harcourt Brace Modern Classics series (1995).
But enough of that mod rants : I read their article, and really like the way they wants people to attack the problem. Too often in the past, neural networks have been treated as "black
boxes, mainly because of lack of mathematical fundations". I specially liked the way they stated it : "the novel essential principles of operation can be deduced based on the experimental results presented here alone. "
I'm planning to read everything tonight (@work now:-() Any./ reader to use that forum to share ideas instead of trying to break the moderation system into pieces ???
Well, we're using Solaris at work, and placing swap and/tmp in the same memory bucket has another interesting "side-effect".
Another rule of the game is : when memory-pigs applications are running, and swap grows too much, the/tmp shrinks accordingly.
Here, we are using an operating system simulator which was designed like a fortran-77 app. That is, at startup, reserve as much memory you think you need (commonly around 100/200M), and then works with it (or die). When a sufficient number of those apps is running (around 5-7), even our 1G-memory entreprise servers began to stumble under the load.
Needless to say, when swap grows up to the point of crushing/tmp in the memory bucket, you've got a file system full on/tmp...
Remember the ol'unix/tmp definition :
/tmp is the place (filesystem) where any file that won't be needed next reboot should be placed, but _EVERYBODY_ should be able at least to write and read there.
It's funny how you re-discover the importance of this rule by noticing how many mundane tool need/tmp for writing. And indeed refuse to move when/tmp is full...
So my.5 cents to whoever will design such a mechanism in (free)*(*n*x). This mechanism really speeds things up, but on the other hand, PLEASE MAKE SURE THAT :
- either your system does not vitally needs/tmp any more
- or/tmp will remain sufficiently large for your system to keep running, whatever the conditions.
Obviously, this is only needed when you run memory-hungry applications. But obviously indeed us modern designer are very carefull not to use to much memory;-)
Any news from the site : because here it is 09:13, Sept 15 (Us&Canadian eastern time), and nothing worth the trouble is showing on http://www.hacksdmi.org/. And like someone pointed out, they have a like to their site into their own site that will create an interesting Escher-like "Recursive Frame stack fault" into you Browser.
As for the boycott : they are clearly trying to avoid a DECSS-like failure.
Maybe they have the same level of confidence for their crypto technical than for their www one ?
This shows that DECSS teached some lessons.
But like usual, thos BIG-CORPORATE-FAT--ETC guys understood the teaching the wrong way, because if their "new" system is not cracked it three weeks, it's going to be cracked in four, five... until the sun blows. And even if the crack is declared illegal their will be a part of the world whete someone will sell it, and the bootleging-vox populi will do the rest.
For every better lock, there will be a better thief ! Hey guys, instead of focusing on the lock, please look at the door design.
On the other hand, like every #$$^#@#$ marketing guys, they gave the delays, blissly disregarding the rules of the game. And like usual the requirements seems to be late.
Bu I will advise for the boycott, because their goal is not clear. Apparently they are going to put a bunch of differents technologies under public scrunity. They seemed to learn at that principle of free software : the most testers you have, the better the product. But testing FOR them will be against our interests. Let them test, and if they cannot get people competent enough to point the flaws in their systems, it means they did not deserve that.
Sorry guys, that must be the weather, but this sorry is sad, very sad. You said that this hopefully not your money. But this is our planet. Assembling all those _VERY_ expensive pieces of hardware and putting them in place involved a huge amount of money, but a huger amount of ressources, from mens to ore. Those 5-6 billions of dollars are only the tip of the iceberg of a huge waste. And no, wasting anything ain't no fun.
There must be a way to reuse all that !
Moreover, since all those people have been so marvelous at planning I just hope that someone else, i.e. _REAL_ experts will be assigned the tasks of getting all that hardware down _PROPERLY_, without doing more harm.
And no, I'm no green-freak;-(. But I have childrens.
Once, when I was young, some hackers of this time tried to translate the "BASIC" language keywords into some french equivalent... And got a very shallow succes, not to say they failed miserably.
That guy (or team) is probably still laughed at.
I did not say it was not working. I just said that, around 20 years ago, a lot of people tried it and let it rust in some corner.
At that time, I did not know english very well, but I clearly found the french-translated basic syntax very clumsy.
This may be caused to the fact that english tend to be more concise (but maybe less accurate, no flame please) than french. I'm not sure.
Slashdot Mirror
Maybe an explanation :
Look closeley at the displayed message :
"(...) hits.
We ask your patience while our best people are reconfiguring the server and bringing her back up
(...)"
Yes, look closely : nothing strikes you ?!?!
Zoom->in : "bringing _HER_ back"
Sun just leaked yet another ground-breaking technology news : sexed servers. They choosed a female one, because they are so much caring for their users request.
But maybe it's PMS time now. Just imagine a bunch of sysadmin trying to convince the managment that boxes of tampaxes are _mandatory_ to run their web server.
Next dowtime : headaches and baby blues.
(I'still hesitating between flamebait/funny myself)
I recommended for the boycott before, partly because I tought that those RIAA/SDMI guys had some secret weapon. But I went on and read about the SDMI organisation, and I do think everybody on the "fair use/ free beer" side can get some rest for some more nights.
No time to go back an re-read my sources, but the SDMI seems to be run by some dictatorial guru, that drags a lot of unwilling industry leaders behind, and especially the hardware manufacturers.
Look at the salon article : lot of the SDMI people probably learned about the cracking like you and me : in that very article. Because the real SDMI zealots are trying to hide the facts. I'm pretty sure more that one has it's job on stake in that issue : that might be the end of SDMI by implosion, or worse, because the SDMI member wants its end !!!
Just to put matter in perspective : no need to be too paranoid there.
The principle behind this meta-patent, also known as recursive patenting, is to patent the patenting process itself.
We want to patent the following idea :
- someone find an "genuine" original idea/process/device/ice cream
- to prevent it to be stolen by someone else, the aforementionned person goes to the patent office, and protects its ideas through the mean of a patent, obtained by a suitable process.
This is also known as patenting, but what's original there is that nobody ever though to patent the patent process itself.
That's what we want to do !
Surprising that nobody thought of it before, since :
- every former patent submission is going to be included, and superceded by this meta-patent
- every next patent submission is going to go through the process patented in this patent, thus invalidated thereafter : this is the ultimate patent !
- since it's recursive nature, it's a patent on itself, and thus protected from every attempt to do something more original.
After this patent is validated (and it will be !), I'll have the power to sue god himself for patent infringment, thus insuring me a steady source of revenue from the (20 ?) next years to come.
I liked that book : the end a bit sad, but I never forgot it.
:-() Any ./ reader to use that forum to share ideas instead of trying to break the moderation system into pieces ???
Hint to (too young) moderators : like in "Grape of wrath", this book deals with "slower" people and mices... and more stuff... So mod this mouse up, and let's keep on reading.
"Flowers for Algernon" by Daniel Keyes.
Published by Harcourt Brace (1966) and by Bantam Books (1967). Reissued in the Harcourt Brace Modern Classics series (1995).
But enough of that mod rants : I read their article, and really like the way they wants people to attack the problem. Too often in the past, neural networks have been treated as "black
boxes, mainly because of lack of mathematical fundations". I specially liked the way they stated it : "the novel essential principles of operation can be deduced based on the experimental results presented here alone. "
I'm planning to read everything tonight (@work now
Well, we're using Solaris at work, and placing swap and /tmp in the same memory bucket has another interesting "side-effect".
/tmp shrinks accordingly.
/tmp in the memory bucket, you've got a file system full on /tmp...
/tmp definition :
/tmp for writing. And indeed refuse to move when /tmp is full...
.5 cents to whoever will design such a mechanism in (free)*(*n*x). This mechanism really speeds things up, but on the other hand, PLEASE MAKE SURE THAT :
/tmp any more
/tmp will remain sufficiently large for your system to keep running, whatever the conditions.
;-)
Another rule of the game is : when memory-pigs applications are running, and swap grows too much, the
Here, we are using an operating system simulator which was designed like a fortran-77 app. That is, at startup, reserve as much memory you think you need (commonly around 100/200M), and then works with it (or die). When a sufficient number of those apps is running (around 5-7), even our 1G-memory entreprise servers began to stumble under the load.
Needless to say, when swap grows up to the point of crushing
Remember the ol'unix
/tmp is the place (filesystem) where any file that won't be needed next reboot should be placed, but _EVERYBODY_ should be able at least to write and read there.
It's funny how you re-discover the importance of this rule by noticing how many mundane tool need
So my
- either your system does not vitally needs
- or
Obviously, this is only needed when you run memory-hungry applications. But obviously indeed us modern designer are very carefull not to use to much memory
Any news from the site : because here it is 09:13, Sept 15 (Us&Canadian eastern time), and nothing worth the trouble is showing on http://www.hacksdmi.org/. And like someone pointed out, they have a like to their site into their own site that will create an interesting Escher-like "Recursive Frame stack fault" into you Browser.
As for the boycott : they are clearly trying to avoid a DECSS-like failure.
Maybe they have the same level of confidence for their crypto technical than for their www one ?
This shows that DECSS teached some lessons.
But like usual, thos BIG-CORPORATE-FAT--ETC guys understood the teaching the wrong way, because if their "new" system is not cracked it three weeks, it's going to be cracked in four, five... until the sun blows. And even if the crack is declared illegal their will be a part of the world whete someone will sell it, and the bootleging-vox populi will do the rest.
For every better lock, there will be a better thief ! Hey guys, instead of focusing on the lock, please look at the door design.
On the other hand, like every #$$^#@#$ marketing guys, they gave the delays, blissly disregarding the rules of the game. And like usual the requirements seems to be late.
Bu I will advise for the boycott, because their goal is not clear. Apparently they are going to put a bunch of differents technologies under public scrunity. They seemed to learn at that principle of free software : the most testers you have, the better the product. But testing FOR them will be against our interests. Let them test, and if they cannot get people competent enough to point the flaws in their systems, it means they did not deserve that.
Sorry guys, that must be the weather, but this sorry is sad, very sad. You said that this hopefully not your money. But this is our planet. Assembling all those _VERY_ expensive pieces of hardware and putting them in place involved a huge amount of money, but a huger amount of ressources, from mens to ore. Those 5-6 billions of dollars are only the tip of the iceberg of a huge waste. And no, wasting anything ain't no fun. ;-(. But I have childrens.
There must be a way to reuse all that !
Moreover, since all those people have been so marvelous at planning I just hope that someone else, i.e. _REAL_ experts will be assigned the tasks of getting all that hardware down _PROPERLY_, without doing more harm.
And no, I'm no green-freak
Point of view from a native french speaker.
.2 ecus.
Once, when I was young, some hackers of this time tried to translate the "BASIC" language keywords into some french equivalent... And got a very shallow succes, not to say they failed miserably.
That guy (or team) is probably still laughed at.
I did not say it was not working. I just said that, around 20 years ago, a lot of people tried it and let it rust in some corner.
At that time, I did not know english very well, but I clearly found the french-translated basic syntax very clumsy.
This may be caused to the fact that english tend to be more concise (but maybe less accurate, no flame please) than french. I'm not sure.
my