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.
well. it was just a thought...
if i would have to do what you want to do , i would install Slack on the other machine, and do the compiling with Slack ( just my feeling.. ).
then copy the bzImage, modules-tree, System.map and config-file to your notebook.( by net or cd-r/w as the data will be obsolete in a few months ).
as i don't know yoper and it's capacities......
Originally posted by egag [...] if i would have to do what you want to do , i would install Slack on the other machine, and do the compiling with Slack ( just my feeling.. ).
then copy the bzImage, modules-tree, System.map and config-file to your notebook. [...]
That's what I'm wanting to know: exactly what files and directories need to be transferred after the compile is finished, and where are the files and directories located?
If you don't install the kernel and the modules you can after running make (2.6.x) or make modules (2.4.x) backup your kernel source dir and transfer it to your machine where you finish the job I guess
after you do ( in Slack ) : make bzImage, make modules, make modules_install there will be:
-/usr/src/linux/arch/i386/boot/bzImage ( that's your kernel , when copying it to your own system's /boot, rename it to smth. like vmlinuz-2.6.9, and add it in your lilo.conf file.
-/lib/modules/2.6.9 ( that's the module dir.tree , goes in /lib/modules )
-/usr/src/linux/System.map ( goes also in /boot )
-/usr/src/.config ( copy that for reference into /boot )
You could use a live cd to boot linux in her comp, then mount the kernel tree as nfs share (assuming the 2 comp are networked) so you can compile the kernel without install Linux in her machine if you want, but in my opinion, it is better to let her enter in Linux world installing slackware into it and help her to discover it
Are you complaining that kernel compiles take too long on your 850Mhz computer? I compile the latest stable kernel everytime one is released on my 350MHz.
Just start the compile and take a nap or something. Or, better yet, start the compile on your computer and use hers until the compile is finished. There it is. You haven't wasted any computer-time, and your kernel is compiled!
Originally posted by MikeZila Or, better yet, start the compile on your computer and use hers until the compile is finished
That's exactly what I've been doing. But I *have* been thinking about using her 3GHz machine to compile kernels, since it seems crazy for my little Thinkpad to sit here working so hard when, just across the room, there's a Big Mama P4 running a screensaver. Besides, I wanted to learn how to produce kernels to use on other machines, anyway.