2.4 will give you a more stable kernel due to being tested better. I am still sticking with 2.4 on my servers, but just because I'm lazy.:)
I've been running 2.6 on all desktop & laptop systems without problems since 2.6.9 (about a year). I certainly would not want to give up the better interactivity, better MM performance, wide hardware support, and features like udev.
2.6.x will have have hickups now and again because that is where the development occurs. That's why a few kernel hackers (Chris Wright & Greg Kroah-Hartman) started maintaining stable point releases (2.6.12.1, 2.6.12.2, etc) to deal with bug fixes only. If you are concerned about stability on 2.6 you can use these releases. You can get them here: http://kernel.org/pub/linux/kernel/v2.6/
bug 211205, which deals with this expoit, was resolved in 2h after the announcement. I had my box patched 15min after the slashdot story hit.
Really good stuff.
"audio ads that cannot be turned off"
on
Prince of Pop-ups
·
· Score: 1
... and with the M$ trusted platform, the speakers will be part of the motherboard and the case locked so that they can only be turned off by by M$. You will get thrown in jail if you tamper with your protective crypto or the hardware.
The funny thing is, that if AMD even wanted to stop people from overclocking using this patented technology, they would have to pay royalties to Intel. So as a result AMD will probably not follow that route and the consummer wins!
When a mail arrives that I have a key for, and one that I have signed, my procmail accepts the mail as legit. It goes into my INBOX.
When a mail arrives that I have a blacklisted key for, my procmail will ditch it.
When a mail arrives that I don't have a key for, I will reply back to the sender, and put the original message on a wait-queue. My auto-generated message will ask them to simply reply to my message (keeping the my message in the reply). This validates that they exist. When I get back their reply I can validate the key and the reply, if it all passes the promail script will push forward the message from the wait-queue into my INBOX.
If at some point I start getting messages in my INBOX from a spammer that wrote a counter script to my testing method, I simly blackmail the key.
Anyway, the spammer will not do this because for them to sign a message back to me means that they have a lot of computing power... we currently have a problem with spam because there is no cost on spam. This approach would reduce spam sending say 1/s.
While I do think the work presented is a great idea, it seems to me that it's a lot of effort just to setup the system.
It would be ideal if the computer -- the thing that is supposed to make life easier -- did the clasification. Until that happens I cannot see myself even considering such a file access method.
Re:Forget about 3G! Take a look at SOMA Networks.
on
America's First WCDMA Call
·
· Score: 5, Informative
Here is the NTT (the telco doing trials of SOMA technology in Japan) tiral page: www.winq-kanazawa.net. But it's not much good if you don't read Japanese -- it does have a pretty picture of the client hardware.
So if slashdot wanted to be malicious... it could just put in a prefetch tag into their front page and everyone that visits it is automatically forced to prefetch the 5M file of some competing service:)
Slashdot Mirror
The only thing that the x300 is missing is DVI out.
A really great way to optimize your SCM is to upgrade to git.
maybe the US schools can teach the metric system right after evolution class, and showing the Gore climate change documentary.
Your uptime should never be greater then the time since the last git snapshot release :)
2.4 will give you a more stable kernel due to being tested better. I am still sticking with 2.4 on my servers, but just because I'm lazy. :)
I've been running 2.6 on all desktop & laptop systems without problems since 2.6.9 (about a year). I certainly would not want to give up the better interactivity, better MM performance, wide hardware support, and features like udev.
2.6.x will have have hickups now and again because that is where the development occurs. That's why a few kernel hackers (Chris Wright & Greg Kroah-Hartman) started maintaining stable point releases (2.6.12.1, 2.6.12.2, etc) to deal with bug fixes only. If you are concerned about stability on 2.6 you can use these releases. You can get them here: http://kernel.org/pub/linux/kernel/v2.6/
If someone told me this, I would have thought that things like RPC and CORBA were teh ones at risk.
Would things like RPC be in danger? Would things like RPC provide prior art?
I am in the same boat. But I am guessing that if the mozilla libs that Gaelon uses are fixed, your Galeon is ok.
a torent would be nice...
The price buged me too.
I went to my local retailer's website and was able to put together the same system* for $3261.
(*) I am not sure if it's ideantical since the articles does not specify what motherboard, case, power-supply, are used.
actually it's patched, and has been since ~ 11:00 EST. you're supposed to have security.d.o in your sources.list if you want security fixes.
yes it does. I looked over the debdiff... but why would you trust me. check for yourself.
probably because the DSA was not drafted yet.
but the packages are in the security deb pool, and more importantly available through apt.
openssh_3.4p1-1.1 is the one you want. Check the patch... openssh_3.4p1-1.1.diff.gz
Debian is absolutely amazing.
bug 211205, which deals with this expoit, was resolved in 2h after the announcement. I had my box patched 15min after the slashdot story hit.
Really good stuff.
... and with the M$ trusted platform, the speakers will be part of the motherboard and the case locked so that they can only be turned off by by M$. You will get thrown in jail if you tamper with your protective crypto or the hardware.
and that would be bad.
The funny thing is, that if AMD even wanted to stop people from overclocking using this patented technology, they would have to pay royalties to Intel. So as a result AMD will probably not follow that route and the consummer wins!
AMD+Linux=Good in deed.
... and I apparently don't know how to spell `expecting'.
Definately did.
:)
I was especting to see a "ClearCase is a registered trademark...." disclaimer.
Here is my solution to this.
When a mail arrives that I have a key for, and one that I have signed, my procmail accepts the mail as legit. It goes into my INBOX.
When a mail arrives that I have a blacklisted key for, my procmail will ditch it.
When a mail arrives that I don't have a key for, I will reply back to the sender, and put the original message on a wait-queue. My auto-generated message will ask them to simply reply to my message (keeping the my message in the reply). This validates that they exist. When I get back their reply I can validate the key and the reply, if it all passes the promail script will push forward the message from the wait-queue into my INBOX.
If at some point I start getting messages in my INBOX from a spammer that wrote a counter script to my testing method, I simly blackmail the key.
Anyway, the spammer will not do this because for them to sign a message back to me means that they have a lot of computing power... we currently have a problem with spam because there is no cost on spam. This approach would reduce spam sending say 1/s.
my 0.2c
Really, the only way to combat this kind of identiy fraud is with PGP. It would be ideal if every mail-program out there supported PGP.
As 10^100 other people will tell you this is not new. I've been seeing this for at least 3 years on my University account.
While I do think the work presented is a great idea, it seems to me that it's a lot of effort just to setup the system.
It would be ideal if the computer -- the thing that is supposed to make life easier -- did the clasification. Until that happens I cannot see myself even considering such a file access method.
Here is the NTT (the telco doing trials of SOMA technology in Japan) tiral page: www.winq-kanazawa.net. But it's not much good if you don't read Japanese -- it does have a pretty picture of the client hardware.
So if slashdot wanted to be malicious... it could just put in a prefetch tag into their front page and everyone that visits it is automatically forced to prefetch the 5M file of some competing service :)
Bringing a new meaning to being slashdoted.