My middle and high schools had TI-81s for students to use if they did not buy their own (I bought a TI-83 for use in non-math classes, like physics...)
If you read the summary, it clearly says the vector of attack was web servers (such as Apache Tomcat). Most desktops are not running a web server - thus not vulnerable.
There's plenty of legacy code for SPARC, MIPS, and POWER. And a lot of code can be recompiled for a different platform without much trouble (and there's plenty that can't).
I suppose that would be on the GCC team then, yes? I'm using it myself (v4.8). I suppose they could try LLVM, but I have no idea how viable that is on AIX.
Operating System - Depends on the use case Database - Oracle - and what does Oracle prefer it run on? Linux or Solaris Web Server - Apache HTTPD beats IIS anyday Server OS? What kind of server? Solaris, AIX, Free/Net/OpenBSD, and IRIX beat Windows anyday. Compiler? The one that's for the platform you're running. ICC on Intel, SunStudio, MIPSPro, etc. And XCode isn't a compiler - it's an IDE. The compiler is either GCC or LLVM
They probably will, much to my (any many others) dismay. The supported Linux options will not go over well with a lot of people I'm willing to bet. I'm seeing enterprises shying away from the abomination that is RHEL 7 because of systemd.
Except they've been targeting DDoS attacks by request. They've taken down (in the past couple of days) League of Legends, Battle.net, PSN, and I think they hit the XBox network earlier.
If you use a graphics installer for Redhat you are not really using a window manager like KDE, Gnome or even Xfce. Anyway have many users are using RHEL for the desktop? (although you could). As for installers for Documentum, Matlab, Oracle, etc they are specific to the software application and will run under most window managers. Actually you would normally install software like what you just mentioned via client software which could even be on a Microsoft Widows machine.
As for "trying to get people not to use the default GUI" that is the wrong thing to say since if you are the system admin it is very easy to set up particular users to only use a specific Window Manager using "kickstart" (very useful if you want a consistent configuration across all machines). Of course you could do a manual installation as well but that can get very tedious across hundreds of machines.
There are cases where that works, and a lot that it does not. For production environments, it's not hard to pull off. In my case, in a lab environment, it does not work. We are strongly pushing users to avoid default setups for CentOS/RHEL 7, use 6 when possible, etc, but for the lab, it boils down to the users being in control of the VMs.
(Ultimately, I'm still pissed at the GNOME team (and Red Hat) for having a desktop environment that composititing cannot be disabled, and soft renders the whole thing when GPU isn't found. And then believing that it's a good idea! The Linux desktop will be its own killer.)
You are stuck with either GNOME or KDE for RHEL, and most users are going to expect GNOME. We also run into where our users have to emulate the users' environments, which often means GNOME for the GUI. Third, there are a lot of situations where a GUI is required (say, the default installer for a lot of things, like Documentum, Matlab, Oracle, etc). Trying to get people not to use the default GUI is near impossible.
Slashdot Mirror
My middle and high schools had TI-81s for students to use if they did not buy their own (I bought a TI-83 for use in non-math classes, like physics...)
If you read the summary, it clearly says the vector of attack was web servers (such as Apache Tomcat). Most desktops are not running a web server - thus not vulnerable.
If you notice, this doesn't effect desktop Linux users. Only servers.
Except we don't see systemd solving any problems. It is a solution searching for a problem.
We're selling them because there is demand for them.
Also, this device clearly is not targeted to be a desktop replacement.
There's plenty of legacy code for SPARC, MIPS, and POWER. And a lot of code can be recompiled for a different platform without much trouble (and there's plenty that can't).
Honest question:
What can you do on x86, that you can't do on POWER or MIPS?
Unless the firmware flash improved performance...
I suppose that would be on the GCC team then, yes? I'm using it myself (v4.8). I suppose they could try LLVM, but I have no idea how viable that is on AIX.
Operating System - Depends on the use case
Database - Oracle - and what does Oracle prefer it run on? Linux or Solaris
Web Server - Apache HTTPD beats IIS anyday
Server OS? What kind of server? Solaris, AIX, Free/Net/OpenBSD, and IRIX beat Windows anyday.
Compiler? The one that's for the platform you're running. ICC on Intel, SunStudio, MIPSPro, etc. And XCode isn't a compiler - it's an IDE. The compiler is either GCC or LLVM
Doesn't work that way. For the business world, Red Hat IS Linux. And a lot of things that get pushed in other distros start in Fedora (RH).
My SGI and Sun knowledge are why I'm employed....
You mean where management ignores the sysadmin and developer's requests and says you're using this because we paid for it.
Can you buy *ANY* prebuilt, 1U or 2U system, commercial, fully loaded, for that price? I didn't think so.
Also, if you want to cheap out on compilers, GCC is a perfectly valid option on AIX.
And nobody ever got fired for choosing IBM.
Actually, GCC runs just fine on these systems.
Sun's certainly on that list too! I wish there was a current SPARC workstation.
They probably will, much to my (any many others) dismay. The supported Linux options will not go over well with a lot of people I'm willing to bet. I'm seeing enterprises shying away from the abomination that is RHEL 7 because of systemd.
More like Microsoft keeping to a release schedule? Vista and Office 2007 were way off track, but they've been pretty constant since then.
Actually, being good at Exchange requires being good at PowerShell these days.
Except they've been targeting DDoS attacks by request. They've taken down (in the past couple of days) League of Legends, Battle.net, PSN, and I think they hit the XBox network earlier.
You'd need classic mode to do that, which was phased out a lot sooner. Rosetta was for running applications that were compiled for OS X on PPC.
Plenty. Matlab, Maya, Documentum, Cisco VPN client, shall I continue? There is plenty of closed, commercial software for Linux.
If you use a graphics installer for Redhat you are not really using a window manager like KDE, Gnome or even Xfce. Anyway have many users are using RHEL for the desktop? (although you could). As for installers for Documentum, Matlab, Oracle, etc they are specific to the software application and will run under most window managers. Actually you would normally install software like what you just mentioned via client software which could even be on a Microsoft Widows machine.
As for "trying to get people not to use the default GUI" that is the wrong thing to say since if you are the system admin it is very easy to set up particular users to only use a specific Window Manager using "kickstart" (very useful if you want a consistent configuration across all machines). Of course you could do a manual installation as well but that can get very tedious across hundreds of machines.
There are cases where that works, and a lot that it does not. For production environments, it's not hard to pull off. In my case, in a lab environment, it does not work. We are strongly pushing users to avoid default setups for CentOS/RHEL 7, use 6 when possible, etc, but for the lab, it boils down to the users being in control of the VMs.
(Ultimately, I'm still pissed at the GNOME team (and Red Hat) for having a desktop environment that composititing cannot be disabled, and soft renders the whole thing when GPU isn't found. And then believing that it's a good idea! The Linux desktop will be its own killer.)
You are stuck with either GNOME or KDE for RHEL, and most users are going to expect GNOME. We also run into where our users have to emulate the users' environments, which often means GNOME for the GUI. Third, there are a lot of situations where a GUI is required (say, the default installer for a lot of things, like Documentum, Matlab, Oracle, etc). Trying to get people not to use the default GUI is near impossible.