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!

Notices

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.

I would strongly advise you against performing write operations on your ntfs partition from Linux. ntfs write support is not very reliable yet and you could very easily trash your ntfs file system. It's just a really bad idea.

If you want to share files between the two, create a fat32 partition and use that for shared files.

Masonm's advice is excellent. I would avoid mounting an NTFS partition with write permissions. It's just asking for trouble. I have a partition on my drive that is vfat. On that partition I have a "win_lin" directory, which I use for common data for both operating systems. The directory is accessible from Windows or any of my distros. This is the safest method at this time, according to all my research.

I do not disagree with the advice already given here, but my personal preference is to have my Windows installation on a FAT32 partition and I have never had any problems. But then again, I hardly ever use Windows now. I'm in love with Linux now.

I do not disagree with the advice already given here, but my personal preference is to have my Windows installation on a FAT32 partition and I have never had any problems. But then again, I hardly ever use Windows now. I'm in love with Linux now.

If his Windows is already installed on a ntfs partition, that's hardly an option at this point.

Thanks very much for all your advice. It seems unanimous that I should not write to my NTFS partition in linux; so I wont!

I have deciced to steal a piece of space from one of my NTFS partitions and create a new partition in the FAT32 format, and then mount it using the linux VFAT option.

However, I would still like to know why it won't let me write to the partition. All the permissions are ok, aren't they?

Anyway, I downloaded an NTFS driver from: http://www.linux-ntfs.org/; which I thought would allow me write to my NTFS partition. If this is not the case, then what is the point of the thing I just downloaded and installed?

And is David the H.'s adivce any good? You all seem to disagree with him; but from what he's saying, that is exaclty what I want to be able to do.

How are you mounting the vfat partition? I use /media/<partition name>. I create a directory within the /media directory named for my vfat partition, then chown the directory with my username (which is the same in all distros) and grant rwx permissions for all users/groups. All my distros automount this partition in the same way. No matter which distro I'm in (including Windows), I can rw or x with no problems.

And is David the H.'s adivce any good? You all seem to disagree with him; but from what he's saying, that is exaclty what I want to be able to do.

Ntfs-3g is a new NTFS driver. It's safe and used by many people. Many distro already include it or replaced their old NTFS driver because ntfs-3g works so perfectly. Debian, Gentoo, Ubuntu, Fedora, etc. See the web page: http://www.ntfs-3g.org

Ntfs-3g is a new NTFS driver. It's safe and used by many people. Many distro already include it or replaced their old NTFS driver because ntfs-3g works so perfectly. Debian, Gentoo, Ubuntu, Fedora, etc. See the web page: http://www.ntfs-3g.org

I'm using it for several months and it works great! :-)

Thanks very much for your adivce iqu. I've tried NTFS-3G. I downloaded it and installed it. The first time I tried to install it, it wouldn't work because it said I needed FUSE. So I downloaded and insalled that, then installed NTFS-3G again; this time it worked, I think.

I haven't installed much software, but usually, when noting is printed out onto the screen, it means it has worked successfully. But when I used make and make install for both FUSE and NTFS-3G, there was loads of stuff printed out - a load of if statements, plus some other stuff that I didn't understand. Is this supposed to happen? That might be the reason that it doesn't work.

1) Please don't work directly as the root user, use 'su' to temporarily switch to root and 'exit' when its done.

Yes, I use/used su.

Quote:

Originally Posted by shrikant.odugoudar

2) When you compiled with make and make install, did you get any errors? For eg., it should say 'make : leaving directory so and so...' if all went well. Can you post it?

When installing FUSE:

When I type ./configure for Fuse I get a load of checks; e.g. checking for dlfcn.h... yes

The last thing that gets printed out is this:

configure:
NOTE: Detected that FUSE is already present in the kernel, so
NOTE: building of kernel module is disabled. To force building
NOTE: of kernel module use the '--enable-kernel-module' option.
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'