SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have Win4Lin working under Slack9.0. It is rather involved, though...
First you need the Slackware kernel sources and 2 kernel patches:
1) "Kernel-Win4Lin3-x.patch" where x=kernel version
Next, make a new directory /usr/src/win4lin and issue the following command:
cp -ravd /usr/src/linux/* /usr/src/win4lin
Also, copy the config from /boot to the /usr/src/win4lin like this
cp /boot/config-ide-x /usr/src/win4lin/.config
Remember, x=kernel version!
Next, copy the 2 patches to /usr/src/win4lin and patch the kernel by issuing the following commands:
The patch logs can be looked at by using the command "less" eg. "less mkipatch.log". Assuming no errors then you can proceed with the kernel config.
NeTraverse recommends the following commands and I suggest following them:
cp .config config-save
cp config-save .config
If you want you can also "make xconfig" if you are in X. Ensure the following kernel options are enabled:
Processor type and features => Maximum Physical Memory<1GB
Loadable module support => Enable loadable module support
General setup => Networking support
General setup => System V IPC
General setup => Kernel support for ELF binaries
Networking options => TCP/IP Networking
File Systems => ISO 9660 CD-ROM filesystem support
Windows Applications support => Include NeTraverse Win4Lin support
Save the kernel config and now run the following sequence of commands:
make bzImage (this takes a loooooong time!"
make modules (this takes even longer...get coffee or beer)
cp ./arch/i386/boot/bzImage /boot/win4lin (moves kernel for booting)
now, editing the /etc/lilo.conf file add the following lines, substituting your root partition for /dev/hda1
I must have a buttload of modules enabled considering I have an AthlonXP 1.6GHz with 512MB RAM. The bzImage may take 3 minutes but to me that's still a loooong time.
The information I gave I got from NeTraverse's web sites, some from this forum, and some I discovered on my own, but the end result is...it works and I have Win4Lin running.
Certain kernel modules are needed. I try to minimize what I compile directly into the kernel to streamline it. The modules are being called from /etc/rc.d/rc.modules. You may want to look there to see what is being called. I do recommend you have some modules. But once the kernel/modules is resolved, Win4Lin is good to go.