Red HatThis forum is for the discussion of Red Hat 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.
Hi. I searched the forums and edited the example given to mount a NTFS partition to:
/dev/hda1 /c ntfs auto,ro,umask=0222 0 0
but when the red hat 9 starts, I can see error mounting ntfs drive : "fs type umask=0222 not supported by kernel"
Tell me whats wrong please.
I have Windows XP C Drive on /dev/hda1 and I have already created the folder /c .
Thanks in advance
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 220.127.116.11, KDE 3.5.8 and KDE 4.0 beta, Plu
The driver from rpm listed is read-only support. It will let you mount but you cannot write to the ntfs partition. I don't recommend writing to ntfs under linux but it does work most of the time. I use this feature to fix XP problems faster than dealing with Windows expensive and very slow tools.
You can recompile the kernel and add NTFS support also. Look at the top of this forum on kernel recompile.
Then mount would be ' mount -t ntfs /dev/hda1 /c '
You can add ntfs to /etc/filesystems and will not have to add -t option to mount.
I downloaded those rpm's but I have to copy the files somehow from my windows drive. I tried with floppy ( Im using a laptop, and its another device that is other from the laptop and is connected to the laptop with USB ) but it didnt work. Also my redhat doesnt detect my CD - I would even burn those files on a CD to make that work.
Also, I checked the recompiling thread but I first want to make my internet work, download the newest kernel, and then recompile.
I really need to make some connection between my linux and windows drives because I also need to copy some information to paste on those forums to make my wireless lan work... thats so complicated
I agree with Brian1. I have a little intranet, and I mount my NTFS partition of a windows xp machine. So first thing is to recompile your kernel to support NTFS partition (read-only). Itīs dangerous to write on it. After that I mount it as follow:
mount -t ntfs -o ip:192.168.200.1 //C /mnt/ntfs
In your case you can use:
mount -t ntfs /dev/hdaX /C /mnt/ntfs (or the directory you have created for this purpose).
Itīs better than use the rpm package. Your kernel must support this. If not, neither a compiled module nor any package will run.
I see lots of discussions regarding NTFS support in linux, and it is clear that the rpm mentioned above (http://linux-ntfs.sourceforge.net/info/redhat.html) is read-only support for NTFS. Is there a way to get read and write support? Will recompiling my kernel to have NTFS support give me write support?
If not, what is the limiting factor with the write support? I have seen that this has been the case for many years, what is holding them back?
OK. If you recompile your kernel you can write in a NTFS partition. But in the actual stable kernels, this option is only experimental, so is a little bit risky. Most of times its works perfectly. And of course, you can read without any problems.
So my opinion the best option is to recompile your kernel to support this.
You state that its experimental in "the actual stable kernels" does this mean that we can expect a stable kernel with non-experimental NTFS write support soon? What I am really asking here, is, are there non experimental versions in unstable kernels which are progressing towards becoming stable
As I understand it, the 2nd NTFS driver (which was introduced in 2.5.11) has extremely limited write abilities. Basically you can overwrite existing files, but you can't add new or delete existing files succesfully (for a typical range of files).
The developers are trying but it is a hobby for many of them and Microsoft doesnt release any information which would fascilitate this process.
That is OK. As you know NTFS is Micro$ property and it is closesource, so it is very difficult to know how it works, how is the file management, Micro$ doesnīt provide any information and every new driver version for linux is better, but incomplete at the moment.
The file *.o is the binary file. So it is the result of compiling the source code written in C (files *.c and *.h) and it must be compiled using your libs version. For this reason, it is not a good idea to download the binary (*.o) because it could be compiled with another libs version.
So if you have installed the rpm package, you can find your *.o (ntfs.o) in "/lib/modules/2.4.x/kernel/fs/ntfs.o". If you have ntfs.o in that location, then you will try "modprobe ntfs.o". If you have some error message after that, then you have a wrong rpm package for your system, and you have to download a different version.
As I said before, the best option is to recompile your kernel, and enable ntfs support either as a module (then you compile it with your own libs) or built-in in the kernel (for me the best option).
My ntfs.o was located in the wrong directory. It was not in /lib/modules/2.4.20-20.9bigmem/kernel/fs but in /lib/modules/2.4.20-20.9/kernel/fs.
So that I understand, I presume that installing the RPM put this file there.
Why did it not put it in the correct place?
Originally I attempted, presumable successfully, to update the kernel from 18.104.22.168.8 for the purpose of seeing the ntfs disk.
my lilo.conf contains:
RPM (Red Hat Package Manager) is a special way of packing files.
It contains the binary files, so they have been yet compiled. So it is an easy way of installing packages, because only you have to do is to execute the rpm application (rpm -i name of package) and automatically install the binary files under /bin directory and the modules and libraries under the appropiate ones. It also check the dependencies and tell you if you need to install some other package before that installation. So I recommend you if you use Red Hat to download all the packages you can in rpm format. Check before download them to ensure that you get the right version (Red Hat version).