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.
When trying to boot my new installationI get an error after a while. It says like this "Remounting root device enabled.
/etc/rc.d/rc.S: /sbin/mount: No such file or directory.
Attempt to remount root device as read-write failed!"
The mount-file is missing. Can I write it myself? What shall be in it?
Any other ideas to what could be wrong???
heh, no you can't write it yourself (well.. maybe you can if you know c) it's a program. BUT it's normally in /bin/ instead of /sbin/ which is why you're probably getting that error.
As to what to do though. I'm not up on slack at all at all, so trickykid can probably tell you the best thing. it really shouldn't ever occur though, so it's quite confusing. i guess you could edit the rc.S script, but there must be a proper explanation for it... over to drew...
Thanks for your help. It feels like I have a thousand question to ask, so I greatful for all help I can get. I have installed one server and one workstation at home with the same CD, so it cant be anything wrong with that. And typically,when I tried to install a server in my office, to testrun it with our network, it wouldn work...
I get the error when I rebooting the first time after installation. I can boot from the CD, and I can mount /dev/hda1 manually to a temp-dir, and read from it. I have noticed that there is an error witn something like missing swapon, or something like that. It hapens ringht after the kernel 2.4.18 starts booting.
Bad CD's are nasty, I recently downloaded slackware-curent from the PSU mirror and found it was incomplete, so I had a friend of mine that goes there talk to the person maintaining that....he complained ftp.slackware.com was never up (complete bs to me), but I had a corrupt CD and didn't notice really untill install time. Everything installed fine even though hardly anything of the base system was there, it gave no errors, and when it booted it booted to an init2.08# and stopped. So I redownloaded and reinstalled and all is well. ;-) Gotta watch those corrupt CD's