(itstool) path: listitem/para
Know how to <link linkend="advanced-networking">set up a network connection</link>.
Context English Portuguese (Brazil) State
<link xlink:href="">WINE</link>, which stands for Wine Is Not an Emulator, is technically a software translation layer. It enables to install and run some software written for <trademark class="registered">Windows</trademark> on FreeBSD (and other) systems.
It operates by intercepting system calls, or requests from the software to the operating system, and translating them from <trademark class="registered">Windows</trademark> calls to calls that FreeBSD understands. It will also translate any responses as needed into what the <trademark class="registered">Windows</trademark> software is expecting. So in some ways, it <emphasis>emulates</emphasis> a <trademark class="registered">Windows</trademark> environment, in that it provides many of the resources <trademark class="registered">Windows</trademark> applications are expecting.
However, it is not an emulator in the traditional sense. Many of these solutions operate by constructing an entire other computer using software processes in place of hardware Virtualization (such as that provided by the <package>emulators/qemu</package> port) operates in this way. One of the benefits of this approach is the ability to install a full version of the OS in question to the emulator. It means that the environment will not look any different to applications than a real machine, and chances are good that everything will work on it. The downside to this approach is the fact that software acting as hardware is inherently slower than actual hardware. The computer built in software (called the <emphasis>guest</emphasis>) requires resources from the real machine (the <emphasis>host</emphasis>), and holds on to those resources for as long as it is running.
The WINE Project, on the other hand, is much lighter on system's resources. It will translate system calls on the fly, so while it is difficult to be as fast as a real <trademark class="registered">Windows</trademark> computer, it can come very close. On the other hand, WINE is trying to keep up with a moving target in terms of all the different system calls and other functionality it needs to support. As a result there may be applications that do not work as expected on WINE, will not work at all, or will not even install to begin with.
At the end of the day, WINE provides another option to try to get a particular <trademark class="registered">Windows</trademark> software program running on FreeBSD. It can always serve as the first option which, if successful, offers a good experience without unnecessarily depleting the host FreeBSD system's resources.
This chapter will describe: Este capítulo descreve:
How to install WINE on a FreeBSD system. Como conectar terminais a um sistema FreeBSD.
How WINE operates, and how it is different from other alternatives like virtualizaton.
How to fine-tune WINE to the specific needs of some applications.
How to install GUI helpers for WINE. Como instalar o novo kernel.
Common tips and solutions for on FreeBSD. Configurar uma placa de som no FreeBSD.
Considerations for WINE on FreeBSD in terms of the multi-user environment.
Before reading this chapter, it will be useful to: Antes de ler este capítulo, você deve:
Understand the <link linkend="basics">basics of <trademark class="registered">UNIX</trademark> and FreeBSD</link>. Entender o <link linkend="basics">básico sobre sistemas <trademark class="registered">UNIX</trademark> e sobre o FreeBSD</link>.
Know how to <link linkend="bsdinstall">install FreeBSD</link>. Saber como <link linkend="bsdinstall">instalar o FreeBSD</link>.
Know how to <link linkend="advanced-networking">set up a network connection</link>. Saber como <link linkend="advanced-networking">configurar uma conexão de rede</link>.
Know how to <link linkend="ports">install additional third-party software</link>. Saber como <link linkend="ports">instalar software adicional de terceiros</link>.
WINE Overview &amp; Concepts
WINE is a complex system, so before running it on a FreeBSD system it is worth gaining an understanding of what it is and how it works.
What is WINE?
As mentioned in the <link linkend="wine-synopsis">Synopsis</link> for this chapter, WINE is a compatibility layer that allows <trademark class="registered">Windows</trademark> applications to run on other operating systems. In theory, it means these programs should run on systems like FreeBSD, macOS, and Android.
When WINE runs a <trademark class="registered">Windows</trademark> executable, two things occur: Usando o <trademark class="registered">Windows</trademark> para gravar a imagem
Firstly, WINE implements an environment that mimics that of various versions of <trademark class="registered">Windows</trademark>. For example, if an application requests access to a resource such as RAM, WINE has a memory interface that looks and acts (as far as the application is concerned) like <trademark class="registered">Windows</trademark>.
Then, once that application makes use of that interface, WINE takes the incoming request for space in memory and translates it to something compatible with the host system. In the same way when the application retrieves that data, WINE facilitates fetching it from the host system and passing it back to the <trademark class="registered">Windows</trademark> application.
WINE and the FreeBSD System Empacotando o sistema básico do FreeBSD
Installing WINE on a FreeBSD system will entail a few different components:
FreeBSD applications for tasks such as running the <trademark class="registered">Windows</trademark> executables, configuring the WINE sub-system, or compiling programs with WINE support.
A large number of libraries that implement the core functions of <trademark class="registered">Windows</trademark> (for example <filename>/lib/wine/</filename>, which is part of the aforementioned memory interface).
A number of <trademark class="registered">Windows</trademark> executables, which are (or mimic) common utilities (such as <filename>/lib/wine/</filename>, which provides the standard <trademark class="registered">Windows</trademark> text editor).
Additional <trademark class="registered">Windows</trademark> assets, in particular fonts (like the Tahoma font, which is stored in <filename>share/wine/fonts/tahoma.ttf</filename> in the install root). Um arquivo de configuração do driver do <trademark class="registered">Windows</trademark> XP com uma extensão <filename>.INF</filename>.
Graphical Versus Text Mode/Terminal Programs in WINE


No matching activity found.

Browse all component changes


English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: listitem/para
Source string location
book.translate.xml:19646 book.translate.xml:43971
String age
a year ago
Source string age
a year ago
Translation file
books/pt_BR/handbook.po, string 3206