|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs |
|
| #
2d68bf45 |
| 04-Dec-2001 |
David E. O'Brien <obrien@FreeBSD.org> |
Default to WARNS=2.
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| #
c894b25a |
| 21-Jun-2001 |
Dima Dorfman <dd@FreeBSD.org> |
Constify mdmaybeload(), add a prototype for usage(), and get rid of a
sizeof(int) == sizeof(long) assumption; clamp down with WARNS=2.
|
|
Revision tags: release/4.3.0_cvs, release/4.3.0 |
|
| #
0a5779d4 |
| 26-Mar-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
- Backout botched attempt to introduce MANSECT feature.
- MAN[1-9] -> MAN.
|
| #
fe655281 |
| 20-Mar-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Set the default manual section for sbin/ to 8.
|
| #
e10469fe |
| 09-Mar-2001 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Make md(4) and mdconfig(8) take over the role of vn(4) and vnconfig(8)
entirely as previously advertised.
md(4) adopted all assets of vn(4) some time back and has proper devfs
support and cloning ab
Make md(4) and mdconfig(8) take over the role of vn(4) and vnconfig(8)
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.
show more ...
|
| #
c2ef0b73 |
| 31-Dec-2000 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Improve cmdline parsing and messages.
Add a rudimentary man-page. (I'm no mdoc wizard, feel free to attack my
mistakes and blunders)
|
| #
70d586c0 |
| 28-Dec-2000 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Preliminary scaffolding for the new integrated vn+md device driver.
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.
Preliminary scaffolding for the new integrated vn+md device driver.
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.
show more ...
|