For one, FAM had to be disabled until SELinux was shut off by default, because it interfered with SELinux too much. So Nautilus didn't update when a directory changed. Apparently RedHat are working on a "long-term solution" -- anyone know what?
Asus is slow to release fixes to things like this (I had a problem with the K7M266 mobo, with the VIA 686b southbridge that corrupted disks with the 2.4 kernel. It took ASUS longer than any other major mobo manufacturer to release a fix. But they did eventually).
Nobody will sell me a brand laptop (Dell, Sony, etc.) without Windows on it. I don't want Windows on it. I never plan on using it. I am forced to buy something I ethically don't want to, to get something I need. I don't want to be forced to pay the MS tax.
Isn't this anticompetitiveness? Why is nobody picking this up as an antitrust case?
Isaiah 13: 19 And Babylon, the glory of kingdoms, the beauty of the Chaldees' excellency, shall be as when God overthrew Sodom and Gomorrah. 20 It shall never be inhabited, neither shall it be dwelt in from generation to generation: neither shall the Arabian pitch tent there; neither shall the shepherds make their fold there. 21 But wild beasts of the desert shall lie there; and their houses shall be full of doleful creatures; and owls shall dwell there, and satyrs shall dance there. 22 And the wild beasts of the islands shall cry in their desolate houses, and dragons in their pleasant palaces: and her time is near to come, and her days shall not be prolonged.
From the 2.6.3 Changelog:
[NETFILTER]: Fix signedness overflow in ip{,6}_tables.c
Bug discovered by Olaf Kirch.
M$ Wouldn't have had the recent embarrassment about a certain BMP import filter if its code was opened earlier. (It was the same type of bug that was exploited...)
While AMD definitely did the right thing, and the Athlon64/Opteron is definitely the best solution for now, I hope the x86 architecture dies a permanent death soon.
What we need is a 64-bit ARM ISA. The ARM2/3 (the first 32-bit desktop processors) had 36,000 transistors, a 3-stage pipeline, and were faster than 386 processors clocked 3x higher. Every instruction gets a 4-bit condition field, removing many branch instructions from the program. Parameters can be shifted transparently, with no additional overhead. Lots of useful addressing modes, and lots of general-purpose registers. Definitely the only ISA I can say it is actually a pleasure to write code for.
Unfortunately Intel seems to be sitting on the XScale (ARM successor), and doing nothing much with it. I hope AMD picks up the "KISS" philosophy of the ARM -- with it, they could produce a bliningly fast processor with very little work.
In Korean, there isn't a sound halfway between "r" and "l" -- they have both sounds -- but context affects which sound you use. So Koreans are prone to say the wrong letter because of surrounding context.
e.g. "n"+"r" => "l"+"l", so "Han River" => "Hal-Liver"
Somebody needs to start lobbying IBM to put a team of, say, 30-50 programmers to work full-time on GNOME/KDE, and particularly on interoperability and common infrastructure. IBM (perhaps more suited to this than the others in OSDL?) has the resources, and it's in their best interests if they are going to be pushing Linux as a desktop replacement soon. They could work on fixing all the bugs (like the 700+ for Nautilus in Bugzilla), interoperability with other DEs (freedesktop.org), efficiency, integration, getting things to "just work", polish, and other features like lock-down for GNOME, and other features that will require OS work, like HAL, "real" plug-n-play, soft-mounted FSs (so you can just pull out a floppy, like on Windows, and not risk trashing it), proper laptop support etc. that people have wanted for a while.
Desktop GNU/Linux needs something like that to ultimately survive -- it has to keep improving or it will stagnate. IBM and others already pay programmers to work on Free/OSS, but we need a good group of fulltime desktop engineers. IBM needs them too, if it is going to roll out 30k Linux desktops internally in the next year. The other companies also need to invest in their future.
About a month ago Google also started redirecting every URL on its search pages through its own site, so they know what you actually click on in the search results too.
Did they compare temperature changes in the cities to temperature changes in areas of low population? If not, their results are meaningless, or at least the conclusion they draw is meaningless.
This is another example of mixing up association with causation.
I'm looking for a VoIP system that registers to a server and works over a firewall, between Linux and Windows (i.e. not GnomeMeeting / NetMeeting, because you have to open pinholes for that). The s/w then has to register with a server somewhere. I need it to work on both OSs. Free/free is best. Any ideas?
I almost wish SCO would sue me as an end-user. Because then it would be in my rights for me to know every detail of their claims against me -- i.e. I would be able to demand that they show me every piece of infringing source code. Then I would show the rest of the world:-)
Of course that would never happen -- they would refuse to show me -- and besides, they can't find me anyway...
Why doesn't someone just make a third version of the worm that installs the patch after it infects a machine, so that everyone's machines get fixed automatically?
I'm glad someone caught this. He makes this mistake in virtually every "conclusion" that he draws. This is bad science. It is the equivalent of, "You have the same comments in your source code as we do. Therefore you copied your source code from us.":o)
Also, maybe those who are more likely to commit crimes just don't get married... And comparing criminals to scientists just doesn't make sense...
Certainly, there are a very many benefits to marriage. It seems that this researcher is trying to discredit marriage by drawing "conclusions" that are statistically and logically invalid.
Re-stated: Being married usually implies something about your age. Losing productivity usually implies something about your age.
You should know that (X => Y) does NOT mean that (Y => X). In this case, ((marriage => old) AND (non-performer => old)) does NOT imply that (marriage => non-performer)...!
You're only believing what you want to believe.
The fact that people both (a) typically lose productivity around or near their early 30s, and (b) typically get married around or near their early 30s, does NOT imply that (a) causes (b), or that (b) causes (a). All it means is that being in your early 30s is somehow related to both (a) and (b); maybe your age is actually the cause of both, and neither (a) nor (b) is actually directly correlated with one another.
The author (or maybe the reporter) made more basic statistical blunders (surrounding causation) in those statements than I have seen in a long time.
Slashdot Mirror
For one, FAM had to be disabled until SELinux was shut off by default, because it interfered with SELinux too much. So Nautilus didn't update when a directory changed. Apparently RedHat are working on a "long-term solution" -- anyone know what?
Note that IBM won't hire Ph.D.s, in general. They cost too much (an IBM guy told me that).
Asus is slow to release fixes to things like this (I had a problem with the K7M266 mobo, with the VIA 686b southbridge that corrupted disks with the 2.4 kernel. It took ASUS longer than any other major mobo manufacturer to release a fix. But they did eventually).
Nobody will sell me a brand laptop (Dell, Sony, etc.) without Windows on it. I don't want Windows on it. I never plan on using it. I am forced to buy something I ethically don't want to, to get something I need. I don't want to be forced to pay the MS tax.
Isn't this anticompetitiveness? Why is nobody picking this up as an antitrust case?
Isaiah 13:
19 And Babylon, the glory of kingdoms, the beauty of the Chaldees' excellency, shall be as when God overthrew Sodom and Gomorrah.
20 It shall never be inhabited, neither shall it be dwelt in from generation to generation: neither shall the Arabian pitch tent there; neither shall the shepherds make their fold there.
21 But wild beasts of the desert shall lie there; and their houses shall be full of doleful creatures; and owls shall dwell there, and satyrs shall dance there.
22 And the wild beasts of the islands shall cry in their desolate houses, and dragons in their pleasant palaces: and her time is near to come, and her days shall not be prolonged.
From the 2.6.3 Changelog: [NETFILTER]: Fix signedness overflow in ip{,6}_tables.c Bug discovered by Olaf Kirch. M$ Wouldn't have had the recent embarrassment about a certain BMP import filter if its code was opened earlier. (It was the same type of bug that was exploited...)
While AMD definitely did the right thing, and the Athlon64/Opteron is definitely the best solution for now, I hope the x86 architecture dies a permanent death soon. What we need is a 64-bit ARM ISA. The ARM2/3 (the first 32-bit desktop processors) had 36,000 transistors, a 3-stage pipeline, and were faster than 386 processors clocked 3x higher. Every instruction gets a 4-bit condition field, removing many branch instructions from the program. Parameters can be shifted transparently, with no additional overhead. Lots of useful addressing modes, and lots of general-purpose registers. Definitely the only ISA I can say it is actually a pleasure to write code for. Unfortunately Intel seems to be sitting on the XScale (ARM successor), and doing nothing much with it. I hope AMD picks up the "KISS" philosophy of the ARM -- with it, they could produce a bliningly fast processor with very little work.
In Korean, there isn't a sound halfway between "r" and "l" -- they have both sounds -- but context affects which sound you use. So Koreans are prone to say the wrong letter because of surrounding context. e.g. "n"+"r" => "l"+"l", so "Han River" => "Hal-Liver"
And in a related story, slashdot started filtering out posts that have "MOD PARENT UP!!!!!!!" in the title.
Desktop GNU/Linux needs something like that to ultimately survive -- it has to keep improving or it will stagnate. IBM and others already pay programmers to work on Free/OSS, but we need a good group of fulltime desktop engineers. IBM needs them too, if it is going to roll out 30k Linux desktops internally in the next year. The other companies also need to invest in their future.
Actually, with a long linear source like a wire, the dropoff is 1/d, i.e. inverse linear. With a point source it's 1/(d^2).
What about Gnumeric? It's one of the most powerful + useful Free s/w apps. I don't know where I'd be without it.
SQL should have been ditched a long time ago.
So now you get a giant scratch across all tracks, rather than just in one place on one track.
About a month ago Google also started redirecting every URL on its search pages through its own site, so they know what you actually click on in the search results too.
Did they compare temperature changes in the cities to temperature changes in areas of low population? If not, their results are meaningless, or at least the conclusion they draw is meaningless. This is another example of mixing up association with causation.
I'm looking for a VoIP system that registers to a server and works over a firewall, between Linux and Windows (i.e. not GnomeMeeting / NetMeeting, because you have to open pinholes for that). The s/w then has to register with a server somewhere. I need it to work on both OSs. Free/free is best. Any ideas?
...anyway, what's Mr. McBride talking about? SCO are clearly in league with Microsoft.
I almost wish SCO would sue me as an end-user. Because then it would be in my rights for me to know every detail of their claims against me -- i.e. I would be able to demand that they show me every piece of infringing source code. Then I would show the rest of the world :-)
Of course that would never happen -- they would refuse to show me -- and besides, they can't find me anyway...
Comparing Round 1 to the rest, isn't it obvious that the problem is in the scaling code?
Why doesn't someone just make a third version of the worm that installs the patch after it infects a machine, so that everyone's machines get fixed automatically?
What is the state of S-ATA support, with and without RAID?
Also, maybe those who are more likely to commit crimes just don't get married... And comparing criminals to scientists just doesn't make sense...
Certainly, there are a very many benefits to marriage. It seems that this researcher is trying to discredit marriage by drawing "conclusions" that are statistically and logically invalid.
You should know that (X => Y) does NOT mean that (Y => X). In this case, ((marriage => old) AND (non-performer => old)) does NOT imply that (marriage => non-performer) ...!
You're only believing what you want to believe. The fact that people both (a) typically lose productivity around or near their early 30s, and (b) typically get married around or near their early 30s, does NOT imply that (a) causes (b), or that (b) causes (a). All it means is that being in your early 30s is somehow related to both (a) and (b); maybe your age is actually the cause of both, and neither (a) nor (b) is actually directly correlated with one another. The author (or maybe the reporter) made more basic statistical blunders (surrounding causation) in those statements than I have seen in a long time.