Hey, that's bullshit. How does this get moderated so high? Timothy has gotten into a fight with "KDE" more than once is in fact a *personal* friend of dep.
It looks 256 MaxClient is hardwired in Apache. Oh well, live and learn. We'll have to recompile Apache for next time. We definitely got the CPU/bandwidth for more.
I was even more disappointed when the KOffice beta release wasn't posted. It's not like we have a release every week like OpenOffice and Mozilla do... and there was some really good stuff in the new beta.
Sorry for being slightly offtopic -- does anyone know of a Linux app that will allow me to visually monitor audio levels under Linux? The sort of thing you usually see on equalizers that indicate when the audio level is too high or in danger of being cut-off.
I would have thought this sort of basic tool to be quite essential for any kind of audio recording or processing under Linux, yet it has been surprisingly hard to find one.
Recognized, sure. Does it let you create them from scratch? The farthest I could go was to create an LVM partition type, but it didn't seem to know how to do anything with it. I couldn't find any command line tools in the install either.
I could create an "LVM partition" but 8.1 didn't know how to format it. If it's there, I really couldn't figure out the GUI. I didn't have any of the LVM tools from the boot prompt.
The rescue boot option most certainly does not recognize my logical volumes.
LVM really ought to be supported in every modern distribution install. For those of you who don't know, LVM basically lets you resize your partitions (and filesystems with resize2fs) on the fly.
This is really sweet, and a godsend to those of us who find it hard to predict how much diskspace one will use on a certain filesystem in the future.
Mandrake 8.1 GE didn't support LVM in the installation, so I had to install it in a round-about bootstrapping manner. The Mandrake "rescue" cd boot does not seem to include LVM support either.
I gave Zope a slap up the head too, so it should be more responsive now. Now that I'm back, I'll have some time to figure out a more robust solution for the dot.
Java does have it draw-backs, such as speed, but this is quickly becoming a non issue on modern computers
*ROTFLOL* Do you know how long people have been saying that? This line must have been quoted since the very beginning of Java's existence.:-)
I agree with most of the rest of what you say.
Re:Dot.KDE.org is a joke ...
on
KDE 2.2 Released
·
· Score: 0, Redundant
Will Windows or Slashcode make an overheating harddrive not crash, or faulty RAM not fault? I don't think so. And your 50% uptime is a gross misrepresentation of the facts.
Let's not mix issues and problems without knowing the whole story. I am getting a lot of heat from people making complaints, most of them are happy to wax poetic without knowing the full facts or carefully considering the options. It's kinda tiring.
About Zope and Squishdot, we are working out the issues with helpful suggestions from the Zope guys. As for Slashcode, I will look at it one day when I have time. You might be surprised to learn that dot.kde.org is not my full-time job. So tell me if you know anything about how to move to Slashcode *and* still preserve backward compatibility with all the sites and documentation that link to dot.kde.org resources.
Don't worry about this. We're working on making our server be able to take these beatings, so it helps to be able to judge how successful we've been from time to time.:-)
Unfortunately, when I came back from a vacation I found the dot had gone down again this weekend... *grmbl* We really need to setup some failsafes. Unfortunately it's not easy, and nobody has time as usual.
Our current Zope setup also seems quite useless for withstanding a slashdot attack. I'll have to consult the Zope guys (who have offered to help), but as a short term solution I switched to static hosting for the Largo article.:-(
Hey, it didn't go down for a week, only a weekend and that was a hardware issue.
Too bad I was asleep when the bulk of the slashdotting occurred, and the server never faltered in fact. I doubt it was an Apache issue per se. Probably a MaxClients/RAM issue or something.
Is how long these LT changes have been going on without anyone noticing or speaking up.
Personally, I've noticed huge changes in LT editorial policies and implementation. It sucks how Linux news coverage has shrunk in quality and quantity over at LT these days. It's practically dead, subsisting on random flamebait and karma whoring from time to time. The manner of censorship of the talkback forums have also often quite bothered me.
I have had friendly exchanges with the editors in the past, but that was about it unfortunately. I'm glad someone is finally shedding light on all this. Finally, we know what happened to Marty Pitts (I never got an answer about that from anyone over there). Thanks, Paul.
This is only a developer's release, not ready for KDE Prime Time, and the security issues are already being considered. There are several options existing to protect Unix users including proper use of non-priviledged accounts (perhaps by setuid'ing reaktivate to nobody), chroot, sandboxes... etc. And after all this, KDE will probably still not enable ActiveX by default on any system. Remember, Konqueror does not even enable Java or JavaScript by default yet.
As for the usefulness of ActiveX in KDE, one of the main purposes of the developers is to help companies with an investment in ActiveX controls (perhaps on their internal sites or intranet) to migrate over to KDE systems. As a plus, of course, us users may get to enjoy Shockwave and QuickTime for which no free software solution is in sight.
So celebrate this for what this is: A rewly hack validating the KDE and WINE technologies that the Free Software wourld has brought us.
I have it on good authority that the interview was edited (as is usual in these kinds of things).
Do you honestly believe Andreas would have said something like "The whole desktop rarely crashes, but you'll have some applications crash, like the browser Konquerer, which is the centerpiece for KDE 2."?
(as an aside, I can't remember the last time
Konqueror crashed. it is no doubt the best of
the best at this point.)
Slashdot Mirror
Dude X1000 wireless works perfectly fine with ndiswrapper and the Intel windows driver. And the speedstepping works like a charm for that matter.
There are tons of Linux X1000 users out there all using the wireless and speedstepping.
Hey, that's bullshit. How does this get moderated so high? Timothy has gotten into a fight with "KDE" more than once is in fact a *personal* friend of dep.
title says it all, increased MaxClients to 800. but looks like they are quickly being used. :-)
It looks 256 MaxClient is hardwired in Apache. Oh well, live and learn. We'll have to recompile Apache for next time. We definitely got the CPU/bandwidth for more.
His page wasn't actually meant to be launched at this point, FWIW. KC KDE (and consequently the dot) leaked it a bit early.
It works, just have to be patient. Bumped MaxClients up to 400 but doubt that'll be enough. Whee!
I was even more disappointed when the KOffice beta release wasn't posted. It's not like we have a release every week like OpenOffice and Mozilla do... and there was some really good stuff in the new beta.
Sorry for being slightly offtopic -- does anyone know of a Linux app that will allow me to visually monitor audio levels under Linux? The sort of thing you usually see on equalizers that indicate when the audio level is too high or in danger of being cut-off.
I would have thought this sort of basic tool to be quite essential for any kind of audio recording or processing under Linux, yet it has been surprisingly hard to find one.
Thanks.
Neil you loser! :)
Recognized, sure. Does it let you create them from scratch? The farthest I could go was to create an LVM partition type, but it didn't seem to know how to do anything with it. I couldn't find any command line tools in the install either.
Oh well, I guess I missed something.
I could create an "LVM partition" but 8.1 didn't know how to format it. If it's there, I really couldn't figure out the GUI. I didn't have any of the LVM tools from the boot prompt.
The rescue boot option most certainly does not recognize my logical volumes.
LVM really ought to be supported in every modern distribution install. For those of you who don't know, LVM basically lets you resize your partitions (and filesystems with resize2fs) on the fly.
This is really sweet, and a godsend to those of us who find it hard to predict how much diskspace one will use on a certain filesystem in the future.
Mandrake 8.1 GE didn't support LVM in the installation, so I had to install it in a round-about bootstrapping manner. The Mandrake "rescue" cd boot does not seem to include LVM support either.
-N.
Sorry about that. dot.kde.org should be more responsive now.
-N.
I gave Zope a slap up the head too, so it should be more responsive now. Now that I'm back, I'll have some time to figure out a more robust solution for the dot.
-N.
AFAIK, Matthias Ettrich wrote QCom, but then again he did say he tends to get things right the second time around (with the rewrite).
And as we all known, Matthias *is* a brilliant programmer with results behind him...
Java does have it draw-backs, such as speed, but this is quickly becoming a non issue on modern computers
:-)
*ROTFLOL* Do you know how long people have been saying that? This line must have been quoted since the very beginning of Java's existence.
I agree with most of the rest of what you say.
Will Windows or Slashcode make an overheating harddrive not crash, or faulty RAM not fault? I don't think so. And your 50% uptime is a gross misrepresentation of the facts.
Let's not mix issues and problems without knowing the whole story. I am getting a lot of heat from people making complaints, most of them are happy to wax poetic without knowing the full facts or carefully considering the options. It's kinda tiring.
About Zope and Squishdot, we are working out the issues with helpful suggestions from the Zope guys. As for Slashcode, I will look at it one day when I have time. You might be surprised to learn that dot.kde.org is not my full-time job. So tell me if you know anything about how to move to Slashcode *and* still preserve backward compatibility with all the sites and documentation that link to dot.kde.org resources.
-N.
There are some here.
Don't worry about this. We're working on making our server be able to take these beatings, so it helps to be able to judge how successful we've been from time to time. :-)
-N.
Unfortunately, when I came back from a vacation I found the dot had gone down again this weekend... *grmbl* We really need to setup some failsafes. Unfortunately it's not easy, and nobody has time as usual.
:-(
Our current Zope setup also seems quite useless for withstanding a slashdot attack. I'll have to consult the Zope guys (who have offered to help), but as a short term solution I switched to static hosting for the Largo article.
Later,
-N.
This is exactly what I needed -- a Slashdotting so that I can finally try to optimize the dot server to handle it. (no joke) :-)
Cheers,
-N.
Hey, it didn't go down for a week, only a weekend and that was a hardware issue.
Too bad I was asleep when the bulk of the slashdotting occurred, and the server never faltered in fact. I doubt it was an Apache issue per se. Probably a MaxClients/RAM issue or something.
Things seem just fine now.
Is how long these LT changes have been going on without anyone noticing or speaking up.
Personally, I've noticed huge changes in LT editorial policies and implementation. It sucks how Linux news coverage has shrunk in quality and quantity over at LT these days. It's practically dead, subsisting on random flamebait and karma whoring from time to time. The manner of censorship of the talkback forums have also often quite bothered me.
I have had friendly exchanges with the editors in the past, but that was about it unfortunately. I'm glad someone is finally shedding light on all this. Finally, we know what happened to Marty Pitts (I never got an answer about that from anyone over there). Thanks, Paul.
-N.
Before people start flaming about security:
This is only a developer's release, not ready for KDE Prime Time, and the security issues are already being considered. There are several options existing to protect Unix users including proper use of non-priviledged accounts (perhaps by setuid'ing reaktivate to nobody), chroot, sandboxes... etc. And after all this, KDE will probably still not enable ActiveX by default on any system. Remember, Konqueror does not even enable Java or JavaScript by default yet.
As for the usefulness of ActiveX in KDE, one of the main purposes of the developers is to help companies with an investment in ActiveX controls (perhaps on their internal sites or intranet) to migrate over to KDE systems. As a plus, of course, us users may get to enjoy Shockwave and QuickTime for which no free software solution is in sight.
So celebrate this for what this is: A rewly hack validating the KDE and WINE technologies that the Free Software wourld has brought us.
Cheers,
-N.
I have it on good authority that the interview was edited (as is usual in these kinds of things).
Do you honestly believe Andreas would have said something like "The whole desktop rarely crashes, but you'll have some applications crash, like the browser Konquerer, which is the centerpiece for KDE 2."?
(as an aside, I can't remember the last time
Konqueror crashed. it is no doubt the best of
the best at this point.)