Steve Werby wrote: > Feel free to test yourself on a RaQ4 as > it'll only take a minute to create a test list and verify the change will > not be overwritten by the GUI, but yes, the config file does not get > overwritten. Whether the same can be said for other models before and after > patches have been applied - I do not know offhand.
Thanks for the information. I read in the past that changes in the gui did overwrite the config file, and when I spoke to Cobalt about two years ago the rep I spoke to then (sorry, I don't remember who it was) told me that the majordomo install was NOT standard and that I shouldn't depend on it for my lists hosting business, so I didn't. Thanks again for bringing me up-to-date. > Might I ask what you "developed"? Is your installation a majordomo source > installation with a frontend like majorcool (I've done this for myself and > clients since the RaQ2 when the need arose) or have you developed a custom > frontend and backend scripts? Nothing too complex, I'm afraid. Pretty much what you've done for your customers, except that we didn't do anything too majorcool-ish; just my own slightly-changed version of majorhelp.pl. I've wanted for a long time to create a package for it, but never got around to it. I create a directory at /home/majordomo, and set up a complete copy of majordomo there. I create an aliases file at /etc/aliases.majord and install sample list-aliases for instructional purposes, and make sure everything works properly under smrsh. Unless I'm forgetting something, that's about it. Jeff -- Jeff Lasman <[EMAIL PROTECTED]> Linux and Cobalt/Sun/RaQ Consulting nobaloney.net P. O. Box 52672, Riverside, CA 92517 voice: (909) 778-9980 * fax: (702) 548-9484 _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
