Steam for Linux > Limited Beta > Topic Details
Santa Claus Dec 2, 2012 @ 2:52am
All content installed to ~/Steam instead of /usr/local
All game content that my be shared beetween users on a computer should placed in /usr/local os something similar instead of /home/user.
Showing 1-13 of 13 comments
< >
kigucdoshu Dec 2, 2012 @ 2:57am 
Then put it there yourself and symlink it. Steam would need root permissions to put it there by itself, which needless to say it shouldn't have.
GER | tuxator Dec 2, 2012 @ 3:06am 
I guess that would be impracticle due to one reason: There is that Steam beta thingi. If now one person want's to be part of it but the other person doesn't...you've a problem. And aside from the Steam binary there isn't anything that could be shared between multiple users.
Barbarian Dec 2, 2012 @ 6:40am 
I agree with defaultusername. I'd be very uncomfortable giving steam root access to my machine, not because I believe they'll do something actively malicious, but because if there's a bug without root, it might crash or self-destruct, or accidentally delete an important file within ~/Steam, but with root permissions bugs could be a hell of a lot scarier. If it's something you feel your system needs, just symlink it, it's a trivial thing to do.
Last edited by Barbarian; Dec 2, 2012 @ 6:47am
Santa Claus Dec 2, 2012 @ 7:06am 
It should be selectable. One option to installing ito home, other is installing for all users.
This could true for all installations. I expect you won't install any application next to the kernel. Put executables to home is not the right way however if someone want to do that who am I to hold back him.
I do not want to run the whole stam with root acces. Only I request a function that make the installed game movable and/or installable to a common Steam directory. For you and me the symlinking is trivial, but Steam will open for general users without real knowledeg how an FS works, what is linikng and so on.
kigucdoshu Dec 2, 2012 @ 7:21am 
Putting executables in /home is indeed not the best practice, but requesting root priviliges to avoid it is orders of magnitude worse.

Personally, I will be happy as long as Steam never asks me for my password. If others wish to play fast and loose with their security, who am I to stop them. Installing games in ~ should remain the default behavior however.
Mr. Soul Dec 2, 2012 @ 12:53pm 
What about if steam created a new steam account during the installer process? Then it could have its own folder in /usr/share/steam or something like that with full write permissions. You can then share data amongst users without resorting to running steam as root.
kigucdoshu Dec 2, 2012 @ 1:22pm 
That would still require root access when creating the user, and is thus no better than simply requesting elevated priviliges when installing games.
Last edited by kigucdoshu; Dec 2, 2012 @ 1:23pm
Neutron Dec 2, 2012 @ 1:52pm 
I was wondering that is it possible to have SteamApps in common directory just by adding a group for all steam users, create a folder in /opt or /usr/local for Steam, make the folder setgid steam and group writable and then add it as installation directory in Steam settings? Never tried such a setup though so I don't know if it would still have permission problems. Sure, Steam would still be in each users' home directory, but at least games wouldn't.
kigucdoshu Dec 2, 2012 @ 1:56pm 
That should absolutely be possible. I don't see how you could get permission problems as long as Steam never tries to write to .. or some such nonsense.
DaVince Dec 2, 2012 @ 2:11pm 
Earlier ideas involve adding a steam user group which each Steam user is added to. The group would have read/write/exec access to an /opt/Steam directory, which would contain all the "common" game files. Setting up the user group would happen at the Steam installation stage (so during the configuration stage in the package manager). I kind of like this idea.

Edit: Ah, Neutron said it.
Last edited by DaVince; Dec 2, 2012 @ 2:12pm
nathan Dec 2, 2012 @ 2:27pm 
Originally posted by DaVince:
Earlier ideas involve adding a steam user group which each Steam user is added to...<snip>
I think this is probably the best solution. Neutron makes a very good point. A single elevation request to add a user and group, then to create /opt/Steam would be marvellous. While it's a little hairy to give a company Root access for *anything*, it's also not unheard of and a simpler solution than dumping the entire Steam directory into each user's homedir.
kigucdoshu Dec 2, 2012 @ 2:55pm 
Becoming root once is functionally identical to becoming root a thousand times. Creating the group and granting the necessary permissions should not be handled by Steam (or if it is, it should be possible for the user to do it themselves and never make Steam root).

I don't see how anything could be simpler than dumbing everything in ~. Better, possibly. Simpler, no.
Last edited by kigucdoshu; Dec 2, 2012 @ 2:55pm
Neutron Dec 2, 2012 @ 3:35pm 
I agree that Steam becoming root is bad, and it could be avoided if Valve continued to initiate Steam bootstrap with installation of steam.deb and just add groupadd into deb's installation script as it is normal for packages to add users and groups during installation and then the client wouldn't need root permissions (provided that Valve sets up their own Steam deb repository instead of directly messing with packaged files).

If users want to have games outside of home, I think they should set it up themselves, which would involve making the directory, setting proper setgid'ed permissions and adding the directory into Steam as installation directory in Steam settings. Only thing for Steam to do would be to always ensure that the files have group read/write-permissions so it could update the game files regardless of who log on.

I'm not convinced that adding a steam user would be absolutely necessary as it would require setuid-binaries, which I think are a bit frowned upon these days or at least it seemed like that a while ago when distros were eager to get rid of them and setgid'ed directory seems to achieve the same thing.
Last edited by Neutron; Dec 2, 2012 @ 3:39pm
Showing 1-13 of 13 comments
< >
Per page: 15 30 50
Date Posted: Dec 2, 2012 @ 2:52am
Posts: 13