where performance problems are easier to mask, and costs for faster hardware are lost amidst huge corporate budgets
Huh, what are you talking about? Well written Java code with a good JVM and JIT (neither of which are hard to find for most platforms) performs just as well, on cheap hardware.
Here's an example (from: http://java.apache.org/faq/fom-serve/cache/300.htm l)
And we're a quite busy site (The Norwegian Yellow Pages) serving almost 200 _servlets_ each minute at peak times. This on a single processor P-II 333, 384MB of memory, RH 5.2. The load never reaches 1, even at peak times.
I really hope this dosen't mean we're going to get a whole bunch of vendors renaming their OSs in a similar fasion.
I can see the advocacy flames already..
>>> QNX-Powered rulez.. >> You don't know what you're fscking talking about >> everyone *knows* MacOSX Powered kicks all the > Get real, lamer! Windows Powered is much more swoonful
The problem is that most people use apt-get update && apt-get upgrade
I've always thought it was the other way around. I *never* use dselect and always use apt-get. Apt will always keep a package back when doing an upgrade if it has unmet deps and tells you if you try doing an install on a similar package.
The thing that put me off dselect was it's immensely annoying habit of selecting common packages to install, even if I don't want them!
The contest sounds like a great idea! One of the longest-running complaints about Mozilla was how daunting the source is.
I think it's interesting to note though, that there are a lot of very complex open source (free or otherwise) out there that are getting a lot more devloper support. The Linux kernel obviously springs to mind. So does Apache. So why aren't people complaining about the complexity of these projects?
Anyway, on the competition page, they say patterns are a new thing. I though the idea had been around for ages.
It sounds like you have a dependency problem from installing that package by hand. In general, it's much better to let apt or dselect do all the downloading and installing for you, so at least the base deps are met. But you probably realise this now. 8)
One big no-no is adding unstable packages to a stable machine. Unstable packages are all compiled against linux2.2/glibc2.1 and so may not function properly.
You could try reinstalling the offending package from your original dist, or do a apt-get check and see exactly what is broken. But if you want to upgrade to unstable, take your entire dist up to it using apt-get dist-upgrade (ensuring you first have an unstable source listed in/etc/apt/sources.list). Take note though, this will upgarde every package on your system to the unstable version, so it may take a while.
I want to run glibc2 stuff but Debian can't do that out of the box now can it?
Out of the box, no, but -unstable is based on linux-2.2/glibc-2.1. Getting slink(stable) up to potato(unstable) is as easy as typing apt-get dist-upgrade.
Potato, as it's unstable designation implies, *may* be unstable, but I generally keep on the cutting edge, package-wise, and have had few problems.
Slashdot Mirror
"Kill all access, must kill all access"
-Mike.
Huh, what are you talking about? Well written Java code with a good JVM and JIT (neither of which are hard to find for most platforms) performs just as well, on cheap hardware.
Here's an example (from: http://java.apache.org/faq/fom-serve/cache/300.htm l)
And we're a quite busy site (The Norwegian Yellow Pages) serving almost 200 _servlets_ each minute at peak times. This on a single processor P-II 333, 384MB of memory, RH 5.2. The load never reaches 1, even at peak times.
Mike
Mike.
I can see the advocacy flames already..
>>> QNX-Powered rulez..
>> You don't know what you're fscking talking about
>> everyone *knows* MacOSX Powered kicks all the
> Get real, lamer! Windows Powered is much more swoonful
Scheesh!
Mike
I've always thought it was the other way around. I *never* use dselect and always use apt-get. Apt will always keep a package back when doing an upgrade if it has unmet deps and tells you if you try doing an install on a similar package.
The thing that put me off dselect was it's immensely annoying habit of selecting common packages to install, even if I don't want them!
-mike
I think it's interesting to note though, that there are a lot of very complex open source (free or otherwise) out there that are getting a lot more devloper support. The Linux kernel obviously springs to mind. So does Apache. So why aren't people complaining about the complexity of these projects?
Anyway, on the competition page, they say patterns are a new thing. I though the idea had been around for ages.
-Mike
One big no-no is adding unstable packages to a stable machine. Unstable packages are all compiled against linux2.2/glibc2.1 and so may not function properly.
You could try reinstalling the offending package from your original dist, or do a apt-get check and see exactly what is broken. But if you want to upgrade to unstable, take your entire dist up to it using apt-get dist-upgrade (ensuring you first have an unstable source listed in /etc/apt/sources.list). Take note though, this will upgarde every package on your system to the unstable version, so it may take a while.
good luck!
-mike
Out of the box, no, but -unstable is based on linux-2.2/glibc-2.1. Getting slink(stable) up to potato(unstable) is as easy as typing apt-get dist-upgrade.
Potato, as it's unstable designation implies, *may* be unstable, but I generally keep on the cutting edge, package-wise, and have had few problems.
mike.