Linked by Thom Holwerda on Mon 27th Nov 2006 10:55 UTC, submitted by Jean Claude
Linux French députés' offices will be equipped with a Linux operating system and open source productivity software. There will be 1154 French parliamentary workstations running on an open source OS, with OpenOffice.org, Firefox and an open source email client.
Thread beginning with comment 185701
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Things to consider
by Almindor on Mon 27th Nov 2006 15:22 UTC in reply to "RE[4]: Things to consider"
Almindor
Member since:
2006-01-16

OK in linux most of shared libraries that you must install for a given application will never be used for another application; so to install 10 applications you will need to install 100 shared libraries that almost all will never be shared because there is no app other than that you installed will use it!

Wrong. From libc and stuff like openSSL to gtk and qt, all are pretty well used by many apps. Only few fringe libs aren't actualy "shared".

The dll hell argument is partially right, but taking all the shared stuff with each copy of program is stupid. You could just as well go with static linking. Try telling that to security experts wise guy.


Compilation or image processing are CPU intensive tasks not memory intensive tasks Mr Genius. You have to try P2P networking with Gigabytes of files sharable or better try java based applications like Azureus and see the results, or open 20 tabs on firefox with heavy graphics and flash aniamtions; add to that a movie that you would like to watch with xine based player.


Java based applications suck equally well on most platforms. Windows happens to have a bit better java implementation (as can be tested by the fact that many java applets crash here while work in windows) but that's about it. It has nothing to do with linux per-se.

Btw. linking is real ram and cpu killer. Ever tried smart-linking a half-million lines of code thing? Probably not. Suffice to say, I had to kill ld AND X. In windows I'd have to kill windows tho ;) .

Image processing is a RAM killer too. Try doing something on 4000 by 4000 image then we can talk again.

Point is we're comparing apples and oranges.

And thing is, windows IO and memory handling is worse than linux one. I can't prove it, but I can sure feel it every day.

Reply Parent Score: 5

RE[6]: Things to consider
by hamster on Mon 27th Nov 2006 16:43 in reply to "RE[5]: Things to consider"
hamster Member since:
2006-10-06

Thats not my experince... last time i had to setup a linux server it needed not only a lot more but double the amount of ram windows needed. It was a fedora core 3. Even without any load on the server it kinda walked insted of running as win2k3 did.

Reply Parent Score: 2

RE[7]: Things to consider
by akro on Mon 27th Nov 2006 16:56 in reply to "RE[6]: Things to consider"
akro Member since:
2005-07-06

How much crap did you leave in the install....

Even Microsoft realizes the everything and a the sink on the server is a bad idea. Look at what they are doing with Longhorn server... between striped down out of the box (no gui) and power shell it's clear the minimal server route with a strong command line is the best way and even microsoft sees this as the case...I think a lot of MCSE's are gonna be in trouble soon...

Reply Parent Score: 3

RE[7]: Things to consider
by dylansmrjones on Mon 27th Nov 2006 21:31 in reply to "RE[6]: Things to consider"
dylansmrjones Member since:
2005-10-02

Hmm... My Windows 2003 Server works as a Desktop OS and it uses pretty much the same amount of RAM as Gnome does. The difference is that in Linux the RAM is used as "swap" and doesn't use the harddisk swap at all, while in Win2K3 it doesn't use RAM that way, but uses as much swap as Linux uses cache. Vista uses the RAM as cache.

It's been a long time ago since I used FC3, so I dare not say if it is particularly memory hungry, but FC3 was the reason why I switched to LFS (and today gentoo).

Reply Parent Score: 1