I have a standard (well out of the box) Suse 7.2 install on a dual boot Thinkpad. There are 4 partitions: hda1 NTFS - For Win2k (Obviously) hda2 ext2 - For /boot hda3 Fat32 - For data storage hda4 ext2 - For suse I want to be able to share hda3 between the two os's. All the reading I've seen says that to mount a fat32 using vfat and read only because corruption may occur. Any comments on this. Are those documents on the suse site current or do those relate to older versions? What is the correct way to mount this partition so that both OS's can read/write to it? Thanks, Ron _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
read write will work fine. i did this about 12 months ago for many many months and never had a problem. and i've not heard of a problem ever happening at all. anyone else? On Thursday 18 October 2001 00:15, Ron Joffe wrote:
I have a standard (well out of the box) Suse 7.2 install on a dual boot Thinkpad. There are 4 partitions: hda1 NTFS - For Win2k (Obviously) hda2 ext2 - For /boot hda3 Fat32 - For data storage hda4 ext2 - For suse
I want to be able to share hda3 between the two os's. All the reading I've seen says that to mount a fat32 using vfat and read only because corruption may occur. Any comments on this. Are those documents on the suse site current or do those relate to older versions? What is the correct way to mount this partition so that both OS's can read/write to it?
Thanks,
Ron
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Just to reassure Ron Joffe, the original poster, I would also like to state that I am successfully using FAT32 in rw mode. NTFS is the filesystem with very experimental writing support. FAT32 is suppored very well, IMO. Once, Win95 Scandisk corrupted the first FAT table, and it would not longer boot. Linux however successfully mounted the partition (w/o error...) and I retrieved all the data I needed before "mkdosfs /dev/hda3". On 17 Oct 2001, Tom Wesley wrote:
read write will work fine. i did this about 12 months ago for many many months and never had a problem. and i've not heard of a problem ever happening at all. anyone else? -- noodlez: Karol Pietrzak PGP KeyID: 0x3A1446A0
Ron Joffe wrote:
I have a standard (well out of the box) Suse 7.2 install on a dual boot Thinkpad. There are 4 partitions: hda1 NTFS - For Win2k (Obviously) hda2 ext2 - For /boot hda3 Fat32 - For data storage hda4 ext2 - For suse
I want to be able to share hda3 between the two os's. All the reading I've seen says that to mount a fat32 using vfat and read only because corruption may occur. Any comments on this. Are those documents on the suse site current or do those relate to older versions? What is the correct way to mount this partition so that both OS's can read/write to it?
Thanks,
Ron
_________________________________________________________
I have three Vfat drives mounted so that I can read/write to them from Linux. Have had no problems what so ever with this. To mount the drive in Linux, add a line to your /etc/fstab to mount it during the boot process. /dev/hda3 /windows (or any name you want) vfat, auto,user 0 0 Also make a directory in root for the drive: /windows or the name you used in the fstab entry. 'auto' with mount the drive on bootup of Linux. If you do not want it to auto mount, replace 'auto' with 'noauto'. If using 'noauto', you will what to manually mount it whenever you wish to read/write to the drive. Nevada
--- Ron Joffe
I want to be able to share hda3 between the two os's. All the reading I've seen says that to mount a fat32 using vfat and read only because corruption may occur. Any comments on this.
What you've read is mostly correct. I've personally had no problems with using vfat in r/w mode, but maybe I've just been lucky. :) You just need something like this in your /etc/fstab: /dev/hda3 /windows vfat defaults,rw 0 0 My syntax may not be entirely perfect (just look at what's in yours), but that's most of it. This will automatically mount /windows every time your computer boots Linux or you issue `mount -a', but you will need to have root or disk privaleges to write or modify contents of that disk. For a little more flexibility, you may try: /dev/hda3 /windows vfat noauto,user,rw 0 0 Which will allow any user with mount privaleges to mount the disk, and the partition will not be mounted automatically. If you're not comfortable with data loss, just change `rw' in the options field to `ro' and you'll be fine. ===== -- -=|JP|=- Hit me! - http://www.xanga.com/cowboydren/ Jon Pennington | Debian 2.3 -o) cowboydren @ yahoo . com | Auto Enthusiast /\\ Kansas City, MO, USA | ICQ UIN 69 67 29 31 _\_V __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
On Wednesday 17 October 2001 04:19 pm, you wrote:
--- Ron Joffe
wrote: I want to be able to share hda3 between the two os's. All the reading I've seen says that to mount a fat32 using vfat and read only because corruption may occur. Any comments on this.
What you've read is mostly correct. I've personally had no problems with using vfat in r/w mode, but maybe I've just been lucky. :) You just need something like this in your /etc/fstab:
/dev/hda3 /windows vfat defaults,rw 0 0
My syntax may not be entirely perfect (just look at what's in yours), but that's most of it. This will automatically mount /windows every time your computer boots Linux or you issue `mount -a', but you will need to have root or disk privaleges to write or modify contents of that disk. For a little more flexibility, you may try:
/dev/hda3 /windows vfat noauto,user,rw 0 0
Which will allow any user with mount privaleges to mount the disk, and the partition will not be mounted automatically. If you're not comfortable with data loss, just change `rw' in the options field to `ro' and you'll be fine.
=====
Perhaps you are confusing the risky read only option with NTFS which IS dangerous to write to. PCHintz
participants (6)
-
Jon Pennington
-
Karol Pietrzak
-
Nevada
-
PCHintz
-
Ron Joffe
-
Tom Wesley