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.
After playing around with linux livecds and frugal installs for a bit I've decided to a 'real' linux install with slackware 12.
I have a working frugal installation (livecd booting off the iso image on harddrive) of PuppyLinux 2.16 on my harddrive using grub. The installation went fine but when I tried to reboot afterwoods using grub
the kernel panics with 'no init found. try passing init = option to the kernel'. I tried booting with noinitrd but this didnt work. Exploring /boot/ with puppy I couldnt find an init image but did find the man page link explaining how to make one to boot slackware, using a slackware utility. This seems a bit catch-22. Should I need an initrd? Is there other ways to make one? My grub menu entry is:
You don't need an initrd to use or install Slackware (beyond the fact that the installer is an initrd, obviously). I have been using Slackware for many years, and have never even looked at the initrd tools.
I am a bit confused by your situation though. Is there a particular reason you can't just put the Slackware CD in and install normally? Or have you already installed Slackware, and are just trying to get GRUB to boot it?
Actually, if you installed one of the "generic" kernels instead of a huge one, you will need an initrd with slack-12
I don't use grub to boot, so I can't give any info on changing the menu.lst file, but here's how I made my initrd
You'll need to reboot your machine, using the slackware install dvd/cd and at the boot prompt type:
hugesmp.s root=/dev/hda1 rdinit= ro
(replace /dev/hda1 with wherever your root directory for slack is, and the space after rdinit= is there on purpose!!)
once it boots, change to the /boot directory cd /boot
and type the following
mkinitrd -c -k 126.96.36.199-smp -m ext3
(leave off the smp if you installed the "other" generic kernel.
however, pat recommends even single processor boxes to use the smp kernels if possible)
if you formatted with reiserfs, or one of the other possibilities, just use -m whateverfilesystemyouchose
you'll need the cpio package installed, along with the corresponding kernel-modules package.
finally, edit grub's menu.lst file and add
initrd=/boot/initrd.gz just below the kernel specification for your slackware install.
Of course, you can always just use the huge.s or hugesmp.s kernels and forget it all!!
Good luck, let me know if it works!! (I'm mostly concerned about the grub part, I had to do a google search to find out where to add the initrd.gz line.
Do you or don't you need initrd to normally boot hugesmp.s?
Originally Posted by MS3FGX
You don't need an initrd to use or install Slackware (beyond the fact that the installer is an initrd, obviously).
This is confusing what is obvious? Slackware Installers are initrd based? I use loadlin 16c
With the changing and increased size of kernels I am confused as to whether or not initrd is need to normally boot hugesmp.s... I have not had a working slackware box for years, only partially working, but I haven't quit. lolol
The installer is an initrd, simply because there is nothing installed on the system yet. The install CD needs to boot the kernel to a self-contained initrd, since there is nothing else to boot. I thought that was a rather obvious conclusion, as you can't boot the kernel to a blank drive (or one with Windows on it, at least...). If there is already an installed Slackware system however, then the install CD can be pointed to that instead, and then becomes somewhat of a rescue CD in the event your installed kernel has become unbootable.
As for what is required for the stock kernels, I honestly don't know for Slackware 12. It was never required in earlier Slackware releases, but the 2.6 kernels have changed the game considerably.
I have never used the stock Slackware kernel on any machine I have ever run, on any Slackware release, so I am certainly an authority pertaining to them.