|
|
| Коментар от: bulg |
Дата: 19-02-2008 |
| [ Други коментари] |
Quick start
===========
To get the support of Linux Unified Kernel, there are 3 basic steps to go:
1. Build Linux kernel
2. Build Linux Unified Kernel module
3. Build Wine
To run Win32 applications on Linux Unified Kernel, just do it like running
a Linux program.
For more details, please read the rest of the file.
Requirements
============
Linux-2.6.23
Wine-0.9.40
The current version (0.2.1) of Linux Unified Kernel provides 2 patches for
both Linux kernel and Wine, so the versions should be specified.
Basic requirements:
Make sure you have installed the X11 development include files
(called xlib6g-dev in Debian and XFree86-devel in Red Hat).
Build tool requirements:
Make sure you have at least gcc 3.2 available which Linux kernel 2.6.23
requires.
Building Linux kernel
=====================
To build Linux Unified Kernel, the first thing is to patch the Linux
kernel 2.6.23. First, cd to the top-level directory of the kernel-source
code (linux-2.6.23), then run the following command:
patch -p1 < path/patchfile
where "path" is the path of the patch file and "patchfile" is its file
name (In this package, it is unifiedkernel-0.2.1-k2.6.23.diff in the
directory "kernel").
After patching kernel, configure it like:
make menuconfig
The general configuration file is provided in the patch (you can also
configure it yourself), you can just save and exit to run the next
commands:
make
make modules_install
make install
Then reboot your system to build the Linux Unified Kernel module.
Building Linux Unified Kernel module
====================================
To build the module, cd to the "module" directory and run the command:
make
Then install the module to get the Linux Unified Kernel support:
insmod unifiedkernel.ko
Building Wine
=============
To use the Win32 programs, you need to build the user space environment.
The script install.sh will help you do this building work automatically:
./install.sh -w wine_path -f patch_file -p prefix
where "wine_path" is the path of the Wine-source code(0.9.40), "patch_file"
is the patch file name of Wine(unifiedkernel-0.2.1-w0.9.40.diff), and
"prefix" is the directory of storing the built-in programs whose default is
"/usr/local"
Running programs
================
After the 3 steps of building, you can run none-installed Win32 programs
that APPLIST lists.
For example:
./calc.exe (running Win32 Program calculator in the
current directory)
/usr/notepad.exe (running Win32 Program Notepad in an
absolute directory)
or double-click the icon created either by the install program or by
yourself.
As this release of Linux Unified Kernel doesn't support build-in EXE
perfectly, so you need to install the Win32 applications like Microsoft
Office 2000 that need installation in the Wine environment.
Everytime you want to install a Win32 program, please follow the 3 steps:
./switch.sh -p prefix -w wine_path -d wine (chang to the Wine
running environment)
wine setupfile (install application)
./switch.sh -p prefix -w wine_path -d unifiedkernel (chang to the Unified
Kernel running
environment)
where "setupfile" is the file name of the installation file like
"setup.exe", and the options "prefix" and "wine_path" represent the same
meanings as they are in the script install.sh.
After that, you can run a Win32 program with the Linux Unified support.
* Note: everytime you want to install a Win32 application, please use the
3-step installation, and after that, it will keeps you running Win32 programs
in Linux Unified Kernel environment.
Linux Unified Kernel is not yet completed, so several programs may crash
or not work exactly as on Microsoft Windows. You can report these bugs to
linux@insigma.com.cn.
UNINSTALL
========
If you don't want to use Linux Unified Kernel any more, you can uninstall
it.
1. Uninstall module:
rmmod unifiedkernel.ko
cd to the directory "module" and run command:
make clean
2. Unpatch Linux kernel 2.6.23 and Wine 0.9.40:
cd to the top-level directory of the kernel-source code or Wine, then run
the command:
patch -R -p1 < path/patchfile
where "path" is the path of the patch file and "patchfile" is its file
name.
And then, you can rebuild them.
|
| << Към: Linux Unified Kernel | Може ли да мислите преди да пишете? >> |
|
|
|
|
|
|
|
|
|
