7 Commits

Author	SHA1	Message	Date
David E. O'Brien	2d68bf45bf	Default to WARNS=2. ... Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike	2001-12-04 02:19:58 +00:00
Dima Dorfman	c894b25a2f	Constify mdmaybeload(), add a prototype for usage(), and get rid of a ... sizeof(int) == sizeof(long) assumption; clamp down with WARNS=2.	2001-06-21 02:10:26 +00:00
Ruslan Ermilov	0a5779d45b	- Backout botched attempt to introduce MANSECT feature. ... - MAN[1-9] -> MAN.	2001-03-26 14:33:27 +00:00
Ruslan Ermilov	fe655281c5	Set the default manual section for sbin/ to 8.	2001-03-20 18:13:31 +00:00
Poul-Henning Kamp	e10469fef8	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.	2001-03-09 20:09:28 +00:00
Poul-Henning Kamp	c2ef0b73df	Improve cmdline parsing and messages. ... Add a rudimentary man-page. (I'm no mdoc wizard, feel free to attack my mistakes and blunders)	2000-12-31 11:20:49 +00:00
Poul-Henning Kamp	70d586c091	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.	2000-12-28 20:57:57 +00:00