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.
First, find out if you already have ntfs support in the kernel. This will probably work:
Oh, if this is RedHat 7.2, no, you don't have it. They decided to be twerps with their last release.
Recompiling the kernel can be a headache. If you do have RH or Mandy, or even SuSe, you specifically had to choose the kernel source and headers, usually as a section called "Kernel Development" as part of your installation, otherwise you won't have the kernel source code and a compiler.
If you don't already have the module, read the kernel compiling HOW-to over at Linux-doc. If you do have it:
mount -t ntfs -ro /dev/hda1 /mnt
This is assuming that windows partition is the first partition of the first hard drive. If it were the second partition: hda2, second drive: hdb1 You can figure the rest.
so the command worked and it just replaced my whole /mnt with the ntfs partition
so now my 2 cdrom mounts and the floppy are gone
so what would i want to do to bring those back and possibly change the ntfs to mount into a folder instead?
Sorry bout that, I gave you a quick and dirty mount point that I knew would be there but wouldn't make the system go kazoo. You might want to create a point like /mnt/win or somesuch. Also, even in read-only, its not a good idea to leave the NTFS partition mounted when you're done file swapping.
Oh yeah... I had a point. What distro and release are you using so I can add it to my mental list of ones that are ntfs ready?
Slackware and Debian both have it pre-compiled, but RedHat stopped with 7.2 for some reason, which I assumed to be that they were worried about people trashing their ntfs partitions and blaming RH. Its good to see that Mandrake still has some cahones about this. Now all I'm left to wonder about is SuSe.
Originally posted by finegan First, find out if you already have ntfs support in the kernel. This will probably work:
If you do have it:
mount -t ntfs -ro /dev/hda1 /mnt
Hey Finegan, How would I load the module? I have it, but its gzipped, as well as being in my 2.4.18 source. I'm not very good with modules, so how would I load it? modules.conf right? If so, what's the syntax? BTW, I'm running MD 8.1 with 2.4.8-26mdk kernel.
It became a convention for a while for all of the kernel modules to be gzipped as a space saving solution, I think so that ISOs could be kept down to size. Regardless, just ignore the fact they're g'zipped, it won't change anything. You just modprobe the module like normal and then mount the drive, just like with those commands from above. If you're wanting to put the ntfs load in modules.conf, I assume you are wanting to have the drive mounted somewhere on boot.
Always having an ntfs mount, even read-only, can lead to memory leaks, corrupted filesystems, bad acne, ear infections, and as always... birth defects, so you've been warned. Its always much safer to mount the drive, copy what you want to copy or read what you want to read, and then unmount it. NTFS support is getting better, but seeing as how MS doesn't exactly publish how the filesystem works, the poor Linux geeks who write the drivers have to figure it out largely on guesswork and bad coffee. If you want it up from boot, you're going to have to change a file called /etc/fstab, and add the line (or something similar):
/dev/hda1 /win ntfs ro,auto,user,umask=022 0 0
This is assuming that the ntfs drive is /dev/hda1 and that you are going to mount the drive on a directory called /win. On boot the kernel module autoloader should pull ntfs.o for the job.
Well, I have a slight problem. When I modprobe the module, even if it isn't gzipped, it says it cannot find the module, when infact it is in the same directory. What can I do to fix this, and what's the problem? Thanks Finegan.
Okay, just to make certain, you have a file called:
and you try to modprobe it with:
modprobe ntfs (don't add the .o or .o.gz)
And it says module not found?
If that's exactly it, I'm a little stumped. Modprobe could be bugging. You could try "insmod" instead, which is more or less a slightly less gentle version of modprobe, but its there, it should at least try.
perhaps its because i added the o. sorry bout that.
however, i will try it after i get a new hard drive. I'm stuck in m$ for a while since its on a separate drive, and my linux drive is making pretty noises; it also won't boot. It locks up on startup, and I'm going to try it with a new drive.