GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
There is Knoppix Linux that can automatically mount NTFS as read-only during boot. The thing is, NTFS is such a closed-source filesystem, Open Source developers must guess how the NTFS file system works to write drivers for it. So far they've only figured out how to read NTFS drives safely. There is experimental read-write drivers for NTFS filesystems, but they are usually not included in distros, and must be manually compiled in the kernel. The developers of the open-source NTFS drivers state over and over that read-write support is strictly experimental and it is a 99% guarentee that you will destroy your NTFS partition.
With things like Slackware-Live and knoppix where you can customize the disc, I'd say yeah. Build your own kernel, customize the patches to have the read/write patch, and edit the fstab, save, create iso and burn. It's not downloadable as an iso, but it doesn't keep it from being live
Not really, but if you only need to copy files from Linux to Windows on a dual-boot machine, see "How to write to NTFS" below for a possible way to work around the lack of write support. For write support in Linux, read on.
There are two drivers, currently. The original driver, in 2.4 has some write code in it, but it is extremely dangerous to use it. The possibility of destroying your filesystem is very high.
The new driver, introduced in 2.5.11, has some write code, but it's very limited. The driver can overwrite existing files, but it cannot change the length, add new or delete existing files.
Adding write support will take a long time. NTFS is built like a database. Any changes you make, necessitate making changes in many places, for consistancy. Make a mistake and the filesystem will be damaged, make too many mistakes and the filesystem will be destroyed. Also, the current developers are only working on NTFS as a hobby, during their free time. If you'd like to help, please email me: firstname.lastname@example.org.
How to write to NTFS. If you are using a dual-boot machine and just need NTFS write support to transfer files from Linux to Windows, you can instead use a Windows driver for ext2/ext3 and, while running Windows, read the files from the Linux partition instead. This way, using two read-only drivers, you can still copy files from one file system type to the other.