| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Submitted by: Colin Percival <cperciva@builder.daemonology.net>
(Who should really get his own bit one of these days!)
PR: 59988
|
|
|
|
|
|
|
| |
example.
PR: docs/51897
Submitted by: Kevin Oberman <oberman@es.net>
|
| |
|
| |
|
|
|
|
| |
always false on 64bit platforms and GCC 3.3.1 issues warning there.
|
|
|
|
|
|
| |
number X, rather than mdX, making it easier to script tests that
use md devices but don't want to make assumptions about any existing
md use (such as in diskless environments).
|
|
|
|
| |
Submitted by: Scot W. Hetzel <hetzels@westbend.net>
|
|
|
|
| |
testting of GEOM.
|
|
|
|
|
|
|
| |
combinations of mdconfig(8) command-line arguments.
Make mdconfig(8) accept "-a -f file -o options"
equally with "-a -f file" (assuming "-t vnode".)
|
| |
|
|
|
|
|
|
| |
MDIOCLIST ioctl instead.
Spotted by: keramida
|
|
|
|
| |
Reviewed by: phk
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: phk
|
| |
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
|
|
|
|
| |
Memory disks may be used for other purposes besides newfs(8), so it
isn't helpful to require the minimum size meet newfs(8)'s criteria.
|
|
|
|
| |
small, instead of a less meaningful error in newfs(8).
|
|
|
|
|
|
| |
not to needlessly break compatibility, decrement MDIOVERSION to 0.
Approved by: phk
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bypass some extra anti-foot-shooting measures. Currently, its only
effect is to allow detaching a device while it's still open (e.g.,
mounted). This is useful for testing how the system reacts to a disk
suddenly going away, which can happen with some removeable media.
At this point, the force option is only checked on detach, so it
would've been possible to allow the option to be passed with the
MDIOCDETACH operation. This was not done to allow the possibility of
having the force flag influence other tests in the future, which may
not necessarily deal with detaching the device.
Reviewed by: sobomax
Approved by: phk
|
| |
|
| |
|
| |
|
|
|
|
| |
sizeof(int) == sizeof(long) assumption; clamp down with WARNS=2.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
driver itself obviously won't configure such a disk, but the error
returned (EDOM) is more cryptic to the average user than it should be.
Also assert that the argument to -u is in fact a valid unit; don't
just accept any string to mean 0.
Approved by: phk
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
| |
|
|
|
|
|
|
| |
implies ``-t vnode''.
Approved by: phk
|
|
|
|
|
|
|
| |
entirely as previously advertised.
md(4) adopted all assets of vn(4) some time back and has proper devfs
support and cloning abilities to boot.
|
|
|
|
|
|
|
|
|
| |
2) Running `mdconfig -l` without any attached devices results in
mdconfig printing "md0" to standard output.
Submitted by: dd [1]
[1] no, not "dd(1)" but "Dima Dorfman"
|
|
|
|
|
|
| |
specify -u.
Spotted by: dcs
|
| |
|
|
|
|
|
|
| |
Implement "-l" option to mdconfig which can list one or all md devices.
Submitted by: Dima Dorfman <dima@unixfreak.org>
|
|
|
|
| |
Submitted by: dcs
|
| |
|
|
|
|
|
|
|
| |
Commit the right version, but without the -b option which is too evil
for the present.
Remove -b and preload from the manpage as well.
|
|
|
|
|
|
| |
Remember to set mode 1777 on /tmp
Submitted by: mjacob
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
extension.
Add ability to create a preload disk giving an address and a length
(suggested by imp)
Fix bug relating to very small md(4) devices.
Update md.c copyright to reflect the status of code copied from vn.c.
(noticed by dillon)
|
|
|
|
|
|
| |
Using the mdconfig(8) program you can now configure memory disks
on malloc(9), swap or a file/vnode. preloaded md disks also work
as usual.
|
|
|
|
|
| |
Add a rudimentary man-page. (I'm no mdoc wizard, feel free to attack my
mistakes and blunders)
|
|
I decided to work on the md(4) driver and integrate the vn(4)
functionality into it mainly based on the name being more suitable.
Ideally 'vd' as in "virtual disk" would probably be the most logical
but our sound-master pointed out that this would cause uncontrollable
fits of giggles in the brits. Another complication would the needed
changes to the ramdisk boot/root functionality.
The vn driver will stay around for some time after I complete this
merge for transition reasons, and I'll make it whine to people that
they should migrate to the md(4) driver for some time before it
dies.
The kernel part of the new md(4) driver will be committed after more
testing.
|