Since it's an independent implementation it contains different bugs from SUN's VM, and you may have better luck with it.
Or it could be that your VM process uses up too much memory and gets killed by the kernel's OOM handler. In that case JRockit will disappear even faster for you.
If North Korea nuked Seoul, South Korea would lose about ten million people, most of whom would be civilians. That's a lot in my book.
What do you think "Kimmy-boy" wants that would make SK safe from a nuclear attack?
First you're saying that SK are well able to defend themselves, they you say that NK could inflict "massive casualities on the US and/or US allies". Who would those allies be, if not SK?
Re-spin the game, call the whole shebang "Taiwan". That will maintain "China's territorial integrity".
Something that doesn't seem to have occured to the Chinese leaders is that if they are so keen on unity with Taiwan, why don't they just ask them nicely? As in "OK, we realize we suck. Our people is suffering, yours are florishing. Here are the keys. There can be only one."
working out the various dependencies for a few packages is just too much work
If you think working out package dependencies by hand is a mess (I definitely agree), why are you using Slackware? On Debian Testing, over 16000 packages are just an "apt-get install foo" away.
If Microsoft integrates a browser with a file manager, or hints at integrating a media player or anything else in the OS, everyone cries foul, so why is that considered good practice in the major *nix environments?
When Microsoft does that, it's an attempt at unfairly strengthening their monopoly. When KDE or GNOME does the same, that's their fair attempts at gaining market share.
Being a convicted monopolist makes all the difference.
What if I want to install Gimp in/opt/gimp instead of where ever the package maintainer decided to put
I'm not saying this isn't a good idea, but I really can't see the point. Why would you want to fight the package manager this way? Why is it so important to you to put apps in non-standard places?
If you get all your rpms from the rpm repository maintained by your distro, everything is fine. If you try mixing-matching distribution rpms, then you will run into problems.
This is still a reason to use Debian. Debian Testing currently has 16237 packages that have all been more or less integration tested with each other. This makes it a lot less common to be forced to install stuff from third party sources than with smaller distros (everybody else AFAIK).
I got that number by downloading the full list of packages in a compressed text file from packages.debian.org and doing zcat thelist | wc -l, and then substracting the six header lines from that result.
try Knoppix. It makes installing Debian easier than installing Windows.
Unforturnately not. Windows comes pre-installed on most systems. Having someone else doing the installation will always be easier than booting off a CD, however easy the process is after that.
I can imagine that those might be weak points for Slackware, and several of the Redhat derivatives, but Debian does well in those areas and has for a long time.
Maybe this doesn't agree with what other people think "stable" means, but my impression is that running stable means that once you've got something working it won't break because of package updates.
IMO "Stable" doesn't attempt to guarantee anything beyond that.
It sounds to me like the decision to go with Unstable probably has at least something to do with your problems.
If you ever find yourself in a similar situation again (let's hope not:-), try getting whoever-makes-the-decisions to run Testing rather than Unstable.
Basically Testing consists of packages that have been in Unstable for a week without getting any critical bugs filed on them. Testing is also kept consistent with regard to dependencies.
Some of the problems you describe (with packages over-writing each other's files) sounds exactly like the kind of problem that is avoided by running Testing.
Anyway, I'm sorry to hear you had such a bad experience with Debian.
Why do you want to run Unstable ("Sid" is the permanent code name for Debian's "Unstable" branch) in a production environment?
Or Fedora for that matter, which afaik is more or less Redhat's answer to Debian's Unstable?
where is the auto-update feature for Firefox á la Windows XP, OS X, YAST or Up2date?
What's wrong with using the OS provided update infrastructure for Firefox as well as all other stuff?
Since I'm on Debian I don't know about your specific examples, but I can upgrade Firefox using apt-get update && apt-get dist-upgrade just like everything else.
Critical FF updates are not found on windowsupdate.microsoft.com!
AFAIK (which isn't that far really), only Microsoft can add stuff to windowsupdate, so the question you really should be asking is IMO:
Hello Windows Update developers! Third party vendors can't use your updating infrastructure! Where is your real auto-update feature?
If what you say about FreeBSD ports is true (I haven't used it so I can't tell), it means that FreeBSD ports are broken, not that automatic updates are a bad idea.
Wouldn't stopping the influx be a better first start? Something like first installing a firewall, then installing some Mozilla derivative and *then* start cleaning the box.
I don't see how cleaning up would do any good as long as the system keeps being a spyware / virus / spambot magnet. You'll just have to do it again after a short while.
Make sure you have a mailing list to which all CVS checkins are logged, and subscribe to this. Then, be open with giving people CVS access if they are interested.
Otherwise lack of developers will kill the project once you grow tired of it.
If I can figure out how to actually submit comments to bugs on the OO site, I will feedback Impress religiously in hopes that it becomes as facile an alternative as the others.
I really hope you succeed better than I did when I tried to do the same. End user bug reports are very valuable to make any project better, so I really hope the OOo guys have started taking their bug reporting system more seriously since then.
Slashdot Mirror
Since it's an independent implementation it contains different bugs from SUN's VM, and you may have better luck with it.
Or it could be that your VM process uses up too much memory and gets killed by the kernel's OOM handler. In that case JRockit will disappear even faster for you.
Disclaimer: I work for BEA.
--------
It's really no harder than that.
Buy a laser instead. IME lasers are hassle free and the toner lasts forever.
Contrast this with ink jet printers that clog if you don't use them every day, and that need new ink all the time.
If you want trouble, buy an ink jet. If you want printouts, buy a laser.
What do you think "Kimmy-boy" wants that would make SK safe from a nuclear attack?
First you're saying that SK are well able to defend themselves, they you say that NK could inflict "massive casualities on the US and/or US allies". Who would those allies be, if not SK?
Something that doesn't seem to have occured to the Chinese leaders is that if they are so keen on unity with Taiwan, why don't they just ask them nicely? As in "OK, we realize we suck. Our people is suffering, yours are florishing. Here are the keys. There can be only one."
If you think working out package dependencies by hand is a mess (I definitely agree), why are you using Slackware? On Debian Testing, over 16000 packages are just an "apt-get install foo" away.
If Microsoft integrates a browser with a file manager, or hints at integrating a media player or anything else in the OS, everyone cries foul, so why is that considered good practice in the major *nix environments?
When Microsoft does that, it's an attempt at unfairly strengthening their monopoly. When KDE or GNOME does the same, that's their fair attempts at gaining market share.
Being a convicted monopolist makes all the difference.
I'm not saying this isn't a good idea, but I really can't see the point. Why would you want to fight the package manager this way? Why is it so important to you to put apps in non-standard places?
This is still a reason to use Debian. Debian Testing currently has 16237 packages that have all been more or less integration tested with each other. This makes it a lot less common to be forced to install stuff from third party sources than with smaller distros (everybody else AFAIK).
I got that number by downloading the full list of packages in a compressed text file from packages.debian.org and doing zcat thelist | wc -l, and then substracting the six header lines from that result.
Unforturnately not. Windows comes pre-installed on most systems. Having someone else doing the installation will always be easier than booting off a CD, however easy the process is after that.
That said, Knoppix rules :-).
You mean just like in Debian?
Software installation is almost mindless.
You mean just like with Debian's apt-get ?
I can imagine that those might be weak points for Slackware, and several of the Redhat derivatives, but Debian does well in those areas and has for a long time.
If everybody would converge on Debian we'd still have the distributed development going but without the cross-distro compatibility problems.
IMO "Stable" doesn't attempt to guarantee anything beyond that.
It reads the repository from a CD.
If you ever find yourself in a similar situation again (let's hope not :-), try getting whoever-makes-the-decisions to run Testing rather than Unstable.
Basically Testing consists of packages that have been in Unstable for a week without getting any critical bugs filed on them. Testing is also kept consistent with regard to dependencies.
Some of the problems you describe (with packages over-writing each other's files) sounds exactly like the kind of problem that is avoided by running Testing.
Anyway, I'm sorry to hear you had such a bad experience with Debian.
Why do you want to run Unstable ("Sid" is the permanent code name for Debian's "Unstable" branch) in a production environment? Or Fedora for that matter, which afaik is more or less Redhat's answer to Debian's Unstable?
As somebody said here, on Gentoo you can get them through e-merge.
On Debian you can "apt-get install blender " or "apt-get install yafray " (or even "apt-get install scons " if you insist on building from source).
I'm sure you should be able to do the same on your favourite distro, just have a look, read some docs or ask your fellow users.
Maybe somebody will even release a movie about it on DVD :-).
What's wrong with using the OS provided update infrastructure for Firefox as well as all other stuff?
Since I'm on Debian I don't know about your specific examples, but I can upgrade Firefox using apt-get update && apt-get dist-upgrade just like everything else.
Critical FF updates are not found on windowsupdate.microsoft.com!
AFAIK (which isn't that far really), only Microsoft can add stuff to windowsupdate, so the question you really should be asking is IMO:
Hello Windows Update developers! Third party vendors can't use your updating infrastructure! Where is your real auto-update feature?
And you can't use Testing because ...?
Yes, SWT. It will use Windows widgets on Windows, and GTK+ on *ix. It's what Eclipse uses.
I'm personally running Debian Testing which is automatically kept free from conflicts like those you describe. And the automated updates of Debian using apt-get work very well.
I don't see how cleaning up would do any good as long as the system keeps being a spyware / virus / spambot magnet. You'll just have to do it again after a short while.
So will they keep their SUN boxes but install Linux on them, or will they buy new PCs for all employees?
Make sure you have a mailing list to which all CVS checkins are logged, and subscribe to this. Then, be open with giving people CVS access if they are interested.
Otherwise lack of developers will kill the project once you grow tired of it.
I really hope you succeed better than I did when I tried to do the same. End user bug reports are very valuable to make any project better, so I really hope the OOo guys have started taking their bug reporting system more seriously since then.
If IBM released the source code for DB2, they would obviously lose a bunch of licensing revenue.
If SUN released the source code to Java, their licensing revenue would go from zero to zero.
I fail to see how the two are comparable.