summaryrefslogtreecommitdiffstats
path: root/sbin/mdmfs
Commit message (Collapse)AuthorAgeFilesLines
* Remove trailing whitespace per mdoc lint warningeadler2012-03-291-4/+4
| | | | | | | Disussed with: gavin No objection from: doc Approved by: joel MFC after: 3 days
* Spelling fixes for sbin/uqs2012-01-071-1/+1
|
* Do not try to change the mode or ownership of the root of the mountpointkib2011-09-131-0/+27
| | | | | | | | | when newly established mdmfs mount is readonly. PR: bin/128427 Tested and reviewed by: jchandra MFC after: 1 week Approved by: re (bz)
* dd -t switch for mdmfs to enable TRIM on the configured filesystem.kib2011-09-062-6/+16
| | | | | | | | While there, fix minor style issues. Submitted by: Alex Kozlov <spam rm-rf kiev ua> MFC after: 1 week Approved by: re (bz)
* Switch the default WARNS level for sbin/ to 6.ru2009-10-191-1/+0
| | | | Submitted by: Ulrich Spörlein
* -n is used by newfs to tell "do not generate a .snap directory" instead ofremko2007-05-141-4/+4
| | | | | | | | specifying rotational-positions, reflect that in the command arguments. PR: bin/110178 Submitted by: Alex Kozlov <spam at rm-rf dot kiev dot ua> Approved by: imp (mentor)
* Fix a typo: argv -> argvpyar2007-04-301-1/+2
| | | | | | | | | | | | | | | | | | | | Rationale: We are interested in the current (last) element of the argv array there, not in its first element. The if construct is there because we want to avoid adding empty (zero-length) arguments to argv, so we just don't advance argvp if the current argument is empty, and it gets overwritten at the next iteration. Note that strsep(3) doesn't treat consecutive delim characters as a single separator, it returns empty fields between such characters, and it's up to the caller to handle them this or that way. Also add a comment that the argv array ends up null-terminated in any case (it's due to the design of the for loop) as an answer to a possible question why the whole argv isn't zero-filled. Submitted by: yongari Tested by: yongari MFC after: 3 days
* Don't leave a NULL value in mdsuffix when a particular mdyar2007-03-071-2/+1
| | | | | | | | | unit w/o suffix is specified. It had better be an empty string as it will be passed to a printf-like function that builds the command line to run. PR: kern/109863 MFC after: 1 week
* Grammar nits.ceri2007-02-151-2/+2
|
* Add examples for configuring and mounting geom_uzip(4) based disks'matteo2007-02-151-0/+20
| | | | | image and sliced/partitioned memory disks. MFC after: 1 week
* Correct -c and -d description.matteo2007-02-152-16/+16
| | | | | | | Other requests made in the PR were already solved in the past. PR: bin/66763 MFC after: 1 week
* Enhances mdmfs(8) to mount md-based device such as uzip.matteo2007-02-151-4/+9
| | | | | | | Examples of use can be found in the PR text. PR: 103501 MFC after: 1 week
* Remove the -C option as it does more harm than good. To be fullyru2006-11-032-80/+15
| | | | | | | | | | | | | | | | | | | | compatible, it would have to (at least): - support the "compat-compat" -T option, - *not* support the -l, -O, and -v options, - default to soft updates being disabled. Worse, the compatibility mode makes it impossible to mount_mfs(8) a file system from fstab(5) with soft updates disabled (-S). [1] Now, the only difference when called as "mount_mfs" or "mfs" (as opposed to "mdmfs") is that the file mode of the mount point is set by default to 01777. All options available to mdmfs(8) are also available to mount_mfs(8); the -C option is still recognized but ignored for backward compatibility. PR: bin/98860 [1] MFC after: 2 weeks
* Fix .Dd arguments.ru2006-10-211-1/+1
|
* The UFS filesystem get created only if -P was not specified.matteo2006-10-011-2/+4
| | | | | | Specify this on the description MFC after: 3 days
* Markup fixes.ru2006-09-181-2/+2
|
* Add new -E option, which allows to specify location of the mdconfig(8)sobomax2006-02-162-8/+20
| | | | | | utility instead of using default _PATH_MDCONFIG (/sbin/mdconfig). MFC after: 1 week
* Add a -P option to allow skipping newfs when using a vnode-backeddd2006-01-022-6/+22
| | | | | | | | | | | | | | | | | disk. Apparently some people want to use mdmfs as mount_* as a shortcut for mounting existing file-based file systems. Note that unlike in the patches from the submitters, this option is not available in compat mode. Compat mode was supposed to support only things that mount_mfs used to support. To use this option from fstab, mdmfs should be called mount_md, not mount_mfs. This distinction has not always upkept for new options, and those can't be fixed now without breaking people's systems, but new options should not usually be allowed in compat mode. (Not sure why -F is allowed there at all.) PR: 57641 Submitted by: Ruben de Groot Submitted independently by: Wojciech A. Koszek, for Urzad Miasta Czestochowa
* If we're operating without running external programs (-N) anddd2005-12-221-1/+1
| | | | | | | autonumbering is requested, set the unit to 0 instead of -1. This option is just for output, and "/dev/md-1" looks disconcerting. Submitted by: Wojciech A. Koszek
* Fix parsing of mdmfs(8) option "-w <user>:<group>" in case <user> orrse2005-10-141-10/+6
| | | | | | | | | | | | | | | | | | | | | | | | | <group> is a numeric user/group ID instead of a user/group name (as explicitly intended to be allowed by both the manual page and the implementation). Before this fix, mdmfs(8) aborted: | # mdmfs -s 32m -w 0:0 md /var/tmp/foo | Assertion failed: (mip->mi_have_uid), function extract_ugid, file /usr/src/sbin/mdmfs/mdmfs.c, line 555. | Abort trap (core dumped) The "mi_have_[ug]id" fields were only set in case a name lookup was successful. Instead they also have to be set in case the string to integer conversion was successful. Additionally, as a result of this fix, two assertions at the end of the function are now always true and hence can be just be removed. It is guarrantied that both the UID and the GID are set when the function returns regularily, else it would have been already bailed out with usage()/exit(3) or errx(3) before. Spotted by: Christoph Schug <chris@schug.net> MFC after: 3 days
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-4/+4
|
* Remove unsigned casts.ssouhlal2005-01-311-4/+8
| | | | | Discussed with: delphij, stefanf Approved by: grehan (mentor)
* - Make WARNS?= 6 cleanssouhlal2005-01-252-2/+4
| | | | | | - Add WARNS?= 6 Approved by: stefanf, grehan (mentor)
* Assorted markup, grammar, and spelling fixes.ru2004-05-171-5/+4
|
* Added -l to usage().ru2004-05-171-2/+2
|
* Add a "-l" parameter to mdmfs so that memory file systems can berwatson2004-02-262-1/+7
| | | | | | | | created with the multilabel flag from inception. This simply passes the "-l" flag on to newfs(8). Obtained from: TrustedBSD Project Sponsored by: DARPA, McAfee Research
* Userland signed char fixes for PPC build. Problems were using a chargrehan2004-01-221-1/+2
| | | | | | | | | return for getopt() and comparing to -1, ditto with fgetc() and EOF, and using the kg_nice value from <sys/user.h> Submitted by: Stefan Farfeleder <stefan@fafoe.narf.at> Reviewed by: obrien, bde (a while back) Tested lightly on: ppc, i386, make universe
* Don't reinvent the wheel: Use setmode(3) to interpretyar2003-08-052-3/+15
| | | | | | a file mode specification from the command line. This approach is more flexible and less error-prone than using a mere strtoul(3).
* Do not compare unsigned int values with ULONG_MAX. The comparison iskan2003-07-111-4/+4
| | | | always false on 64bit platforms and GCC 3.3.1 issues warning there.
* Remove pathnames.h.gordon2003-06-291-2/+0
| | | | Pointed out by: Mathieu Arnold <mat@mat.cc>
* Move path definitions to include/paths.h. This makes it easier to overridegordon2003-06-292-14/+5
| | | | | | these definitions in the /rescue case. Submitted by: Tim Kientzle <kientzle@acm.org>
* mdoc(7) fix: Add the forgotten paragraph command.ru2003-05-171-0/+1
| | | | Approved by: re (blanket)
* Add an example of how to create an fstab entry.dougb2003-05-051-0/+4
|
* Use __FBSDID() to quiet GCC 3.3 warnings.obrien2003-05-031-4/+2
|
* Also MLINK the man page for mount_mfs.dougb2003-04-272-2/+4
|
* Install a mount_mfs symlink so that you can specify something like thisdougb2003-04-271-0/+1
| | | | | | | | | | | in /etc/fstab to get a memory disk: md /tmp mfs rw,-s8m,noatime 2 2 Back when mdmfs was created, there was vague discussion about doing this, but it never materialized. Reminded by: Ralf S. Engelschall <rse@engelschall.com>
* english(4) police.schweikh2002-12-271-1/+1
|
* Teach mdmfs how to pass UFS version numbers through to newfs. Becauserwatson2002-12-012-1/+15
| | | | | | | | | | | | of an argument name collision with -O, use -v, and default to whatever the newfs default is for the platform (generally, UFS1). This is required to support diskless workstations that use UFS2 for their mdmfs file systems. Reviewed by: dd, bmah Approved by: re (bmah) Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Don't disklabel(8) the md(4) device, it is not needed, and we don't wantphk2002-09-223-22/+3
| | | | | | to propagete BSD disklabels to architectures not already so polluted. Sponsored by: DARPA & NAI Labs.
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-212-11/+11
|
* The .Nm utilitycharnier2002-07-061-4/+6
|
* Usage style sweep: spell "usage" with a small 'u'.des2002-04-221-2/+2
| | | | | Also change one case of blatant __progname abuse (several more remain) This commit does not touch anything in src/{contrib,crypto,gnu}/.
* Default to WARNS=2.obrien2001-12-041-1/+0
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Enable bug-for-bug compatibility with mount_mfs when the programiedowse2001-09-302-5/+7
| | | | | | | | | | name is "mount_mfs" or "mfs". Previously, the condition was that the program name must start with "mount_", but this both missed the case where mount(8) invokes mdmfs with argv[0] = "mfs", and it included cases such as "mount_md" where compatibility is not required. Reviewed by: dd
* mdoc(7) police: Section cross-references are marked with .Sx.ru2001-08-161-3/+2
| | | | -compat is not a valid keyword.
* Implement a better compatibility mode with mount_mfs. It is thedd2001-08-162-6/+120
| | | | | | | | | | | | | | | | | default if the executable is named (called as) "mount_*", or can be enabled with the -C option. This allows users to leave their old fstab entires unchanged (modulo symlink'ing mdmfs to mount(md|mfs)) and have things behave the way they should (by emulating mount_mfs silliness), while still allowing mdmfs to be used as a generic make-an-md-and-mount-it type thing. Right now, the only effects of this option is to set the mount-point mode to 01777 as if "-p 1777" was given, and to complain about getting command-line options that mount_mfs didn't take (e.g., -X, -L, et al). The latter is mostly to try to catch operator errors. Also implement -U, which turns on soft-updates. It's redundant (since softdep is the default), but implement it anyway for compatibility.
* style(9) tweakobrien2001-08-141-24/+24
| | | | Approved by: dd
* Document -X.dd2001-07-301-0/+3
| | | | Submitted by: kris
* Nuke my e-mail address since it seems out of place here.dd2001-07-302-3/+2
|
* Add __printflike() to those static functions which need it.kris2001-07-011-3/+3
|
OpenPOWER on IntegriCloud