The translation is temporarily closed for contributions due to maintenance, please come back later.


Pre-Basic Installation Tasksand Usage
(itstool) path: sect2/title
Basic Installation and Usage
Context English Turkish (tr_TR) State
Using a Common Installation of WINE
If, on the other hand, there are many applications to be shared, or they require specific tuning in order to work correctly, a different approach may be required. In this method, a completely separate user is created specifically for the purposes of storing the WINE prefix and all its installed applications. Individual users are then granted permission to run programs as this user using the <application>su</application> command. The result is that these users can launch a WINE application as they normally would, only it will act as though launched by the newly-created user, and therefore use the centrally-maintained prefix containing both settings and programs. To accomplish this, take the following steps.
Create a new user with the following command (as root), which will step through the required details:
<prompt>#</prompt> <userinput>adduser</userinput> <prompt>#</prompt> <userinput>ggated</userinput>
Enter the username (e.g., <replaceable>windows</replaceable>) and Full name ("Microsoft Windows"). Then accept the defaults for the remainder of the questions. Next, install the <application>sudo</application> utlity using binary packages with the following:
<prompt>#</prompt> <userinput>pkg install sudo</userinput> <prompt>#</prompt> <userinput>pkg install sudo</userinput>
Once installed, edit <filename>/etc/sudoers</filename> as follows: Sonra <filename>/etc/krb5.conf</filename>‘u aşağıdaki gibi düzenleyin:
# User alias specification

# define which users can run the wine/windows programs
User_Alias WINDOWS_USERS = user1,user2

# define which users can administrate (become root)
User_Alias ADMIN = user1

# Cmnd alias specification

# define which commands the WINDOWS_USERS may run
Cmnd_Alias WINDOWS = /usr/bin/wine,/usr/bin/winecfg

# Defaults
Defaults:WINDOWS_USERS env_reset
Defaults:WINDOWS_USERS env_keep += DISPLAY
Defaults !lecture,tty_tickets,!fqdn

# User privilege specification
root ALL=(ALL) ALL

# Members of the admin user_alias, defined above, may gain root privileges

# The WINDOWS_USERS may run WINDOWS programs as user windows without a password
The result of these changes is the users named in the <emphasis>User_Alias</emphasis> section are permitted to run the programs listed in the <emphasis>Cmnd<subscript>Alias</subscript></emphasis> section using the resources listed in the <emphasis>Defaults</emphasis> section (the current display) as if they were the user listed in the final line of the file. In other words, users designates as <emphasis>WINDOWS_USERS</emphasis> can run the <application>wine</application> and <application>winecfg</application> applications as user <emphasis>windows</emphasis>. As a bonus, the configuration here means they will not be required to enter the password for the <emphasis>windows</emphasis> user.
Next provide access to the display back to the <emphasis>windows</emphasis> user, as whom the WINE programs will be running:
<prompt>%</prompt> <userinput>xhost +local:windows</userinput> <prompt>%</prompt> <userinput>locale</userinput>
This should be added to the list of commands run either at login or when the default graphical environment starts. Once all the above are complete, a user configured as one of the <literal>WINDOW_USERS</literal> in <filename>sudoers</filename> can run programs using the shared prefix with the following command:
it is worth noting that multiple users accessing this shared environment at the same time is still risky. However, consider also that the shared environment can itself contain multiple prefixes. In this way an administrator can create a tested and verified set of programs, each with its own prefix. At the same time, one user can play a game while another works with office programs without the need for redundant software installations.
The following section describes some frequently asked questions, tips/tricks, or common issues in running WINE on FreeBSD, along with their respective answers.
Basic Installation and Usage Yükleme Öncesi Görevleri
How to Install 32-bit and 64-bit WINE on the Same System?
As described earlier in this section, the <application>wine</application> and <application>i386-wine</application> packages conflict with one another, and therefore cannot be installed on the same system in the normal way. However, multiple installs can be achieved using mechanisms like chroots/jails, or by building WINE from source (note this does <emphasis>not</emphasis> mean building the port).
Can DOS Programs Be Run on WINE?
They can, as "Console User Interface" applications as mentioned eariler in this section. However, there is an arguably better method for running DOS software: <application>DOSBox</application>. On the other hand, there's little reason not to at least try it. Simply create a new prefix, install the software, and if it does not work delete the prefix.
Should the "wine-devel" Package/Port be Installed to Use the Development Version of WINE Instead of Stable?
Yes, installing this version will install the "development" version of WINE. As with the 32- and 64-bit versions, they cannot be installed together with the stable versions unless additional measures are taken.
Note that WINE also has a "Staging" version, which contains the most recent updates. This was at one time available as a FreeBSD port; however, it has since been removed. It can be compiled directly from source however.
Install Optimization Compiz Fusion'ı Yükleme
How Should <trademark class="registered">Windows</trademark> Hardware (e.g., Graphics) Drivers be Handled? Görüntüyü Yazmak için <trademark class="registered">Windows</trademark> Kullanma
Operating system drivers transfer commands between applications and hardware. WINE emulates a <trademark class="registered">Windows</trademark> environment, including the drivers, which in turn use FreeBSD's native drivers for this transfer. it is not advisable to install <trademark class="registered">Windows</trademark> drivers, as the WINE system is designed to use the host systems drivers. If, for example, a graphics card that benefits from dedicated drivers, install them using the standard FreeBSD methods, not <trademark class="registered">Windows</trademark> installers.
Is There a way to Make <trademark class="registered">Windows</trademark> Fonts Look Better? Görüntüyü Yazmak için <trademark class="registered">Windows</trademark> Kullanma
A user on the FreeBSD forums suggests this configuration to fix out-of-the-box look of WINE fonts, which can be slightly pixelated.
According to <link xlink:href="">a post in the FreeBSD Forums</link>, adding the following to <filename>.config/fontconfig/fonts.conf</filename> will add anti-aliasing and make text more readable.
&lt;?xml version="1.0"?&gt;
&lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd&gt;"


&lt;!-- antialias all fonts --&gt;
&lt;match target="font"&gt;
&lt;edit name="antialias" mode="assign"&gt;&lt;bool&gt;true&lt;/bool&gt;&lt;/edit&gt;&gt;
&lt;edit name="hinting" mode="assign"&gt;&lt;bool&gt;true&lt;/bool&gt;&lt;/edit&gt;&gt;
&lt;edit name="hintstyle" mode="assign"&gt;&lt;const&gt;hintslight&lt;/const&gt;&lt;/edit&gt;&gt;
&lt;edit name="rgba" mode="assign"&gt;&lt;const&gt;rgb&lt;/const&gt;&lt;/edit&gt;&gt;
&lt;match target="font"&gt;
&lt;test name="size" compare="less"&gt;
&lt;edit name="antialias" mode="assign"&gt;
&lt;match target="font"&gt;
&lt;test name="pixelsize" compare="less" qual="any"&gt;
&lt;edit mode="assign" name="antialias"&gt;
Does Having <trademark class="registered">Windows</trademark> Installed Elsewhere on a System Help WINE Operate? Görüntüyü Yazmak için <trademark class="registered">Windows</trademark> Kullanma


User avatar None

Source string changed

FreeBSD Doc (Archived) / books_handbookTurkish (tr_TR)

Pre-Basic Installation Tasksand Usage
a month ago
Browse all component changes


English Turkish (tr_TR)
installation kurulum FreeBSD Doc (Archived)
usage kullanım FreeBSD Doc (Archived)

Source information

Source string comment
(itstool) path: sect2/title
Source string location
String age
a month ago
Source string age
a month ago
Translation file
books/tr_TR/handbook.po, string 3462