Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
The message is telling you that, for some reason (not listed), your root file system has been mounted in read-only mode. This is most often caused by an error mounting the file system when the fsck is run, and should be fixed before trying anything else. (Since most commands won't work with a read-only file system mounted.)
FYI: The usual Linux mount sequence is:
1) Mount the root file system in read-only mode
2) Check that there are no file system errors that need to be corrected. (This is done in read-only mode because corrections to a file system where writing can take place almost always destroy the file system.)
3) Remount the fs in read/write mode
4) Proceed with the rest of the boot
By the way, if you just want a list of dependencies, depmod -n works better. (And, if you have a writable file system, depmod -n | less will let you see the whole output.)
Another point: I notice you're running as "root," which should only be done when absolutely necessary. (For example, while fixing file system errors. But checking dependencies is not, I believe, a good reason.)
Last edited by PTrenholme; 02-16-2006 at 12:10 PM.
Sorry, I was typing my reply when you posted your comment that you were using a live cd.
Before you did the chroot (assuming you did one), try a umount and mount -o rw for the mount point where the live CD mounts your root file system.
Um, that, of course, is assuming that the live CD is not pointing to itself (the CD) as root. If that's the case, there's no way to write to the CD, so ro is the only possibility. Most live CDs create a ram disk to use as work space, but the command you tried to use (with the -a option is trying to create a file for later use by modprobe, so it needs write access. The -n option just outputs the dependencies to stdout, and (assuming your live CD has set up a RAM disk) the command I suggested (pipe into tail) should work.
In any case, if you're having problems setting up ndiswraper, I'd suggest you review the various tutorials and threads here for suggestions. I'm not sure why you'd be using a live CD to attempt to set up ndiswraper on another system. It seems, to me, like it might be an unnecessary complication.
thanks a lot for your help i'll print this and try it tonight. I'll also google chroot and the other commands you suggested.
Basically the reason why i'm using this is because i don't want to install Linux on my laptop. I just want to check it out before i decide to do the switch. Also i want to test me wireless network to see if i could be braked in or not.
I stil have a lot of reading to do. Before trying to break into my network I first have to configure my hardware lol. Seems to me like hours of fun.
Well, basically, you can't configure ndiswraper unless you've got a system installed. After all, where would the configuration information be stored when you have no storage device?
If your laptop has a DVD reader, I'd suggest that you download and burn one of the bootable live DVD distributions (e.g., Knoppix might be a good choice). Also, check the HCL button at the top of the page. Someone may have already evaluated your laptop and network card for use with Linux.
About the Knoppix Live DVD: It attempts to automatically configure everything for you when it starts, and contains drivers for a large number of different types of hardware. It also can use a file on your HD (in your existing partition) to store your configuration information so you can modify things as you wish and have them saved between reboots from the DVD. (Of course, you don't have to save anything, but it's handy and doesn't take much space.)
Re ndiswraper: You'd only need to use that if there were no drivers available for your network card under Linux, and you had to attempt to use the drivers written for Microsoft systems. Before going that route, I'd (again) suggest checking the HCL to see what other people using the same network card have done to get it to work.