*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Has anyone tried running valve's steam client with the linux binary compatibility? Which non-obvious steps did you have to take to get it working... and which games have you had success with running under FreeBSD?
I'm not sure if the linux_base-* version will be up to date enough for the glibc version required by the steam client. linux compatibility is usually well behind current Linux and GNU libs and is usually based on a given fedora release. //edit: I think steam depends on pulseaudio as well, no idea how that will work out...
tl;dr: This may be more of a ball ache than you might imagine. If you really want to run steam and proprietary games, it's best to stick to Windows or maybe Linux.
From the Slackware release, I can say that no, Steam does not rely upon Pulse Audio. It does need openAL but afaik that runs on BSD well. Otherwise, yes, I'm not too sure about how the versions of glibc and related libs in BSD ports will compare to what Steam expects to see. Lately, Steam requires Ubuntu 12.04 or better, which is, like 2 years old or so? so quite possibly the stuff in Ports will be current enough.
It would certainly be interesting to hear about the experiment if you do make the attempt! I'd try it myself for kicks, but I haven't got the time at the moment.
I think FreeBSD still provides Fedora Core 6 support as a base for Linux compatibility. The Gentoo layer might be more up to date, but might not be the most compatible.
I am not quite sure how Linux compatibility works on BSDs, but if the sole problem is a too old glibc this should be easily solvable the same way it is solved on Debian Wheezy (which also has a too old glibc): Just use the Ubuntu ones. Have a look here for that solution: https://github.com/GhostSquad57/Stea...ler-for-Wheezy
It's not just glibc. It's the comprised layer itself operates off a string of packages well over a couple of years in age that are outdated for certain usages, but viable enough to get the basics working.
The base Linux layer runs off Fedora Core 10 now on 10.1(?) Take into account Fedora is at the 20s in release and you'll realize how outdated the Linux layer is. It'll run most things, but not all things.
You probably could rip Fedora 20ish binary packages and install them on FreeBSD, but I don't know how well they'd operate.
I don't know how many packages native to the OS steam actually needs, the only problem I ever heard of is a too old glibc, like caused by the fact that Steam comes with its own runtime libraries based on Ubuntu 12.04.
I would at least give it a try, what harm could be done?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.