From the screenshot caption: This photo provided by Microsoft shows Their search tool and the prefenece rankings that can be defined by the user. (AP Photo/HO/Microsoft)
If these MS allegations that Linux and Open Source software may violate certain patents turns out to be true (highly unlikely) - MS itself may be in trouble considering what they use to use their own products;)
See the caption below This photo provided by Microsoft shows Their search tool and the prefenece rankings that can be defined by the user. (AP Photo/HO/Microsoft)
I notice a number of posts indicating that this is just pure uninformed journalism but is it? Or is he actually just blowing up a different related issue out of proportion.
In the Linux Kernel Development Summit back in July, the core developers announced they weren't creating a 2.7 development kernel any time soon (discussed here and here).
Developers liked the way things were going with the new BitKeeper in use by Linus and at the time, they didn't see the need to fork a 2.7.
Traditionally before BitKeeper, kernel maintainers would send Linus 10-20 patches at once, then wait for him to release a snapshot to determine whether or not the patch made it in. If not, they would try again. During the 2.5 development cycle, problems started over dropped patches and that is when Linus decided to try BitKeeper.
According to Greg Kroah-Hartman, kernel maintainer, Bitkeeper has increased the amount of development and improved efficency. From 2.5 and 2.6, they were doing 1.66 changes per hour for 680 days. From 2.6.0 to 2.6.7 they were at 2.2 patches per hour thanks to the ability of wider range of testing of patches that went into the tree. The new process is - 1) Linus releases a 2.6 kernel release. 2) Maintainers flood Linus with patches that have been proven in the -mm tree 3) After a few weeks, Linus releases a -rc kernel 4) Everyone recovers from a load of changes and starts to fix any bugs found in the -rc kernel 5) A few weeks later, the next 2.6 kernel is released and the cycle starts again.
Because this new process has proved to be pretty efficient and is keeping mainters happy, it was predicted that no new 2.7 kernel was to be forked any time soon unless a set of changes appeared big enough and intrusive that a 2.7 fork is needed. If that is the case, Linus will apply the experimental patches to the new 2.7 tree, then he will continue to pull all of the ongoing 2.6 changes into the 2.7 kernel as the version stabilizes. If it turns out that the 2.7 kernel is taking an incorrect direction, the 2.7 will be deleted an deveryone will continue on the 2.6. If 2.7 becomes stable, it will be merged back into 2.6 or will be declared 2.8.
In conclusion, there was no plan for a 2.7 any time soon thanks to maintainers working well in the current setup but this was not carved in stone. It might just be that big enough changes are calling for a fork.
Cars that are environmentally friendly may be coming to drivers in North America faster than anyone expected after the Canadian government pledged this week to a dramatic 25 per cent reduction in greenhouse gas emissions from all vehicles sold inside its borders by the end of the decade.
...took part in a web chat about it (good read if you want to see less techy user's reactions).
"Deltona, Fla.: Can you run Firefox on netscape and not lose I.E. until you know for sure you like it? Stupid question? Any info would be appreciated...Thanx"
SUN paid 9 mil for Solaris and Microsoft paid almost double that and yet MS doesn't even have a real UNIX OS product. I agree, that "licensing" money was really spent in something else.
Many of you have heard or noticed the way in which the msn bot is pounding and raping away sites as of lately. The thing is behaving like a drunk man knocking on random apartment doors over and over again. Here is some sample data from my personal site..
Note that 207.46.98.33 is registered to Microsoft so lets assume it's the msn bot. Notice that the damn thing blindly keeps on downloading the same file! The requests are just a few minutes from each other. The other ip address is from google's bot. This can be dangerous for those of us who have transfer caps. I know that a simple tweak in robots.txt and/or meta tags should (hopefully) solve the problem but why do I have to do extra work because of their "ways" of implementing this thing? Beta or not they are using the whole web as their test subject and unless there is a reasonable explanation as to why this is being done, tests are not going well and well it's just annoying.;)
Could someone enlighten me with an explanation as to why this could be happening?
Note that 207.46.98.33 is registered to Microsoft so lets assume it's the msn bot. Notice that the damn thing blindly keeps on downloading the same file! The requests are just a few minutes from each other. The other ip address is from google's bot.
Please people, use the mirrors or the mozilla.org ftp redirect. The plugin finder is suffering from the slashdotting and massive surge in traffic. We don't want to drive people away as the first thing they experience is problems finding/updating their extensions/themes.
Slashdot Mirror
Firefox is indeed a good browser, even Microsoft agrees.
From the screenshot caption:
This photo provided by Microsoft shows Their search tool and the prefenece rankings that can be defined by the user. (AP Photo/HO/Microsoft)
If these MS allegations that Linux and Open Source software may violate certain patents turns out to be true (highly unlikely) - MS itself may be in trouble considering what they use to use their own products ;)
See the caption below
This photo provided by Microsoft shows Their search tool and the prefenece rankings that can be defined by the user. (AP Photo/HO/Microsoft)
I notice a number of posts indicating that this is just pure uninformed journalism but is it? Or is he actually just blowing up a different related issue out of proportion.
In the Linux Kernel Development Summit back in July, the core developers announced they weren't creating a 2.7 development kernel any time soon (discussed here and here).
Developers liked the way things were going with the new BitKeeper in use by Linus and at the time, they didn't see the need to fork a 2.7.
Traditionally before BitKeeper, kernel maintainers would send Linus 10-20 patches at once, then wait for him to release a snapshot to determine whether or not the patch made it in. If not, they would try again. During the 2.5 development cycle, problems started over dropped patches and that is when Linus decided to try BitKeeper.
According to Greg Kroah-Hartman, kernel maintainer, Bitkeeper has increased the amount of development and improved efficency. From 2.5 and 2.6, they were doing 1.66 changes per hour for 680 days. From 2.6.0 to 2.6.7 they were at 2.2 patches per hour thanks to the ability of wider range of testing of patches that went into the tree. The new process is - 1) Linus releases a 2.6 kernel release. 2) Maintainers flood Linus with patches that have been proven in the -mm tree 3) After a few weeks, Linus releases a -rc kernel 4) Everyone recovers from a load of changes and starts to fix any bugs found in the -rc kernel 5) A few weeks later, the next 2.6 kernel is released and the cycle starts again.
Because this new process has proved to be pretty efficient and is keeping mainters happy, it was predicted that no new 2.7 kernel was to be forked any time soon unless a set of changes appeared big enough and intrusive that a 2.7 fork is needed. If that is the case, Linus will apply the experimental patches to the new 2.7 tree, then he will continue to pull all of the ongoing 2.6 changes into the 2.7 kernel as the version stabilizes. If it turns out that the 2.7 kernel is taking an incorrect direction, the 2.7 will be deleted an deveryone will continue on the 2.6. If 2.7 becomes stable, it will be merged back into 2.6 or will be declared 2.8.
In conclusion, there was no plan for a 2.7 any time soon thanks to maintainers working well in the current setup but this was not carved in stone. It might just be that big enough changes are calling for a fork.
In related news, Canada is also doing its part.
Cars that are environmentally friendly may be coming to drivers in North America faster than anyone expected after the Canadian government pledged this week to a dramatic 25 per cent reduction in greenhouse gas emissions from all vehicles sold inside its borders by the end of the decade.
Forget moving as soon as it's green, how about actually respecting yellow/red lights!
very true. It has to be all of none.
I'd trust a well written, tested and proven piece of software more than I trust some of the drivers I've seen.
I'm already trusting computers with my health, flying, etc.
...took part in a web chat about it (good read if you want to see less techy user's reactions).
"Deltona, Fla.: Can you run Firefox on netscape and not lose I.E. until you know for sure you like it? Stupid question? Any info would be appreciated...Thanx"
Indeed good read.
SUN paid 9 mil for Solaris and Microsoft paid almost double that and yet MS doesn't even have a real UNIX OS product. I agree, that "licensing" money was really spent in something else.
Many of you have heard or noticed the way in which the msn bot is pounding and raping away sites as of lately. The thing is behaving like a drunk man knocking on random apartment doors over and over again. Here is some sample data from my personal site..
;)
2004-11-09 15:17:56 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 14:25:37 permit-1.0.tar.gz 207.46.98.33
2004-11-09 10:32:15 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 06:25:07 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 06:19:18 permit-1.0.tar.gz 207.46.98.33
2004-11-09 02:51:34 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 02:46:07 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 02:35:36 MultiplyWithMFC-1.0_src.zip 66.249.64.199
2004-11-09 00:55:05 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 00:12:03 permit-1.0.tar.gz 207.46.98.33
2004-11-09 00:10:57 permit-1.0.tar.gz 207.46.98.33
2004-11-09 00:05:21 sync.X-1.0.tar.gz 207.46.98.33
2004-11-08 21:03:10 permit-1.0.tar.gz 207.46.98.33
Note that 207.46.98.33 is registered to Microsoft so lets assume it's the msn bot. Notice that the damn thing blindly keeps on downloading the same file! The requests are just a few minutes from each other. The other ip address is from google's bot. This can be dangerous for those of us who have transfer caps. I know that a simple tweak in robots.txt and/or meta tags should (hopefully) solve the problem but why do I have to do extra work because of their "ways" of implementing this thing? Beta or not they are using the whole web as their test subject and unless there is a reasonable explanation as to why this is being done, tests are not going well and well it's just annoying.
Could someone enlighten me with an explanation as to why this could be happening?
I'd like to share these few entries from my website, which is getting raped by the msn bot.
2004-11-09 15:17:56 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 14:25:37 permit-1.0.tar.gz 207.46.98.33
2004-11-09 10:32:15 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 06:25:07 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 06:19:18 permit-1.0.tar.gz 207.46.98.33
2004-11-09 02:51:34 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 02:46:07 cdp-1.0.tar.gz 207.46.98.33
2004-11-09 02:35:36 MultiplyWithMFC-1.0_src.zip 66.249.64.199
2004-11-09 00:55:05 sync.X-1.0.tar.gz 207.46.98.33
2004-11-09 00:48:03 permit-1.0.tar.gz 207.46.98.33
2004-11-09 00:10:57 permit-1.0.tar.gz 207.46.98.33
2004-11-09 00:05:21 sync.X-1.0.tar.gz 207.46.98.33
2004-11-08 21:03:10 permit-1.0.tar.gz 207.46.98.33
Note that 207.46.98.33 is registered to Microsoft so lets assume it's the msn bot. Notice that the damn thing blindly keeps on downloading the same file! The requests are just a few minutes from each other. The other ip address is from google's bot.
Apparently this MS director has a fan club aquired thanks to his popularity from his previous job.
See here
Here is to the greatest mp3 player ...
They should interviewed in National Geographic or something..
Please people, use the mirrors or the mozilla.org ftp redirect. The plugin finder is suffering from the slashdotting and massive surge in traffic. We don't want to drive people away as the first thing they experience is problems finding/updating their extensions/themes.
l eases/
http://ftp.mozilla.org/pub/mozilla.org/firefox/re
See the problem is that unfortunetly, I don't find that remaining % at my local HMV :)
The reason I usually don't buy CDs is because 90% of the mainstream music sold out there is simply SHIT.
According to this article, they started by selling Napster source code back in July and then stopped but have started again.
It used to be ok to share funny commercial clips but sadly some of them might not be legal anymore.
I totally agree. Although, I've seen the same mistake done by Canadians.
..and the majority of the rest of the world.
https://bugzilla.mozilla.org/show_bug.cgi?id=26693 2
I can confirm on Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
sounds sweet! could i send you my resume? :-)
I think I trust Linux more