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.
Boot from CD, mount your hdd, cd to it and issue tar xzpf /system.tar.gz (or where it resides). You still will have to chroot to your hdd afterwise and reinstall bootloader (don't know what Slack uses now).
Slackware still uses lilo, so you'd have to chroot and re-run lilo. If you've substituted grub, you'll have to do a similar thing for that. Be careful, if you are moving the drives around in a computer, your lilo/grub entries may change (hda1->hdb1 etc.)
Chroot is giving you a shell for which named directory is /. So all paths to configuration and libraries, usually hardcoded as absolute paths in programs, change to paths relative to given dir. For example, lilo will go to /boot for kernel - and it will be on hdd, not rescue cd.