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've got SuSE 8.2 running on my machine and recently tried installing slackware too, only to find that it destroyed my SuSE 8.2 kernel . I've since reinstalled SuSE (I couldn't get on the net in Slack) but want to try Slack again, without destroying my other distro this time.
How do I do it? I'm pretty sure it must have something to do with renaming my SuSE kernel image to something else so it doesn't get overwritten but other than that I'm pretty clueless
Can someone please tell me what to do? Please make it simple (I still feel like a bit of a noob)
i did install to a different partition, and the kernel was the only thing that was replaced other than the bootloader (which I replaced out of choice). I thought all the kernels were stored together in /boot
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
you put the kernels where ever you wish. it's only important that the boot loader
knows where it is. /boot can be a directory or a partition. it may or may not
be shared with another linux install. i would suggest putting all of slackware
in that other partition, and setting it up to boot manually, after you install.
just dont' let it install lilo or grub, and after, add the slackware kernel to your
other lilo or whatever you are using.
Thanks for the advice, will try that later. I gotta admit I'm still pretty confused as to how I managed to overwrite my kernel last time - on my system /boot isn't a separate partion and my hdd looked like:
I'm happy editing my lilo conf, but in SuSE whenever I start with a new option that i say is an image it wants to use the /boot/vmlinuz that is on /dev/hda5 what do I have to write into lilo conf to force it to use the one on /dev/hda9?
Thanks for all the help (and your patience!!!)
ps. my lilo conf is below
# Modified by YaST2. Last modification on Fri Feb 13 17:19:54 2004