Re: [Oscar-devel] GUI changes & MAC saving

[Jason B.]

First of all, this is a fairly moot point, since the change has already been made (thank you Sean).

As I said before, I believe the purpose of this was to take a file from
some collection method and be able to import it into the process, not as
a backup utility.

The Import button is for this purpose, the Export button is meant to export a list of MACs that the window is dealing with.

You could save the entire client defs like this:
mksimachine --List > filename

I could, but that's also going to give a lot of unnecessary cruft that I'd have to sort through.

To get just the MACs would require some scripty-fu stuff, but it would
be simple.

Personally, I just create a script that has the required mksimachine
--Update commands to put the MACs in the database eg
mksimachine --Update --name node1 --MAC aaaaaaaaaaaa
mksimachine --Update --name node2 --MAC aaaaaaaaaaab

This works for one cluster with one type of installation... not something we want to deal with

Not an integrated solution, but useful for test/development.

Of course, you could just backup the whole /var/lib/sis directory and
get the whole database, but there's no way to restore it and get all the
right API triggers run.

Backing up /var/lib/sis would be useless, partially for the reasons you state. We're just dealing with MACs for now.

Jason



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel