Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Have searched and searched but have not found what I am looking for. Maybe anyone behind another screen can help me.
Did not know where to post this thread so I went with the easiest.
I am running fedora 20 with mate, x86_64.
-----------------------------
Linux XXX.XXX.XXX 3.15.6-200.fc20.x86_64 #1 SMP Fri Jul 18 02:36:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
-----------------------------
I recently was the victim och the 16-bit bug in kernel 3.14 but it has been looking up now since the arrival och 3.15. But I still need to run "echo 1 > /proc/sys/abi/ldt16" to get the old program to run under wine.
That why I thought of creating a .sh script to run when I log in. The problem is that it works when I run it manually but noting happens when I but the script in .bash_profile.
This is the script (.wine16bit.sh)
-----------------------------
!/bin/bash
# A script to enable 16-bit for Wine
# 2014-07-25
I have put it in bash_profile as /home/krister/.wine16bit.sh
I have hidden it and made sure it is able to be executed. As I said above it works when I run it after I have logged in. Have added to visudo my user so I can run scripts.
If it is going to be set always, why not put in an init script such as rc.local? That way it gets set on boot, and no need to create complicated methods for all users to use to set it.
If it is going to be set always, why not put in an init script such as rc.local?
Linux distributions commonly use /etc/sysctl.conf. Additionally Fedora (now?) has /etc/sysctl.d/ for local additions.
Quote:
Originally Posted by jpollard
That way it gets set on boot, and no need to create complicated methods for all users to use to set it.
In this case it's quite valid to "create complicated methods", do check the comment in commit Id fa81511bb0bbb2b1aace3695ce869da9762624ff.
I would suggest the OP creates (or modifies) the script that starts WINE and not only add a "echo 1 > /proc/sys/abi/ldt16" before starting WINE but also a "echo 0 > /proc/sys/abi/ldt16" when exiting.
T3RM1NVT0R: I'am sorry to say that your solution don't work. It works when I run it manually after I have logged in (have to sudo it).
unSpawn: Your thoughts are interesting and I think that your solution would be best. Why enable 16-bit all of the time? But how would I make it do this? Could you point me in the right direction or give me a hint where to look. Should I modify the link that starts the program, how would I disable it when I quit the program?
This is the current link that is on my desktop to start the program:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.