On Tue, 15 Aug 2006, Horms wrote: > I was having a similar discussion with Andrew. My 2c worth is to rename > IPaddr to IPaddr1, then make IPaddr a new wrapper, that calls IPaddr1 or > IPaddr2 according to what OS/kernel the user has. That way people will > get what we think is best by default. And if they want to do something > special, they can call IPaddr1 or IPaddr2 directly.
Sounds reasonable to me: the important bit is the public interface always being the same thing: "IPaddr" (with the same args and same XML etc. unless there is a really good reason to diverge). One thing to consider: might the switching mechanism (into "IPaddr-XYZ") be feature-based (e.g. presence of "modprobe") rather than OS-based? Just a thought. If you think so, a little cautionary checking. For instance if the script uses the availability of "modprobe", we would first need a correction to "configure.in" which currently incorrectly puts a non-null value into "@MODPROBE@" on machines which lack it. > Actually, thats a slight revision of my idea, but thats where I'm up to > now. Look forward to it! -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. : _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
