To whom it may concern, Just a quick one: The architecture of ebox seems to make it impossible to prevent custom configurations from being overwritten. Since ebox stores all config data in XML files and then re-creates the real config file from the XML, all customisation disappears. This i discovered when implementing ebox in an LTSP environment. ebox doesn't have "filename" or "next-server" dhcp options, so a manual addition works well. Add another dhcp host and all customisation is lost. ebox will of course only store "known" options in it's XML file, otherwise there is possibility for corruption. In short, one strength of ebox is this "known" options storage in the XML, if that is circumvented, ebox becomes less bullet-proof.
By the way, why was webmin discarded - I tried out the latest release tonight and I thought is was quite comprehensive. Regards, Danson Joseph -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
