help.html

Unix下基于Web的管理工具

			Because DOS has no concept of file ownership or real
			file permissions, all files in the mounted directory
			will have the same owner and access mode. The ownership
			or rights of individual files cannot be changed. <br>
			The following options are available :
			<table border>
			</table><p>
			
		<li><b>Windows 95 Filesystem (vfat)</b><br>
			This filesystem is found on disks formatted by Windows 95
			and possibly NT. Like the MS-DOS filesystem above it has
			no concept of file ownership or permissions. However, it
			can support long filenames. <br>
			Available options are :
			<table border>
			</table><p>

		<li><b>ISO9660 Filesystem (iso9660)</b><br>
			This is the standard format for CD-ROMs. The basic format
			only supports 8.3 filenames like <tt>fat</tt>, but there
			is an extended format called Rock Ridge that allows
			files to have long names and Unix permissions.<br>
			The options for this filesystem are :
			<table border>
			</table><p>

		<li><b>OS/2 Filesystem (hpfs)</b><br>
			Hard disks formatted by OS/2 use this filesystem format.
			Long filenames are supported, but Unix permissions and
			file ownership are not.<br>
			Available options are :
			<table border>
			</table><p>

		<li><b>Linux on MS-DOS Filesystem (umsdos)</b><br>
			This filesystem is used only for installing Linux
			on a system has only an MS-DOS filesystem, and cannot
			be re-partitioned. It works by using the directory
			\linux on the DOS filesystem as the root for the
			Linux filesystem. When mounted under Linux, long
			filenames, file ownership and permissions are supported.
			This filesystem is not supported by default in
			RedHat Linux, and should only be used if you have no
			other option as performance is poor. <br>
			The valid options for <tt>umsdos</tt> are :
			<table border>
			</table><p>

		</ul><p>
	
	<li><b>Solaris 2.5+</b><br>
		For disk-based Solaris filesystems, the mount source can
		be one of :
			<ul>
			<li><b>SCSI Disk</b><br>
				Under Solaris, every SCSI disk is identified
				by 4 numbers:
				<ul>
				<li><b>Controller</b> - The SCSI controller the
				    disk is connected to. Always 0 for the built-in
				    controller on Sparc boxes.<br>
				<li><b>Target</b> - The SCSI unit number. For
				    internal hard drives this is 0 or 1. For
				    external drives it is typically settable by
				    a selector on the drive box.<br>
				<li><b>Unit</b> - Almost always 0.<br>
				<li><b>Partition</b> - The number of the partition
				    to mount.<br>
				</ul><p>
			<li><b>MetaDisk Device</b><br>
				If you have striped, mirrored or RAIDed devices
				created using Sun's Metadevice software, choose
				this option and enter the Metadevice number. <p>
			<li><b>Other Device</b><br>
				This choice requires you to enter the full path
				to the device file to mount. <p>
			</ul><p>
		Before a filesystem on a local SCSI disk can be mounted,
		the partition must be setup and a filesystem built on it.
		The <a href=/format/>Partition Manager</a> module can be
		used to do this, or you can use the <tt>format</tt> and
		<tt>newfs</tt> Unix commands. <p>

		Under Solaris, CDROMs and floppy disks are mounted automatically
		by the volume manager. Unless this has been disabled, floppies
		and CDROMs never need to be manually mounted. Devices mounted
		by the volume manager are not displayed in the list of mounted
		filesystems on the main page. This may also apply to removable
		SCSI devices (such a Jaz or Syquest drives), depending on
		how volume management is set up on your system. <p>

		Once the filesystem mount source has been chosen, you can also
		set a number of filesystem-specific options :
		<ul>
		<li><b>Solaris Unix Filesystem (ufs)</b><br>
			This is the standard filesystem type used by Solaris
			for local disks. <br>
			The available options are :
			<table border>
			<tr> <td><b>Read-only</b></td>
			<td>If yes, then nobody can write, create, delete or 
			chmod anything on this filesystem</td> </tr>
			</table><p>

		<li><b>Network Filesystem (nfs)</b><br>
			NFS is the standard Unix way of sharing files between
			systems. For NFS, the mount source is not a local disk
			but instead a hostname and remote directory. The hostname
			is the name (or IP address) of the system you want to
			mount from. The remote directory is a directory on the
			remote system that is exported to your system. <br>

			NFS filesystems have the following additional options :
			<table border>
			</table><p>

		<li><b>Virtual Memory (swap)</b><br>
			The mount source for virtual memory can be a SCSI disk,
			MetaDisk device or normal file. If you enter a filename
			that does not exist, Webmin will ask you for the size of
			the swap file to create. Once the file is created, it
			will be mounted as swap. <br>
			There are no options for Virtual Memory mounts. <p>

		<li><b>Caching Filesystem (cachefs)</b><br>
			This filesystem uses space on a local disk to cache
			files from another filesystem, typically NFS. This
			means that commonly accessed files from an NFS server
			are kept locally, resulting in a significant speedup.
			When you create a new Caching Filesystem mount, Webmin
			assumes that the back filesystem is of type NFS. <p>

			The mount source for <tt>cachefs</tt> filesystems is the
			NFS server and directory to cache. ??? 
			When you mount a Caching filesystem, two mounts are
			really made - the back mount and the <tt>cachefs</tt>
			mount on the actual directory. Webmin does not show back
			mounts on the list of mounted filesystems. <p> 

			<tt>cachefs</tt> uses a cache directory to store
			cached files, specified in the mount options. You can
			either use the <tt>cfsadmin</tt> Unix command to create
			a cache directory with the parameters you want, or let
			Webmin set it up automatically. In the latter case, the
			cache will be limit to 10% of the size of the filesystem
			it is on. <br>
			Valid options for this filesystem are:
			<table border>
			</table><p>

		<li><b>Ram Disk Filesystem (tmpfs)</b><br>
			Files stored in a filesystem of this type exist only
			in RAM, and are lost when unmounted or the system is
			rebooted. The <tt>/tmp</tt> directory in Solaris uses
			this filesystem type. Because it is stored only in
			memory, there is no mount source section of the
			filesystem form. <br>
			The only option is :
			<table border>
			</table><p>

		<li><b>Automounter Filesystem (autofs)</b><br>
			The Automounter does automatic mounting and unmounting
			of NFS directories on demand. A subdirectory under an
			automounter directory will come into existance and
			mount a file server when the user first refers to it,
			such as by cd'ing into the subdirectory. After some idle
			time, the subdirectory will be unmounted an disappear. <p> 

			The mount source for filesystems of this type has 3
			different options :
				<ul>
				<li><b>All NFS Servers (-net)</b><br>
					When the user cd's into a subdirectory, it is
					taken as the hostname of an NFS server. If
					this server exists, all the available exports
					from the server will be mounted under the
					new subdirectory. <br>
					Solaris by default has the <tt>/net</tt>
					directory mounted with this source, so a user
					can do something like<br>
					<tt>cd /net/bar.foo.com/usr/local/bin</tt><br>
					<tt>ls -l</tt><p>
				<li><b>XFN Server (-xfn)</b><br>
					No idea??? <p>
				<li><b>Automounter map</b><br>
					For this option, the name of an NIS map or
					local file containing an automounter map
					must be given. The configuration of which
					servers and directories to mount is specified
					in this map. For more information, see the
					<tt>automount</tt> man page. <p>
				</ul><p>
			The options for automounter filesystems are the same
			as those for NFS. These options apply to the automatically
			mounted subdirectories inside the automount directory. <p>

		<li><b>MS-DOS Filesystem (pcfs)</b><br>
			Disks formatted under MS-DOS use this filesystem. Files
			in are limited to 8.3 filenames, and have no Unix
			ownership or permissions. Typically, you will never
			need to use Webmin to mount <tt>pcfs</tt> filesystem
			floppy, as they are handled automatically by the volume
			management system. <br>
			The options available for MS-DOS filesystems are :
			<table border>
			</table><p>

		<li><b>CDROM Filesystem (hsfs)</b><br>
			

		</ul><p>
	</ul><p>

<hr>
<h3>Editing an Existing Filesystem</h3>
To edit an existing mount, click on the mount point from the list on 
the main page. This will display the form used for creating a new 
mount with the current mount point, source and options filled in. You can
now change any of these on the form, in the same way as you would create
a new mount (described above). <p>

An existing mount will be either permanently saved, currently mounted or
both. If you change the mount to be not saved or mounted, then it will be
deleted from the mount list. Note that some filesystem types will not
have both these options. <p>

Under Unix a directory cannot be unmounted if it is currently in use,
either by a process having a file in the directory open or by a user having
some subdirectory as his current directory. 
Similarly, a swap file cannot be unmounted if the amount of free memory
is less than the size of the swap file. When you change the directory,
source or options of an existing mount, Webmin will unmount and remount
it to apply the changes. This will fail if the directory or swap file
is in use, and an error displayed. <p>

<hr>
<a href="/"><img alt="<-" align=middle border=0 src=/images/left.gif></a>
&nbsp;&nbsp;<a href="">Return to module</a><p>