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 am almost there...got Slack installed, net card is finally working, sound enabled. I have one last hurdle to overcome. I cannot seem to get the right grub.conf file entries to get it to boot. Slack is installed on the same SATA hard drive as WinXP. The partitions are this:
When I choose Slack from the grub boot menu, I get this error:
Error 1: Filename must be either absolute pathname or blocklist
This is the grub entry for Slack that was recommended elsewhere and on other sites.
If anyone has Slackware booting from Grub successfully with a similar configuration to mine, would you be so kind as to showing me your grub.conf entry?
Again, as I understand it, the initrd entry is not required for Slackware. And, yes, I have rooted around in the /boot directory of Slack and found nothing revealing about the file name. I can only assume there is more to the filename than just 2.4.31, but I have not found it.
sorry if I mess around with things I don't know well, but are you sure that your kernel is in fact named vmlinuz-2.4.31? If I understand you correctly you are not sure. In that case please tell what files do you have in /boot. For other things with grub I can't help you, as I don't use it.
Just a quick post to all who helped me with my new installation of Slackware 10.2. I added this distro to my collection as a training tool because of it rock solid stability reputation and it's lack of hand holding (like the other distros do). I want to become an advanced user and I believe Slack will let me to that.
I have two pending posts in this forum asking for help in writing code to enable me to boot Slack from my grub menu. Everything else had been solved (sound, net, etc.) but this one last thing was eluding me. Here is how I solved it:
I simply used the same entry I had described in my previous posts in my grub.conf file, BUT SIMPLY LEFT THE KERNEL VERSION OUT. As such:
Thank you for your response..As it turns out I have solved the issue (please see my other post today). I knew the kernel version, but my entries weren't working. Out of a mindset of "one more try", I reedited the grub.conf file and simply left the kernel version out. BANG! It worked.
I always have vmlinuz as a soft link to the kernel I'm using as my 'current'
ln -s /boot/vmlinuz-2.6.15a vmlinuz
and one to the older 'bootable' kernel
ln -s /boot/vmlinuz-2.6.15 vmlinuzsafe
That way, I can change the kernel (like I do almost once a week), and don't have to woory as much about bootloaders. I just make sure that 'vmlinuz' and 'vmlinuzsafe' are what is called from the bootloader.