LinuxAnswers DiscussionThis forum is to discuss articles posted to LinuxAnswers.
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.
It should be noted that the "umask" option in /etc/fstab deserves special mention because in Linux, permission control works differently for FAT32 and NTFS filesystems than it does for native Linux filesystems (ext2, ext3, reiser, etc.).
- The UNIX permissions of a directory onto which you mount a Windows filesystem can't be changed while the fileystem is mounted (the chang might appear to work, but it won't persist). If you need to change the UNIX permissions of the mount point, unmount the Windows filesystem before doing so.
- Windows doesn't support UNIX-style permissions, so you can only apply permissions to the entire Win filesystem, not to individual files/folders. The default permission mask applied to FAT32 volume at mount time are rwx for root, but only rx for normal users; this is modified with the "umask" option of the mount command.
- The value of the permission bits used with umask are the opposite of those used with the chmod command. For example, the following pairs are equivalent:
the mkfs and mkfs.vfat commands didn't work for me ("no such file or directory," "command not found," etc.). a search showed that seems to be common with those commands. if you're having similar trouble, mkdosfs is probably what you want. i used mkdosfs -F 32 /dev/hdx and that worked fine. see man mkdosfs or mkdosfs -h for the other command line options.
Last edited by synaptical; 11-25-2003 at 11:14 AM.
I ddn't want to mess with partitions and stuff, as I want to preserve my windows stuff. It's already buggy as it is . I bought a secondary 80 GB HD and dual booted my computer. In windows disk management, I created a 20 GB FAT 32 Partition on the new drive, thinking I could use it for file sharing. Windows detects and uses the partition, but Linux doesn't . How can I 'mount' or whatever the drive to linux. Also, if I cant do that, How can I access a usb drive from linux? Oh, and BTW, I can delete the 20 GB partition if neccessary, but I'm not very familiar with the linux command line and most of the things I've tried with it don't work. For instance I can't get the 'tree' command to work?
Remember, this post is not for asking for help, just for commenting the article at the beginning of the post.
Simply read this article, it will answer most of your questions.
If not, here is how you could make the thing work :
Just type fdisk in order to try to guess how your partitions are named from a Linux point of view.
Then add the mount points in /etc/fstab with the correct syntax.
/mnt/win_c is my Windows C: disk
/mnt/win_d is my Windows D: disk
/mnt/win_e is my Windows 200 E: disk.
this was created automatically before the partitions existed before I install Linux, but I was also successful (on another system) adding filesystems created after Linux installation.
Homp this helps.
@Forezt, with my umask=0 parameter I use these filesystems as normal user, not as root.
Since I'm a newbie, the slightest wrong syntax for my version would be wrong. Luckily, i figured some of it out.
So here is what i did:
[root@electrolinux root]# fdisk /dev/hda
The number of cylinders for this disk is set to 1216.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 10.0 GB, 10005037056 bytes
255 heads, 63 sectors/track, 1216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 522 4192933+ b Win95 FAT32
/dev/hda2 523 535 104422+ 83 Linux
Command (m for help): n
p primary partition (1-4)
Partition number (1-4): 3
First cylinder (536-1216, default 536):
Using default value 536
Last cylinder or +size or +sizeM or +sizeK (536-1216, default 1216):
Using default value 1216
Command (m for help): t
Partition number (1-4): 3
Hex code (type L to list codes): c
Changed system type of partition 3 to c (Win95 FAT32 (LBA))
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
[root@electrolinux root]# mkdosfs -F 32 /dev/hda3
mkdosfs 2.8 (28 Feb 2001)
You have new mail in /var/spool/mail/root
Are NTFS partitions still only accessable as read-only from Linux? The problem with Fat32 is there is a 32GB limit, so my 90GB data disk had to be partitioned into 3 for me to share between Windows and Linux.