Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
This is for Fedora but should be applicable to most xorg setups.
http://serverfault.com/questions/148491/how-can-i-start-an-x11-session-on-my-headless-fedora-13-server
If you've actually got decent GPU performance on the server then GPU Passthrough would be a good option for you.
http://nimbledais.com/?p=21
But home many servers actually have decent GPUs? Unless you're bitcoin mining ;)
Headless Linux would be nearly useless in this situation as most of the games you'll want to stream will be Windows based (And NO SteamOS won't play Windows games out of the box, Valve don't have a super-secret way to run windows games without installing Windows OS!)
If you go with a Linux server then you'll have to do the hard work off installing wine and all the required tweaking to get games to run poorly. or install a Virtual Machine to run Windows in. Which would be silly resource wise! may as well just install windows on to the server and remove a lot of hassle and performance issues.
But they do have a not-so-secret one.
http://www.winehq.org/about/
https://appdb.winehq.org/objectManager.php?sClass=version&iId=19444
http://en.wikipedia.org/wiki/Wayland_(display_server_protocol)
It's not a VM. It's native. Wine is a string of custom libraries that literally take Windows input and give linux output to linux. The equivalent of rewriting DirectX, Win32 APIs etc to sit on top of Linux drivers and kernel etc. Theres no background processes or emulated computer underneath, just the application and it's commands being literally translated to linux ones of the fly. If it runs, it runs like it's native at full hardware speed, much faster than passtrough with a VM, which is actually quite slow.
Steam does not have to launch in 'Windows mode' or even touch it's Linux or OS X version on that level, there are many "Ports" out there that are basically using Wine to translate the Windows version of a game already. What steam can do is install and launch a "bottle", which is a predesigned environment (you can select your bottle to replicateany version of Windows, XP, Vista, 7, 8 etc) basically composed of these translation DLLs that are seen by the game as normal Windows ones but actually translate whatever is sent to them to Linux/OpenGL data and pass it on to Linux hardware libraries.
Have a look at crossover's compatibility list, a commercial release of Wine that does all the technical bits of preconfiguring Wine to work on OS X (and it's UNIX core). Any game that works for crossover works for Wine as it's Wine's code in Crossover. Wine devs have estimated that the max slowdown you can experience in your "Wineskinned game" from Wine vs real Windows is 3%, the problem is that it doesn't work on games that utilize XNA, certain forms of .NET or anything that hasn't been reverse engineered by the open source Wine community yet.
http://www.codeweavers.com/products/cxgames/
And for those who won't look at linkies here's a list of the first few on the page.
Civ5, GuildWars, Diablo 3, Perfect World, Rift, SC2, Skyrim. I even own a Wineskinned (out of the box) Mac copy of X3:Albion Prelude and Wineskinned EVE:Online. (Wineskinning is basically making an environment for a program individually) Devs can and will fix that if Linux/SteamOS gets off the ground.