Collaborative process is at the heart of Open Source software development
True. If you look around you will occasionally find a single-person project, but you would for sure also find pledges for help on the projects home-page:-)
The collaborative Open Source process allows widely distributed contributors to participate
Actually I'm pretty sure it'll be something to do with the fact that Sun don't want to have to tell people like Veritas, Oracle and other ISV's, "Errrrm, sorry guys you're going to have to pay arbitrary fees to TrollTech, cos we've decided to go with a desktop toolkit that doesn't belong to us".
Yeah. And its not only Sun that reason this way. Everyone with just some remote recollection of a mortgage bill or even kids to feed thinks the same. In fact its the entire problem of the Gnome/KDE split. Now if just someone with a large pile of cash could bye-out TrollTech...
But its probably too late now since Sun et.al seems to be committing themselves wholeheartedly to Gnome.
I gave up on coding for Gnome about 6 months ago because I got fed up chasing my tail with new and incompatabile libararies popping up every five minutes.
Thats my experience too. Overall KDE seems to be much better managed than Gnome - or one could say: Gnome is much worse managed than the most of the other open source projects.
I wouldn't regard Sci.Am as a neutral observer of these matters. The man behind Sci.Am's review of The Skeptical Environmentalist is a certain Mr. Scheider who is widely quoted for the following statement on the role of environmentalist scientists:
[We] are not just scientists but human beings as well. And like
most people we'd like to see the world a better place...To do
that we need to get some broad-based support, to capture the
public's imagination. That, of course, entails getting loads of
media coverage. So we have to offer up scary scenarios, make
simplified, dramatic statements, and make little mention of any
doubts we might have...Each of us has to decide what the right
balance is between being effective and being honest.
Pretty damaging to the credibility of Mr Schneider in my book
Red Hat: "Red Hat Inc. has investigated this vulnerablity, and currently has a candidate fix which is undergoing regression testing. Updated ucd-snmp packages incorporating this fix will be available shortly from this page shortly."
Actually, as of 2001-02-13 12:45:00 GMT the notice reads:
with updated versions of the ucd-snmp package for all supported releases and architectures. For more information or to download the update please visit this page.
Upgraded just a few minutes ago. RedHat Network rocks.
a ready, higher-priority process can kick off a running, lower priority process before the running process's time slice expires
This is not entirely correct. The kernel always had the possibility of interupting userland processes even if they didn't use up all of their timeslice.
What the preemption patch adds to this scheme is that a kernel process can now be interrupted by a userland process. This is done at the existing SMP scheduling points already in the kernel code - and thats IMO a very elegant approach of this patch.
The reason modyfier is truely the best of the new features. Just try reading the thread with and without a setting of Funny: -6. Makes quite a differnece.
Now if we could get an -6 bonus on all posts containing the word "karma":-)
I would add that MPlayer has recently been named "The Project From Hell" in the linux press due to their extremely arrogant attitude towards users and others.
I don't know what exactly Brett Glass had done to deserve this honorable mentioning.
Am I not an American, but I don't think your responce should be limited to striking back.
I feel USA up to today have shown far too much restraint in tackling those groups who presumedly did this terrible action. USA have for years resented to a containment strategy towards terrorism (embargos, fligt-restrictions, and other low-level sanctions) instead of aggresively pursuing the people and regimes behind these organizations.
What is needed is a change of strategy: You need to fight the regimes supporting those groups more directly than today.
Yes, that would mean US soldiers in Afghanistan, in Irak, in Libya, in Sudan... everywhere on the
planet earth where terrorism has is roots, where it rests, where it plan these gross misdeeds. And yes, it will costs many of your soldiers life, but theres no alternative if you wan't to stay free.
gcc 3.0, the current "stable" release (released quite some time after Red Hat released gcc 2.96-RH), fixes some problems, but introduces many others - for example, gcc 3.0 can't compile KDE 2.2 beta 1 correctly. Until the first set of 3.0 updates is released, I still claim 2.96 is the best compiler yet.
Deeming from occasional lurking on the gcc mailing list the general consensus seems to be that the GCC 3.0 release is not amongst the best in recent history. To wit:
But don't worry - theres been looking into that and a solution has already shown up (and probably been included in RedHat gcc 3.0).
I would also like to add that I have successfully compiled KDE version 2.0.1, 2.1, 2.1.1, 2.1.2, 2.2beta1 (and some snapshots from time to time) using the RedHat gcc compiler. KDE is a LOT of C++ code and it speaks pretty much of the quality of the RedHat gcc to digest all that without any (*) problems !
(*) Hey bero: How about shipping a non-statically linked libcdda package ?
The "other" moon of earth is not gravitionally captured by earth. Instead its movement around the sun is synchronized with the earth in a way that make it looks like a moon, as seen from earth.
A link is here . And if you got a lot of time to kill, you could also visit this place.
I've been considering buying the ATI All-In-Wonder card for just that reason when I put my next system together. (Just how well is that card - the AGP version - supported under Linux?).
I am using ATI All-In-Wonder AGP version for my RH 6.1: It's ok.
2D performance is a little low when you shift desktops - perhaps some more video RAM would have helped. TV is working although the (third party open source) TV program is somewhat rough. I can't tell you about 3D performance because I am not using any 3D programs. There are some not-so-active Linux projects working with ATI cards (GATOS), and some optimized ATI drivers on its way together with XFree86 4.0.
The main reason for me to choose ATI was the ergonomic qualities of ATI products: Refresh rate >= 100MHz in 1024x768 resolution or better (I think NVidia does that too).
All-In-All: All-In-Wonder is an ok card. Recommended.
IO. Both in terms of read/write speed and in terms of access time. Were are in talking about systems running databases in the terabyte range with access times in the nanosecond range !
High availability. If your business is relying on your database, and if you're putting everything into one huge database running on a single (or a few) mainframes, then you want to be pretty sure, that this machine is having max. uptime.
If you OTOH are running a supercomputer for research or simulations, you don't bother that much for an occasionally break-down. In fact: Chances are that it was your program, that brought down the system.
In my last job, I was working in one of the biggest mainframe installations in Europe. We had close to 10000 users on our systems and the cost of having them sitting idle while we were bringing the system back on its feets were something like 5000$ a minute ! Not to mention the cost of lost business oppertunities.
Slow CPUs ! This may come as an surprise, but mainframes are having relatively slow CPUs due to the fact, that their performance limited by the IO subsystem. In addition: Business transactions are for the overwhelmingly majority consisting of simple additions/subtractions/assignments. An occasional multiplication sneeks in here and there, but generally you don't need a fast CPU.
The mainframes I was nursing was in fact far slower than my linux box at home.
Transactions. Mainframes are transaction machines. You're interfacing a mainframe in terms of transactions and the system is specifically optimized towards being able to handle a large amount of transactions and to do it fast. A transaction in this context could be a bank account transfer or a click. What matters is that you can't afford loosing any data and you can't afford losing your data integrity (customers don't like being billed twice, and your managers don't like customers not being billed at all:). Mainframes are optimized towards this kind of data processing.
OTOH non-transactional based interfaces suffer from this: If your editor was connected direcly to the system, then every single tap on your keyboard would be treated like an transaction - with rollback/rollforward options, logging, backup etc. etc. All of which would bring your very poor conceived performance.
Being a closed envirronment and often tied to a single supplier don't help either, so the standard of the userland software on mainframes are very poor.
A better name than Mainframe would probably be "database machine".
Slashdot Mirror
redundant pigeons will be given to the state's wildlife
:-)
And what would they do with them? How would they keep them from _not_ returning?
Perhaps the pigeons will be given to the wildlife as a food supplement
grep -i "[Ä]" test.txt
Ok. Here is what I did:
Works like a charm on both 7.1 and 7.2 .
True. If you look around you will occasionally find a single-person project, but you would for sure also find pledges for help on the projects home-page
True. The original pre-java version of ACS was fully open sourced. Their new java version is not, though.
Actually I'm pretty sure it'll be something to do with the fact that Sun don't want to have to tell people like Veritas, Oracle and other ISV's, "Errrrm, sorry guys you're going to have to pay arbitrary fees to TrollTech, cos we've decided to go with a desktop toolkit that doesn't belong to us".
Yeah. And its not only Sun that reason this way. Everyone with just some remote recollection of a mortgage bill or even kids to feed thinks the same. In fact its the entire problem of the Gnome/KDE split. Now if just someone with a large pile of cash could bye-out TrollTech...
But its probably too late now since Sun et.al seems to be committing themselves wholeheartedly to Gnome.
I gave up on coding for Gnome about 6 months ago because I got fed up chasing my tail with new and incompatabile libararies popping up every five minutes.
Thats my experience too. Overall KDE seems to be much better managed than Gnome - or one could say: Gnome is much worse managed than the most of the other open source projects.
- optimizations in the dynamic linker. binaries created by recent binutils versions start up quicker due to reduced time spend on relocations.
If I am reading this correctly, this is the much talked-about fix for the long startup times of KDE programs.Yay
I wouldn't regard Sci.Am as a neutral observer of these matters. The man behind Sci.Am's review of The Skeptical Environmentalist is a certain Mr. Scheider who is widely quoted for the following statement on the role of environmentalist scientists:
[We] are not just scientists but human beings as well. And like
most people we'd like to see the world a better place...To do
that we need to get some broad-based support, to capture the
public's imagination. That, of course, entails getting loads of
media coverage. So we have to offer up scary scenarios, make
simplified, dramatic statements, and make little mention of any
doubts we might have...Each of us has to decide what the right
balance is between being effective and being honest.
Pretty damaging to the credibility of Mr Schneider in my book
Thats a heck of a Tiger in the Tank :-)
Actually, as of 2001-02-13 12:45:00 GMT the notice reads:
Upgraded just a few minutes ago. RedHat Network rocks.
a ready, higher-priority process can kick off a running, lower priority process before the running process's time slice expires
This is not entirely correct. The kernel always had the possibility of interupting userland processes even if they didn't use up all of their timeslice.
What the preemption patch adds to this scheme is that a kernel process can now be interrupted by a userland process. This is done at the existing SMP scheduling points already in the kernel code - and thats IMO a very elegant approach of this patch.
The reason modyfier is truely the best of the new features. Just try reading the thread with and without a setting of Funny: -6. Makes quite a differnece.
Now if we could get an -6 bonus on all posts containing the word "karma" :-)
I would add that MPlayer has recently been named "The Project From Hell" in the linux press due to their extremely arrogant attitude towards users and others.
I don't know what exactly Brett Glass had done to deserve this honorable mentioning.
Here's the story.
Newer research has revealed that Santa is employing quantum wave functions which explains a lot - look here
Beware of the evils of HTML formatting !
Only belive in the one and true Linux Kernel Mailing List and cut'n paste from here into a file.
Then this should do it:
I feel USA up to today have shown far too much restraint in tackling those groups who presumedly did this terrible action. USA have for years resented to a containment strategy towards terrorism (embargos, fligt-restrictions, and other low-level sanctions) instead of aggresively pursuing the people and regimes behind these organizations.
What is needed is a change of strategy: You need to fight the regimes supporting those groups more directly than today.
Yes, that would mean US soldiers in Afghanistan, in Irak, in Libya, in Sudan... everywhere on the planet earth where terrorism has is roots, where it rests, where it plan these gross misdeeds. And yes, it will costs many of your soldiers life, but theres no alternative if you wan't to stay free.
2.4.6 is now included
I am a little worried about that. Kernel 2.4.6 still has some "issues" regarding virtual memory.
The 2.4.7 pre-releases seems to fix that. Do anyone know if theres a chance RedHat will upgrade to 2.4.7 before the final release of 7.2 ?
That was a truely informed posting.
gcc 3.0, the current "stable" release (released quite some time after Red Hat released gcc 2.96-RH), fixes some problems, but introduces many others - for example, gcc 3.0 can't compile KDE 2.2 beta 1 correctly. Until the first set of 3.0 updates is released, I still claim 2.96 is the best compiler yet.
Deeming from occasional lurking on the gcc mailing list the general consensus seems to be that the GCC 3.0 release is not amongst the best in recent history. To wit:
Ouch !!
But don't worry - theres been looking into that and a solution has already shown up (and probably been included in RedHat gcc 3.0).
I would also like to add that I have successfully compiled KDE version 2.0.1, 2.1, 2.1.1, 2.1.2, 2.2beta1 (and some snapshots from time to time) using the RedHat gcc compiler. KDE is a LOT of C++ code and it speaks pretty much of the quality of the RedHat gcc to digest all that without any (*) problems !
(*) Hey bero: How about shipping a non-statically linked libcdda package ?
The "other" moon of earth is not gravitionally captured by earth. Instead its movement around the sun is synchronized with the earth in a way that make it looks like a moon, as seen from earth.
A link is here . And if you got a lot of time to kill, you could also visit this place.
Bzzt - Wrong. A five users license costs around $800.
I am using ATI All-In-Wonder AGP version for my RH 6.1: It's ok.
2D performance is a little low when you shift desktops - perhaps some more video RAM would have helped. TV is working although the (third party open source) TV program is somewhat rough. I can't tell you about 3D performance because I am not using any 3D programs. There are some not-so-active Linux projects working with ATI cards (GATOS), and some optimized ATI drivers on its way together with XFree86 4.0.
The main reason for me to choose ATI was the ergonomic qualities of ATI products: Refresh rate >= 100MHz in 1024x768 resolution or better (I think NVidia does that too).
All-In-All: All-In-Wonder is an ok card. Recommended.
-Claus
Four things characterize a mainframe:
If you OTOH are running a supercomputer for research or simulations, you don't bother that much for an occasionally break-down. In fact: Chances are that it was your program, that brought down the system.
In my last job, I was working in one of the biggest mainframe installations in Europe. We had close to 10000 users on our systems and the cost of having them sitting idle while we were bringing the system back on its feets were something like 5000$ a minute ! Not to mention the cost of lost business oppertunities.
The mainframes I was nursing was in fact far slower than my linux box at home.
OTOH non-transactional based interfaces suffer from this: If your editor was connected direcly to the system, then every single tap on your keyboard would be treated like an transaction - with rollback/rollforward options, logging, backup etc. etc. All of which would bring your very poor conceived performance.
Being a closed envirronment and often tied to a single supplier don't help either, so the standard of the userland software on mainframes are very poor.
A better name than Mainframe would probably be "database machine".
-Claus