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.
You have to enable write support in the kernel I think. But it is listed as DANGEROUS when you run menuconfig for kernel configuration. I guess write support still doesn't work well. I haven't tried it myself. I have a Fat32 partition for sharing files between windows and linux.
Originally posted by Mathieu You are taking a big risk ...
NTFS support is Read-Only.
Do NOT write to NTFS from Linux.
It may corrupt your NTFS filesystem.
In fact, I believe that you actually definitely WILL corrupt the filesystem if you do write to it. I remember reading somewhere that the NTFS write capability always (intentionally) corrupts the filesystem, but it tries to do so in a way that's easy to repair by the NTFS repair utility.
OK, sounds like it would not be a good idea then.
The reason I was wanting to was because everything that I copy from the windows side is "read-only" and I have to do a chmod on the files each time. Is there an automatic way to do this?
I don't know whether this'll stick across the filesystems when copied though. And the 0 in that umask will not enable the write bit even though it'll essentially be creating a chmod of 7 (because of the above mentioned kernel compile requirement).
Yeah, I didn't mean that it would enable write access to the NTFS volume, I meant it would make it so he doesn't have to change permissions when he copies files from the NTFS volume over to his Linux partition(s). I've never really used umask, was I correct about it?
mount -a -o remount
To issue the remount command in 2 commands rather than one.
And I don't know if it'll work either, but according to the umask, that is correct, but copying FROM windoze TO linux is a ball park I'm not all that familiar with.
SLC and WA eh? I'm in WA, and moving back to SLC I was originally from there. What part you from? Me, Glendale originally, moved to West Valley, went to Kennedy Junior High and Hunter High, graduated from Granite. Feel free to email me so we don't clog this guys thread (sorry for the temporary heist ).
It has been established (yet for unknown reasons) that you need a umask=000 for NTFS to work for simple read-only for users. The script idea sounds like the best solution at this point. That or an alias (alias might be better actually).