There are still Christians in Iraq, though - last time I looked around the thought was about 3% of the population, followers of five distinct churches - check http://www.al-bab.com/arab/background/assyrian.htm for example.
You didn't read well enough, AC - it is the NVidia ICD 96.85 with full acceleration - with all tweaks I know to speed it up. It's just that Aero takes way too much, and being only superficial decoration level, doesn't deserve anything else other than switching off. It *may* be once NVidia releases properly optimized Vista drivers, taking into account that, somehow limiting what goes into Aero at driver level, the remainig will be enough for normal OpenGL work, but not yet.
The standard Microsoft WDM NVidia driver is unusable for OpenGL applications. It's as good as software acceleration.
E&S Glaze OpenGL benchmark is about twice as fast on Vista with classic theme, compared to the default Aero. This is on a reasonable dual Opteron system with 4GB memory and Quadro FX560 graphics card (and yes, build 6000 with the currently available NVidia driver).
The first thing I do on Vista is switch to classic (the second being turn off the side bar forever). I wonder if Microsoft have ever heard that their OS is being used by real people to run CAD/CAM applications... not that they want it, but they are forced to.
Will try the same this week with a FireGL card to see if ATI are better.
You lose the license to deploy any application software on the W2K3 server running the virtualization software (VMware | Microsoft Virtual Server) though - unless it is related to it's management. Overall it is a gain - Microsoft policy being "one function - one server"... IMHO it is easier to manage four simply configured virtual servers than one running everything. (when I got Microsoft Virtual server SP1 some times ago, I downloaded the relevant license documentation and even spent some times reading it). On that W2K3 server I have now a few virtual machines configured - an OpenBSD 3.9 firewall, dual-homed on the physical i/f of the server and the virtual internal network, acting as a firewall for the rest of the virtual machines, which are only on the virtual network. It's kinda neat... in a S&M sort of way... The rest is a bunch of NetBSD/FreeBSD/W2Kserver/WXP machines - very convenient for testing stuff (the disk benchmarks were not so good, so take your pick).
I was about to say the same. It started with my laptop - OpenBSD not supporting the modem part of a Xircom combo cardbus adapter, FreeBSD completely failing even to begin installation - and that's the whole sequence of them between 4.4 and 5.3 (haven't tried since). NetBSD (1.6 at the time) ran first time and the Xircom got me connected to the ISP first time. Since then I have it running permanently on some five machines in the office doing various In(ter|tra)net serving and desktop duties; only one box is running FreeBSD (6.0 currently) because NetBSD's INSTALL kernel (at least) did not find the RAID part of a HighPoint card; FreeBSD did - I wanted it mirrored and setting up RaidFrame on a boot disk was a bit over what I wanted to do quickly... Anyway, I carried on adding additional software on that box via source ports; this has been mostly succesful, but nowhere as smooth as is normally with pkgsrc. I do run two or three OpenBSD firewalls (including several at customer sites), but generally performance issues have stopped me from other deployment.
NetBSD performance has been excelent recently; BTW I run -current on all but one system (that one follows the latest release, therefore will get 3.0 this Wednesday).
I also maintain some five Solaris(mostly 10/11) systems - the latest Express with the ZFS id awesome!
Haven't touched the L*x thing for some three years now - don't start me on it...
In favour of Gentoo I might add I had an old Dell P90 (upgraded with an Evergreen AMD to I think 266) which managed about 440 days uptime with Gentoo (it wasn't used too much, though, and I had some problems with the portage database; it retired itself when one of the old 1GB SCSI disks packed away; the rest now is living it's last days running OpenBSD 3.5 as a firewall between a DMZ and a wireless setup). I liked Gentoo because of the BSD portage ideas, which generally work, but again in my view there is nothing to compare to NetBSD pkgsrc - and that is portable itself!
Running Fedora/Core 2 on dual Athlon MP2800, as well as dual Opteron 242; comparing with NetBSD-current (2.0F nowadays) - give me NetBSD any day. You don't want to see the numbers.
And yes, FreeBSD 5.2.1 works fine on AMD64 as well. It was a bit inconlusive compared to NetBSD, but you might like better the FreeBSD install CD giving you the minimum startup packages; with NetBSD-current you install the OS proper in, like, 5 minutes and then spend quite a bit of time compiling from pkgsrc.
SMP is down in the priorities list of the OpenBSD developers, even if recently there have been some advances. Anyway, all it takes to setup an OpenBSD firewall from scratch is 15 minutes... and then just forget it is there ( I have about 5-6 deployed with customers - and not a single call related to them! ).
can be PITA. I even had a poster in my cubicle in the office saying "DON'T USE make update!"... The results may be difficult to predict... and you don't want all your KDE or Gnome packages suddenly disappear because of some weird dependency. I have also an occasion I found myself in a loop - a needs b needs c... needs a...
What I normally do nowadays on my NetBSD systems is use just 'make'; if there are dependencies, it will 'make install' them and if there were older versions of these in place already, it will fail. At this moment one has to use a bit of judgement - cd to the failed package directory and issue 'make replace' - and there is a good deal of chance you will get away with it (well, you may have to manually create a few links in/usr/pkg/lib...).
I know NetBSD purists will say that this is wrong, but it has worked for me more or less OK for about a year; I am on NetBSD 2.0D now, just finished KDE3.2.2 compile (Gnome 2.6 a few days earlier - rocks!), and generally very happy with NetBSD.
I have; indeed sun-jre-1.4.2_05 works fine on the laptop; on the dual-cpu box I use in the office it seems to have problems; I am currently upgrading suse-* packages to see if the problem is in the emulation. (BTW --- > uname -a NetBSD... 2.0A NetBSD 2.0A (GENERIC.MP) #0: Tue Mar 30 00:13:15 BST 2004...:/sys/arch/i386/compile/GENERIC.MP i386 > file/bin/sh/bin/sh: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for NetBSD 2.0A, dynamically linked (uses shared libs), not stripped - both on the workstation and the laptop)
I have been tracking (more or less on a weekly basis) -current on my laptop (Omnibook 6000, before that - -4000, using the same disk without reinstall...), as well as on a couple of servers and a workstation in the office, including an old IPX, some dual Athlon MPs, even a dual Opteron system. One needs a bit of time to get used to some quirks in the process, but the result is most rewarding, especially with the native threads (scheduler activations) in place. I do have occasional glitch - most likely due to my habit of using 'make replace' way too often to upgrade packages, but the stability generally has been excelent. I started with NetBSD at the time as it was the only BSD to support both the modem and the Ethernet part of my Xircom adapter (OpenBSD did not support the modem part, FreeBSD and - at least - Mandrake up to 9.2 - refused to install on the laptop for some reason - never bothered to check, as NetBSD did all what was required...).
If only there were a native pkg for OpenOffice (recent - the earlier port did not work at all under -current for me).
I have been toying since yesterday with
LarsWM . It is based on 9wm, takes a quarter of the memory a typical xterm does, is as fast as a lightning, easy to get used to and super-minimalistic. Compiled straight on my HP-UX 10.20 box, and ofcourse on my Linux laptop. I usually use Enlightenment, which is fine on a reasonable machine, but a bit on the slow side on a HP 715/50 (which also got Gnome 1.0 compiled and used from time to time just for the sake of the exercise - it wasn't the most straightforward operation...). This thing was just what I was looking for; the only gripe being that I will have to create eventually.xmodmaprc file for my HP keyboard.
Slashdot Mirror
There are still Christians in Iraq, though - last time I looked around the thought was about 3% of the population, followers of five distinct churches - check http://www.al-bab.com/arab/background/assyrian.htm for example.
pkgsrc works just fine under Solaris. And it is arguably better than ports.
You didn't read well enough, AC - it is the NVidia ICD 96.85 with full acceleration - with all tweaks I know to speed it up. It's just that Aero takes way too much, and being only superficial decoration level, doesn't deserve anything else other than switching off. It *may* be once NVidia releases properly optimized Vista drivers, taking into account that, somehow limiting what goes into Aero at driver level, the remainig will be enough for normal OpenGL work, but not yet.
The standard Microsoft WDM NVidia driver is unusable for OpenGL applications. It's as good as software acceleration.
E&S Glaze OpenGL benchmark is about twice as fast on Vista with classic theme, compared to the default Aero. This is on a reasonable dual Opteron system with 4GB memory and Quadro FX560 graphics card (and yes, build 6000 with the currently available NVidia driver).
The first thing I do on Vista is switch to classic (the second being turn off the side bar forever). I wonder if Microsoft have ever heard that their OS is being used by real people to run CAD/CAM applications... not that they want it, but they are forced to.
Will try the same this week with a FireGL card to see if ATI are better.
You lose the license to deploy any application software on the W2K3 server running the virtualization software (VMware | Microsoft Virtual Server) though - unless it is related to it's management. Overall it is a gain - Microsoft policy being "one function - one server"... IMHO it is easier to manage four simply configured virtual servers than one running everything.
(when I got Microsoft Virtual server SP1 some times ago, I downloaded the relevant license documentation and even spent some times reading it).
On that W2K3 server I have now a few virtual machines configured - an OpenBSD 3.9 firewall, dual-homed on the physical i/f of the server and the virtual internal network, acting as a firewall for the rest of the virtual machines, which are only on the virtual network. It's kinda neat... in a S&M sort of way... The rest is a bunch of NetBSD/FreeBSD/W2Kserver/WXP machines - very convenient for testing stuff (the disk benchmarks were not so good, so take your pick).
it's a standard part of -current nowadays, not the latest version though.
I was about to say the same. It started with my laptop - OpenBSD not supporting the modem part of a Xircom combo cardbus adapter, FreeBSD completely failing even to begin installation - and that's the whole sequence of them between 4.4 and 5.3 (haven't tried since). NetBSD (1.6 at the time) ran first time and the Xircom got me connected to the ISP first time. Since then I have it running permanently on some five machines in the office doing various In(ter|tra)net serving and desktop duties; only one box is running FreeBSD (6.0 currently) because NetBSD's INSTALL kernel (at least) did not find the RAID part of a HighPoint card; FreeBSD did - I wanted it mirrored and setting up RaidFrame on a boot disk was a bit over what I wanted to do quickly... Anyway, I carried on adding additional software on that box via source ports; this has been mostly succesful, but nowhere as smooth as is normally with pkgsrc. I do run two or three OpenBSD firewalls (including several at customer sites), but generally performance issues have stopped me from other deployment.
NetBSD performance has been excelent recently; BTW I run -current on all but one system (that one follows the latest release, therefore will get 3.0 this Wednesday).
I also maintain some five Solaris(mostly 10/11) systems - the latest Express with the ZFS id awesome!
Haven't touched the L*x thing for some three years now - don't start me on it...
http://www.allthelyrics.com/lyrics/king_crimson/th rak/dinosaur/ .... ....
ignorance has alway been something i excel in
followed by naivete and pride
Since when is 33 less than 25?
In favour of Gentoo I might add I had an old Dell P90 (upgraded with an Evergreen AMD to I think 266) which managed about 440 days uptime with Gentoo (it wasn't used too much, though, and I had some problems with the portage database; it retired itself when one of the old 1GB SCSI disks packed away; the rest now is living it's last days running OpenBSD 3.5 as a firewall between a DMZ and a wireless setup). I liked Gentoo because of the BSD portage ideas, which generally work, but again in my view there is nothing to compare to NetBSD pkgsrc - and that is portable itself!
Go and try SMP in NetBSD-current and then post...
Running Fedora/Core 2 on dual Athlon MP2800, as well as dual Opteron 242; comparing with NetBSD-current (2.0F nowadays) - give me NetBSD any day. You don't want to see the numbers.
And yes, FreeBSD 5.2.1 works fine on AMD64 as well. It was a bit inconlusive compared to NetBSD, but you might like better the FreeBSD install CD giving you the minimum startup packages; with NetBSD-current you install the OS proper in, like, 5 minutes and then spend quite a bit of time compiling from pkgsrc.
SMP is down in the priorities list of the OpenBSD developers, even if recently there have been some advances. Anyway, all it takes to setup an OpenBSD firewall from scratch is 15 minutes... and then just forget it is there ( I have about 5-6 deployed with customers - and not a single call related to them! ).
What I normally do nowadays on my NetBSD systems is use just 'make'; if there are dependencies, it will 'make install' them and if there were older versions of these in place already, it will fail. At this moment one has to use a bit of judgement - cd to the failed package directory and issue 'make replace' - and there is a good deal of chance you will get away with it (well, you may have to manually create a few links in
I know NetBSD purists will say that this is wrong, but it has worked for me more or less OK for about a year; I am on NetBSD 2.0D now, just finished KDE3.2.2 compile (Gnome 2.6 a few days earlier - rocks!), and generally very happy with NetBSD.
Got it... thanks for reminding me that it works...
/emul/linux tree - OOo fails miserably...
It might be useful for someone - DON'T symlink your home directory to the
I have; indeed sun-jre-1.4.2_05 works fine on the laptop; on the dual-cpu box I use in the office it seems to have problems; I am currently upgrading suse-* packages to see if the problem is in the emulation. ... 2.0A NetBSD 2.0A (GENERIC.MP) #0: Tue Mar 30 00:13:15 BST 2004 ...:/sys/arch/i386/compile/GENERIC.MP i386 /bin/sh /bin/sh: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for NetBSD 2.0A, dynamically linked (uses shared libs), not stripped
(BTW ---
> uname -a
NetBSD
> file
- both on the workstation and the laptop)
I have been tracking (more or less on a weekly basis) -current on my laptop (Omnibook 6000, before that - -4000, using the same disk without reinstall...), as well as on a couple of servers and a workstation in the office, including an old IPX, some dual Athlon MPs, even a dual Opteron system. One needs a bit of time to get used to some quirks in the process, but the result is most rewarding, especially with the native threads (scheduler activations) in place. I do have occasional glitch - most likely due to my habit of using 'make replace' way too often to upgrade packages, but the stability generally has been excelent. I started with NetBSD at the time as it was the only BSD to support both the modem and the Ethernet part of my Xircom adapter (OpenBSD did not support the modem part, FreeBSD and - at least - Mandrake up to 9.2 - refused to install on the laptop for some reason - never bothered to check, as NetBSD did all what was required...).
If only there were a native pkg for OpenOffice (recent - the earlier port did not work at all under -current for me).
I have been toying since yesterday with LarsWM . It is based on 9wm, takes a quarter of the memory a typical xterm does, is as fast as a lightning, easy to get used to and super-minimalistic. Compiled straight on my HP-UX 10.20 box, and ofcourse on my Linux laptop. I usually use Enlightenment, which is fine on a reasonable machine, but a bit on the slow side on a HP 715/50 (which also got Gnome 1.0 compiled and used from time to time just for the sake of the exercise - it wasn't the most straightforward operation...). This thing was just what I was looking for; the only gripe being that I will have to create eventually .xmodmaprc file for my HP keyboard.