Wine is a Windows compatibility layer that will allow you to run many Windows applicationsnatively on Linux। Though you could run the Windows operating system on it, the actualWindows operating system is not required. Windows applications will run as if they wereLinux applications, able to access the entire Linux file system and use Linux-connected devices.Applications that are heavily driver dependent, such as graphic-intensive games, most likelywill not run. Others, such as newsreaders, which do not rely on any specialized drivers, mayrun very well. For some applications, you may also need to copy over specific Windows DLLsfrom a working Windows system to your Wine Windows system32 or system directory.To install Wine on your system, search for wine on you distributions repositories. Forsome distributions you may have to download wine directly from winehq.org. Binaries forseveral distributions are provided. Once installed, a Wine menu will appear in the Applications menu. The Wine menuholds entries for Wine configuration, the Wine software uninstaller, and the Wine filebrowser, as well as a regedit registry editor, a notepad, and a Wine help tool.To set up Wine, a user starts the Wine Configuration tool. This opens a window withpanels for Applications, Libraries (DLL selection), Audio (sound drivers), Drives, DesktopIntegration, and Graphics. On the Applications panel you can select which version ofWindows an application is designed for. The Drives panel will list your detected partitions,as well as your Windows-emulated drives, such as drive C:. The C: drive is really just adirectory, .wine/drive_c, not a partition of a fixed size. Your actual Linux file system will belisted as the Z: drive.Once configured, Wine will set up a .wine directory on the user’s home directory (thedirectory is hidden, so enable Show Hidden Files in the file browser View menu to displayit). Within that directory will be the drive_c directory, which functions as the C: drive,holding your Windows system files and program files in the Windows and Program File subdirectories. The System and System32 directories are located in the Windows directory.Here is where you place any needed DLL files. The Program Files directory will hold yourinstalled Windows programs, just as they would be installed on a Windows Program Files directory.To install a Windows application with Wine, you can either use the Wine configurationtool or open a Terminal window and run the wine command with the Windows applicationas an argument. The following example installs the popular newsbin program: $ wine newsbin.exe To install with the Windows Configuration tool, select the Applications panel and thenclick Add.Some applications, such as newsbin, will also require that you use certain DLL files froma working Windows operating system. The DLL files are normally copied to the user’s .wine/drive_c/Windows/system32 directory.Icons for installed Windows software will appear on your desktop. Just double-click anicon to start up the application. It will run normally within a Linux window, as would anyLinux application.Installing Windows fonts on Wine is a simple matter of copying fonts from a Windowsfont directory to your Wine .wine/drive_c/Windows/fonts directory. You can just copy anyWindows .ttf file to this directory to install a font. You can also use the Microsoft commonweb fonts available from fontconfig.org (this will require cabextract to extract them).Wine will use a stripped-down window style for features like buttons and the title bar. Ifyou want to use the XP style, download and install the Royal theme from Microsoft. Keep inmind, however, that supporting this theme is very resource intensive and will likely slowdown your system.
Custom Search
Introduction
A shell is a command line interpretor. It takes commands and executes them. As such, it implements a programming language. The Bourne shell is used to create shell scripts -- ie. programs that are interpreted/executed by the shell. You can write shell scripts with the C-shell; however, this is not covered here.
Necessity of Structured Shell Programming
Shell scripts remain a staple of the business world.With high development costs, it is not practical to develop everything in a high-level language. Many business processes are simply a matter of following a series of steps, after which the results are labeled and archived.This is the very type of activity scripts are made to handle. Over time, shells have collected new features, often by copying the capabilities of other shells. In his book, The Humane Interface, Apple Macintosh interface designer Jef Raskin once spoke with a pilot regarding the design of the plane’s autopilot.The device was designed with five ways to enter coordinates.The reason for this design was to reduce training costs by emulating other autopilots. However, a pilot pointed out that the operator of the aircraft is responsible for knowing how to operate every piece of equipment, and that meant he had to know how to adjust the autopilot in each of the five ways.
Many shells, including Bash, have developed a mixture of features with specialized or arcane applications. Like the autopilot, it is not always clear how these features should be
used nor which features are provided primarily for compatibility.Too often, poorly designed scripts are all-but illegible to another programmer, or even to the same programmer a few months after a script was hastily assembled.
This presents a problem for serious business scripts.The cost of developing a highlevel language solution is high, but a disorganized shell script can be expensive to maintain
over time. As the needs of the business change, and the shell script is modified by successive generations of programmers, the problem escalates.
As a rule of thumb, business programs never go away.At one place I recently worked,what started off as a simple shell script used to print reports gradually evolved into a Web-based reporting system complete with personal customizations and secure access.
The original programmer had no idea what his script would become. Because of the essential openness and complex syntax of Bash, it’s to the benefit of any serious project to adapt some kind of standard. Bash is very forgiving, but the costs are not. For example, there are many ways to add 2 + 2 in Bash. Like the autopilot anecdote, it’s not practical to expect the programmers who maintain the scripts to have to deal with this kind of redundancy. Likewise, shell word quoting is sometimes optional, sometimes required, depending on the context. A command that works with one form of quotation can suddenly stop working when different data appears in the quotes. Issues like shell word quoting, specialized capabilities, or portability features, when abused, can lead to increased maintenance and long-term development costs.
Many shells, including Bash, have developed a mixture of features with specialized or arcane applications. Like the autopilot, it is not always clear how these features should be
used nor which features are provided primarily for compatibility.Too often, poorly designed scripts are all-but illegible to another programmer, or even to the same programmer a few months after a script was hastily assembled.
This presents a problem for serious business scripts.The cost of developing a highlevel language solution is high, but a disorganized shell script can be expensive to maintain
over time. As the needs of the business change, and the shell script is modified by successive generations of programmers, the problem escalates.
As a rule of thumb, business programs never go away.At one place I recently worked,what started off as a simple shell script used to print reports gradually evolved into a Web-based reporting system complete with personal customizations and secure access.
The original programmer had no idea what his script would become. Because of the essential openness and complex syntax of Bash, it’s to the benefit of any serious project to adapt some kind of standard. Bash is very forgiving, but the costs are not. For example, there are many ways to add 2 + 2 in Bash. Like the autopilot anecdote, it’s not practical to expect the programmers who maintain the scripts to have to deal with this kind of redundancy. Likewise, shell word quoting is sometimes optional, sometimes required, depending on the context. A command that works with one form of quotation can suddenly stop working when different data appears in the quotes. Issues like shell word quoting, specialized capabilities, or portability features, when abused, can lead to increased maintenance and long-term development costs.
The Origin of Linux
The Linux operating system was created as a hobby by a young student, Linus Torvalds, at the University of Helsinki in Finland. Linus, interested in the Unix clone operating system Minix, wanted to create an expanded version of Minix with more capabilities. He began his work in 1991 when he released version 0.02 and invited programmers to participate in his project.Version 1.0 was released in 1994.
Linux uses GNU General Public License (GPL) and its source code is freely available to everyone. Linux distributions, CD-ROMs with the Linux kernel and other software ready for installation, do not have to be free, but the Linux source code must remain available. Making source code available is known as distributing open source. The word “Linux” is properly pronounced using a Swedish accent, making it difficult to say in North America. It is most often pronounced with a short “i” and with the firstsyllable stressed, as in LIH-nicks, but it is sometimes pronounced LYE-nicks (the anglicized “Linus’ Unix”) or LEE-nucks. Strictly speaking, Linux refers to the operating system kernel that starts and manages other programs and provides access to system resources.The various open source shells, compilers, standard libraries, and commands are a part of another project called GNU. The GNU project was started by the Free Software Foundation (FSF) as an attempt to create a free version of Unix.The main Linux C compiler, gcc, is a part of the GNU project. There is also a GNU kernel project, but the Linux kernel has largely superseded thiseffort.
X Windows is also not strictly a part of Linux. Xfree86, the open source version of X Windows, was adapted to the Linux operating system and was released under a different license.
Linux uses GNU General Public License (GPL) and its source code is freely available to everyone. Linux distributions, CD-ROMs with the Linux kernel and other software ready for installation, do not have to be free, but the Linux source code must remain available. Making source code available is known as distributing open source. The word “Linux” is properly pronounced using a Swedish accent, making it difficult to say in North America. It is most often pronounced with a short “i” and with the firstsyllable stressed, as in LIH-nicks, but it is sometimes pronounced LYE-nicks (the anglicized “Linus’ Unix”) or LEE-nucks. Strictly speaking, Linux refers to the operating system kernel that starts and manages other programs and provides access to system resources.The various open source shells, compilers, standard libraries, and commands are a part of another project called GNU. The GNU project was started by the Free Software Foundation (FSF) as an attempt to create a free version of Unix.The main Linux C compiler, gcc, is a part of the GNU project. There is also a GNU kernel project, but the Linux kernel has largely superseded thiseffort.
X Windows is also not strictly a part of Linux. Xfree86, the open source version of X Windows, was adapted to the Linux operating system and was released under a different license.
