Sponsored Content
Full Discussion: mounting vfat...
Special Forums Hardware Filesystems, Disks and Memory mounting vfat... Post 16596 by AtleRamsli on Tuesday 5th of March 2002 06:48:49 AM
Old 03-05-2002
Please remember that vfat is an MSDOS single-user filesystem. The multi-user-related manipulations can only be done in the 'Unix-part' - as soon as you are in MSDOS land, you are in single-user-land, and 'groups', 'users' and such have no existence.
I think that means that the answer to the last part is NO!.
But NO in Linux is not always NO ... check out UMSDOS - "Unix on MSDOS" - it will put some control files in the system to give the appearance of a Unix system.
Document everything you do, because I'm not sure anyone has ever thought about all these issues.


8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Newbie: RH Linux: Mounting vfat as readable

Hi there! I have a question about mounting a file system as readable. I have the following line in my fstab for that purpose: /dev/hda1 /mnt/nt vfat defaults 0 0 It mounts the filesystem but I can only read from this, not write :( what do I have to change to make it readable? TIA! (4 Replies)
Discussion started by: D-Lexy
4 Replies

2. Filesystems, Disks and Memory


Hi everyone, this is the first time I have ever properly used Linux - I run Red Hat Linux 8. I have two hardrives, my main 80gig, and my "extra" 15gig, I would like to be able to gain access to my 15gig and view the files. I know to view files on a floppy disk or a cd you need to mount the... (1 Reply)
Discussion started by: mo0ness
1 Replies

3. UNIX for Dummies Questions & Answers

Mounting help.

Hello, I am trying to mount a second scsi hard drive on a SCO box. (5.0.5.) And I can't figure out what the device file for it is so I can mount it. Can anyone help me? thanks. (1 Reply)
Discussion started by: iconn
1 Replies

4. Solaris

mounting windows(vfat) file system

how can i mount windows file system into solaris using vfstab or mount command. also please tell me how to display the partition information. (1 Reply)
Discussion started by: ajoy patel
1 Replies

5. BSD


Hi I mounted disk which have two partition C: , D: ( i am not sure if both partition have same file system) with this commad: mount -t msdosfs /dev/ad2s1 /mnt/windows but this is mounted only first partition with fat file system. ( in windows XP C: ) How can i mount another partition... (2 Replies)
Discussion started by: sniper007
2 Replies

6. Ubuntu

rdiff-backup using escape codes on vfat thumbdrive

I thought it may be nice to use rdiff-backup to backup my websites to a thumb drive. But all the capital letters are substituted with octal escape codes. How can I over come this? There are no issues backing up to another ext3 drive. The source drive is ext3 the thumb drive is vfat mounted... (0 Replies)
Discussion started by: mikemc
0 Replies

7. Filesystems, Disks and Memory


I generally use mount many times to mount an iso image or as a bind between directories or mounting a squash file system. Y does one require root permission to do a mount --bind between two of his own directories or just mount an iso/squash image in directory he owns? Also I wish mount had an... (0 Replies)
Discussion started by: bbala
0 Replies

8. Shell Programming and Scripting


I have a big confusion in mounting........so please tell me whats the exact meaning of it nd do other os have this concept or not? (8 Replies)
Discussion started by: Mac91
8 Replies
File::Basename(3pm)					 Perl Programmers Reference Guide				       File::Basename(3pm)

File::Basename - Parse file paths into directory, filename and suffix. SYNOPSIS
use File::Basename; ($name,$path,$suffix) = fileparse($fullname,@suffixlist); $name = fileparse($fullname,@suffixlist); $basename = basename($fullname,@suffixlist); $dirname = dirname($fullname); DESCRIPTION
These routines allow you to parse file paths into their directory, filename and suffix. NOTE: "dirname()" and "basename()" emulate the behaviours, and quirks, of the shell and C functions of the same name. See each function's documentation for details. If your concern is just parsing paths it is safer to use File::Spec's "splitpath()" and "splitdir()" methods. It is guaranteed that # Where $path_separator is / for Unix, for Windows, etc... dirname($path) . $path_separator . basename($path); is equivalent to the original path for all systems but VMS. "fileparse" my($filename, $directories, $suffix) = fileparse($path); my($filename, $directories, $suffix) = fileparse($path, @suffixes); my $filename = fileparse($path, @suffixes); The "fileparse()" routine divides a file path into its $directories, $filename and (optionally) the filename $suffix. $directories contains everything up to and including the last directory separator in the $path including the volume (if applicable). The remainder of the $path is the $filename. # On Unix returns ("baz", "/foo/bar/", "") fileparse("/foo/bar/baz"); # On Windows returns ("baz", "C:fooar", "") fileparse("C:fooaraz"); # On Unix returns ("", "/foo/bar/baz/", "") fileparse("/foo/bar/baz/"); If @suffixes are given each element is a pattern (either a string or a "qr//") matched against the end of the $filename. The matching portion is removed and becomes the $suffix. # On Unix returns ("baz", "/foo/bar/", ".txt") fileparse("/foo/bar/baz.txt", qr/.[^.]*/); If type is non-Unix (see "fileparse_set_fstype()") then the pattern matching for suffix removal is performed case-insensitively, since those systems are not case-sensitive when opening existing files. You are guaranteed that "$directories . $filename . $suffix" will denote the same location as the original $path. "basename" my $filename = basename($path); my $filename = basename($path, @suffixes); This function is provided for compatibility with the Unix shell command basename(1). It does NOT always return the file name portion of a path as you might expect. To be safe, if you want the file name portion of a path use "fileparse()". "basename()" returns the last level of a filepath even if the last level is clearly directory. In effect, it is acting like "pop()" for paths. This differs from "fileparse()"'s behaviour. # Both return "bar" basename("/foo/bar"); basename("/foo/bar/"); @suffixes work as in "fileparse()" except all regex metacharacters are quoted. # These two function calls are equivalent. my $filename = basename("/foo/bar/baz.txt", ".txt"); my $filename = fileparse("/foo/bar/baz.txt", qr/Q.txtE/); Also note that in order to be compatible with the shell command, "basename()" does not strip off a suffix if it is identical to the remaining characters in the filename. "dirname" This function is provided for compatibility with the Unix shell command dirname(1) and has inherited some of its quirks. In spite of its name it does NOT always return the directory name as you might expect. To be safe, if you want the directory name of a path use "fileparse()". Only on VMS (where there is no ambiguity between the file and directory portions of a path) and AmigaOS (possibly due to an implementation quirk in this module) does "dirname()" work like "fileparse($path)", returning just the $directories. # On VMS and AmigaOS my $directories = dirname($path); When using Unix or MSDOS syntax this emulates the dirname(1) shell function which is subtly different from how "fileparse()" works. It returns all but the last level of a file path even if the last level is clearly a directory. In effect, it is not returning the directory portion but simply the path one level up acting like "chop()" for file paths. Also unlike "fileparse()", "dirname()" does not include a trailing slash on its returned path. # returns /foo/bar. fileparse() would return /foo/bar/ dirname("/foo/bar/baz"); # also returns /foo/bar despite the fact that baz is clearly a # directory. fileparse() would return /foo/bar/baz/ dirname("/foo/bar/baz/"); # returns '.'. fileparse() would return 'foo/' dirname("foo/"); Under VMS, if there is no directory information in the $path, then the current default device and directory is used. "fileparse_set_fstype" my $type = fileparse_set_fstype(); my $previous_type = fileparse_set_fstype($type); Normally File::Basename will assume a file path type native to your current operating system (ie. /foo/bar style on Unix, fooar on Windows, etc...). With this function you can override that assumption. Valid $types are "MacOS", "VMS", "AmigaOS", "OS2", "RISCOS", "MSWin32", "DOS" (also "MSDOS" for backwards bug compatibility), "Epoc" and "Unix" (all case-insensitive). If an unrecognized $type is given "Unix" will be assumed. If you've selected VMS syntax, and the file specification you pass to one of these routines contains a "/", they assume you are using Unix emulation and apply the Unix syntax rules instead, for that function call only. SEE ALSO
dirname(1), basename(1), File::Spec perl v5.12.1 2010-04-26 File::Basename(3pm)

Featured Tech Videos

All times are GMT -4. The time now is 08:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy