RFC: new rc.d/mdconfig{,2} startup scripts

[Florent Thoumie]

Hey fellas,

I'm currently working at extending rc.d/ramdisk{,-own} to support
vnode-backed md(4) devices and I'm wondering if I should :

- add my rc.d/mdconfig{,2} scripts and keep the existing
rc.d/ramdisk{,-own} scripts for backward compatibility (adding a
deprecated note somewhere),
- merge rc.d/ramdisk{,-own} into rc.d/mdconfig{,2} (still adding a note
about ramdisk_* variable deprecation),
- keep the existing names (rc.d/ramdisk{,-own}) and just add my stuff in
them.

I like the first choice better, at some point it will be easier to just
'cvs rm' those files and this prevents adding mess in new scripts.

Also, is there some standard timeout for removing old variables support?

-- 
Florent Thoumie
flz at FreeBSD.org
FreeBSD Committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-rc/attachments/20060509/5a4860a2/attachment.pgp