Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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'm really interested in trying out slackware. i have a new hard disk (SATA) that I plan to attach as the primary slave. I've never tried this before however. I've looked around LQ and can't find any similar situations. After I attach the hard disk, how do access it to begin partitioning?
another issue i was thinking about is booting. i have winxp and mandrake on my primary master and I believe I should be able to boot slack from my existing lilo. can this be done? any "better" way to do it?
When installing slackware and it boots up and prompts for you to partition the disks, etc, you can partition your secondary drive by doing the following:
And you will only be partitioning your second hd. If you need to partition your master drive, simply typing cfdisk or cfdisk /dev/hda will prompt to partition only that drive, etc.
And yes, you can easily use your existing loader to load slack at boot time, just be sure to skip over installing lilo during the install. And you'll need to edit your boot loader accordingly afterwards on the slackware specific details, etc.
To set up lilo you need to create a new entry in the /etc/lilo.conf file.
Run your other distro and edit lilo.conf. duplicate an existing entry and change the label, image and root references to point to your Slackware installation. You may still need a bootdisk with support for SATA though.
hmmm..i never thought of that. That was one of things I wasn't sure what would happen. I know SATA is not supported by the 2.4.x series so I'm wondering if Slack will even be able to boot up from there?
i've connected my SATA drive via host adapter. i have an existing pata drive which is my boot drive. however, when i rebooted with the slack cd after installing the sata drive, i can't run fdisk on /dev/hdb. How do I know which drive is the SATA drive?
I think i read somewhere that SATA drives have "boot priority" is that true? I can't even get into Mandrake 9.2 (w/ 2.6.2 that has SATA support) without kernel panic. What's going on?
You either have to boot with a kernel that has support for SATA compiled in, or a kernel/initrd image that will load the modules, so that the SATA drive can bemounted as root. If the SATA is the boot device you need akernel with support compile-in. You can make one in another running system. then boot with that and copy your distro over or install packages to the new HD. chroot into the new drive/installation and run lilo there.
i see. problem is, slack doesn't seem to detect my other hard disk ( the pata) which has mandrake and winxp on it. i have 2.6.2 in mandrake but slack seems to think my new SATA is /dev/hda. is soemthing wrong?