Stop Microsoft
Operating Systems => Linux and UNIX => Topic started by: Doogee on 19 October 2002, 14:23
-
If i was to download files, eg music using linux and i saved them to a mounted drive (/dev/hda1 mounted at /c) if i chose to save at, for example /c/My Documents/My Music/ would it be saving into the actual winbloze partition or what? if not, how would i go about doing this?
I'm using Red Hat 7.3
-
Yes, if you save them in the location you mention, when you reboot into Windows you will find them under the C:\Same\Path\You\Mentioned
-
provided of course that the partition is mounted read-write -- it's not NTFS, is it?
-t.
-
experimental NTFS support lets you write and read (http://tongue.gif)
-
nah no ntfs, its FAT32 (but thats really FAT16, innit)
-
it's no problem then; just mount the drive with read-write and it will work; however, most apps and programs (especially in console mode) will require you to either escape the spaces [\ ] or put quotes around the "directories with spaces". GUI browsing for reading and writing should work normally, just point and click.
FAT32 works on the same basic principle that FAT16 does, but there are differences (like the size of the HD supported) that aren't really necessary knowledge. Incedentally, DOS floppies use FAT12, but they all work with the "-t vfat" option to mount.
-t.
-
how do i make read-write access, cos at the moment if i try to save it says access denied.
Idont mount from command line i edited the file for the startup and it mounts it automatically, the post is around somewhere...
-
If you want everyone that uses your system to have read write access use the "umask=000" mount parameter in your fstab:
Or if you mount on the command line it would be:
# mount /dev/hda1 /c -t vfat -o umask=000
-
quote:
Originally posted by TheQuirk:
experimental NTFS support lets you write and read (http://tongue.gif)
More like "erase and read" - read what the kernel info has on it. It's horrible.
-
Hey void i get errors at startup heres my fstab :-
-
[/QB][/QUOTE]
Make that umask=0, not unmask.
-
thanks sorry, misread.... must be the MS brainwashing
-
quote:
Originally posted by Doogee:
Hey void i get errors at startup heres my fstab :-
[/b]
Not only should the "unmask" be "umask" but you also need to delete the word "defaults" since you are no longer using the "defaults" and using the "umask=000".