summaryrefslogtreecommitdiffstats
path: root/sbin/mount
Commit message (Collapse)AuthorAgeFilesLines
* Warn about "mount -u" bug.des1998-10-161-1/+5
|
* Add a CAVEAT section documenting the minimum permissions required for a mountjkoshy1998-07-091-1/+8
| | | | | | point to be traversable in both directions by all users. PR: 7172
* Remove unused #includes. Spelling. Add rcsid. Do not dot terminate err()charnier1998-07-066-49/+36
| | | | strings.
* Print the write counts if they are nonzero even if we're mountedbde1998-06-081-4/+3
| | | | | | readonly, since they tell us about previous write activity. Use the correct format to print the write counts.
* Remove extraneous ")" from output.dt1998-05-171-2/+2
|
* New mount option nosymfollow. If enabled, the kernel lookup()wosch1998-04-083-3/+11
| | | | | function will not follow symbolic links on the mounted file system and return EACCES (Permission denied).
* Don't print the 'writes: sync & async' stuff if we're mounted readonlypeter1998-03-271-3/+6
| | | | or if the fs isn't keeping the stats..
* Fix a type mismatch between a scanf format string and thejdp1998-03-081-3/+3
| | | | corresponding argument.
* Make this compile again.steve1998-03-081-3/+3
| | | | | PR: 5948 Submitted by: Brian Feldman
* If we are mounting the root filesystem, and we're accessing it throughmsmith1998-03-082-3/+38
| | | | | | | | | | | | | | something that might refer to the compatability slice rather than the correct slice entry, try all the possible slice entries first. This is a compatability hack to deal with the case where the kernel has correctly mounted the root filesystem out of its slice, but the user has not updated their /etc/fstab file to reflect this. A diagnostic is emitted if the mount succeeds, indicating that the file should be updated. This is a prelude to fixing the kernel to behave as alluded to above. Reviewed by: (discussed with) julian, phk
* Reviewed by: dyson@freebsd.org (john Dyson), dg@root.com (david greenman)julian1998-03-081-2/+6
| | | | | Submitted by: Kirk McKusick (mcKusick@mckusick.com) Obtained from: WHistle development tree
* Converted putfsent() to Lite2 mount interface - don't use numericbde1998-02-131-2/+2
| | | | filesystem types.
* Removed definition of _NEW_VFSCONF. The new vfsconf interface is nowbde1998-01-201-2/+1
| | | | the default.
* Add mount_devfs(8) to the SEE ALSO section.steve1997-12-011-1/+2
| | | | PR: 5125
* Reviewed by: hackers@freebsd.org in generaljulian1997-11-133-3/+22
| | | | | | | | | | | | | Obtained from: Whistle Communications tree Add an option to the way UFS works dependent on the SUID bit of directories This changes makes things a whole lot simpler on systems running as fileservers for PCs and MACS. to enable the new code you must 1/ enable option SUIDDIR on the kernel. 2/ mount the filesystem with option suiddir. hopefully this makes it difficult enough for people to do this accidentally. see the new chmod(2) man page for detailed info.
* Add noclusterr and noclusterw options. The noclusterr and noclusterwkato1997-09-273-4/+18
| | | | | | disable clustered read and write, respectively. Reviewed by: bde
* Removed duplicate MOPT_FORCE and sorted the first one. Rev.1.5 andbde1997-08-251-3/+2
| | | | Lite2 messed up the ordering differently.
* Moved getmntops() stuff back to mntopt.h so that it is visible in otherbde1997-08-252-8/+5
| | | | mount utilities.
* Backed out previous commit - don't clobber the (normally equivalent)bde1997-08-251-2/+1
| | | | default for NOSHARED.
* Forgot to cvs add this new file.steve1997-08-241-0/+40
|
* Try to avoid mounting filesystems multiple times. Also whilesteve1997-08-247-29/+99
| | | | | | | I'm here do some -Wall cleaning. PR: kern/1839 Reviewed and corrected by: joerg
* Mention the various reasons for messages of the form:joerg1997-08-241-1/+17
| | | | | | xxxxx filesystem is not available Inspired by: PR 3311, and a following discussion with Mikhail
* Always include the section name in the .Xr macro and cleanupsteve1997-08-241-11/+14
| | | | | | | .Nm macro usage. PR: docs/3940 Submitted by: Kazuo Horikawa <k-horik@yk.rim.or.jp>
* Fix parsing of mount options with '=' in their name.msmith1997-04-301-1/+1
| | | | | PR: bin/3027 Submitted by: Louis Mamakos <louie@TransSys.COM>
* Change vfork to fork, too many memory-clobbering actions present in childache1997-04-231-2/+2
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* Finished (?) merging with Lite2: cleaned up #include mess; fixed mergingbde1997-03-121-62/+48
| | | | | | | | | | errors (mis-sorted prototypes, duplicated MNT_NOATIME, duplicated NULL mntopts fixup). Updated getopt() usage. Fixed style bugs in FreeBSD changes (one or two per line for putfsent() stuff).
* Merge from Lite2peter1997-03-117-154/+147
| | | | | | | - use new getvfsbyname() interface and mount(2) interface **DANGER WILL ROBINSON!!** You must be running a -current kernel from within a week or so in order for this to work!
* This commit was generated by cvs2svn to compensate for changes in r23412,bde1997-03-051-0/+92
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Attempt to import Lite2's mount.bde1997-03-058-137/+255
| |
* | Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
| |
* | Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | | | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* | Add mount_msdos(8) referenceache1996-11-101-1/+2
| | | | | | | | 2.2 candidate
* | Added description of "noatime" option.dg1996-09-081-1/+7
| |
* | Implemented user side of "noatime" mount option. This option disablesdg1996-09-032-1/+4
| | | | | | | | | | | | the file access time update on reads and can be useful in reducing filesystem overhead in cases where the access time is not important (like Usenet news spools).
* | [HISTORY] command appeared in Version 1 AT&T UNIXwosch1996-08-291-1/+2
| | | | | | | | Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
* | I have added a new option -p to the mount command. This wasjkh1996-07-212-8/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | inspired by SunOS version of mount which uses option -p to indicate that the mount information should be printed in fstab format. This is a neat way to create a new fstab file to use later when one has modified the mount points or mount options or added or removed mount some mount points. You just type mount -p > /etc/fstab.new and there is your new fstab file ready to be used though you will of course have to add any necessary noauto flags manually. [Committers note: This also seems to do the wrong thing for AMD mounts, but in the more average case this is a nifty feature nonetheless and one can always edit the bogus entries out] Submitted-By: Jukka Ukkonen <jau@jau.csc.fi>
* | Document that suid wrapper like suidperl(1) break option 'nosuid'.wosch1996-07-021-0/+4
| |
* | Change the messages slightly when there is no "mount_type" executableasami1996-03-151-4/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | found when the user specifies "mount -t type". Instead of printing out one message for each path element (/sbin, /usr/sbin), it prints out: mount: exec mount_type not found in /sbin, /usr/sbin: No such file or directory The code is quite long for such a stupid little piece of aesthesism but it is very straghtforward so I guess it's ok. Besides, I don't want to do a "char foo[100];" and have malloc break down when someone decides to add a few more paths to a variable that's far apart from this code. :) By the way, there is no malloc() off-by-one error for the '\0' at the end of the string although I don't explicitly add 1 to the length. The code allocates strlen(path element)+2 bytes for each path element, and doesn't use the last two bytes (for the delimiting ", "). Reviewed by: the list (I hope)
* | Backout my changes to disallow "mount /mnt /mnt" until I can verifympp1996-03-111-22/+0
| | | | | | | | | | that nfs mounts work again (I locked up my home machine testing it and can't see what happened until I get home from work tonight).
* | Only restrict the user from doing something like "mount /mnt /mnt"mpp1996-03-111-4/+7
| | | | | | | | | | for file system types that actually cause a panic (ufs, msdos, cd9660). This makes /proc mountable again.
* | Do not allow the caller to specify the same path for the specialmpp1996-03-101-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | device file and the mount point. This prevents the "unexpected recursive lock" panic from happening. This is a temporary fix. A kernel fix would be much much more ugly than this, and still wouldn't be the "right" way to fix it. After some of Terry's file system rework is installed, it will be possible to properly fix this problem in a clean manner. Until then, this change should prevent use from getting a problem report on this every month or so (and I just noticed that someone in one of the freebsd news groups was complaining about this problem, too).
* | Close PR#17. This may be a contraversal fix in that now mount willjkh1996-03-031-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | spit out two error lines for a bogus filesystem type, e.g: root@time-> mount -t foo /dev/sd0a /mnt mount: exec /sbin/mount_foo for /mnt: No such file or directory mount: exec /usr/sbin/mount_foo for /mnt: No such file or directory But I would submit that if you're even going to scan multiple directories for a mount_foo (which I actually think is somewhat bogus - if it's not in /sbin, you're probably in big trouble anyway), you should emit an error for each one. I got multiple complaints (in addition to the PR) that the existing behavior was very confusing.
* | Another round of various man page cleanups.mpp1996-02-091-1/+0
| |
* | Document the -a option, and mention ``noauto''.dg1995-08-261-0/+5
| |
* | The changes for adding the "noauto" option were mostly wrong. MNT_NOAUTOdg1995-08-263-11/+5
| | | | | | | | | | is a kernel flag, and the kernel definately doesn't need to know about it.
* | Sigh. This isn't my night. I forgot the manpage updates too!jkh1995-08-231-0/+5
| | | | | | | | Thanks, Andrey.
* | Add a "noauto" flag so that you can do things like prevent your systemjkh1995-08-232-3/+8
| | | | | | | | | | | | from not coming up multiuser just because you have a CD mount in fstab but no CD in the drive. Submitted by: "Full Name Not Supplied" <simon@masi.ibp.fr>
* | Remove trailing whitespace.rgrimes1995-05-301-2/+2
| |
* | Fixed incompleteness that would allow dirty filesystems to get mounteddg1995-05-151-2/+5
| | | | | | | | | | | | | | | | | | when the single user shell was terminated. These changes disallow mounting or R/W upgrading filesystems that are dirty unless "-f" (force) option is used with mount. /etc/rc has been modified to abort the startup if one or more non-nfs partitions fail to mount. Reviewed by: Poul-Henning Kamp, Rod Grimes
OpenPOWER on IntegriCloud