Results 1 to 3 of 3

Thread: How do I allow other users to use programs in my main account?

  1. #1
    Join Date
    Sep 2005
    Beans
    61

    How do I allow other users to use programs in my main account?

    I have Warcraft and other games installed under WINE on my main account.

    I would like to let my son play these games on his own account.

    However, I can't see any way to do this.

    any help would be appreciated.

    Thanks.

  2. #2
    Join Date
    Apr 2010
    Location
    Denver, Colorado
    Beans
    802
    Distro
    Kubuntu 10.04 Lucid Lynx

    Re: How do I allow other users to use programs in my main account?

    You need to change the permissions on the file to allow "others" to read,write, and execute or create a group like "games" and give the permissions 777 to the files you want to allow. And include your sons user name in the group.
    KDE SC 4.4

  3. #3
    Join Date
    Jan 2006
    Location
    U.S.A.
    Beans
    971

    Re: How do I allow other users to use programs in my main account?

    Quote Originally Posted by -humanaut- View Post
    You need to change the permissions on the file to allow "others" to read,write, and execute or create a group like "games" and give the permissions 777 to the files you want to allow. And include your sons user name in the group.
    After you have created the group (e.g. "games"), you would change the group identifier on the files in question (in Nautilus or using the command 'chown' ("change owner"). To execute the command recursively on an entire directory and all its subdirectories, you add the option '-R' (refer to 'man chown'). For example, to make a folder called "games" in your home directory accessible to users who are members of the group "games", you would do:
    Code:
    chown -R :games ~/games
    Now, having done that, exactly what access members of group "games" have is governed by the specific group permissions that are set for each file. You change permissions with the command 'chmod' ("change mode", which can also be applied recursively).

    Setting permissions to 777 makes all those files (including any that are executables) accessible to anyone and everyone. That's generally a bad idea. The only files you'll generally see with 777 permissions should be temporary files and symbolic links. You shouldn't have to set 777 permissions for another user to be able to use files, unless it's somebody who does not have an account on the system (i.e., a remote user logged in anonymously). If there is something Wine-specific I don't know about, somebody please correct me.

    For security, you typically want to limit the write access you give others (e.g., mode 750 on directories, 640 on files, and 750 on executable files, which amounts to read-write access for you, read-only access for the group (so people can't accidentally uninstall your applications or delete your files, etc.), and no access for "others". Something like that is probably set up as your default (automatically used when you create files -- see 'man umask'). If you take that more cautious approach, then you need to build from there, and specifically allow write access where group members should have it.

    If you can't figure out what group members need write access to, then just give the group the same privileges as owner (i.e. 770, 660, etc.) That approach is probably quite suitable in this case. If you look, you may find this is already the case (depending on the installation process and/or your umask). If they are the same, then all you need to do is create the group (e.g. "games"), 'chown -R :games <the files>', and add your son to group 'games'.
    Last edited by BoneKracker; May 26th, 2010 at 05:50 AM.
    Favorite man page quote: "The backreference \n, where n is a single digit, matches the substring previously matched by the nth parenthesized subexpression of the regular expression." [excerpt from grep(1)]

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •