Maybe you should try scripting a configuration change by manipulating a text file versus manipulating the registry. When fixing common issues remotely, the repeatability you get from a script is nice. When the script works reliably and it doesn't hurt your brain to look at, that's nice too.
If Office were written in pure.NET and all of the libraries were available everywhere, then it would run on the platform of your choosing. A Java application would have the same caveats.
However Mono's primary goal is NOT portability to.NET applications. It's primary goal is to provide developers a top notch development platform on Linux (using native technologies like dbus, GTK, etc), which it does very well.
Oh, and good luck making an office suite using nothing outside the POSIX standard.
That doesn't solve the stability problem. If one of those worker threads does something naughty, the whole process is going down.
Although process creation time on Windows is slow compared to other OSes its more than fast enough for spawning a process per tab. Chrome and IE8 have already proved this in the real world.
...and trying to find a way to unify the gaming experience across mobile platforms, computers, and consoles.
I got it! We'll build a giant computer network that spans the entire globe. Then we can hook all of these mobile platforms, computers, and consoles up to it so they can communicate seamlessly. In fact, we can hook just about anything up to it. I propose we call this new invention "The Internet."
If I'm reading this right, the point of the web application is to manage the VMs. If it didn't have privilege to manage (or destroy in this case) the VMs, it would be pretty useless.
Except CentOS follows upstream's releases quite closely. Ubuntu essentially takes Debian unstable once in a while and tries to stabilize it as much as they can and release it within 6 months.
Compare that to the amount of time it takes for Red Hat or Debian to stabilize a release. Usually they won't release until they're happy with it either, unlike Ubuntu's "stick to the schedule at (almost) all costs" approach.
In the article they specifically mention "work group server" where they have a 77% share. The big problem being that they leveraged their desktop OS monopoly in an anti competitive manner to gain that share.
I hate to break it to you, but Postgres is owned by its individual contributors. There is no copyright assignment as there is with MySQL. Additionally, its BSD licensed so anyone can do pretty much anything with it.
After doing this, my old IBM T30 runs full screen flash videos much smoother. Even with external speakers, I'm unable to tell a difference in audio quality except that it doesn't stutter.
Many Microsoft products cluster pretty well. Bring one down. Patch it. Bring it back up. Repeat with the other server. Works well in the event of hardware failures too.
They don't need to go GPL, you can write an ext driver under whatever license you want. The important part is the patents, which are never really safe given the rather thick minefield of software patents out there.
I'd be interested to see UDF become the standard. I believe Vista actually has decent support for it and the drivers work in XP. Linux and OSX also have semi-decent support AFAIK.
WINE is just Win32 for POSIXy platforms. It's not able to rewrite x86 binary for ARM. You could perhaps take Windows software compiled for an ARM processor and run it, but that kind of defeats the point of using Linux for portability in the first place. KVM/Xen also do not rewrite binary for other architectures. QEMU could do it, but performance and battery life would drop dramatically.
Samba3 domains have the old style NT system policies, but not group policy. Group policy is quite a bit more powerful and is much easier to find precooked templates for these days.
As the Samba devs have found out, group policy is very tied to AD so needs to wait until AD server support lands.
Samba4 will be able to replace Windows Active Directory servers, or serve along side of them. Seamlessly.
This includes being able to use use the standard admin tools, 3rd party tools and schema extensions, replication to Windows servers, group policy, Kerberos with PAC, etc, etc.
Slashdot Mirror
Maybe you should try scripting a configuration change by manipulating a text file versus manipulating the registry. When fixing common issues remotely, the repeatability you get from a script is nice. When the script works reliably and it doesn't hurt your brain to look at, that's nice too.
If Office were written in pure .NET and all of the libraries were available everywhere, then it would run on the platform of your choosing. A Java application would have the same caveats.
However Mono's primary goal is NOT portability to .NET applications. It's primary goal is to provide developers a top notch development platform on Linux (using native technologies like dbus, GTK, etc), which it does very well.
Oh, and good luck making an office suite using nothing outside the POSIX standard.
Oh yeah? Well I say that DRM promotes piracy.
You can download all the SRPMs for free. How do you get any more open source than that?
The latency issues many people had initially were actually from Pulse/ALSA bugs. One of the design goals of Pulse is lower latency than ALSA + dmix.
Connect(m_ui.messageLineEdit, SIGNAL("textChanged(QString)"), this, SLOT("TextChangedSlot(QString)"));
Connect(m_ui.sendButton, SIGNAL("clicked(bool)"), this, SLOT("SendClickedSlot()"));
Connect(m_ui.actionChangeNickname, SIGNAL("triggered(bool)"), this, SLOT("ChangeNickname()"));
Connect(m_ui.actionAboutQt, SIGNAL("triggered(bool)"), this, SLOT("AboutQt()"));
Connect(qApp, SIGNAL("lastWindowClosed()"), this, SLOT("Exiting()"));
Magic strings galore. It's completely out of place in CLI land.
That doesn't solve the stability problem. If one of those worker threads does something naughty, the whole process is going down.
Although process creation time on Windows is slow compared to other OSes its more than fast enough for spawning a process per tab. Chrome and IE8 have already proved this in the real world.
...and trying to find a way to unify the gaming experience across mobile platforms, computers, and consoles.
I got it! We'll build a giant computer network that spans the entire globe. Then we can hook all of these mobile platforms, computers, and consoles up to it so they can communicate seamlessly. In fact, we can hook just about anything up to it. I propose we call this new invention "The Internet."
If I'm reading this right, the point of the web application is to manage the VMs. If it didn't have privilege to manage (or destroy in this case) the VMs, it would be pretty useless.
Except CentOS follows upstream's releases quite closely. Ubuntu essentially takes Debian unstable once in a while and tries to stabilize it as much as they can and release it within 6 months.
Compare that to the amount of time it takes for Red Hat or Debian to stabilize a release. Usually they won't release until they're happy with it either, unlike Ubuntu's "stick to the schedule at (almost) all costs" approach.
Because they can blame you for pushing them into an OS they otherwise wouldn't have used.
You do know that the OpenDocument Foundation had nothing to do with ODF's creation, right? That would be OASIS.
In the article they specifically mention "work group server" where they have a 77% share. The big problem being that they leveraged their desktop OS monopoly in an anti competitive manner to gain that share.
I hate to break it to you, but Postgres is owned by its individual contributors. There is no copyright assignment as there is with MySQL. Additionally, its BSD licensed so anyone can do pretty much anything with it.
Mono already has a good chunk of the ASP.NET 3.5 APIs. Enough to get most ASP.NET MVC applications up and running with this newly open source library.
Try changing your the audio resample method on pulse audio as described here: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/330006/comments/14
After doing this, my old IBM T30 runs full screen flash videos much smoother. Even with external speakers, I'm unable to tell a difference in audio quality except that it doesn't stutter.
I don't believe the implementation of long file names in SMB have anything to do with long file names in FAT32.
What fantasy world are you living in? Although antitrust laws may say the government _should_ do that, they almost certainly won't.
Use puppet. Not only can you configure policies and configuration, but you can _sanely_ manage software as well.
Many Microsoft products cluster pretty well. Bring one down. Patch it. Bring it back up. Repeat with the other server. Works well in the event of hardware failures too.
Or perhaps more of a "let's see if we can pull this shit off".
Personally I hope the judge answers with a resounding "NO".
They don't need to go GPL, you can write an ext driver under whatever license you want. The important part is the patents, which are never really safe given the rather thick minefield of software patents out there.
I'd be interested to see UDF become the standard. I believe Vista actually has decent support for it and the drivers work in XP. Linux and OSX also have semi-decent support AFAIK.
WINE is just Win32 for POSIXy platforms. It's not able to rewrite x86 binary for ARM. You could perhaps take Windows software compiled for an ARM processor and run it, but that kind of defeats the point of using Linux for portability in the first place. KVM/Xen also do not rewrite binary for other architectures. QEMU could do it, but performance and battery life would drop dramatically.
Samba3 domains have the old style NT system policies, but not group policy. Group policy is quite a bit more powerful and is much easier to find precooked templates for these days.
As the Samba devs have found out, group policy is very tied to AD so needs to wait until AD server support lands.
Samba4 will be able to replace Windows Active Directory servers, or serve along side of them. Seamlessly.
This includes being able to use use the standard admin tools, 3rd party tools and schema extensions, replication to Windows servers, group policy, Kerberos with PAC, etc, etc.