But SuSE is no longer a European company. They're a Utah company now. And thus things like the fantastic i18n, l10n, and l12y capabilities of SuSE no longer matter. Indeed, it most likely will be their downfall. The quality of GNOME's support for such technology falls short of that of KDE.
But when the feeble die, young blood arises to continue on. And in that case it will be distros like Kubuntu.
Put simply, Matt Dillon was a FreeBSD contributor for many years. He was responsible for some of the most important and beneficial work, such as the virtual memory subsystem rewrite.
He did not feel that the direction of FreeBSD 5.x was a good one, and thus did the open source thing and forked his own kernel from FreeBSD 4.8.
DragonFly BSD is incorporating many features useful for multiprocessor systems. It includes a vastly improved kernel memory allocator and improved threading and messaging constructs, for instance.
While it is still under development now, it is poised to become the leading general-purpose desktop/workstation/server BSD of the future. It's partaking in the innovations that will be needed with the advent of multicore and multiprocessor systems.
This was on uniprocessor, non-hyperthreaded servers.
What astounded me most was the massive performance boost over OpenBSD. 60% isn't a small amount, by any means. That's nearly getting the capabilities of another physical server, without actually having to get any new hardware.
You do realize that JDK 1.4 is not JDK 1.5, correct? There have been significant improvements.
I recently set up several servers running FreeBSD 5.4, the native JDK 1.5, and Tomcat 5.5.12. They work perfectly, each handling upwards of 9 to 10 million hits per day.
Chances are you won't get OpenDarwin to run at all. It has very picky hardware requirements, and much less support than any of the other BSDs, and even x86 Solaris.
When it comes to running a server, it's probably best to just stick with FreeBSD or Solaris if you want performance, or OpenBSD if you want security. The hardware support is far better, bugfixes are quicker, and support is easier to obtain.
They need to sign a contract with a large transportation provider in Europe and Japan, so as to provide this service on all buses, trains and other public transport vehicles. That would give people the incentive needed to purchase the hardware necessary to take advantage of this new system.
Vast performance improvements.
on
FreeBSD 6.0 Released
·
· Score: 4, Interesting
Earlier today a client came to me, requesting that a FreeBSD 6.0 demo box be set up as a potential replacement for their current OpenBSD mail server. Indeed, 6.0 may be the release we have all been waiting for. The performance is vastly improved, and the stability is fantastic.
We found that the server was able to process about 60% more mail when running FreeBSD 6.0, as compared to OpenBSD. That's not to suggest that OpenBSD is bad, but performance wise, FreeBSD has taken the lead. And that was without significant tuning, and running a GENERIC kernel.
I'm not certain yet if it is improvements in the network stack, the filesystem subsystem, or in the scheduling. It may be a combination of all three. Some more time will be needed to determine exactly where the benefits are coming from.
Writing a JVM equivalent to what Sun or IBM offers would be a very, very difficult task. It's easy enough to write a simple one, even with rudimentary JIT capabilities, but for anything serious you need massive amounts of money, many developers, and a lot of time.
That's much the same reason why the *BSD projects use GCC: it would take far too long and would consume far too many resources to produce a quality C and C++ compiler suite.
GCJ is most likely unsuitable. Classpath, its Java class library implementation, lacks a serious Swing and AWT implementation. Thus it is basically useless for non-SWT GUI applications written in Java.
Then again, in previous discussion it was stated that Java caused a lot of the startup performance problems noted with OpenOffice.org. So a better idea may to be avoid the use of Java with OO.o.
For those who are unaware, DragonFly BSD is a heavily modified continuation of FreeBSD 4.x. It is done by Matt Dillon and many others who are/were prime FreeBSD developers in the past, but disagreed with the current FreeBSD development path.
If there's a truly serious problem going on, go and inform the manager. Now, if two people are talking a bit loud before the movie starts, suck it up. But if there are punks and beatniks throwing popcorn, the manager will usually kick such people out. After all, he already has their money. He doesn't necessarily want them to come back in the future, either.
Germany had very serious problems at cinemas in the late 1970s and early 1980s. With the punk movement raging there, it was often the case that feces and urine were thrown at other viewers. Eventually the viewers formed coalitions, and they went to the managers each time troublemakers were active. Soon enough the theatres kicked out the punks, and stopped admitting them in the future. The cinematic experience ended up improving for many people, and in the end the cinema managers gained from extra legitimate traffic.
It seems that you're suggesting that Oracle is getting SGI'ed. Is that the case? Perhaps. There are now several competitors to its product, and what was once unique from them is now far more common. However, there are many companies that have invested huge sums of money in Oracle products, and nothing is going to change that fact. Oracle will most likely be around for a while.
It will be interesting to see if Oracle eventually goes the way of SGI, or if they manage to pull a Sun and revive themselves before it's too late.
You should never be coding for ten hours. Anybody working on serious software would never pull a stunt like that. Like you said, you start making mistakes. So it's better just to stop at eight hours, and start fresh the next day. Chances are you'll actually be in a better position to hit your deadline, because you're not stuck tracking down and fixing all the errors you made while drugged.
Who suggested that anything was "perfect"? I sure didn't. You see to be the only one considering that possibility.
Developers hyped on caffeine or mentally clouded from drinking too much the night before do not formally prove systems very well. But then again, only fools rely strictly on formal proofs of software systems. You need to know the system you're developing for inside and out. You have to be able to consider each and every interaction that may occur. Drugged developers do not do that very well.
Actually, those people don't exist. You hallucinated them while extremely buzzed on caffeine, and drinking piss from your father's cock (thinking it was good ol' American beer).
Regular exercise is a far better option than resorting to caffeine highs. With such exercise you're able to maintain a better mental state, and do not tire as easily. It's better to give developers a gym pass than a coffee machine.
Why are you so worried about what other people put in their bodies?
I don't want the developers of mission critical software being impaired while designing and implementing software. I'm talking about software that can result in people dying if it contains errors. The sort of software controlling nuclear power plant shutdown systems, or aeroplane flight control software.
WTF kind of programmers are you around? When I tell people that I avoid caffiene, they look at me like I'm crazy.
I worked with real programmers. The kind who develop mission critical software where mistakes are not tolerated. Aeroplane flight control software systems, for instance.
Such people cannot be impaired while coding, and thus avoid alcoholic and caffeinated beverages completely.
They may not kill you, but they sure as hell don't help you. And no, they do not have health benefits. Certain alcoholic drinks, like red wine, contain substances that do offer health benefits. But the alcohol does not.
All alcohol does is impair the drinker's mind. Caffeine causes undue anxiety. Those are not good things to suffer from when you're trying to write solid software, especially when facing deadlines and changing requirements.
Slashdot Mirror
But SuSE is no longer a European company. They're a Utah company now. And thus things like the fantastic i18n, l10n, and l12y capabilities of SuSE no longer matter. Indeed, it most likely will be their downfall. The quality of GNOME's support for such technology falls short of that of KDE.
But when the feeble die, young blood arises to continue on. And in that case it will be distros like Kubuntu.
The Wikipedia article does a good job describing the reasons for the fork:
http://en.wikipedia.org/wiki/DragonflyBSD
Put simply, Matt Dillon was a FreeBSD contributor for many years. He was responsible for some of the most important and beneficial work, such as the virtual memory subsystem rewrite.
He did not feel that the direction of FreeBSD 5.x was a good one, and thus did the open source thing and forked his own kernel from FreeBSD 4.8.
DragonFly BSD is incorporating many features useful for multiprocessor systems. It includes a vastly improved kernel memory allocator and improved threading and messaging constructs, for instance.
While it is still under development now, it is poised to become the leading general-purpose desktop/workstation/server BSD of the future. It's partaking in the innovations that will be needed with the advent of multicore and multiprocessor systems.
From where are you an alumni? I recall my son talking about a Greg Casamento who was in several of his courses.
This was on uniprocessor, non-hyperthreaded servers.
What astounded me most was the massive performance boost over OpenBSD. 60% isn't a small amount, by any means. That's nearly getting the capabilities of another physical server, without actually having to get any new hardware.
You do realize that JDK 1.4 is not JDK 1.5, correct? There have been significant improvements.
I recently set up several servers running FreeBSD 5.4, the native JDK 1.5, and Tomcat 5.5.12. They work perfectly, each handling upwards of 9 to 10 million hits per day.
Chances are you won't get OpenDarwin to run at all. It has very picky hardware requirements, and much less support than any of the other BSDs, and even x86 Solaris.
When it comes to running a server, it's probably best to just stick with FreeBSD or Solaris if you want performance, or OpenBSD if you want security. The hardware support is far better, bugfixes are quicker, and support is easier to obtain.
They need to sign a contract with a large transportation provider in Europe and Japan, so as to provide this service on all buses, trains and other public transport vehicles. That would give people the incentive needed to purchase the hardware necessary to take advantage of this new system.
Earlier today a client came to me, requesting that a FreeBSD 6.0 demo box be set up as a potential replacement for their current OpenBSD mail server. Indeed, 6.0 may be the release we have all been waiting for. The performance is vastly improved, and the stability is fantastic.
We found that the server was able to process about 60% more mail when running FreeBSD 6.0, as compared to OpenBSD. That's not to suggest that OpenBSD is bad, but performance wise, FreeBSD has taken the lead. And that was without significant tuning, and running a GENERIC kernel.
I'm not certain yet if it is improvements in the network stack, the filesystem subsystem, or in the scheduling. It may be a combination of all three. Some more time will be needed to determine exactly where the benefits are coming from.
Writing a JVM equivalent to what Sun or IBM offers would be a very, very difficult task. It's easy enough to write a simple one, even with rudimentary JIT capabilities, but for anything serious you need massive amounts of money, many developers, and a lot of time.
That's much the same reason why the *BSD projects use GCC: it would take far too long and would consume far too many resources to produce a quality C and C++ compiler suite.
GCJ is most likely unsuitable. Classpath, its Java class library implementation, lacks a serious Swing and AWT implementation. Thus it is basically useless for non-SWT GUI applications written in Java.
Then again, in previous discussion it was stated that Java caused a lot of the startup performance problems noted with OpenOffice.org. So a better idea may to be avoid the use of Java with OO.o.
Unfortunately, we probably won't see a new release of DragonFly BSD until after the new year.
0 05-10/msg00030.html
http://leaf.dragonflybsd.org/mailarchive/kernel/2
For those who are unaware, DragonFly BSD is a heavily modified continuation of FreeBSD 4.x. It is done by Matt Dillon and many others who are/were prime FreeBSD developers in the past, but disagreed with the current FreeBSD development path.
There is a native port of JDK 1.5.x. Even if it isn't listed as the current release, it still works very well.
http://www.freebsd.org/java/dists/15.html
If there's a truly serious problem going on, go and inform the manager. Now, if two people are talking a bit loud before the movie starts, suck it up. But if there are punks and beatniks throwing popcorn, the manager will usually kick such people out. After all, he already has their money. He doesn't necessarily want them to come back in the future, either.
Germany had very serious problems at cinemas in the late 1970s and early 1980s. With the punk movement raging there, it was often the case that feces and urine were thrown at other viewers. Eventually the viewers formed coalitions, and they went to the managers each time troublemakers were active. Soon enough the theatres kicked out the punks, and stopped admitting them in the future. The cinematic experience ended up improving for many people, and in the end the cinema managers gained from extra legitimate traffic.
That is totally a literary masterpiece.
That's a fantastic link, Barry. Thanks for letting us all know about it.
Ideed! You're correct again, Barry.
It seems that you're suggesting that Oracle is getting SGI'ed. Is that the case? Perhaps. There are now several competitors to its product, and what was once unique from them is now far more common. However, there are many companies that have invested huge sums of money in Oracle products, and nothing is going to change that fact. Oracle will most likely be around for a while.
It will be interesting to see if Oracle eventually goes the way of SGI, or if they manage to pull a Sun and revive themselves before it's too late.
You should never be coding for ten hours. Anybody working on serious software would never pull a stunt like that. Like you said, you start making mistakes. So it's better just to stop at eight hours, and start fresh the next day. Chances are you'll actually be in a better position to hit your deadline, because you're not stuck tracking down and fixing all the errors you made while drugged.
Who suggested that anything was "perfect"? I sure didn't. You see to be the only one considering that possibility.
Developers hyped on caffeine or mentally clouded from drinking too much the night before do not formally prove systems very well. But then again, only fools rely strictly on formal proofs of software systems. You need to know the system you're developing for inside and out. You have to be able to consider each and every interaction that may occur. Drugged developers do not do that very well.
Actually, those people don't exist. You hallucinated them while extremely buzzed on caffeine, and drinking piss from your father's cock (thinking it was good ol' American beer).
Regular exercise is a far better option than resorting to caffeine highs. With such exercise you're able to maintain a better mental state, and do not tire as easily. It's better to give developers a gym pass than a coffee machine.
Why are you so worried about what other people put in their bodies?
I don't want the developers of mission critical software being impaired while designing and implementing software. I'm talking about software that can result in people dying if it contains errors. The sort of software controlling nuclear power plant shutdown systems, or aeroplane flight control software.
WTF kind of programmers are you around? When I tell people that I avoid caffiene, they look at me like I'm crazy.
I worked with real programmers. The kind who develop mission critical software where mistakes are not tolerated. Aeroplane flight control software systems, for instance.
Such people cannot be impaired while coding, and thus avoid alcoholic and caffeinated beverages completely.
They may not kill you, but they sure as hell don't help you. And no, they do not have health benefits. Certain alcoholic drinks, like red wine, contain substances that do offer health benefits. But the alcohol does not.
All alcohol does is impair the drinker's mind. Caffeine causes undue anxiety. Those are not good things to suffer from when you're trying to write solid software, especially when facing deadlines and changing requirements.
And? That's still no reason for the server to crash.