xfm_dev(5) [debian man page]

XFM_DEV(5)								XFM								XFM_DEV(5)

NAME

       /etc/X11/xfm/xfm_dev - xfm device configuration

DESCRIPTION

       When  starting  xfm(1)  - the X file and application manager - reads this file to determine mount and umount commands for specific directo-
       ries.

FORMAT

       One entry per line.  Lines starting with a hash (#) and empty lines are ignored.  Each line consists out of three or four fields, separated
       by colons (:).  Backslashes and colons within those fields have to be escaped using backslashes.

FIELDS

   directory
       The  first  field describes which directory this entry is about.  If this this directory or and child directory of this is opened, while no
       other one is open, the mount command is executed. If the last file window showing this directory or a child thereof, the unmount command is
       executed.

       This field can also be the special string GETFSENT, which is described in a special paragraph below.

   mount command
       The second field is the command to execute for mounting.  It is given the shell as one argument after a -c.

   unmount command
       The third field is the command to execute for unmounting.  It is given the shell as one argument after a -c.

   icon
       The  fourth  field  is  optional.   It  is  only  used to specify an icon for the 0 No icon field is equivalent to an icon field containing
       dev_disk.xpm, which differs from an empty icon field.  (See xfm(5)).

automatic configuration via GETFSENT
       If the first field of an entry is the special string GETFSENT, and the systen xfm was compiled on had a fstab.h file, the getfsent(3) func-
       tion is used to get mount point information.

       Every  mount  point  which contains a mount option starting with user.  (like user, or users) for which no specification does yet exists is
       added to the list.

   mount and unmount command
       These commands are expanded with a space and the directory in question and the result is handled a in the normal  case.	 This  needs  some
       fixing with directories containing spaces.

   icon field
       The icon field can in this case be appended by an arbitrary number of rules of the form
       ,fstype=iconname
       If the filesystem has type fstype, the icon iconname is used instead.

EXAMPLES

       /media/cdrom:mount /media/cdrom:umount /media/cdrom:cdrom.xpm
       /floppy:mount /floppy:umount /floppy
       GETFSENT:mount:umount:dev_disk.xpm,iso9660=dev_cdrom.xpm,ext2=bla.xpm

FILES

       $HOME/.xfm/xfm_dev
	      Unless otherwise specified in the X resources, this is the first location xfm looks for this file.

       /etc/X11/xfm/xfm_dev
	      Unless otherwise specified in the X resources, this file is tried when the previous could not be read.

       /etc/fstab
	      This is the file getfsent most likely gets its information from.

SEE ALSO

       xfm(1), mount(8), getfsent(3).

xfm								  20 April, 2006							XFM_DEV(5)

Check Out this Related Man Page

GETFSENT(3)						     Linux Programmer's Manual						       GETFSENT(3)

NAME

       getfsent, getfsspec, getfsfile, setfsent, endfsent - handle fstab entries

SYNOPSIS

       #include <fstab.h>

       void endfsent(void);

       struct fstab *getfsent(void);

       struct fstab *getfsfile(const char *mount_point);

       struct fstab *getfsspec(const char *special_file);

       int setfsent(void);

DESCRIPTION

       These functions read from the file /etc/fstab.  The struct fstab is defined by

       struct fstab {
	    char *fs_spec;	    /* block device name */
	    char *fs_file;	    /* mount point */
	    char *fs_vfstype;	    /* filesystem type */
	    char *fs_mntops;	    /* mount options */
	    const char *fs_type;    /* rw/rq/ro/sw/xx option */
	    int fs_freq;	    /* dump frequency, in days */
	    int fs_passno;	    /* pass number on parallel dump */
       };
       Here  the  field fs_type contains (on a *BSD system) one of the five strings "rw", "rq", "ro", "sw", "xx" (read-write, read-write with quo-
       tas, read-only, swap, ignore).

       The function setfsent() opens the file when required and positions it at the first line.

       The function getfsent() parses the next line from the file.  (After opening it when required.)

       The function endfsent() closes the file when required.

       The function getfsspec() searches the file from the start and returns the first entry found for which the fs_spec field	matches  the  spe-
       cial_file argument.

       The  function  getfsfile()  searches  the  file	from  the  start and returns the first entry found for which the fs_file field matches the
       mount_point argument.

RETURN VALUE

       Upon success, the functions getfsent(), getfsfile(), and getfsspec() return a pointer to a struct fstab, while setfsent() returns 1.   Upon
       failure or end-of-file, these functions return NULL and 0, respectively.

HISTORY

       The getfsent() function appeared in 4.0BSD; the other four functions appeared in 4.3BSD.

CONFORMING TO

       These functions are not in POSIX. Several operating systems have them, e.g., *BSD, SunOS, Digital Unix, AIX (which also has a getfstype()).
       HP-UX has functions of the same names, that however use a struct checklist instead of a struct fstab, and calls these  functions  obsolete,
       superseded by getmntent(3).

NOTES

       These functions are not thread-safe.

       Since  Linux  allows  mounting a block special device in several places, and since several devices can have the same mount point, where the
       last device with a given mount point is the interesting one, while getfsfile() and getfsspec() only return the first occurrence, these  two
       functions are not suitable for use under Linux.

SEE ALSO

       getmntent(3), fstab(5)

Linux 2.5							    2002-02-28							       GETFSENT(3)

Linux and UNIX Man Pages

xfm_dev(5) [debian man page]

Check Out this Related Man Page