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 just done a reformat, reinstalled Win 2k and wanna try out Slackware (was using RH 8 before).
I downloaded the ISO and burned it, MD5SUM is ok. I booted the disk and used fdisk to make one root partition and one swap on my /dev/hdb.
When I run setup, I'm having these problems:
Sometimes the keyboard kinda stops working; I can move down through the options and somewhere along the way, it'll just stop responding. I read this can happen if you have a USB keyboard, but mine's PS2.
When I manage to get through to actually installing stuff, the menu screws up and a whole load of text shows up (sometimes the command prompt), once one of the lines was 'Bad EIP Code' or something :/.
Any ideas as to what I can do to fix this? Usually, I just reboot and try the install again, hope it gets a bit further :/.
No idea about the keyboard freeze, but you might try copying the slackware directory from the cd to your hard drive then reboot and tell setup to install from there. You'll want to skip the (re)formatting step, of course.  Afterwards, you can delete the slackware directory, if you like [/edit]
I've had troubles in the past with slack not being able to read from the cd (even a good cd) during the install procedure. For some reason, it seems to be more finicky during install.
I finally got it to install. The only problem I had was not being able to set up LILO, so it said I've gotta boot from a disk (didn't give me any specific reasons as to why LILO couldn't be set up).
The bookdisk I created doesn't seem to work. Restarted my machine, it tried to boot from CD first and then the floppy. The light on the drive went on and could hear it reading. It didn't say 'non system disk' or anything, but didn't book Slack. Windows loaded :/.
Hmmm, sounds like a job for Tom's root/boot (google for it) the best rescue disk around for my money (or for no money at all)
Boot from it then look at man lilo (or man chroot, I'm not sure which) it'll tell you all you need to know.
Your problem with lilo may be due to your root partition (and your /boot directory, I presume) being on a slave drive. You may actually be better off using the NT boot loader, but I'm certainly no expert on this. I recall a site that explained how to use w2k to choose between slack and windows boot. Again, try google or the search for this forum.
/sbin/e2fsck: Is a directory while trying to open /
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains and ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>.
Heh, I chose ext3 on install.
An error occurred during the root filesystem check. You will now be given a chance to log into the system in single user mode to fix the problem.
It then asks for the root password and then I'm getting /dev/console: Read-only file system, so can't edit lilo.conf or my fstab.
Would it be better to just reformat and repartition the disk and start over?