On Wednesday, 24 April 2002 at 12:06:39 -0400, [EMAIL PROTECTED] wrote: > On Wed, Apr 24, 2002 at 04:14:44PM +0200, Miguel Mendez wrote: >> On Thu, Apr 25, 2002 at 12:05:29AM +1000, Joshua Goodall wrote: >>> On Wed, Apr 24, 2002 at 03:52:18PM +0200, Miguel Mendez wrote: >>> However you present the UI, when it comes to making changes, please >>> have it queue up the actual commands which are then visible to the >>> sysadmin for approval, backout, single-stepping, recording etc. >>> Way too many graphical management tools have been corrupted by the >>> microsoft control panel &c. >> >> Well, if you've used recent versions of the veritas volume manager >> fronted you'll notice that they give the cli command output in a window, >> that's what I intend to do. > > You might want to look at EVMS on Linux. They have a few good ideas, > like building a library and API underneath the user interfaces. From > what I can see, that project has some nice underlying concepts, but the > user interfaces need to evolve for a few years. (Worst CLI ever, and the > GUI is very confusing.)
To be fair to the EVMS people, the tools are still evolving. I'd certainly like to see more documentation, though. > I wonder if that API could interface with vinum? I don't think so. User interface maybe, but Vinum and EVMS have a very different API. > It would be very nice to have a cross-platform library interface to > operate on disk volumes. Yes, we've discussed that in the past. The problem is that EVMS, AIX LVM and Linux LVM have different objects from VERITAS and Vinum. I can't see an easy way of bringing them to a common denominator. It's hard enough explaining the two concepts in the first place. > For that, it might even be worth improving the EVMS API, rather than > starting from scratch. If you want to help work on EVMS, I know people would love the help. Personally I'd prefer to see work on Vinum, of course :-) Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
