Slashdot Mirror
Steam Client for Mac Launches, Linux Client On the Way
CyDharttha writes with news that the Mac version of Steam went live today, along with Mac versions of Portal, Team Fortress 2, and many other games. Valve plans to make more games available every Wednesday. Several publications are also reporting that a Linux version of Steam has been confirmed, and is expected within the next few months. Quoting Phoronix:
"Found already within the Steam store are Linux-native games like Unreal Tournament 2004, World of Goo, and titles from id Software such as Enemy Territory: Quake Wars and Doom 3. Now that the Source Engine is officially supported on Linux, some Source-based games will be coming over too. Will we finally see Unreal Tournament 3 surface on Linux too? Only time will tell, but it is something we speculated back in 2008. Postal III is also being released this year atop the Source Engine and it will be offering up a native client. We have confirmed that Valve's latest and popular titles like Half-Life 2, Counter-Strike: Source, and Team Fortress 2 are among the first of the Steam Linux titles, similar to the Mac OS X support. The released Linux client should be available by the end of summer."
GNU is Not Unix ... except when everyone calls Linux UNIX and spends countless hours arguing about it.
One thing OSS is good for is ... the worst possible names on the planet, ones which they think are 'witty' but are often just retarded.
WINE is no exception. It is most certainly a emulation layer, regardless of what they want to call it.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Apple said they plan to change that default, because yes, it is silly and not performant, in a Unicode world.
Also, NFS is usually case-sensitive, so if you copy something NFS -> HFS+ -> NFS you can end up with an unfaithful copy.
pkgsrc will not work on case-insensitive filesystems. In general, many Unix programs have trouble building there.
I go out of my way to install macs with case-sensitive filesystems, which is why the question is coming up.
It's also an indication that the code is shit, and written by Windows morons who don't give a shit about a clean mac port. The case-sensitivity problems are really easy to fix if the developer cares. That's why mac zealots who do give a shit often share this information: it's a warning sign of a bad port.