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 just recently installed slack 8.1 again, so this is honestly about the 150th time. i have never had this problem with my install though, i getthrough it fine, bu when i go to reboot, the system panics, and gives me a:
"Kernel tried to kill init. Try passing init= XX to kernel"
what gives?? i thought that i might have missed something during theinstall, so i went bad and installed everything over again fresh, and i got the same message. i do not think that i am missing anything, but i am not quite sure.
another quick question.....i want to use reiserfs, but everytime time the setup asks me to choose my root partition and my usr, and home, it appears to mount the fs's but i see an error in the F4 console that says:
"filesystem error; either wrong fs mount option, bad superblock, or too many mounted filesystems."
i have never gotten this error either, and i am quite baffled by this. i also know that if i am using reiserfs as as my root fs type that i need te -notail option, but i am using a seperate /boot partition, that is ext3. if anyone has ny answers about this one as well, you help is greatly appreciated.
alright thanks guys, i dont have internet at home,so last night i installed slack 9.0 with all ext3 partitions and it worked, now i am jsut curious to know if the bare.i 9.0 kernel has reiserfs support already built in?? cause i had some problms when i tried to use reiserFS on my home and usr partitions only, i made my / ext3 and my boot ext3 which is ok, it says so in the gentoo install guide at least so thats what i am going by. so if ayone could just answer the question of wheather or not there is reiser support in the 9.0 kernel that would help alot!! thanks again guys
alright thanks, i am gonna try this again when i get home, but in the meantime, anyone who knows of any other reasons that i would be getting the mount error, please feel free to chime in and let me know if you have had similar problems...thanks again to everyone who helped